Claim rejection

A rejection means the claim never got in. Somewhere between your practice management system and the payer’s adjudication engine, an edit failed: the file did not meet the X12 standard, a required field was blank, an identifier was in the wrong format, or the payer’s own front-end rule did not like something. The claim is returned and the payer has no record of it. Rejections arrive on clearinghouse reports and on the acknowledgment transactions X12 defines: the 999 reports whether the file itself passed syntax, and the 277 claim acknowledgment (277CA) reports which claims were accepted or rejected.

The distinction from a denial matters for timely filing. A denied claim was received, so the receipt date is on record. A rejected claim was not, so the filing clock keeps running as if nothing was sent. A batch that rejects and sits unread for a month can push every claim in it past the payer’s limit. Rejection reports have to be worked the day they arrive.

The mistake is watching the payer’s remittance and not the clearinghouse. Claims that reject never appear on an ERA, so a practice that only works denials never sees them; they show up months later as old A/R with no payer response. Read the 999 and 277CA for every batch, confirm the accepted count matches the sent count, and fix and resend rejections inside the original filing window.