A three-physician orthopedic practice asked us to look at their accounts receivable because patient balances seemed high. Within an hour the problem turned out to be somewhere else. The bank statement showed $612,400 in deposits for January. The practice management system showed $577,900 posted for the same month. Nobody had noticed the $34,500 gap because the practice had no payment posting workflow that compared the two numbers. Some of it was unapplied cash. Some was electronic remits that had downloaded but never posted. About $6,000 was a Medicare recoupment netted out of a deposit and never recorded on the accounts it came from.
Payment posting is the least glamorous job in the billing office and the one that decides whether every other report is true. Days in AR, denial rate, collection rate, patient balances: all are calculated from posted transactions, and if posting is late, wrong or incomplete, the practice is managing from fiction. Here is the workflow we set up: what auto-posts, what a person has to touch, and the daily match to the bank that catches a $34,500 gap on the day it opens rather than the quarter after.
A glossary line first. An 835 is the electronic remittance advice (ERA), the standard file a payer sends to explain what it paid and why for each claim. An EFT is the electronic funds transfer, the actual money landing in the bank. They travel separately and often arrive on different days, which is the root of most reconciliation trouble. Auto-posting means the practice management system reads the 835 and records payments and adjustments without a person keying them.
Key takeaways
- Every deposit in the bank must tie to a posted batch in the billing system, and the tie-out should be done by someone who did not post the batch.
- Auto-posting rules decide what gets written off without review, so the rules, not the poster, are the main control over revenue leakage in this step.
- The 835 carries provider-level adjustments (recoupments, interest, forwarding balances) that never appear on a patient account and are the usual reason a remit total does not match its deposit.
- Posting lag, auto-post rate and unreconciled items are the three numbers to watch weekly.
The payment posting workflow, end to end
Whatever door the money comes through, it ends in a posting batch with a control total that equals a specific deposit in the bank. First thing in the morning, someone downloads the 835 files from the clearinghouse, opens the paper remits, and pulls the prior day's bank activity. Each 835 is matched to its EFT using the trace number: the 835 carries a TRN segment with a reassociation trace number, and the EFT addenda from the bank carries the same number. Under the CAQH CORE operating rules that HIPAA-covered payers have had to follow since January 1, 2014, that number is required on both sides; if your bank's report omits the addenda, ask for it.
Once matched, the 835 runs through auto-posting. The system reads each claim (the CLP segment) and each service line, posts the paid amount and the contractual adjustment, moves patient responsibility to the patient balance, and routes denials and unusual adjustments to a work queue. Anything it cannot match to a claim lands in an exception list. A person then works the exceptions, posts paper remits and patient payments by hand, and closes each batch with a total that is compared to the deposits before anyone leaves.
Auto-posting 835s: the rules matter more than the software
Auto-posting is only as safe as the adjustment rules behind it. Every 835 adjustment carries a group code and a claim adjustment reason code (CARC): CO for contractual obligation, PR for patient responsibility, OA for other adjustment, PI for payer-initiated reduction. The system needs a rule for every CARC it may post automatically and an instruction to stop on the rest. Three failure patterns come up repeatedly.
The first is writing off everything coded CO. CO-45 (charge exceeds fee schedule) is a legitimate contractual write-off and should post automatically against the expected allowable. CO-97 (bundled), CO-B16 (new patient qualifications not met), CO-4 (modifier inconsistent with the procedure) and CO-197 (precertification absent) are denials wearing a CO group code. A rule that writes off all CO adjustments turns denials into contractual adjustments silently, and nobody appeals a write-off. In one audit we traced a practice's entire drop in denial rate to a posting rule change; the denials had been reclassified, not fixed.
The second is reversal handling. A claim status of 22 in the CLP segment is a reversal of a prior payment, usually followed by a corrected claim. Systems that post the reversal but lose the corrected line, or post both without netting, produce phantom credits and duplicate payments. The third is the crossover: when Medicare forwards a claim to a supplemental plan, the 835 says so with claim status 19, 20 or 21, and the system should hold the patient balance rather than billing the patient.
| 835 element | What it means | Auto-post action we recommend |
|---|---|---|
| CO-45 | Charge exceeds contracted fee schedule | Post as contractual; flag if the allowed amount is below the loaded fee schedule |
| PR-1, PR-2, PR-3 | Deductible, coinsurance, copay | Move to patient balance; hold if a secondary payer is on file |
| CO-97, CO-B16, CO-4, CO-197, CO-16 | Denials expressed as adjustments | Do not write off; route to the denial work queue |
| CLP status 22 | Reversal of a prior payment | Post the reversal; hold the account until the corrected claim posts |
| CLP status 19, 20, 21 | Forwarded to a secondary payer | Suppress the patient statement for 30 days |
| PLB WO | Overpayment recovery (recoupment) | Post to the original account with the recoupment date |
| PLB L6 | Interest paid by the payer | Post to a non-patient interest ledger |
The PLB segment, provider-level adjustments, is what breaks the deposit match most often. The BPR segment at the top of the 835 states the total payment, and that is what hits the bank. The claim-level payments will not sum to it when the payer has recouped an overpayment (WO), paid interest on late claims (L6), or carried a balance forward (FB). A Medicare remit with $18,240 in claim payments and a $1,100 WO recoupment deposits $17,140. If the poster records $18,240, the reconciliation is off by $1,100 and the recouped account still shows as paid.
Manual posting: paper remits, patient payments and virtual cards
Some payers still send paper, and so do most workers' compensation and auto liability carriers. Manual posting from an EOP is done line by line with the same discipline as the 835: paid amount, adjustment with a reason, patient responsibility, denial to the queue. Posters key the payer's reason code as written rather than a generic "contractual" adjustment, because the appeal team needs the payer's language later. Every paper batch gets a control total taken from the check before posting starts, and the batch cannot close until the posted total matches it.
The front desk batch is closed and totaled by the person at the desk at the end of each session and counted by a second person. Cash, checks and card receipts are batched separately because they reach the bank on different days. Virtual credit cards from payers are a special headache: the payer sends a single-use card number and the practice runs it through its own terminal, paying a merchant fee on money it was already owed. If you are enrolled for EFT with that payer, you can decline the card. Until then, the virtual card batch needs its own line in the reconciliation, because the deposit arrives net of the fee and the posted amount is gross.
The daily reconciliation of posted payments to bank deposits
This is the control everything else depends on, and it takes twenty minutes a day when it is done daily. Every deposit on the bank statement is matched to one or more closed posting batches whose totals sum to the deposit, and every closed batch is matched to a deposit. Anything unmatched on either side is listed by name and chased that day.
We use a three-column log per business day: bank deposits (amount, date, source from the addenda), posting batches (batch number, source, total), and variance with a note. A payer EFT of $23,415.62 matches an 835 batch of $23,415.62. A patient card settlement of $2,180.40 matches the front desk card batch of $2,214.00 less $33.60 in merchant fees, recorded to the fee ledger. A Medicare deposit of $17,140.00 matches an 835 batch showing $18,240.00 in payments and a $1,100.00 PLB recoupment. When a line doesn't balance, the note says why and who owns it. Someone other than the poster signs the log; in a small office that is the practice manager or the physician owner.
Two exceptions are worth naming. An 835 that arrives without its EFT, or an EFT without its 835, usually means a payer enrollment problem or a clearinghouse routing issue; if it persists for more than two business days, someone calls. Unapplied cash, meaning money posted to the practice but not to any patient account, has to be identified within five business days; it is usually a payment for a patient not in the system, a check for a provider who has left, or a payer paying under a different NPI.
The numbers to watch and what they usually mean
Three measures tell you whether the payment posting workflow is healthy. Posting lag is the number of business days between deposit and posting; we want it at one, and anything over three is a staffing or process problem. Auto-post rate is the share of 835 dollars that post without a human touch; practices with clean ERA enrollment can usually get above 80 percent, and a sudden drop means a new payer or a rule that broke. Unreconciled items is the count of deposits and batches without a match at close of business; the target is zero.
Once a month, look at the CO write-off amount by CARC, which tells you what the auto-posting rules are quietly doing; a rise in CO-97 write-offs with no rise in denials worked means denials are being posted as adjustments. This is the check our RCM audit spends the most time on, because it is where we find money that no report was ever going to show.
Questions we hear
Our clearinghouse posts the 835s for us. Do we still need the daily bank match?
Yes. The clearinghouse posts what the 835 says; it does not know what the bank received. Missing EFTs, netted recoupments and payments sent to an old bank account are exactly the problems the bank match finds and auto-posting hides.
How do we handle a payment for a claim we never billed, or a patient we don't have?
Post it to unapplied cash the same day with the payer, check number and any identifiers, then research it within five business days; most turn out to be a claim billed under another provider in your group or a patient registered under another name. If it is truly not yours, notify the payer and return it; for Medicare, the 60-day rule for returning identified overpayments applies once you know.
Who should do the reconciliation in a two-person billing office?
Not the person who posted; separation of duties is the point. The practice manager or the physician can sign off the log in ten minutes a day using the bank portal and the batch report. If that is not possible, an outside billing partner's reconciliation is one of the things to ask about; ours is described under medical billing.
What to do this week
- Compare last month's bank deposits to the posted payments report for the same month and explain the difference to the dollar.
- Export the auto-posting adjustment rules, mark every CARC that is written off automatically, and remove the denial codes from that list.
- Pull the unapplied cash report and age it; anything older than five business days is researched this week.
- Ask the bank to include EFT addenda (the TRN trace number) on the daily activity report if it isn't there already.
- Set up the three-column daily log and assign the sign-off to someone who does not post.
