Chapter 28 — Payment Posting: Remittance Advice, EOBs, Allowed Amounts, and Reading What You Actually Got Paid

📍 Where you are

Chapter 27 got the claim to the payer and stopped. The 999 accepted, the 277CA accepted, and then nothing happened for fourteen days.

This is the day something happens.

The remittance advice is the most information-dense document in the revenue cycle and the least carefully read. It says what the payer allowed, what it paid, what it took away and why, who owes the rest, and — if you know how to look — whether it paid you correctly, which is a different question from whether it paid you.

Six earlier chapters have promised you §28.8. This is where that debt comes due.

Overview

Posting a payment sounds like data entry. It is the point at which every earlier chapter's work becomes a number, and it is where four different kinds of loss become visible to somebody who is looking and invisible to everybody else.

Consider what a single remittance line decides.

Whether you were paid. The obvious one, and the only one most people check.

Whether you were paid correctly. Chapter 23 priced the service; the remittance says what the payer actually allowed. When those differ, nothing about the transaction announces it.

Who owes the remainder. A group code decides whether an amount is written off or billed to a patient. The same dollar, under two different group codes, is either your loss or the patient's bill — and posting it wrong is either a lost balance or a bill you had no right to send.

And what happens next. A denial that posts as a contractual adjustment has been silently accepted. Nobody appeals a write-off, because a write-off looks like a decision somebody made.

This chapter's argument in one line: posting is not recording what happened. Posting is deciding what happened, and a practice that treats it as clerical work has handed that decision to whoever configured the software.

28.1 The 835 and the paper remittance

The document has three names and you will hear all of them.

Remittance advice — the general term. Electronic remittance advice (ERA) — the electronic one. Standard paper remittance (SPR) — the printed one. The 835 is the transaction that carries the ERA, Chapter 27 §27.2.

They contain the same information. The electronic one is machine-readable and can be posted automatically; the paper one has to be keyed or scanned. That is the whole practical difference, and it is a large one.

What a remittance contains

   THE CHECK / EFT LEVEL
     payer, payee, payment amount, payment method,
     check or EFT trace number, production date
        │
        ├── ONE CLAIM
        │     patient, PATIENT CONTROL NUMBER (Ch. 26 §26.2),
        │     payer's claim number, claim status,
        │     total charge, total paid, patient responsibility
        │        │
        │        ├── ONE SERVICE LINE
        │        │     procedure code and modifiers,
        │        │     CHARGE, PAID, units,
        │        │     ADJUSTMENTS — each with a GROUP CODE,
        │        │       a CARC, and an amount
        │        │     REMARK CODES (RARCs)
        │        │
        │        └── (more lines)
        │
        ├── (more claims)
        │
        └── PROVIDER-LEVEL ADJUSTMENTS
              things done to YOU, not to a claim — §28.9

Four structural facts worth fixing now.

The remittance is organized by check, not by claim. One payment covers many claims, and reconciling the deposit to the remittance is a real task — the total of the claim payments plus the provider-level adjustments must equal the payment amount. When it does not, something has been missed.

Every adjustment has three parts: a group code (who bears it), a CARC (why), and an amount. §28.3 and §28.4.

The line's arithmetic always balances. Charge = paid + the sum of the adjustments. Every line. If your posting does not balance, you have missed an adjustment, and the missing one is frequently the interesting one.

And the patient control number comes back. Chapter 26 §26.2 said FL 3a exists so the payment can be posted; this is where that happens, and it is why §28.7's autoposting works at all.

🎓 Exam Watch

Two distinctions exams test relentlessly.

The 835 versus the 837. The 837 is the claim going out. The 835 is the remittance coming back. Odd pairs are questions and answers, but these two are not a pair — they are the two ends of a transaction, and a surprising number of people confuse them under time pressure.

And the remittance versus the EOB. The remittance advice goes to the PROVIDER. The explanation of benefits goes to the PATIENT. §28.2, and they say different things on purpose.

One more, easy to miss: the 835 is the transaction; ERA is the document it carries; SPR is the paper version. A question asking "which transaction carries the remittance" wants 835.

28.2 The EOB and why the patient's copy says something else

The patient receives a document about the same claim, and it does not match yours. This produces a phone call in every practice in the country, every week.

An explanation of benefits (EOB) is the payer's statement to the MEMBER about how their benefits were applied. It is not a bill. It usually says so, in a place nobody reads.

Why the two documents differ, in four parts:

They have different purposes. Your remittance explains a payment. The EOB explains a benefit — what the plan covered, what the member's cost sharing is, how much of the deductible was consumed, how much annual maximum remains. None of that appears on your remittance because none of it is yours.

The EOB shows the CHARGE prominently. Chapter 23 established that a charge is not a price. The patient does not know that, and the largest number on the page is the one they submitted nothing to receive.

"You may owe" is an estimate. Most EOBs say some version of what you may owe your provider, and they are frequently right and occasionally not — because a plan does not know what the practice collected at check-in, what a secondary payer will do, or whether the practice will bill at all.

And the EOB arrives on its own schedule, which may be before your remittance, after it, or on a day that makes a patient call about a bill you have not sent.

What an EOB typically shows, and it is worth knowing so you can read one over the phone: the date of service and provider · the amount billed · the plan's allowed amount, sometimes labeled "eligible expense" · what the plan paid · the member's deductible, coinsurance, and copay applied · a running deductible and out-of-pocket accumulator · a reason or remark for anything not paid · and a "what you may owe" figure. The accumulators are the fields you do not have and cannot see, and they are frequently the reason a patient's bill is larger than they expected — a deductible that had not been met on the date of service.

