You pull the week’s deposit report and set it next to what your practice management system says should have come in. The two numbers do not match. Not by a lot, a few hundred dollars scattered across a handful of claims, but enough that closing the books this month means someone spending an afternoon tracing each remittance back to the original claim.
This article breaks down what payment posting actually involves, why the common framing of manual versus automated posting misses the real risk sitting underneath it, and a practical way to check whether your current process is catching money you are actually owed, not just money that already showed up in a file.
We have reviewed posting workflows across independent practices ranging from single physician offices to multi provider groups, and the pattern holds up. The practices with the cleanest books are rarely the ones with the most software. They are the ones where someone is checking the math against the actual contract, every single day.
When “Posted” Doesn’t Mean “Paid Correctly”
Here is what usually happens. Someone on your team pulls the ERA, matches it to the claim, and posts the payment. The system marks the claim closed. Everyone moves on.
Three weeks later, a patient calls confused about a balance that does not match what they were quoted. Or a biller notices, almost by accident, that a payer has been reimbursing at a rate lower than the actual contract specifies, and has been for months. Neither of these shows up as a denial. Neither trips an alert. The claim was posted. The system called it done.
So which is it, a coding problem, a posting problem, or a collections problem? Most of the time it traces back to posting, specifically to the gap between “this matches the remittance” and “this matches what we are actually owed.” Those are two different checks, and most practices, whether they post by hand or run a fully automated ERA feed, are only running the first one.
That gap is not a rare edge case. It is the default state of payment posting almost everywhere, until someone deliberately builds a second check into the process.
What Is Payment Posting in Medical Billing?
Payment posting is the step where payments and adjustments from insurance payers and patients get recorded, line by line, against the original claim in your billing system. It happens after a claim has been adjudicated, meaning the payer has already decided what to pay, what to adjust, and what to deny.
At the line item level, payment posting typically records:
- The amount the payer actually paid
- Contractual adjustments, the difference between your billed charge and what the payer’s contract allows
- Denial or rejection codes, when a line was not paid at all or only partially paid
- What remains as patient responsibility, such as a copay, deductible, or coinsurance amount
This information usually arrives through one of two documents: an Electronic Remittance Advice (ERA), a standardized electronic file also known as an 835 transaction, or a paper Explanation of Benefits (EOB), the older format that still shows up for some smaller payers, workers’ compensation claims, and out of network reimbursements.
Payment posting is not the same as charge posting, which happens earlier, when a claim is first entered and submitted. Payment posting happens after the payer has responded. It is the step that turns “we billed for this” into “here is what we actually collected,” and it is the step that determines whether your accounts receivable numbers reflect reality or a comfortable guess.
Why “Manual vs Automated” Is the Wrong Question
What ERA Auto-Posting Actually Automates
Electronic Remittance Advice changed payment posting by removing the slowest, most error prone part of the job: keying numbers by hand off a paper EOB. When a practice enrolls with a payer for ERA delivery, usually through a clearinghouse, the 835 file arrives already broken into payment, adjustment, and denial segments. Billing software reads that file and posts the matching line items automatically, updating the claim status and the patient balance without anyone typing a single number.
According to the 2023 CAQH Index, roughly 88 percent of remittances across the industry now arrive as fully electronic 835 files, which means most practices already have the infrastructure to auto-post the bulk of routine payments. That is a real gain. Data entry errors, the transposed digit, the misapplied line, the payment posted to the wrong account, drop sharply once a human is no longer typing every figure by hand.
What ERA Auto-Posting Does Not Check
Here is the part most guides skip. ERA auto-posting reconciles the payment to the claim. It confirms the amount posted matches what the remittance says the payer decided to pay. It does not, on its own, confirm that what the payer decided to pay matches what your contract actually says they owe you.
Those are two separate checks, and only the first one is automatic by default. If a payer applies an outdated fee schedule, processes a code at the wrong contracted rate, or quietly underpays a bundled service, the ERA will still generate cleanly. The remittance will match the posted amount. The claim will close as paid. Nothing about that transaction looks broken, because nothing in the automated workflow is comparing it against your actual contract.
What we consistently see when independent practices move to full ERA processing is relief, followed months later by the discovery that the same underpayment pattern is still there, just automated instead of handwritten. The software removed the typing. It did not remove the need for someone to check the payer’s math.
The Pattern We See Across Independent Practices
A four physician family medicine practice we support had been running ERA auto-posting for over a year and considered payment posting a solved problem. Claims were adjudicating fast, remittances were posting automatically, and days in accounts receivable looked reasonable on the monthly report.
When we cross-checked six months of posted remittances against the practice’s actual payer contracts, line by line, the picture changed. In payments had posted as fully paid when the contracted allowed amount was actually higher. None of it had triggered a denial code. None of it had shown up in a report anyone was reviewing. It simply looked like a slightly smaller number than expected, month after month, easy to miss unless someone is specifically looking for it.
That is not a story about bad software or a careless biller. The ERA feed was doing exactly what it was built to do, matching payments to claims and posting them cleanly. Nobody had built in the second check, the one that asks whether the payer’s number actually matches the contract’s number. Once that check existed, the practice started catching discrepancies the same week they occurred instead of finding them, if they were found at all, during an annual reconciliation nobody had time to run properly.
The Three-Layer Posting Check
Getting payment posting right is not about choosing manual or automated. It is about making sure three specific checks happen on every remittance, regardless of who or what is doing the posting. We call this the Three-Layer Posting Check, and it is the model our VMAs apply to every ERA and EOB that comes through a client practice.
Layer 1: Match Every Line to the Original Claim
Before anything gets posted, each line on the remittance needs to tie back to the exact claim, patient, and date of service it corresponds to, not just the claim number as a whole. A single claim can carry multiple service lines, and a payer can approve some lines while denying or adjusting others on the same remittance. Posting at the claim header level instead of the line level is how a partial denial quietly disappears inside a claim that looks, on the surface, like it paid in full.
Layer 2: Verify Against the Actual Contract, Not Just the Remit
This is the layer most posting processes skip, whether they are manual or automated. The remittance tells you what the payer decided to pay. It does not independently confirm that decision was correct. Layer 2 means comparing the posted allowed amount against your actual fee schedule or contracted rate for that payer and that code, and flagging anything that does not match.
For practices without a fee schedule that is fully loaded and actively maintained inside their billing software, this check depends on a person who knows what to look for. It is exactly the layer Care VMA’s medical billing virtual assistants are trained to run as a normal part of daily posting, not as a once a year audit project squeezed in whenever someone finally has time.
Layer 3: Route Exceptions the Same Day
Once a line fails Layer 1 or Layer 2, meaning it does not match the claim cleanly or it does not match the contract, it needs to move into a follow-up queue the same day, not whenever someone gets around to it. A denial that sits untouched for three weeks is a denial getting closer to missing its appeal deadline. An underpayment flagged today is usually recoverable. The same underpayment flagged eight months from now, buried inside a batch reconciliation, often is not.
This is also where how a billing VMA works denied and underpaid claim lines matters more than most practices expect. Same-day routing is less about speed for its own sake and more about protecting the appeal window every payer contract builds in. Miss that window, and money that was technically recoverable simply becomes a write-off, whether anyone consciously decided to write it off or not.
The Mistake Most Practices Make After They Automate
Trusting the Remit Without Checking the Contract
Once ERA auto-posting is running smoothly, it is tempting to treat payment posting as finished business. The claims close automatically. The reports look clean. Nobody is manually keying numbers anymore, so surely the hardest part is over.
It usually is not. A 2024 revenue cycle survey from the Healthcare Financial Management Association ranked payment posting among the top three bottlenecks to clean revenue reporting, trailing only prior authorization and eligibility verification, two categories most practices already know are a problem. Posting rarely gets the same attention, precisely because it looks solved the moment the ERA feed is running.
That assumption, that a working ERA feed means the checking already happened, is exactly what lets underpayments hide in plain sight for months. Understanding how the allowed amount gets tracked against what a payer actually pays is the difference between a posting process that only confirms receipt and one that confirms accuracy. Automation solves the data entry problem. It does not solve the contract verification problem, and those are not the same problem, no matter how clean the dashboard looks.
Letting Zero-Pay and Partial-Pay Lines Slip Through
Zero-pay and partial-pay lines often get the least attention, precisely because they do not look urgent the way a full denial does. A line that pays $40 against a $65 contracted rate does not trigger the same alarm as a line that pays nothing, but the revenue impact adds up the same way, one line at a time, across every claim it happens to.
The fix is not more software. It is a rule: every line that pays less than expected gets flagged and routed, not just the lines that pay zero. Most posting workflows, even automated ones, are configured to catch the obvious denials and quietly let the smaller shortfalls pass through unflagged.
When Fee Schedules Drift, So Does Your Accuracy
How Often Contracted Rates Actually Change
Most physicians don’t realize that a fee schedule is not a document you load once and trust indefinitely. Payers update contracted rates on their own schedule, sometimes annually, sometimes mid-year for specific codes or specialties, and those updates rarely arrive with a clear notification to your billing team.
If your Layer 2 check is running against a fee schedule from eighteen months ago, it is comparing new payments against old numbers. Depending on the direction of the change, that either creates false alarms your team learns to ignore, or worse, it stops catching real underpayments because the outdated baseline has drifted to match the underpayment instead of the correct rate.
Who Should Own Keeping the Data Current
This is where the staffing question actually matters, more than the manual versus automated question does. Software does not update itself with new contract terms. Someone has to. In a small practice, that responsibility often has no clear owner. It falls somewhere between the front desk, whoever handles billing that week, and the physician who signed the contract in the first place and may not remember its exact terms a year later.
Deciding who owns that is really a question of how a billing VMA’s role compares to hiring an in-house biller, since the answer changes depending on whether that responsibility sits with one more employee to manage or with a managed service built to carry it. If your ERA feed has been running clean for two years, when was the last time anyone actually checked whether clean still means correct? For most of the practices we have reviewed, the honest answer is longer ago than anyone expected.
Getting Payment Posting Right Without Adding Headcount
None of this means ERA automation is the wrong investment. One published case study from a payment automation vendor described a multi-location group that eliminated an outsourced posting vendor entirely after automating remittance validation, saving $240,000 in annual fees and cutting days in accounts receivable to 36. That kind of return is real, and for a practice running any meaningful claim volume, auto-posting is not optional. It is the only way the math holds together day to day.
The Three-Layer Check does not replace that automation. It makes sure the automation is checking the thing that actually protects your revenue, not just the thing that happens to be easiest to automate.
In our view, most practices do not have a technology problem with payment posting. They have an ownership problem. Nobody is specifically responsible for the contract-verification layer once the software goes live, and it quietly falls off everyone’s list. That is the gap a fully managed, HIPAA-compliant Virtual Medical Assistant is built to close. A Care VMA handling your payment posting runs all three layers as a standard part of daily work, matching, verifying against contract, and routing exceptions the same day, without asking you to hire, train, and manage another full-time employee to do it.
If you want a clearer picture of what that could look like for your own posting numbers, schedule a free consultation with the Care VMA team.
FAQ
What is the difference between payment posting and charge posting? Charge posting happens when a claim is first created and submitted, before the payer has responded. Payment posting happens afterward, once the payer has adjudicated the claim and sent back an ERA or EOB showing what was actually paid, adjusted, or denied.
How long should payment posting take after a claim is paid? For claims arriving through ERA, posting should happen within 24 to 48 hours of receipt. Paper EOBs typically take longer to process, but delays beyond a few business days start pushing denial follow-up closer to the payer’s appeal deadline.
Can automated payment posting still miss underpayments? Yes. Automated posting confirms the posted amount matches the remittance, but it does not automatically confirm the remittance itself matches your actual contracted rate. Without a separate check against your fee schedule, underpayments can post as paid in full and go unnoticed.
Who should be responsible for payment posting in a small practice? In most independent practices this sits with billing staff or an outsourced billing partner, but ownership often becomes unclear once ERA automation is in place. Someone still needs to own contract verification and same-day exception routing, whether that is an in-house biller, a billing company, or a managed VMA.
How much does incorrect payment posting actually cost a practice? The cost varies by claim volume and payer mix, but it consistently shows up as underpayments that are never recovered, denials that miss appeal deadlines, and staff hours spent on month-end reconciliation instead of AR follow-up.
