Remittance Advice in Medical Billing: ERA, EOB, and Remark Codes

Remittance advice is the payer's explanation of your payment. It says which claims were paid, which were adjusted or denied, and why.

Every time a payer processes a batch of your claims, it sends one of these back. In electronic form it is called an ERA (electronic remittance advice). On paper it is usually called an EOB (explanation of benefits), though strictly speaking the EOB goes to the patient and the remittance goes to you. Either way, it is the document that turns a deposit into information you can act on: what landed, what got cut, and what the next step is for every line that did not pay in full.

What a remittance advice actually contains

Open one and you will see the same skeleton every time:

• The payment header. The total amount paid, the payment date, and the payer and payee names. On an ERA this rides with a trace number that ties the file to the bank deposit.
• Claim-level detail. Each claim in the batch, the amount billed, the amount paid, and any adjustments, each with a group code and reason code explaining the difference.
• Service-line detail. On electronic versions, the same breakdown per procedure line: what each line paid, what was adjusted, and which remark codes add context.
• Provider-level adjustments. Anything not tied to a single claim: interest the payer owes you, takebacks, recoupments. These explain why a deposit is smaller than the claim payments add up to.

That last section matters more than it looks. When a deposit does not match the sum of the claim payments, the difference is often sitting in the provider-level adjustments. Practices that post only to the deposit total never find out.

The two forms: ERA and paper

Remittance advice comes in two forms, and which one you get changes how your week goes.

The ERA is the ASC X12 835 transaction: a standard electronic file the payer sends (or sends through your clearinghouse) that your billing software can read and post automatically. HIPAA adopted the 835 as the standard for the health care claim payment and advice transaction, which is why every payer speaks the same file format even when their rules differ.

The paper remittance (often called a standard paper remittance, or SPR) carries the same kind of information on paper or as a PDF. It cannot post automatically. Someone reads it and keys the payments in by hand, which is slower and leaves more room for a denied line to slip through unnoticed.

Most practices aim to get everything electronic. A payer will not send an ERA until you enroll for it, and each payer has its own process: usually the payer portal or your clearinghouse, sometimes a separate enrollment for each tax ID. If one payer still sends paper while the rest are electronic, that is two workflows to keep straight, and it is worth the enrollment effort to get everyone onto the same stream.

One thing the form does not change: neither an ERA nor a paper remittance decides the claim. Both report the decision. The denial arrived on the remittance; the work of fixing it still sits with your team. Remittances matter for payment posting and denial follow-up, not for preventing denials. Prevention happens before the claim goes out.

Remittance advice vs EOB

People use the terms interchangeably, and in a practice that is usually harmless. But they are two different documents with two different audiences.

When a patient calls confused about a bill, they are looking at the EOB. When your billing team is posting payments or working a denial, they are looking at the remittance. Same claim, two views.

How to read a remittance: the three-code chain

Every adjustment on a remittance carries codes. Read them in this order, because that is the order they answer your questions: who owns the amount, why, and what exactly.

1. The group code: who owns the balance. A two-letter code in front of every adjustment. The common ones:

• CO (contractual obligation). A contract rule or regulation caused the adjustment. Generally a provider write-off, not billed to the patient. Check it against your actual contract before writing it off.
• PR (patient responsibility). Deductibles, copays, coinsurance. This amount can be billed to the patient or sent to a secondary payer.
• OA (other adjustment). Used when no other group code fits. Read the reason code carefully before deciding who owns it.
• PI (payer-initiated reduction). A reduction the payer made that is neither a contractual obligation nor the patient's responsibility.

2. The CARC: why the amount was adjusted. CARC stands for claim adjustment reason code. It is a numeric code (sometimes with a letter, like B4) that gives the reason: deductible, duplicate claim, missing authorization, filing deadline missed. Every adjustment on a remittance carries exactly one, so a line with three problems shows up as three adjustments.

3. The RARC: the detail. RARC stands for remittance advice remark code. An alphanumeric code (starting with M, MA, or N, like N130 or MA130) that adds supplemental explanation to the CARC: which field is missing, which policy applied, what to do next. Some CARCs are too vague to act on alone, like CARC 16 (the claim lacks information needed for adjudication), and those require at least one RARC naming the specific problem.

Group code first, then reason, then remark. Three steps, and the fix usually names itself.

CARC vs RARC: what each one does

The two code systems get confused because they arrive together. They do different jobs.