📞 On the Phone

"My insurance says I owe \$17.58 but you sent me a bill for \$47.58."

(Or the reverse, which is worse.)

This is Account 10-4471, and §28.11 shows exactly where both numbers come from. The patient's total responsibility for the encounter is \$47.58**. They paid **\$30.00 at check-in. The balance is \$17.58** — and if your statement's largest number is \$47.58 with no visible credit, the patient is right to be confused and you have made a document that invites this call.**

Four things to say, in order:

"Let's look at the same claim." Confirm the date of service and the total responsibility. Do not start with your system's balance — start with the number the patient is holding.

"You paid \$30.00 on March 14. Here is where that shows on your account." This is the whole call, nine times in ten, and it takes fifteen seconds if the credit is visible and five minutes if it is not.

"Your plan's document is an explanation of benefits, not a bill." Say it plainly and without condescension. Most people have never been told.

"The remaining \$17.58 is coinsurance on the injection, the drug, and the lab draw." Naming the services matters — Chapter 32 §32.10 is about explaining a bill, and the difference between a defensible bill and a hostile one is frequently that somebody said what it was for.

What does not work: "That's what the insurance sent us." It is true, it explains nothing, and it tells the patient you have not looked.

28.3 Group codes: CO, PR, OA, PI

Four two-letter codes, and they decide who bears each dollar.

The group code decides WHO OWES. The CARC decides WHY.

They are different questions and the group code is the consequential one, because it is the field that moves money between your accounts receivable and a person.

Three things that follow.

A CO adjustment is the contractual adjustment. Chapter 23's spread between your charge and the allowed amount arrives here. You agreed to it, and billing the patient for it is a contract violation and frequently worse.

A PR adjustment creates a patient balance, and the CARC tells you which kind — PR-1 deductible · PR-2 coinsurance · PR-3 copay are the three you will see constantly.

And the same denial can arrive under different group codes at different payers, which is the part that catches people. A service denied as not medically necessary may arrive as CO — you cannot bill the patient, because you did not obtain an advance beneficiary notice — or as PR, where the payer has determined the patient is liable. Chapter 22 §22.7's ABN is precisely the instrument that decides which, and the modifiers (GA, GX, GY, GZ) are how you told the payer in advance.

⚠️ Where Claims Die

Posting a PR amount as CO, or a CO amount as PR. Both directions are damaging and they are damaging differently.

PR posted as CO — you have written off a balance the patient owed. Nobody will ever bill it, and nobody will ever notice, because a contractual adjustment is exactly what a contractual adjustment is supposed to look like. This is silent revenue loss with no error message, and it is one of the few losses in this book that is invisible from every angle including an audit of the claim.

CO posted as PR — you have billed a patient for money your contract says they do not owe. This one is visible, because the patient will call, and it is worse than the first: it is a contract violation, it may violate state balance-billing protections, and at scale it is a compliance matter, not a billing error. Chapter 32 §32.4.

The mechanism is almost always the same: a posting rule mapping a CARC to a destination without checking the group code. Chapter 27's Case Study 2 is the same failure in a different system — a configuration making an assertion nobody chose.

The check is trivial and almost nobody runs it: pull a month of adjustments by group code and reason code, and look for any CARC appearing under more than one group code. Where one does, one of the two is probably being posted from a rule rather than from the remittance.

28.4 CARCs and RARCs, and how to read them together

Two code sets, maintained nationally, and they do different jobs.

A CARC — claim adjustment reason code — states WHY an amount was adjusted. It always accompanies a group code and an amount.

A RARC — remittance advice remark code — provides ADDITIONAL EXPLANATION. It carries no amount. It is the sentence that makes the CARC actionable.

The CARCs you will meet constantly:

And the RARCs that do the most work:

CO-16 alone is unactionable. CO-16 with its RARC is a work item.

"Lacks information needed for adjudication" tells you nothing. The RARC names the missing element, and a remittance report that shows CARCs and suppresses RARCs — many do, by default — converts every CO-16 into a phone call.

Check your report's configuration once. It is a settings problem masquerading as a payer problem.

Reading them together

Take Account 10-4471's line 1.

   LINE 1   99214-25   charge 185.00   PAID 0.00

   CO   97    128.40   the benefit for this service is included
                       in the payment for another service that
                       has already been adjudicated
   RARC N19            procedure code incidental to the
                       primary procedure

Now read what the payer actually said, which is more specific than "it denied":

The group code is CO. The payer is asserting you may not bill the patient for this.

The CARC is 97. The payer is asserting this service was already paid for inside another service's payment — a bundling assertion, which is Chapter 21's entire subject.

The RARC is N19. The payer is naming which relationship it believes exists: this code is incidental to the primary procedure. In this case, the primary procedure is the injection, 20610.

And the amount is \$128.40, which is the full allowed amount of the office visit.

Read together, the payer has said: "the office visit was part of the injection."

That is a claim about clinical reality, and it is wrong — Chapter 15 §15.5 documented three chronic conditions separately assessed, and Chapter 14 §14.4's modifier 25 is on the line asserting exactly that. The payer's edit fired anyway.

