For years, plans could use No Surprises Act remark codes voluntarily, and adoption was inconsistent. From January 2027, the codes become a reliable signal that tells posting teams whether a claim is eligible for Federal IDR, belongs in a state process, or is already final. Reading them correctly at posting is the cheapest way to avoid missed open negotiation windows and wrong-venue filings.
The nine required codes
| RARC | What it signals | Federal IDR possible? | Posting action |
|---|---|---|---|
| N877 | Initial payment based on the lesser of the QPA or billed charge | Yes, after open negotiation | Do not write off. Start the 30-business-day open negotiation clock from the remittance receipt date. |
| N876 | Notice of denial of payment; amount based on the QPA or billed charge | Yes, after open negotiation | Do not treat as a routine coverage denial. Route to open negotiation review. |
| N871 | Initial payment based on a specified state law | No | Route to the state process for that state. |
| N944 | Denial of payment where a specified state law or All-Payer Model Agreement applies | No | Route to the state process or verify the All-Payer Model Agreement. |
| N872 | Final payment based on a specified state law | No | Reconcile against the state determination or rate. |
| N873 | Final payment based on an All-Payer Model Agreement | No | Reconcile against the agreement rate. |
| N874 | Final payment agreed through open negotiation | No | Reconcile against the signed settlement. |
| N875 | Final payment reflecting a certified IDR entity determination | No | Audit against the written determination; escalate short pays after 30 calendar days. |
| N943 | Item or service not subject to No Surprises Act surprise billing protections | No | Audit before accepting: confirm the plan did not misclassify protected emergency or ancillary care. |
Verify each code's exact text against CMS's guidance document before configuring rules; this table summarizes the guidance for routing purposes.
Where the codes appear
On electronic remittances, the codes appear at the service line level with the other remark codes for that line, so they must be read line by line, not claim by claim. On paper remittances, they appear on the remittance itself. Configure your system to capture the code for each line and attach it to the claim record your dispute team sees.
Turning codes into rules
- Map each of the nine codes to a work queue: open negotiation, state process, reconcile, or audit.
- Stamp the remittance receipt date on every N877 and N876 line; open negotiation is counted from it.
- Block automatic contractual write-offs on N877 and N876 lines.
- Send N943 lines to a reviewer who checks emergency and ancillary status before accepting.
- Compare N875 payments with the determination amount within 30 calendar days.
Until January 2027
Claims for services furnished in 2026 may still arrive with inconsistent or missing codes. Keep your manual screening in place for those claims: check plan type, state law and QPA disclosures as described in our QPA review checklist. For the deadlines that follow each code, see the IDR deadline guide.
CARCs and RARCs in plain terms
A claim adjustment reason code (CARC) explains why a payment differs from the billed amount. A remittance advice remark code (RARC) adds detail. The No Surprises Act guidance makes specific RARCs mandatory so providers can tell how the payment was determined and which dispute path, if any, is open. Plans keep discretion over which CARC to use for now.
Configuring your systems
- Ask your clearinghouse and practice management vendor to confirm they capture line-level RARCs from electronic remittances.
- Create a lookup table for the nine required codes with a routing rule for each.
- Make the receipt date a required field on any line with N877 or N876.
- Prevent automatic write-off for those lines until a person reviews them.
- Report weekly on lines by code, payer and age.
An exception queue
Some remittances will arrive with no required code, a code that contradicts the payment, or a code that seems wrong for the service, such as N943 on an emergency claim. Send these to an exception queue staffed by someone who knows the No Surprises Act rules, and resolve each within a set number of business days so open negotiation deadlines are not missed.
Measuring payer compliance
| Metric | How to calculate it | Why it matters |
|---|---|---|
| Code coverage | Out-of-network lines with a required RARC ÷ all out-of-network lines for 2027 services | Shows which payers follow the guidance |
| Code accuracy | Lines where the code matches the payment and service ÷ coded lines | Flags misclassification |
| Disclosure completeness | Lines with QPA and required disclosures ÷ coded lines | Supports complaints and negotiation |
Share these metrics with payer relations teams; a documented pattern of missing or wrong codes is useful in contract and complaint discussions.
