Payment Posting in Medical Billing: Process, Errors, KPIs, and Best Practices
Payment posting is where denials, underpayments, and unapplied cash first become visible. Here is the process, the errors that cost the most, and the KPIs that prove posting is accurate.
A payment arriving is not the same as a claim being finished. Someone still has to match that payment to the right patient, claim, and service line, record the adjustments, assign what the patient owes, and decide whether anything on the remittance was denied or underpaid.
That work is harder than it sounds. One payment can cover many claims and many service lines, carry several types of adjustment, and leave balances that belong to the patient, a secondary payer, or the A/R team. Whatever your staff records at this step becomes your A/R, your denial reports, your collection rate, and your view of cash. Post it wrong and every number downstream is wrong with it.
This guide covers what payment posting is, where it sits in the revenue cycle, how ERA and paper EOB posting differ, what actually gets recorded, the step by step process, the errors that cost the most, the KPIs worth tracking, and the practices that keep posting accurate.
What Is Payment Posting in Medical Billing?
Payment posting is the process of recording what the payer decided after adjudicating a claim. It captures the payment, the adjustments, the patient responsibility, any denied or zero-pay lines, and the balance that remains, and it writes all of that against the correct claim and service line in the billing system.
It is a bookkeeping step with an analytical job attached. Recording the money is the easy half. The valuable half is noticing what the remittance is telling you about claims that did not pay the way they should have.
Where payment posting sits in the revenue cycle
Posting comes after the payer processes the claim and before denial work and A/R follow-up. It is the hinge between payer processing and everything your team does about the result.
- Patient registration
- Eligibility and benefits verification
- Coding
- Claim submission
- Payer processing
- Payment posting
- Denial and A/R follow-up
- Final collection
When a claim pays correctly, posting closes the account. When it does not, posting is where the problem is supposed to be identified and routed. That is the whole reason accuracy matters here: posting decides which claims your team believes are finished and which ones still need work.
Why Accurate Payment Posting Matters to Your Revenue
Posting errors do not stay in the patient account where they were made. They travel into A/R, denial reporting, patient statements, collection rates, and credit balances. Here are the four ways that plays out.
Payment posting is where hidden denials first surface
The remittance is the first place your practice learns that something went wrong. A payer can deny the whole claim, pay some lines and not others, reduce the allowed amount, or pay nothing for one specific service.
Consider a claim with four services where the payer pays three and denies the fourth for missing information. If the poster records that denied amount as a contractual adjustment, the account balances to zero and the claim looks complete. Nothing reaches the denial queue, nobody calls the payer, and the appeal window closes on a claim that would have paid after a correction. The service was denied, but the billing system says it was resolved.
This is why zero-pay, denied, and short-paid lines have to be flagged at the moment they are posted rather than discovered later in an aging report.
Inaccurate payment posting distorts every report that follows
Every revenue cycle report reads from what posting recorded. Book an unpaid balance as a contractual adjustment and A/R understates what the practice is owed. Apply a payment to the wrong patient and you have created two wrong accounts at once: one still showing a balance, one carrying a credit.
Denial reporting fails the same way. When the recorded reason does not match the reason the payer gave, the claim is routed to the wrong follow-up process and the denial report describes categories rather than causes. Practice leaders then make staffing, contracting, and workflow decisions from numbers that do not describe reality.
Unapplied cash creates phantom A/R and hidden revenue leakage
Sometimes money arrives and the poster cannot match it to a claim or patient, so it sits in suspense. Two problems start immediately.
First, the claim still reads as unpaid even though the practice has the money, which inflates A/R with balances that are already settled. Second, your A/R team works those claims. Staff call payers, resubmit, and follow up on services that were paid weeks earlier. These are the claims nobody chases, in reverse: the money is already in the bank and simply is not visible.
Unapplied cash needs a worklist and an owner, reviewed on a schedule, with the oldest items cleared first.
Incorrect patient balances erode trust and delay collections
Posting also determines what the patient owes after insurance: deductible, copay, coinsurance, or another valid patient responsibility amount. Move the wrong balance and the patient receives a bill that is wrong.
Coordination of benefits is the common failure. A patient has primary and secondary coverage, and the balance is transferred to the patient before the secondary claim is filed. The statement goes out, the patient disputes it, staff spend time on a call that should not have happened, and the payment that was collectible now arrives late or not at all. Resolve secondary coverage before any balance moves to the patient.
ERA vs. EOB: The Two Documents Posting Runs On
Posting needs remittance information to work from, and that information arrives in one of two forms: an Electronic Remittance Advice, which is the HIPAA standard 835 transaction, or a paper Explanation of Benefits. Both describe payments, adjustments, denials, and patient responsibility. They differ in format, in speed, and in how they fail.
| Factor | ERA (835) | Paper EOB |
|---|---|---|
| Format | HIPAA-standard ASC X12N 835 transaction | Printed payer statement |
| Delivery | Clearinghouse or payer portal, by secure file transfer or API | Mail, with a paper check or a separate EFT |
| Posting method | Auto-posts against the original claim | Manual keying, line by line |
| Speed | Minutes per batch | Hours per batch |
| Error profile | Systematic. One bad posting rule affects every claim it touches | Random. Transcription and transposition mistakes |
| Denial codes | CARC and RARC delivered as structured data | Printed text that staff have to interpret |
| Reconciliation | Balances to the deposit using trace and payment segments | Manual matching to the check or deposit |
ERA posting is faster because the system does most of the matching. It does not remove the need for review, it changes the shape of the risk. A wrong posting rule applies itself consistently to hundreds of claims before anyone notices, while paper posting produces scattered keying and account-matching errors that are easier to spot and slower to fix.
What the 835 actually contains
The 835 is the standard electronic remittance format. The raw file is organized into segments, and a handful of them carry the information posting depends on.
- BPR. Payment information for the remittance as a whole.
- TRN. Trace information that ties the remittance to the related payment.
- CLP. Claim level detail showing how the payer adjudicated an individual claim.
- SVC. Service line detail showing what was paid for each individual service.
- CAS. Adjustment detail, with the reason codes attached to each adjustment.
- PLB. Provider level adjustments, which apply to the provider rather than to a specific claim, such as recovered overpayments.
Together these connect the billed amount, the allowed amount, the payment, each adjustment, and the remaining balance. Read properly, the 835 does not just report the payment, it shows how the payer arrived at it, which makes it a built-in control for payment accuracy.
CARC and RARC codes: preserve the payer's original reason codes
When a payer reduces or denies a payment, it explains why in coded form. Two code sets do that work.
- CARC. Claim Adjustment Reason Code. States why the payer adjusted or denied the claim or service line.
- RARC. Remittance Advice Remark Code. Adds supporting detail about the decision.
Group codes sit alongside them and assign responsibility for each adjustment.
- CO. Contractual Obligation
- PR. Patient Responsibility
- OA. Other Adjustment
- PI. Payer Initiated Reduction
In practice your team sees them in combination.
| Code | What it generally means |
|---|---|
| PR-1 | Deductible |
| PR-2 | Coinsurance |
| PR-3 | Copayment |
| CO-16 | Claim or service needs additional information, or has a submission issue |
| CO-45 | Charge exceeds the applicable allowable or contracted amount |
| CO-97 | Payment for this service is included in another service already adjudicated |
| OA-23 | Adjustment related to the payment or adjudication of a prior payer |
Keep these codes exactly as the payer sent them. Collapsing them into an internal label such as "denied" destroys the only information that makes denial work efficient. A general category tells you something went wrong. The original codes tell you what went wrong, which claim to correct, and which team should correct it. Use internal groupings for reporting if you need them, but layer those on top of the payer codes instead of replacing them.
Match the ERA to the EFT before you post the payment
The remittance and the money travel separately. The ERA describes the payment and the Electronic Funds Transfer deposits it, and the two can arrive on different days. Match them using the trace and reference detail before you close the batch.
If an ERA totals $12,500, confirm that a deposit of $12,500 arrived and that the reference information ties the two together. When the amounts or references do not agree, investigate before posting rather than after. A variance caught at the batch is a five minute question. The same variance found during a month end close is a reconciliation project.
What Actually Gets Posted
Payment posting records several distinct transaction types, and mixing them up is where most accuracy problems begin.
Payer payments
The amount the insurance company paid after adjudicating the claim, applied to the correct patient, claim, and service line. Applying it at the claim level when line detail is available is a small shortcut with expensive consequences, covered below.
Contractual adjustments vs. write-offs
A contractual adjustment is the amount you agreed not to collect under your payer contract. A write-off removes a balance for another approved reason, such as a small balance policy or an uncollectible account. They look identical on a zero balance account and mean completely different things about your revenue. Record them separately, always.
Patient responsibility
The portion of the allowed amount the payer assigns to the patient.
- Deductible
- Copay
- Coinsurance
- Other valid patient responsibility
Review the remittance and any other coverage on file before this balance moves to a statement.
Denials and zero-pay lines
A zero payment is not permission to close the balance. Read the payer codes and establish why nothing was paid. The line may need a correction, additional documentation, an appeal, submission to a secondary payer, or another form of follow-up. Each of those is a different worklist, and posting is where the routing decision gets made.
Takebacks, offsets, and refunds
Payers recover prior overpayments by reducing a later payment. Tie the recovery back to the original payment or account it relates to. Posting the full deposit as new revenue while ignoring the offset overstates collections and leaves a balance that will not reconcile, which is the kind of error that surfaces months later during a close.
The Payment Posting Process, Step by Step
A defined sequence is what turns posting from data entry into a control. Each step either records something or catches something.
Step 1: Receive payment and remittance information
Collect the payment and the remittance that goes with it, log the batch, and track it from receipt through posting and reconciliation. Batches that are not logged are the ones that go missing.
Step 2: Match the payment to the correct claim
Match on claim and payment identifiers rather than on patient name and amount. Anything that does not match cleanly goes to the unapplied cash worklist for review, not into a best guess account.
Step 3: Review the ERA or EOB
Read the remittance before recording anything: payment amount, adjustments, patient responsibility, denial and remark codes, and the balance remaining. This is the review that decides whether the rest of the steps are accurate.
Step 4: Post payments at the claim or service-line level
Apply the payment to the specific claim and service. When line detail exists on the remittance, post at line level so per-service outcomes stay visible.
Step 5: Apply contractual adjustments and patient responsibility
Record valid contractual adjustments and the patient portion, each with a reason that matches what the payer sent. Every adjustment should be traceable to a payer code or a documented internal policy.
Step 6: Identify denials, underpayments, and exceptions
Work through denied lines, zero-pay claims, underpayments against the contracted rate, duplicate payments, and anything else that does not reconcile. This step is the difference between posting and simply recording deposits.
Step 7: Route remaining balances
Send what remains where it belongs: to the patient, to a secondary payer, to denial management, or to A/R follow-up. Every balance should leave posting with an owner attached.
Step 8: Reconcile the payment batch
Compare what was posted against what was received, investigate the difference, and correct it before closing. A batch that does not balance is a signal, not a rounding artifact.
Step 9: Close or escalate the account
Close accounts where every balance is resolved, and escalate the rest with enough detail that the next team does not have to reread the remittance from scratch.
Common Payment Posting Errors That Cost Revenue
These are the posting mistakes that cost practices the most, and none of them look like errors on the account they touch.
| Error | What happens | What it costs |
|---|---|---|
| Denial posted as a contractual adjustment | The claim shows closed and fully resolved | The denial never enters the appeal queue and the money is gone at the filing deadline |
| Lump-sum posting at claim level | No service-line detail is retained | Underpayments on specific CPT codes become invisible |
| Underpayment posted as full payment | No comparison against the contracted rate | Systematic payer underpayment continues indefinitely |
| Patient responsibility posted before COB resolves | A statement goes out prematurely | Patient dispute, delayed collection, and a missed secondary claim |
| Payment applied to the wrong account | Two accounts become wrong at once | Phantom A/R on one, an unexplained credit balance on the other |
| CARC or RARC codes remapped or dropped | The payer's original reason is lost | Denial analytics report categories instead of causes |
| Takeback posted as a new payment | The batch never balances | A recovered overpayment reappears as revenue that does not exist |
| Unapplied cash left in suspense | Money is received but never attributed | Staff work claims the payer already paid |
| Transposed amount on manual entry | A payment of $409 is keyed as $4,090 | The financial picture stays distorted until someone reconciles |
Best Practices for Accurate Payment Posting
Accurate posting is a set of habits rather than a software feature. These ten cover the failure modes above.
Reconcile every payment batch to the bank deposit daily
Compare posted totals against what actually landed in the bank, match ERA and EOB totals to the related deposit, and investigate every difference. Daily reconciliation finds missing, duplicated, and misposted payments while the remittance is still fresh and the correction is still cheap.
Post payments at the service-line level
Line level posting is what makes a denied or underpaid CPT code visible. Post a lump sum at claim level and a partially denied claim looks like a paid claim, which is exactly the failure that keeps payer underpayments running for years.
Preserve payer codes exactly as received
Keep the original CARC, RARC, and group codes on the account. They are the record of why the payer did what it did, and they are what makes denial follow-up specific instead of general.
Maintain accurate, up-to-date fee schedules
You cannot identify an underpayment without knowing what the payment should have been. Load contracted rates, compare actual payments against expected reimbursement, and refresh the schedules whenever a contract or rate changes.
Separate contractual adjustments from write-offs
Contractual adjustments are the cost of participating with a payer. Write-offs are revenue you decided not to pursue. Recording them in the same bucket hides which one is growing.
Connect payment posting directly to denial management
A denial identified during posting should reach the denial worklist the same day, not surface later in an aging report. Every day of delay is a day removed from the correction and appeal window.
Set and enforce a 24 to 48 hour posting standard
Post remittances within 24 to 48 hours of receipt. Anything slower keeps paid claims sitting in A/R, makes aging reports describe the past, and delays every denial hiding inside those batches.
Clear unapplied cash and credit balances regularly
Review unapplied cash and credit balances on a schedule, assign owners, and work the oldest items first. Unapplied cash wastes staff time on settled claims, and aged credit balances are a compliance exposure that grows quietly until someone asks about it.
Audit posted batches for accuracy each month
Sample posted batches monthly and check payments, adjustments, payer codes, patient responsibility, denial routing, and reconciliation. When the same issue appears twice, fix the posting rule or the training rather than the individual account.
Automate routine posting and staff the exceptions
Let ERA auto-posting handle clean, fully paid claims, and put people on the work that requires judgment: denials, underpayments, unmatched payments, takebacks, and coordination of benefits. Review the automation rules regularly, because an unexamined rule repeats its mistake at scale.
Payment Posting KPIs Medical Practices Should Track
Posting quality is measurable. These seven metrics show whether payments are recorded promptly, attributed correctly, and mined for the denials and underpayments hiding inside them.
| Metric | What it measures | Why it matters |
|---|---|---|
| Posting lag | Days between receiving a remittance and posting it | Determines whether your A/R aging reflects reality |
| ERA auto-post rate | Share of remittance dollars posted without manual touch | A direct measure of automation coverage and staff load |
| Unapplied cash | Value and age of money received but not yet attributed | Money you already hold that is invisible in your reporting |
| Reconciliation variance | Difference between posted totals and related deposits | The core accuracy check. It should sit near zero |
| Denial capture rate | Share of zero-pay and short-pay lines routed to a worklist | Shows whether denials are caught at posting or missed |
| Credit balance aging | Value and age of overpayments awaiting refund | Compliance exposure that grows quietly |
| Underpayment identification rate | Share of lines checked against contracted rates | Shows whether you are detecting payer underpayments at all |
Should You Outsource Payment Posting?
Posting can run in house or with an RCM partner. The decision comes down to payment volume, the experience of your billing team, what your billing system automates, and how much manual EOB work you are absorbing each week.
In house posting works when volume is manageable and the team is experienced enough to recognize a denial dressed up as an adjustment. Outsourcing makes sense when the symptoms are already visible: posting backlogs, stacks of manual EOB entry, batches that do not reconcile, unapplied cash nobody has time to clear, and denials that are being found in aging reports rather than at posting.
A partner takes on daily posting, reconciles payments to deposits, clears unapplied cash and credit balances, and routes denials and underpayments to the right worklist. The practical benefit is not only lower workload. It is that posting stays current, so every report your practice reads is describing this week instead of last month.
Reduce Payment Posting Errors With CureMed's RCM Solutions
CureMed treats payment posting as a control point rather than a data entry queue. Our team reviews payer payments and remittance detail, posts to the correct account and service line, records adjustments against the reason the payer actually gave, and identifies the claims that need follow-up while there is still time to act on them.
- ERA auto-posting. Clean remittances posted automatically, with rules reviewed so a single bad rule does not repeat itself across a batch.
- Daily reconciliation. Every batch matched to the related deposit, with variances investigated before the batch closes.
- Denial and underpayment capture. Denied, zero-pay, and short-paid lines flagged during posting and routed the same day.
- Unapplied cash and credit balance cleanup. Suspense accounts worked on a schedule, oldest first, so cash stops hiding and refunds do not age.
- Patient responsibility handling. Patient portions posted only after coordination of benefits is resolved, so statements go out right the first time.
- A/R follow-up. Remaining balances pursued with the payer or the patient rather than left to age.
If your A/R includes claims that were already paid, or your denial reports describe categories instead of causes, the problem usually starts at posting. The CureMed team can review your current posting and reconciliation process and show you where the money is sitting.
Curious what your revenue cycle is actually leaving on the table?
Spend 30 minutes with our revenue cycle team and we'll walk through your current setup, surface where money is leaking from denials, slow payer follow up, undercoded encounters, and quantify what cleaning it up is worth in your first 90 days. No prep, no slide deck, just a working conversation with people who do this every day.