This is the difference between reading a denial and reading a remittance. "Line 1 denied" leads to resubmission or a write-off. "The payer asserts the E/M was incidental to the injection, and the note documents three unrelated problems" leads to an appeal that wins — Chapter 30, and it did.

🔢 Code It

Four adjustments. Say what the payer asserted and what you do about it.

text 1. CO 16 145.00 RARC M76 — missing/incomplete diagnosis 2. PR 204 88.00 not covered under the patient's current benefit plan 3. CO 29 212.00 the time limit for filing has expired 4. CO 151 94.00 the information submitted does not support this many services

1 — The claim is missing a diagnosis or has an invalid one. The RARC is doing all the work here — CO-16 by itself would tell you nothing. Correct and resubmit as a corrected claim (Chapter 25's item 22 / Chapter 26's frequency 7). Not an appeal: nothing was decided about the service, only about the claim's completeness.

2 — The service is not a benefit of this plan. PR means the payer holds the patient liable — and Chapter 22 §22.7 decides whether you may actually collect it. For Medicare, a GA on the line says a valid ABN exists and you may bill; GZ says one does not and you may not. This is the moment those modifiers pay off, or fail to.

3 — Filing expired. Chapter 27 §27.7. Before writing this off, ask whether the claim was REJECTED earlier and resubmitted late — because if it was, the write-off is preventable and belongs in §28.6's administrative category with a name attached, not in the contractual bucket.

4 — A units or frequency assertion. Chapter 20 §20.3's dose arithmetic and Chapter 21's medically unlikely edits both land here. Check the units against the documentation before you do anything else, because the two possible findings — you billed the wrong units, or you billed the right units and the payer's limit is wrong — go in opposite directions.

The lesson: four adjustments, four completely different next actions, and only one of them is an appeal. A practice that routes all denials to one queue and works them the same way is doing three of these four wrong.

28.5 Posting a payment line by line

Posting is the act of recording, against each service line, what the payer allowed, paid, adjusted, and assigned to the patient.

   FOR EVERY LINE:

   CHARGE  −  CONTRACTUAL ADJUSTMENT (CO)
           −  OTHER ADJUSTMENTS (OA / PI)
           −  PATIENT RESPONSIBILITY (PR)
           =  PAYMENT

   and equivalently:

   CHARGE  −  ALLOWED  =  the contractual adjustment
   ALLOWED −  PATIENT RESPONSIBILITY  =  the payment

Three rules that prevent most posting errors.

Post at the LINE, not at the claim. A claim-level posting hides which service was reduced, and every question anyone will later ask — Chapter 29's root cause, §28.8's underpayment detection, Chapter 36's quality reporting — is a line-level question. A four-line claim posted as one number has thrown away the information that made the remittance worth reading.

Post what the remittance says, not what you expected. This sounds obvious and is violated constantly by systems that compute an expected contractual adjustment and post the difference. The remittance is the fact. Your expectation is the thing you are testing against it — §28.8.

And post the zero lines. A line that paid nothing still has adjustments, a group code, a CARC, and a RARC. A posting process that skips zero-payment lines has skipped precisely the lines that need attention, and it is astonishing how many do.

The copay that was already collected

Chapter 25 §25.10 put \$30.00 in item 29 — the amount the patient paid at check-in.

Here is what happens to it. The payer adjudicates the claim, applies the benefit, and reports a PR adjustment for the copay. It does not know or care that you already have the money.

So the remittance creates a patient responsibility your account has already satisfied. The posting must apply the existing payment against it, not create a second balance.

This is the single most common source of "you billed me for something I already paid." It is not a billing philosophy problem. It is a posting sequence problem, and §28.11 shows it happening.

Two related habits worth adopting:

Reconcile the deposit before you post, not after. The check or EFT amount, the sum of the claim payments, and the provider-level adjustments must agree. A mismatch found before posting is a question; found after, it is an investigation.

And keep the remittance. Not the posting screen — the remittance itself, retrievable by claim. Chapter 27's Case Study 2 turned on a practice being able to produce an old transaction, and the same argument applies here. Every payment dispute in your future is a document-retrieval problem.

🔍 Check Your Understanding

A line shows: charge \$150.00 · allowed \$78.60 · CO-45 \$71.40 · PR-2 \$15.72 · paid \$62.88.

1. Does the line balance? Show it.
2. What is the contractual adjustment, and who bears it?
3. What may you bill the patient?
4. The payer's fee schedule says this service allows \$85.00. What is your finding, and what is the dollar amount at issue?
5. A second line on the same claim shows charge \$18.00 · paid \$0.00 · CO-97 \$6.28 and your posting process skips it because the payment is zero. What have you lost?

Answers:

1 — Yes. \$150.00 − \$71.40 − \$15.72 = \$62.88 ✓. Charge minus all adjustments equals payment, on every line, always.

2 — \$71.40, borne by the practice under the contract. Chapter 23's spread between charge and allowed. CO means the patient may not be billed for it.

3 — \$15.72, the PR-2 coinsurance. That amount and nothing else.

4 — An underpayment of \$6.40 on the allowed amount** (\$85.00 − \$78.60). §28.8. Note what did not happen: nothing denied, nothing was flagged, and the line balanced perfectly.** A line can be internally consistent and wrong.

5 — The CARC, the group code, and the fact that the payer bundled a drug into something. You have lost the only record of a decision that cost you \$6.28 and that will recur on every claim with this pairing. The dollar amount is trivial. The pattern is not.

