CLAIM WORKFLOWBilling reference

Rejections and denials are not the same problem.

Confusing the two is one of the most common causes of claim abandonment and timely filing losses — each type requires a completely different response, from a different document, with a different deadline clock.

The core difference

The fundamental distinction is whether the claim ever reached the payer's adjudication system. A rejection stops the claim before that happens. A denial means the payer received the claim, processed it, and decided not to pay.

Clearinghouse rejection

  • Claim never reached the payer
  • Error caught at clearinghouse or payer front-end
  • Document: 277CAwith “rejected” status
  • Fix: correct the error, resubmit
  • Timely filing clock: may still be open (depends on payer)

Payer denial

  • Claim reached payer and was adjudicated
  • Payment refused for clinical, administrative, or coverage reason
  • Document: 835 ERA or paper EOB
  • Fix: review CARC/RARC, correct or appeal
  • Timely filing clock: satisfied — the claim was filed

Reading the 277CA

The 277 Claim Acknowledgment is the payer's (or clearinghouse's) response to the 837 claim transmission. The status code in the transaction tells you what happened. A status of “20” (Accepted) means the claim entered the payer's system. A status of “27” (Denied) on a 277CA typically indicates a front-end rejection — not the same as a denial on a 277 Claim Status response or an 835 remittance. Loop 2200 in the 277CA transaction contains the rejection reason details.

The distinction between a 277CA rejection and a 277 Claim Status denial matters: the 277CA is about transmission acknowledgment, and the 277 Claim Status is about adjudication status. Not all clearinghouse portals make this obvious in their UI.

If you're looking at a 277CA and not an 835 or EOB, the payer has not yet adjudicated the claim. There is no denial to appeal — there is a submission error to fix. Treating a rejection as a denial and opening an appeal wastes time and doesn't restart the timely filing clock.

Common rejection reasons and fixes

Most front-end rejections fall into a small set of categories. The fix is always the same structure: identify the specific field causing the rejection from the clearinghouse edit report, correct it, and resubmit promptly.

RejectionFix
NPI not foundVerify enrollment; confirm taxonomy code matches payer's record
Duplicate claimVerify the original claim's status first; void and resubmit with corrected claim indicator if needed
Eligibility failureVerify coverage with the payer; check for retroactive eligibility; submit COB documentation if secondary
Claim format errorReview clearinghouse edit report; correct the field (often rendering provider NPI in loop 2310B)
Rendering provider not enrolledCheck credentialing status; submit with group NPI if individual enrollment is pending and payer allows it

Working a denial queue (835 / EOB)

Once the 835 Electronic Remittance Advice arrives, use the CARC and RARC codes to understand why the claim was denied. The group code tells you the adjustment category:

  • COContractual Obligation— the provider agreed not to bill the patient for this adjustment. The amount is the provider's write-off.
  • PRPatient Responsibility — the patient owes this amount (deductible, copay, coinsurance). Bill the patient accordingly.
  • OAOther Adjustment— catch-all for adjustments that don't fit CO or PR. The RARC typically provides the specific context.

The RARC (Remittance Advice Remark Code) attached to the CARC is often where the actionable information lives — specifying what documentation the payer needs, what clinical policy applied, or how the payment was calculated. See the CARC and RARC reference guide for a breakdown by code.

Timely filing and rejections

A clearinghouse rejection generally does not satisfy the payer's timely filing requirement. The clock starts when the payer receives a clean, accepted claim — confirmed by a 277CA with “accepted” status. If a claim was rejected and resubmitted, the timely filing window is measured from the resubmission date, not the original submission date.

Most payers will consider the original 277CA — the one showing the rejected submission with its timestamp — as partial evidence when appealing a timely filing denial on the corrected claim. Whether they credit it depends on the payer's policy and sometimes on how quickly the resubmission happened after the rejection. Call the payer and ask before assuming your original submission date will be honored.

Common questions

We got a 277CA saying “accepted” but the claim hasn't paid in 45 days. What's happening?
An accepted 277CA confirms the claim entered the payer's system — it doesn't guarantee timely processing or payment. Pull a 276/277 Claim Status inquiry (through your clearinghouse or directly through the payer portal) to see the claim's current adjudication status. Common holds at this stage include pending clinical review, a coordination of benefits hold waiting for primary payer information, or a provider credentialing verification queue. Each has a different resolution path.
Our clearinghouse sends a rejection report but doesn't label it 277CA — how do I know which rejections are clearinghouse-level vs payer-level?
Ask your clearinghouse vendor directly — this is a reasonable support question and most vendors have documentation on it. Most portals distinguish between clearinghouse edits (caught before the claim was transmitted to the payer) and payer front-end edits (the payer received the 837 and rejected it before adjudication). The distinction matters for timely filing because clearinghouse-level rejections mean the payer never saw the claim, while payer front-end rejections mean the transmission happened but the claim failed the payer's intake validation.