Payment posting in medical billing is the process of recording and reconciling payments, adjustments, denials, and patient responsibility amounts after a payer adjudicates a claim.
It converts the raw output of claim adjudication — what was paid, what was denied, what was adjusted, what the patient owes — into actionable financial data inside your billing system.
That translation step is where most practices either catch revenue leakage early or let it compound silently for months.
In this guide, we’ll explore:
- Where payment posting connects to denial management & underpayment recovery
- The difference between ERA, EOB, and EFT (and why they’re not the same thing)
- How the payment posting workflow moves from remittance to reconciliation
- How manual and electronic posting compare in accuracy and speed
- Which KPIs signal whether your posting process is working
TLDR: What payment posting actually controls in your revenue cycle
Payment posting is not data entry. It is the earliest point in the revenue cycle where underpayments, denials, and contract violations become visible — or stay hidden.
- ERA (Electronic Remittance Advice) explains what was paid and why; EFT (Electronic Funds Transfer) moves the money — they are complementary transactions, not the same thing
- Healthcare electronic claim payments reached 510 million ACH transactions in 2024, a 2,556% increase since 2013 (Nacha, February 2025)
- CMS confirms that ERA transactions allow automatic posting to billing systems, eliminating the time and cost of manual remittance entry
- Payment posting is where underpayments surface — a claim paid at $95 against a contracted rate of $120 only becomes recoverable when someone (or something) catches the $25 gap during posting
- The 2024 Change Healthcare cyberattack disrupted ERA delivery across the industry, with billing teams reporting manual posting of over $3 million in payments when electronic workflows went down
How does the payment posting process work step by step?
Payment posting sits after claim adjudication and before denial management in the revenue cycle. It is the point where a payer’s decision becomes a financial record in your system.
Receive the remittance
After a payer adjudicates a claim, it sends payment information through one of three channels:
ERA
Electronic Remittance Advice (ERA) is the HIPAA-standard X12 835 electronic transaction containing line-level payment, adjustment, and denial details.
EOB
Explanation of Benefits (EOB) is a paper or PDF document presenting the same payment and claim information in a format designed for people to read.
Paper Check
A paper check is typically mailed with a paper remittance advice that explains the associated payment and adjustments.
ERA and EFT arrive separately. The ERA explains the payment; the EFT delivers the money. Matching them is a core reconciliation task.
Verify and post payments
Each payment line is matched against the corresponding claim. The posting records:
- Amount paid by the insurer
- Any secondary payer information
- Denial codes (using standardized CARCs and RARCs)
- Patient responsibility (deductible, copay, coinsurance)
- Contractual adjustments (the difference between billed charges and the payer’s allowed amount)
Identify exceptions
During posting, the team flags:
- Partial payments (potential underpayments)
- Zero-pay claims (denials requiring follow-up)
- Incorrect adjustment codes (possible contract violations)
- Missing claims (submitted but not appearing on the remittance)
Reconcile
Reconciliation matches three data sources:
- Bank deposits (actual money received)
- ERA/EOB data (what the payer says it paid)
- Practice management system (what’s recorded in the billing software)
When all three align, the posting cycle is clean. When they don’t, the difference is either a posting error, a payer error, or a missing transaction.
Route exceptions to denial management
Claims flagged during posting move into the denial management workflow — appeals, corrected claims, or payer follow-up depending on the denial reason.
What is the difference between ERA, EOB, and EFT?
These three terms get used interchangeably in many billing guides, but they represent different things. Confusing them creates reconciliation problems.
| Term | What it is | What it does | Format |
| ERA (Electronic Remittance Advice) | Payment explanation from payer | Explains what was paid, adjusted, denied, and why | HIPAA X12 835 electronic file |
| EOB (Explanation of Benefits) | Same explanation, different format | Same information as ERA but in paper or PDF | Human-readable document |
| EFT (Electronic Funds Transfer) | Actual money transfer | Moves payment from payer’s bank to provider’s bank | ACH bank transaction |
The relationship is simple — ERA tells you what happened; EFT delivers the payment. They arrive through different systems and must be matched manually or through automated reconciliation tools.
CMS confirms that ERA transactions contain standardized CARCs (Claim Adjustment Reason Codes) and RARCs (Remittance Advice Remark Codes) specifically designed to explain why adjustments occurred.
POSTING EXAMPLE
How a Single Claim Gets Posted
Billed charge
$250
Insurance paid
$140
Contractual adjustment
$70
Patient coinsurance
$40
All four components are posted separately. The insurance payment and contractual adjustment close the payer portion. The $40 coinsurance becomes a patient balance for collection.
How does manual posting compare to electronic posting?
The shift from manual to electronic posting has accelerated dramatically. Nacha reported that healthcare ACH claim payments reached 510 million transactions in 2024 — a 2,556% increase from 2013.
| Factor | Manual posting | Electronic posting |
| Data source | Paper EOBs, checks | ERA files (X12 835) |
| Entry method | Human data entry | Automated import |
| Speed | Slow — limited by staff capacity | Fast — batch processing |
| Error rate | Higher (transcription, misallocation) | Lower (but configuration errors can occur) |
| Scalability | Limited | Strong |
| Best for | Low-volume practices, paper-only payers | Most modern practices |
Electronic posting is not error-proof.
Misconfigured auto-posting rules, incorrect ERA-to-claim matching, and outdated fee schedule mappings can create systematic errors that repeat across hundreds of claims.
The advantage of automation is speed and consistency — the risk is that a configuration mistake scales just as fast.
The 2024 Change Healthcare cyberattack demonstrated this dependency.
When ERA delivery was disrupted, billing teams across the country were forced to manually post payments from paper remittances — with one professional reporting manual posting of over $3 million in payments during the outage.
How does payment posting connect to denial management?
Payment posting is the first place denials become visible in your billing system.
A zero-pay line on an ERA, a CARC code indicating “non-covered service,” or a partial payment below the contracted rate — these all surface during posting.
The connection works in both directions:
Posting Identifies Denials
During payment posting, CARCs and RARCs identify why a claim was adjusted or denied, allowing the claim to be routed to the appropriate follow-up or denial management queue.
Denial Patterns Improve Automation
Recurring payer behaviors—such as consistently underpaying a specific CPT code—can be incorporated into payment posting workflows or auto-posting rules so similar claims are automatically flagged for review.
Practices that separate payment posting from denial management into isolated departments often miss the feedback loop.
The posting team sees the first signal; the denial team needs that signal to act. When those two functions don’t communicate, underpayments age into uncollectable write-offs.
Which KPIs should you track for payment posting?
Most practices measure denial rates and days in AR but overlook posting-specific metrics that reveal operational problems earlier.
| KPI | What it measures | Target |
| Posting accuracy rate | Percentage of payments posted correctly on first attempt | 98%+ |
| Payment lag days | Time between payment receipt and posting | Under 2 business days |
| Unposted cash | Payments received but not yet applied to claims | Under 1% of weekly receipts |
| ERA auto-post rate | Percentage of ERA lines posted without manual intervention | 80%+ |
| Underpayment detection rate | Percentage of below-contract payments identified during posting | Track monthly |
| Reconciliation variance | Difference between bank deposits and posted amounts | Zero (investigate any gap) |
Tracking these monthly exposes trends that broader RCM metrics miss. A rising payment lag, for example, often signals a staffing bottleneck — not a payer problem.
Stop letting payments sit unposted while revenue leaks
Payment posting errors compound silently — every unmatched ERA, every uncaught underpayment, and every unreconciled deposit is revenue that gets harder to recover with each passing week.
MedHeave operates as a full revenue cycle department, managing payment posting alongside denial management, AR follow-up, and financial reporting.
Dedicated Payment Posting Team
Specialists trained in ERA processing, CARC/RARC interpretation, and payer-specific adjustment rules ensure accurate payment posting.
Automated + Manual Workflows
Combines automated payment posting with manual verification and daily reconciliation to maintain financial accuracy.
Underpayment Detection
Identifies underpayments by comparing reimbursements against loaded payer fee schedules and contract terms.
Performance-Based Pricing
MedHeave only gets paid when your practice gets paid, aligning incentives with your revenue goals.
Proven Revenue Cycle Performance
Practices benefit from strong financial performance backed by disciplined payment posting, reconciliation, and denial management.
Contact MedHeave to discuss how structured payment posting and reconciliation can close the revenue gaps your current process is missing.
Frequently asked questions
Here are the questions billing teams and practice managers ask most about payment posting.
ERA (Electronic Remittance Advice) and EOB (Explanation of Benefits) contain the same information — what was paid, denied, adjusted, and what the patient owes. The difference is format. ERA is an electronic file (HIPAA X12 835) designed for automated import into billing systems. EOB is a paper or PDF document that requires manual reading and data entry. Most modern practices prioritize ERA enrollment with payers to reduce manual posting workload.
Payment posting doesn’t directly reduce denials, but it is the earliest detection point. When posting staff identify denial patterns — a specific payer consistently denying a particular code, or a recurring adjustment that shouldn’t apply — that intelligence feeds back into claim submission and coding workflows. Practices that treat posting as an isolated data-entry task miss this feedback loop and end up appealing the same denials repeatedly.
Reconciliation is the process of matching posted payments against bank deposits and remittance data to confirm that financial records are accurate. A clean reconciliation means the amount deposited in the bank matches what the ERA says was paid, which matches what the billing system shows as posted. Discrepancies may indicate posting errors, missing ERA files, unmatched EFT transactions, or payer payment issues that need investigation.
Outsourcing payment posting can make sense for practices dealing with high claim volume, staffing shortages, or reconciliation backlogs. The key question is whether your current team can post payments within two business days of receipt, catch underpayments consistently, and reconcile deposits daily. If any of those are falling behind, outsourcing the function to a team with ERA processing infrastructure and payer-specific posting rules often recovers more revenue than it costs.
The 2024 Change Healthcare cyberattack disrupted ERA delivery for healthcare organizations across the country. Without electronic remittance files, billing teams had to manually post payments using paper EOBs and check stubs. Revenue-cycle professionals reported posting millions of dollars manually, dealing with delayed reconciliation, and managing increased payment research workloads. The incident highlighted how dependent modern billing operations have become on automated ERA and EFT infrastructure.
