Every claim a practice sends out eventually comes back as a remittance: a statement from the payer explaining what was paid, what was reduced, what was denied, and why. Reading that statement well is where a billing team either protects revenue or quietly leaks it. This guide walks through the standard electronic remittance format, the code sets payers use to explain their decisions, and a posting routine that keeps denials from disappearing into the pile.
What remittance advice is
Remittance advice is the payer's itemized response to a claim. For each service line it shows the amount billed, the amount allowed under the contract, any patient responsibility such as copay, deductible, or coinsurance, the amount paid, and adjustment codes explaining every dollar of difference. It arrives either on paper, usually called an explanation of benefits or explanation of payment, or electronically as the HIPAA standard transaction known as the ASC X12 835.
The 835 is one of the transaction standards adopted under HIPAA's Administrative Simplification provisions. Health plans that conduct the transaction electronically must use the standard format, which is why an 835 from a national commercial payer and an 835 from a state Medicaid program share the same structure even when their fee schedules differ.
ERA versus EOB
People use the terms loosely, so it helps to be precise. An explanation of benefits, or EOB, is the document sent to the patient. It explains the claim in consumer language and is not designed for posting. An electronic remittance advice, or ERA, is the 835 file delivered to the provider, typically through a clearinghouse. A paper remittance sent to the provider is sometimes called an EOP or a provider remittance and contains the same information as the ERA but in a printed layout that must be keyed by hand.
The practical difference is time and accuracy. An ERA can be auto-posted into the practice management system, matching each line to the open claim and applying adjustments automatically. A paper remit requires manual posting, which is slower and where transposition errors creep in. Most payers offer ERA enrollment at no cost, and pairing it with electronic funds transfer means the payment and its explanation arrive together and can be reconciled against the bank deposit.
Anatomy of an 835
An 835 is organized in layers. At the top is the payment itself: the total check or EFT amount, the trace number, and the payment date. Beneath that are claim-level records, each identified by the patient control number the practice assigned when the claim went out, the payer's claim number, and the claim status. Within each claim are service lines, one per procedure code, each with the billed, allowed, and paid amounts and any adjustments.
Two things trip up new billers. First, the payment total at the top may not equal the sum of the claims below it, because payers apply provider-level adjustments such as recoupments of prior overpayments, interest, or withholding. These show up in their own segment and must be posted separately. Second, a claim with zero payment is not necessarily a denial. It may have been applied entirely to the patient's deductible, which is an allowed claim with full patient responsibility. The adjustment codes tell you which case you are looking at.
Decoding CARC, RARC, and group codes
Every adjustment on a remittance carries a combination of three elements. The group code says who is responsible for the amount. The claim adjustment reason code, or CARC, gives the reason. An optional remittance advice remark code, or RARC, adds detail.
| Group code | Meaning | What it usually implies |
|---|---|---|
| CO | Contractual obligation | Provider write-off under the contract; do not bill the patient |
| PR | Patient responsibility | Bill the patient (deductible, copay, coinsurance, non-covered by benefit design) |
| OA | Other adjustment | Neither party is liable, often informational or coordination of benefits |
| PI | Payer initiated reduction | Payer reduced payment for a reason not tied to the contract; often appealable |
The CARC list is maintained by a national code committee and is used across all payers, so CARC 1 always means the amount went to the deductible, CARC 45 always means the charge exceeded the fee schedule, and CARC 197 always means precertification or authorization was absent. RARCs refine the story. A RARC beginning with N or M often points to a missing modifier, an invalid place of service, or a documentation request.
The same CARC can be a write-off or an appeal depending on the group code. CO-45 is a routine contractual reduction. PI-45 or an unexpected CO-197 on an authorized service deserves a second look.
Posting payments and catching underpayments
Posting is more than recording cash. Done properly it is the practice's first line of denial management. A good posting routine does three things on every line. It confirms the allowed amount matches the contracted rate for that procedure code, because payers make loading errors and a systematic underpayment is invisible if nobody compares. It routes every non-contractual adjustment into a work queue rather than writing it off. And it moves patient responsibility promptly to a patient statement so the balance does not age.
Auto-posting rules in the practice management system should be configured conservatively. Automatically accept only the group and reason combinations you have decided are true contractual write-offs. Everything else should stop for a human. A rule that auto-adjusts every CO code will silently absorb timely-filing denials and bundling edits that were worth appealing.
A remittance workflow for a small office
- Enroll in ERA and EFT with every payer that offers them, and route all files through one clearinghouse inbox.
- Post daily. Remittances that sit for a week create a backlog that hides trends.
- Reconcile each 835 to the bank deposit by trace number before closing the day.
- Work the exception queue in order of appeal deadline, not dollar amount. A ninety-day appeal window closes regardless of the balance.
- Track the top five CARCs by count each month. Repeated codes point to a fixable upstream problem: eligibility not verified, a modifier missing from a template, or an authorization step skipped.
- Send patient statements within a few days of posting so patient balances are collected while the visit is still fresh.
Remittance advice is dense, but it is also completely standardized. Once a team learns the structure and the handful of codes that dominate its payer mix, the file stops being a chore and becomes the most reliable source of intelligence the office has about where its revenue is going.
Common questions
Is a payer required to send an electronic remittance advice?
Health plans that conduct the remittance transaction electronically must use the HIPAA-adopted 835 standard, and CMS operating rules require them to offer ERA and EFT enrollment. A plan may still send paper if the provider has not enrolled, so the first step is to enroll with each payer or through your clearinghouse.
What is the difference between a CARC and a RARC?
A claim adjustment reason code explains why an amount was not paid, such as deductible, bundling, or lack of authorization. A remittance advice remark code adds supplemental detail, such as which data element was missing or what documentation is requested. A CARC is always present on an adjustment; a RARC is optional.
Can we bill the patient for a CO adjustment?
No. Group code CO means the provider is contractually obligated to accept the reduction. Billing the patient for a contractual write-off generally violates the participation agreement. Patient responsibility amounts are identified with group code PR.
How long should we keep remittance advice files?
Remittances are financial and, because they contain patient identifiers and services, are also records subject to HIPAA retention requirements for documentation. Many practices keep them at least six years to align with the HIPAA documentation retention period and payer audit look-back windows; check state law and your payer contracts for longer requirements.