📋 Read the Chart

Source: a remittance handed to you because "the payment looks short" What it says:

text PAYER [commercial plan] EFT 1,284.16 ───────────────────────────────────────────────────────── CLAIM A pt control no. [the patient's chart number] LINE 1 CHG 240.00 PAID 118.00 CO 45 92.00 PR 2 30.00 LINE 2 CHG 95.00 PAID 0.00 CO 97 62.00 ───────────────────────────────────────────────────────── CLAIM B [processed as primary] LINE 1 CHG 310.00 PAID 172.40 CO 45 115.60 OA 23 22.00 ───────────────────────────────────────────────────────── PROVIDER-LEVEL ADJUSTMENT WO −418.20 [ref: claim 88-3312]

What it means: at least five things need attention, and only one of them is the short payment.

The EFT is short because of the provider-level adjustment. \$418.20 was offset against a prior overpayment on claim 88-3312. The payment is not short; money was taken back, and §28.9 says post the claims in full and the offset separately. Netting it down would corrupt every claim on this page.

Claim A line 1 does not balance. 240.00 − 92.00 − 30.00 = 118.00 ✓. It does balance — check it rather than assuming, because this is the habit that finds the ones that do not.

Claim A line 2 is a CO-97 with no RARC shown. §28.4: the remark code may exist and be suppressed by your report configuration. Before treating this as unexplained, look at the raw 835.

Claim B carries OA-23, which reports the impact of prior payer adjudication. That means a primary paid before this one — and this claim says "processed as primary." One of those two statements is wrong, and §28.10's whole section is about what happens next if nobody asks.

And the patient control number is the chart number. Chapter 26 §26.2. This claim will not autopost, and if the same value appears on every one of that patient's claims, none of them will.

What to do about it: four of the five are non-clinical and none requires opening a chart. A reviewer who checks whether the payment matches the fee schedule will answer the question that was asked and miss the offset, the OA-23, and the control number.

Where it appears: every remittance anyone hands you with a vague complaint. The complaint names the symptom; the page contains the findings.

28.6 Contractual adjustment versus write-off: two different decisions

Two things that look identical in a general ledger and are opposite in meaning.

A CONTRACTUAL ADJUSTMENT is the difference between your charge and the contracted allowed amount. It was never collectible. You agreed to it when you signed the contract. It is not a loss; it is the gap between a number you set and a price somebody negotiated.

A WRITE-OFF is a decision to stop pursuing money you were entitled to collect. Timely filing expired. The balance is too small to chase. The appeal was not worth the effort. It was collectible and you are choosing not to collect it.

Why the distinction matters, in three parts.

They measure different things. Chapter 23 §23.9's gross and net collection rates depend on this separation. Contractual adjustments belong in the denominator adjustment; write-offs are performance. A practice that posts everything as "adjustment" has made its own collection rate uninterpretable.

They have different owners. Nobody decides a contractual adjustment — the contract does. Every write-off is somebody's decision, and a decision that nobody is named for is a decision nobody reviews.

And a denial posted as a contractual adjustment disappears.

This is the most expensive single posting error in this chapter.

A CO-97 for \$128.40 posted as "contractual adjustment" produces an account that looks paid in full. The claim balances. The patient owes nothing. Nothing appears on an aging report, in a denial log, or in a work queue.

The money is gone and the account looks correct. Chapter 29's denial management cannot work a denial it never sees, and the denial rate does not count it, for the same structural reason Chapter 27 §27.7's rejections did not count.

A workable write-off taxonomy — and every practice needs one:

   CONTRACTUAL           the contract's spread. Not a loss.
   ─────────────────────────────────────────────────────────
   ADMINISTRATIVE        timely filing · no authorization ·
   (PREVENTABLE)         credentialing · registration error
                         ► every one of these is somebody's
                           process failure and BELONGS IN A
                           REPORT (Ch. 29 §29.7)
   ─────────────────────────────────────────────────────────
   SMALL BALANCE         below the threshold. Ch. 31 §31.7.
   ─────────────────────────────────────────────────────────
   CHARITY / FINANCIAL   Ch. 32 §32.8. A DIFFERENT THING
   ASSISTANCE            ENTIRELY and must never be mixed
                         with bad debt.
   ─────────────────────────────────────────────────────────
   BAD DEBT              pursued and not collected.

The middle category is the one that pays for itself. Preventable administrative write-offs are the practice's own failures, priced. Chapter 29 §29.7 builds the report; this is where the data has to be created, and it can only be created if the person posting has a reason code to choose.

28.7 Autoposting, and what it gets wrong

Automatic posting takes an 835 and applies it without human intervention. It is a genuine advance and you should want it.

What it does well:

Volume, accurately. A machine posting a thousand lines makes no arithmetic errors and no transposition errors. A human posting a thousand lines makes both.

Speed. Payments post the day they arrive rather than when someone gets to them, which matters for Chapter 31's days in accounts receivable and for knowing what you have.

And consistency. Every CO-45 is posted the same way, which is the precondition for §28.8's detection and Chapter 29's classification to mean anything.

The prerequisite nobody mentions

Autoposting requires ERA enrollment, which — Chapter 27 §27.5 — is a separate enrollment from EDI, and is done per payer.

A practice that cannot autopost usually does not have a technology problem. It has an enrollment gap. Somebody enrolled to send claims and never enrolled to receive the remittance, and paper remittances have been arriving ever since while the software's autoposting module sits unused.

Check this before buying anything.

The four things it gets wrong

Autoposting is a rule engine, and a rule engine does exactly what it was configured to do — including in situations nobody configured it for.

One: it posts denials as adjustments. §28.6. This is the big one. A rule mapping "any CO adjustment" to the contractual adjustment bucket will bury every CO-97, CO-50, and CO-151 alongside the legitimate CO-45s. The claim balances; the denial vanishes.

Two: it applies a group code from a rule rather than from the remittance. §28.3's damage, at scale and consistently, which is worse than intermittently.

Three: it cannot see an underpayment. A machine posting what the remittance says is doing its job correctly. §28.8's question — should this have been more? — is not a posting question and no autoposter answers it unless somebody built the expected-allowed comparison separately.

Four: it handles the exceptions worst. Takebacks, offsets, reversals, interest, capitation payments, and any provider-level adjustment (§28.9) are exactly the items a rule engine either mishandles or routes to a queue nobody watches.

⚠️ Where Claims Die

The failure pattern is specific and it has a name in every practice that has been through it: the exception queue.

Autoposting posts what it recognizes and routes the rest to a queue for a human. That is correct design. The queue is where the interesting items go, by construction — the offsets, the unmatched payments, the reversals, the denials the rules could not classify.

And it is unowned in a large fraction of practices, for the same reason Chapter 27's Case Study 1 report was unread: it is not anybody's job, it does not generate an alert, and every day it does not get worked, the practice's payments still post.

Two questions, and if you cannot answer both, you have found something:

"Who works the autoposting exception queue, and how many items are in it right now?"

"What is the oldest item in it?" The answer to the second is diagnostic. In a healthy practice it is measured in days.

28.8 Underpayments and how to find them

Six chapters have promised this section, and the promise was always the same shape: "how do you know you were paid correctly?" — Chapters 14, 18, 19, 20, 21, and 23 each ran into it and deferred.

Here is the answer, and it starts with why the question is hard.

**An underpayment does not deny. It does not reject. It does not appear on any exception report.

It arrives as a payment.**

And Chapter 23 §23.10 stated the sharpest version of the problem:

A silent underpayment RAISES your net collection rate.

That deserves unpacking, because it is genuinely counterintuitive. The net collection rate is payments divided by what you should have collected — and "should have collected" is normally computed as the allowed amount the payer reported. If the payer reports a lower allowed amount than your contract requires, the denominator shrinks with the numerator, and the ratio improves. The measurement designed to tell you how well you collect is blind to being paid the wrong amount, and mildly flattered by it.

The method

Detection requires one thing that most practices do not have: an expected allowed amount, per line, per payer, computed independently of the remittance.

   FOR EVERY POSTED LINE:

   1.  EXPECTED ALLOWED
         from the contract — Ch. 23:
         a percentage of a fee schedule, a flat rate,
         a case rate, or a per-diem
                    ▼
   2.  ACTUAL ALLOWED
         from the remittance
                    ▼
   3.  VARIANCE  =  expected − actual
                    ▼
   4.  THRESHOLD
         report variances above a dollar OR percentage
         floor — you cannot work every \$0.02
                    ▼
   5.  CLASSIFY
         is it the CONTRACT, the CLAIM, or the PAYER?

Step 1 is the whole difficulty, and it is why this is not universal. It requires your contracts in a computable form — the multiplier, the base schedule, the year of that schedule, the carve-outs, the lesser-of provisions. Chapter 23 §23.6 built exactly that for Northfield Mutual, line by line, and found something worth remembering:

133.03% · 124.21% · 115.44% · 100.00% — blended 128.55%, and NOT ONE LINE is at 128.55%.

A practice checking payments against a blended percentage would find every line wrong and no line wrong. The expected amount has to be built the way the contract is written, per line.

Step 5 — and this is where the money is

A variance has three possible explanations and they lead three different places.

The CONTRACT is loaded wrong. Your expected amount is wrong and the payment is right. This is the most common finding on a first pass, it is unglamorous, and finding it is still valuable — because until the contract is right you cannot detect anything else.

The CLAIM was wrong. A missing modifier, wrong units, a wrong place of service. Chapter 23's Case Study 1 — the place of service that was never updated — is an underpayment that looks exactly like a payer error and is not. Chapter 25 §25.8.

Or the PAYER is wrong. The contract says one thing and the payment is another. This is the finding that produces recovery, and it is the least common of the three by count and frequently the largest by dollars, because a payer's error is systematic — it is a configuration, and it has been applying to every claim of that type since it was made.

🧮 Run the Numbers

Why a small per-line variance is not a small problem. (Constructed and illustrative.)

```text A LINE UNDERPAID BY ...................... $6.40 THE CODE IS BILLED, PER MONTH ........... 40 times ──────── PER MONTH ............................... $256.00 PER YEAR ................................ $3,072.00

AND IT HAS BEEN WRONG SINCE THE CONTRACT LOADED, WHICH WAS ....................... 26 months ago ───────── AT ISSUE ................................ $6,656.00 ```

Check: 6.40 × 40 = 256.00 ✓ · 256.00 × 12 = 3,072.00 ✓ · 256.00 × 26 = 6,656.00 ✓

Three things to read off this.

The per-line number is beneath anyone's attention and the total is not. \$6.40 does not survive a conversation about priorities. \$6,656.00 does, and they are the same finding.

The duration is the multiplier that matters. A payer configuration error does not happen once — it applies from the moment it was made, and the recoverable period is bounded by the contract's reconsideration window rather than by when you noticed.

And this is one code. A practice billing three hundred distinct codes across eight payers has two thousand four hundred contract-and-code combinations, each of which is right or wrong independently. You cannot check them by reading remittances, which is the argument for building step 1.

Where to start if you are starting from nothing: your top twenty codes by volume, at your top three payers by revenue. Sixty combinations. It is a week of work and it is the highest-yield week available to most practices, because volume concentration means those sixty combinations are the large majority of the money.

28.9 Takebacks and offsets inside a remit

A remittance does not only pay you. It can also take money back, and the mechanism catches people because the money does not come out of the claim it belongs to.

A takeback (or recoupment) is a payer recovering a prior overpayment. An offset is the mechanism: rather than asking for a check, the payer reduces a future payment by the amount owed.

   A REMITTANCE THAT LOOKS WRONG UNTIL YOU READ IT

     claim payments on this remittance ......  4,812.00
     PROVIDER-LEVEL ADJUSTMENT (offset) .....   −612.40
                                               ─────────
     ACTUAL PAYMENT / EFT ...................  4,199.60

The provider-level adjustment section is where these live — things done to YOU rather than to a claim. It carries a reason and, where applicable, a reference to the original claim.

What belongs there: recoupments and offsets · interest paid on late claims · capitation payments · penalties · advance payments and their recovery · and various balance-forward mechanics.

⚠️ Where Claims Die

The error is posting the NET as if it were the payment, and it produces a specific and durable mess.

What happens: the poster reconciles to the deposit — \$4,199.60 — and forces the claim payments to match by shorting them. Now every claim on that remittance is posted for slightly less than the payer actually paid, and:

Dozens of accounts carry small false balances, which will be billed to patients or chased as underpayments.

The original overpaid claim never gets corrected, so your records still show a payment the payer has since taken back.

And §28.8's detection now reports variances on every line of that remittance, which is noise generated by your own posting.

The correct handling: post every claim at its full remitted amount, then post the offset as a separate provider-level transaction referencing the original claim, then reconcile. The deposit and the postings agree, and every claim is right.

And read the offset's reference. It names the claim being recovered. That claim is a finding — either a legitimate correction you should understand or an improper recoupment you can dispute. Chapter 31 §31.9 covers the sixty-day rule and the obligations that attach to a known overpayment.

Reversals and corrections

A second mechanism sits alongside offsets and is easier to misread, because both halves of it are on the same page.

A payer that reprocesses a claim frequently reports it twice on one remittance: a REVERSAL of the original adjudication, and then the CORRECTED adjudication. The reversal carries the original amounts with the signs inverted; the correction carries the new ones.

Two things to do with it.

Post both. A poster who sees a familiar claim and posts only the correction has left the original payment on the account and doubled it. A poster who sees a negative and stops has left the claim unpaid. The pair is one event and both halves belong on the account.

And read what changed. The corrected adjudication is a payer's own restatement of what it should have done — which means a reprocessing you did not request is telling you something. A wave of unrequested reprocessings for the same code is a payer fixing a systematic error, and it is worth asking whether every affected claim was reprocessed or only the ones somebody complained about.

Two practical notes.

An offset is not an appeal decision. A payer recovering an overpayment has made a determination, and determinations can be disputed — Chapter 30. Posting an offset without reading it is accepting it.

And interest arrives here too. Payers owe interest on claims paid late under various rules. It is small, it is real, and a practice that never sees a line of interest income should ask why — not because interest matters, but because the absence of something the rules produce is information.

28.10 Secondary billing and the balance that moves

A patient responsibility balance is not always the patient's.

Coordination of benefits (COB) determines which plan pays first when a person has more than one. The primary pays first. The secondary considers what remains.

The sequence, and the vocabulary is simple once seen:

   PRIMARY adjudicates
      ► allowed, paid, and a PR balance
                 │
                 ▼
   The PR balance is NOT YET the patient's
                 │
                 ▼
   SECONDARY receives the claim WITH the primary's
   remittance information
      ► applies ITS benefit
      ► may pay some, all, or none
                 │
                 ▼
   WHAT REMAINS after the secondary is the PATIENT'S

Three things that go wrong here, constantly.

Billing the patient after the primary. The PR balance from a primary remittance looks exactly like a patient balance and is not, when a secondary exists. This is the single most common improper patient bill, and it is generated by a posting process that does not know a second coverage exists — which is Chapter 24 §24.4's eligibility question arriving thirty days late.

Not billing the secondary at all. The balance sits, ages, and is eventually written off. Chapter 25 §25.2's items 9a–9d and item 11d exist to prevent this — the claim was supposed to say another coverage exists.

And the crossover assumption. Many secondary claims cross over automatically — the primary transmits directly to the secondary — and many do not. A practice that assumes crossover for a payer that does not do it produces a stack of never-billed secondary claims. The remittance usually says whether a claim was forwarded. Read it.

⚖️ Compliance Check

The balance that moves is where a patient gets billed for something they do not owe, and the obligation runs in both directions.

You may not bill a patient for a CO amount. §28.3. That is contractual.

You may not bill a patient for an amount a secondary payer is obligated to pay, and for Medicare-Medicaid dually eligible individuals the protections are stronger still — Chapter 3 established that a QMB may not be billed for Medicare cost sharing, and a practice that bills a PR-2 coinsurance to a QMB has done something prohibited, not merely awkward.

And when you learn later that a balance was not the patient's, you owe a correction — a refund if paid, a reversal if not, and a statement that says so. Chapter 32 §32.10.

The practical control is one question at posting: "does this patient have other coverage?" If your posting process cannot answer it from the account, the answer is being guessed. Chapter 24 §24.4's eligibility response is where it should have been recorded, and Chapter 25's item 11d is where the claim asserted it.

28.11 🗂️ The Encounter — posting Account 10-4471's first remit

Day 17, Friday, March 31, on Chapter 1's Encounter timeline. The remittance arrives.

   REMITTANCE ADVICE — NORTHFIELD MUTUAL
   payment date 03/31   ·   EFT
   ─────────────────────────────────────────────────────────────
   PATIENT CONTROL NUMBER  10-4471
   CLAIM STATUS            processed as primary
   TOTAL CHARGE            367.00      TOTAL PAID   70.30
   ─────────────────────────────────────────────────────────────
   LINE 1   99214-25   CHG 185.00   PAID   0.00
              CO   97   128.40
              CO   45    56.60
              RARC N19
   LINE 2   20610-RT   CHG 150.00   PAID  62.88
              CO   45    71.40
              PR    2    15.72
   LINE 3   J1030      CHG  18.00   PAID   5.02
              CO   45    11.72
              PR    2     1.26
   LINE 4   36415      CHG  14.00   PAID   2.40
              CO   45    11.00
              PR    2     0.60
   ─────────────────────────────────────────────────────────────

Check every line before posting anything.

   LINE 1   185.00 − 128.40 − 56.60 =  0.00  ✓
   LINE 2   150.00 −  71.40 −  15.72 = 62.88 ✓
   LINE 3    18.00 −  11.72 −   1.26 =  5.02 ✓
   LINE 4    14.00 −  11.00 −   0.60 =  2.40 ✓

   PAID     62.88 + 5.02 + 2.40 = 70.30  ✓  (matches the EFT)
   PR       15.72 + 1.26 + 0.60 = 17.58

Line 1 is worth reading slowly, because it carries two adjustments and most people see one.

CO-45 \$56.60** is the ordinary contractual adjustment — the spread between the \$185.00 charge and the \$128.40 allowed amount. The payer allowed the service.**

CO-97 \$128.40 then takes the entire allowed amount away as bundled.

The payer priced the visit and then declined to pay for it. That is not a contradiction; it is how a bundling denial looks on a remittance, and it is why the appealable amount is \$128.40 rather than \$185.00. Chapter 23 §23.7's rule — you are owed the allowed amount, not the charge.

The posting

   LINE 1   contractual adjustment ..............   56.60
            DENIAL — CO-97 / N19 ................  128.40
            ► NOT an adjustment. A DENIED AMOUNT,
              routed to the denial work queue.
              Ch. 29 §29.5.
   LINE 2   contractual adjustment ..............   71.40
            payment .............................   62.88
            patient responsibility (PR-2) .......   15.72
   LINE 3   contractual adjustment ..............   11.72
            payment .............................    5.02
            patient responsibility (PR-2) .......    1.26
   LINE 4   contractual adjustment ..............   11.00
            payment .............................    2.40
            patient responsibility (PR-2) .......    0.60
   ─────────────────────────────────────────────────────────
   PAYMENT POSTED ..............................   70.30
   PATIENT RESPONSIBILITY CREATED ..............   17.58
   OPEN DENIED AMOUNT ..........................  128.40

Now the copay.

The \$30.00 collected on day 0 is sitting on the account. This remittance does not touch it — the E/M line, which is where the copay belongs, paid nothing and produced no PR-3. The payer never adjudicated a copay because it never paid the visit.

**So on day 17, the patient's balance is \$17.58 and the account holds a \$30.00 credit that

belongs to a line that has not been paid yet.**

Do not bill anything. The appeal is coming (Chapter 30), and the \$30.00 will find its home on day 66 when the second remittance pays the E/M \$98.40** and reports the **\$30.00 as PR-3.

This is why the statement did not go out until day 70.

What the denial actually cost, and what it did not

   ALLOWED, HAD LINE 1 PAID ..................  216.28
   ALLOWED AS ADJUDICATED ....................   87.88
                                                ────────
   AT ISSUE ..................................  128.40

\$128.40 on one line of one claim, and three things follow from it.

The account did not look broken. Three lines paid, the arithmetic balanced, an EFT arrived. A posting process that recorded "payment received" and moved on would have been telling the truth.

The \$128.40 had to be routed somewhere on purpose. §28.6: posted as a contractual adjustment, it disappears — the account zeroes out, nothing ages, no denial is logged, and nobody appeals. Posted as a denied amount, it becomes Chapter 29's day-20 work item and Chapter 30's day-24 appeal, which was upheld on day 59.

And nothing in the pipeline could have prevented it. Chapter 27 §27.10 made this point about acknowledgment; the remittance makes it about adjudication. The claim was correct. The modifier was correct. The payer's edit fired anyway, and the only available response was to read what came back and disagree in writing.

Q4 remains open. The denial has now been read, priced, and routed. What it cost to resolve is not this chapter's arithmetic, and no chapter before 40 may perform it.

Summary

The remittance advice comes in three forms with three names — remittance advice generally, ERA electronically, SPR on paper — and the 835 is the transaction carrying the electronic one. They contain the same information; only one of them can be posted by a machine.

A remittance is organized by check, then claim, then line, with PROVIDER-LEVEL ADJUSTMENTS at the bottom — things done to you rather than to a claim. Every adjustment has three parts: a group code, a CARC, and an amount. And every line balances: charge = paid + adjustments.

The patient's EOB says something different on purpose. It explains a benefit, not a payment; it shows the charge prominently; "you may owe" is an estimate; and it arrives on its own schedule.

The GROUP CODE decides WHO OWES. The CARC decides WHY.

CO — contractual obligation, the patient may not be billed. PR — patient responsibility (PR-1 deductible, PR-2 coinsurance, PR-3 copay). OA — other, most often coordination of benefits. PI — payer initiated.

PR posted as CO is silent revenue loss with no error message. CO posted as PR is a contract violation and possibly worse. The check that finds both: any CARC appearing under more than one group code.

A CARC without its RARC is frequently unactionable — CO-16 is the standing example, and a report configured to suppress remark codes converts every one of them into a phone call.

Post at the LINE. Post what the remittance says, not what you expected. And post the zero lines, because a line that paid nothing still carries the group code, the CARC, and the RARC that explain why.

A CONTRACTUAL ADJUSTMENT was never collectible; a WRITE-OFF is a decision to stop pursuing money you were entitled to. Conflating them makes the collection rates uninterpretable, hides which decisions somebody made, and — the expensive one — turns a denial into an account that looks paid in full. Nobody appeals a write-off.

Autoposting is genuinely good at volume, speed, and consistency, requires ERA enrollment nobody mentions, and gets four things wrong: it posts denials as adjustments · it applies group codes from rules · it cannot see an underpayment · and it handles the exceptions worst. Ask who works the exception queue and what the oldest item in it is.

An underpayment does not deny, does not reject, appears on no exception report, and arrives as a

payment — and it RAISES your net collection rate.

Finding one requires an expected allowed amount per line per payer, computed from the contract independently of the remittance, compared, thresholded, and classified into contract loaded wrong · claim wrong · payer wrong. Start with your top twenty codes at your top three payers, which is a week of work and the highest-yield week most practices have available.

Takebacks and offsets live in the provider-level adjustment section. Post every claim at its full remitted amount and post the offset separately — never net the claims down to match the deposit — and read the offset's reference, because it names a claim that is itself a finding.

A reprocessed claim arrives as a REVERSAL followed by a CORRECTION, both on the same remittance. Post both halves: posting only the correction doubles the payment, and stopping at the negative leaves the claim unpaid. And a reprocessing you did not request is a payer restating what it should have done — worth asking whether every affected claim was corrected or only the ones somebody complained about.

A PR balance is not the patient's when a secondary exists. The primary's PR moves to the secondary, and only what survives that is the patient's. Do not assume crossover; the remittance usually says whether the claim was forwarded.

And Account 10-4471's first remittance paid \$70.30 on three lines, created \$17.58 of patient responsibility, and left \$128.40 open on line 1 under CO-97 with RARC N19 — the payer asserting the office visit was incidental to the injection, on a claim carrying modifier 25 and a note documenting three unrelated chronic problems. The \$30.00 copay stayed where it was, because the line it belongs to had not been paid.

Three lines paid. The arithmetic balanced. An EFT arrived. And the account was \$128.40 short in a way that only a person routing the CO-97 on purpose would ever see.

Key Terms

Remittance advice · electronic remittance advice (ERA) · standard paper remittance (SPR) · 835 · explanation of benefits (EOB) · claim adjustment reason code (CARC) · remittance advice remark code (RARC) · group code · CO · PR · OA · PI · CO-45 · CO-97 · CO-16 · PR-1 / PR-2 / PR-3 · N19 · allowed amount · contractual adjustment · write-off · preventable administrative write-off · payment posting · line-level posting · zero-pay line · autoposting · exception queue · underpayment · expected allowed amount · variance threshold · takeback · recoupment · offset · provider-level adjustment · coordination of benefits · secondary claim · crossover

Spaced Review

From Chapter 3 — QMB protections. A PR-2 coinsurance billed to a dually eligible beneficiary is prohibited, not merely awkward.

From Chapter 21 — bundling. CO-97 with N19 is an NCCI-type assertion arriving as money, and Chapter 21's six-way triage is how you decide whether to appeal it.

From Chapter 22 §22.7 — the ABN. It is the instrument that determines whether a necessity denial arrives as CO or PR, and GA/GX/GY/GZ are how you said so in advance.

From Chapter 23 §23.6, §23.7, §23.9, §23.10 — the per-line contract, the lesser-of rule, the collection ratios, and the promise this chapter's §28.8 just kept.

From Chapter 24 §24.4, §24.11 — eligibility and the \$30.00. Both arrive here as posting decisions.

From Chapter 25 §25.2, §25.8 — items 9a–9d and 11d for the secondary; the place of service that underpays silently.

From Chapter 26 §26.2 — FL 3a comes back on the remittance. That is what makes autoposting possible.

From Chapter 27 §27.5, §27.7 — ERA enrollment, and the rejection that never became a denial and so never appeared here at all.

Coming up: Chapter 29 takes the \$128.40 and asks what kind of denial it is, why the category matters more than the fix, and what a denial log tells a practice about itself.