277CA Claim Acknowledgment: How to Read and Fix Claim Rejections

Jupiter RCM article cover: 277CA Claim Acknowledgment: How to Read and Fix Claim Rejections

A 277CA is the electronic claim acknowledgment a payer or clearinghouse sends after you submit claims. For each claim it says whether the claim was accepted into the payer’s system or rejected, and if rejected, why. Rejected claims never reach adjudication, so they must be corrected and resubmitted before the filing deadline.

999 vs. 277CA vs. 835

TransactionWhat it tells youWhen it arrives
999Whether the claim file was built correctly (syntax)Minutes to hours after submission
277CAWhether each claim was accepted into the payer’s system or rejectedUsually within a day or two
835 (ERA)How each accepted claim was paid, adjusted or deniedAfter adjudication

How to read the STC segment

Each claim’s status is in an STC segment. Its first element has up to three parts: a claim status category code, a claim status code, and an entity identifier code. For example, STC*A7:562:85 means: rejected for invalid information (A7), Entity’s National Provider Identifier (562), billing provider (85). Clearinghouse reports translate these codes into text, which is why the same rejection can look different from one report to the next.

Claim status category codes

CategoryMeaningWhat to do
A1Received, not yet accepted for adjudicationWait for a further status
A2Accepted into the adjudication systemNothing; watch for the 835
A3Returned as unprocessable, not entered into the systemCorrect and resubmit
A4Claim not foundConfirm it was sent to the right payer
A6Rejected for missing informationAdd what the status code names and resubmit
A7Rejected for invalid informationCorrect what the status code names and resubmit
A8Rejected for relational field in errorFix the fields that conflict with each other

Category wording is summarized from the X12 Claim Status Category Codes list (opens in a new tab).

Common 277CA rejection codes

Status codeX12 descriptionGuide
33Subscriber and subscriber id not foundRead the fix
562Entity’s National Provider Identifier (NPI)Read the fix
116Claim submitted to incorrect payerRead the fix
128Entity’s tax idRead the fix
145Entity’s specialty/taxonomy codeRead the fix
496Submitter not approved for electronic claim submissions on behalf of this entityRead the fix

Codes 128, 145, 496 and 562 require an entity code that names the party with the problem; that is what the “Usage: This code requires use of an Entity Code” note means. See our entity code guide for what each entity code points to.

Rejection vs. denial

A rejection is reported on the 277CA before adjudication: the payer never processed the claim, so you correct it and send it as a new claim. A denial is reported on the 835 after adjudication: the payer processed the claim and decided not to pay, so you correct, appeal or write off. Our claim denial guide covers the 835 side.

A daily rejection workflow

  1. Pull the 999 and 277CA reports every day.
  2. Sort rejections by status code, because one setup error can reject dozens of claims.
  3. Fix the source data, such as the patient record, provider file or payer ID, not only the claim.
  4. Resubmit as a new claim and confirm an A2 acceptance on the next 277CA.
  5. Track rejections by cause each month.

Keep timely filing in mind: in most cases a rejected claim does not count as received, so the deadline keeps running.

Related claim rejection guides

Status code wording is quoted from the X12 Claim Status Codes list (opens in a new tab) at the time of writing. Clearinghouse reports may show the same codes with slightly different text.

Rejections stacking up?

Send us your 277CA reports and we will sort them by cause and fix the setup behind them.

About this article

This article was published by the Jupiter RCM editorial team for general information about medical billing and revenue cycle management. It is not legal, compliance or coding advice for your specific situation. Payer policies and code sets change, so always check the current requirements.

Let’s take a closer look at your revenue cycle

Tell us what’s getting stuck. Denials, old A/R, credentialing, reports nobody reads? We’ll look at how you work now and tell you straight what we’d change, and why.