The difference is whether a decision exists
A rejection happens before adjudication. The clearinghouse or the payer’s front end refused the file, usually on a format or identifier problem, so the claim was never processed. There is no decision, so there is nothing to appeal. You correct and resend.
A denial happens after adjudication. The payer processed the claim and decided not to pay it, and that decision arrives on a remittance advice with an adjustment reason code attached.2 A denial can be appealed, and it has an appeal deadline.
Everything downstream follows from that one distinction: who fixes it, what they change, which clock is running, and whether an appeal is even possible.
How to tell which one you are holding
Three tells, in order of reliability:
- Where it came from. A rejection arrives from the clearinghouse or a front-end acknowledgement. A denial arrives on the remittance advice, ASC X12N 835.1
- Whether there is a reason code. Denials carry a Claim Adjustment Reason Code describing why a line was paid differently than billed, often with a remark code adding detail.23 Rejections carry an error message, not an adjustment.
- Whether the payer has the claim at all. A claim status request, ASC X12N 276/277, settles it.1 If the payer has no record, it was a rejection whatever anyone called it.
The vocabulary is not consistent across systems, which is why the third tell is worth more than the first two. Software will happily label a rejection a denial.
What changes next
| Rejection | Denial | |
|---|---|---|
| When it happened | Before adjudication | After adjudication |
| Does the payer have it | No | Yes |
| Can it be appealed | No, there is no decision | Yes |
| What you do | Correct and submit | Correct and resubmit, or appeal |
| Clock that matters | Timely filing | Appeal deadline, then timely filing |
| Where you see it | Clearinghouse or front-end response | Remittance advice |
The row that costs the most money is the last-but-one. Filing an appeal on a rejection does nothing, and the time it takes is deducted from the filing window that was the only real constraint.
Why the distinction is worth enforcing internally
A practice that records both as “denied” cannot answer a basic question: are we failing to get claims accepted, or failing to get accepted claims paid? Those have different causes and different fixes.
Rejections usually point upstream, at registration, identifiers, or a payer’s submission rules. Denials usually point at documentation, coverage, authorization or coding. Collapsing the two hides which half of your revenue cycle is actually leaking.
The VixisTrace™ page covers the eight-stage process CareVixis uses on both, and the duplicate-claim guide works through the most common rejection of all.
CareVixis is not affiliated with, endorsed by, sponsored by or certified by TherapyNotes. No API integration, native integration, certification or partnership with TherapyNotes is claimed. TherapyNotes is a trademark of its respective owner and is referred to here only to describe how a practice using it works. Uploading a remittance file is a supported data import, not a native integration.
Related reading
- VixisTrace™ claim root cause analysis
- TherapyNotes says a claim is a duplicate
- ERA, EOB and claim status
- Denial management for mental health practices
Sources
- CMS, Adopted Standards and Operating Rules, Administrative Simplification. The federally adopted standards include ASC X12N 837 for health care claims, ASC X12N 835 for health care payment and remittance advice, ASC X12N 276/277 for claim status request and response, and ASC X12N 270/271 for eligibility and benefits. Accessed 26 September 2026. Source
- X12, Claim Adjustment Reason Codes. CARCs describe why a claim or service line was paid differently than billed. The Claim Adjustment Group Codes are CO (Contractual Obligation), CR (Corrections and Reversal, not used with 005010 and up), OA (Other Adjustment), PI (Payer Initiated Reductions) and PR (Patient Responsibility). Maintained by the X12-03 External Code List Oversight subcommittee. Accessed 26 September 2026. Source
- X12, Remittance Advice Remark Codes. RARCs "are used to provide additional explanation for an adjustment already described by a Claim Adjustment Reason Code (CARC) or to convey information about remittance processing." Informational RARCs are prefaced "Alert:" and are never tied to a specific adjustment. Accessed 26 September 2026. Source
Find Out Which Half Is Leaking
VixisTrace™ separates rejections from denials in your own data and groups each by cause. The analysis is free and read-only.
Analyze My Claims Free