A few examples of how they pair up. CO-45 says the charge exceeded the fee schedule. CO-97 says the service was bundled into another paid procedure. CO-18 means the payer saw the claim as a duplicate. PR-1 tells you the patient's deductible was not met. On the remark side, N130 says to consult the plan's benefit documents for restrictions on the service. M15 says separately billed services were bundled as components of the same procedure, so separate payment is not allowed. N29 says requested information was not received, and MA130 says the claim was unprocessable because of incomplete or invalid information: submit a new claim, because there are no appeal rights on an unprocessable claim. The informational RARCs marked "Alert" are worth reading even when nothing was adjusted: they flag things like balance-billing rules under the No Surprises Act, which change who you can bill.

The practical rule from all of this: when you see an adjustment, read the CARC for the category and the RARC for the specific fix. Two lines with the same CARC can need completely different fixes, and the RARC is what separates them.

Where the code lists come from, and why it matters

HIPAA requires payers to use approved codes instead of making up their own, which is what makes the system work across payers. A national committee maintains the CARC list, CMS maintains the RARC list, and the official lists live with Washington Publishing Company. Both lists are updated about three times a year: codes get added, revised, and retired.

That update cycle is the warning. A code cheat sheet taped to someone's monitor goes stale. When the lists change, an old sheet either misreads a new code or misses a retirement, and the practice writes off a balance it could have collected or appeals a denial it could have corrected. Before acting on an unfamiliar code, look it up in the current published list, and check the payer's own guidance too, because payers layer their own edits on top of the standard codes.

Decode one line, start to finish

Take one denied line and read it the way the chain above says to. It looks like this on the remittance: CO-16, with a remark code of N290.

Group code CO says the payer treats this as a contractual or regulatory adjustment, which points the first question at the practice rather than the patient. CARC 16 says the claim lacked information needed for adjudication, which is so general it could mean almost anything. Then the RARC earns its place: N290 says the rendering provider's identifier was missing, incomplete, or invalid. Now the fix is concrete. Someone adds the rendering provider's NPI to the claim and resubmits. Three codes, one clear next step.

Another one: CO-96 with N130. CO again, so the starting question points at the practice. CARC 96 says non-covered charges. N130 says to consult the plan's benefit documents for restrictions on this service, which means the plan excludes the service. The group code tells you what to do with that finding: under CO, the provider absorbs it, either as a write-off or an appeal. Had the same line arrived as PR-96, it would belong on the patient's side, billable to them under the plan.

Once you have read a few lines this way, a pattern emerges. Leave out the routine lines, the deductibles and contract adjustments that post clean, and rank the rest by dollars. Group by root cause instead of by code: CO-16 with N290 and a cluster of CO-185 codes might both trace back to provider enrollment going stale. Fix the top few causes at their source, registration, authorization, coding, documentation, and re-run the same report each month. That is what turns remittance reading from a daily chore into a trend line that goes the right direction.

What the practice does with the remittance

Here is the routine that puts the remittance to work.

Match the deposit to the remittance first. The ERA and the electronic funds transfer travel separately. They pair up on a trace number. Resolve any difference before posting anything, because a gap between the deposit and the file means something is missing: a file, a claim, or a provider-level adjustment.

Auto-post the clean lines. Payments that match the contracted rate with expected adjustments post without a human touch. That is the whole point of electronic remittances.

Give every exception an owner. Denials, zero-pays, unfamiliar codes, payments below the contracted rate. Each one lands in a work queue with a name next to it. A remittance only helps if every line that does not post cleanly gets worked by a person.

Move patient balances out. PR amounts go to secondary coverage or onto the patient statement. Sitting in limbo, they age into write-offs.

Track the codes by payer. Count the same reason code per payer each month. A CARC that spikes for one payer is a front-end problem, registration, authorization, or coding, not a posting problem. Fix the pattern at its source. Denial management is this loop run continuously, and our breakdown of claim denials, their causes, and fixes covers what the most common reason codes point to.

Mistakes practices make with remittances

A few patterns come up often enough to name:

• Posting to the deposit total. Skipping the line detail hides denials and patient-responsibility amounts. The deposit is one number; the remittance is the story.
• Letting paper and electronic mix. Two streams for one payer means double posting or gaps. Enroll the stragglers for ERA and keep one stream.
• Treating CO as always safe. A contractual adjustment is a write-off only if the amount matches your contract. Compare before you post.
• Ignoring provider-level adjustments. Takebacks and recoupments sit outside the claim lines. Read them the day the remittance arrives, or they become surprise changes to your accounts receivable.
• Trusting a stale cheat sheet. Code lists update several times a year. The payer's current list and its own guidance outrank anything printed before the last update.

Read it as a work order and it pays for itself. The practices that get their money in are the ones that read it.