What should a payment posting workflow include?
A solid payment posting workflow covers ERA and EOB intake, accurate posting of payments and contractual adjustments, flags for underpayments and denials buried in remits, daily or near-daily reconciliation to bank/deposit, and reporting on posting lag. Multi-client billing teams also need client-specific posting rules and a clear escalation path when remit data does not match expected allowed amounts.
Why posting is a control function, not just data entry
Payment posting is where cash meets the claim. Done well, it keeps AR truthful and surfaces payer underpayments early. Done poorly, it creates phantom AR, delayed denial work, and client reporting that cannot be trusted. For billing companies running many practices, posting discipline is a delivery differentiator.
- Unposted payments inflate Days in AR and hide true collection speed
- Misapplied adjustments distort net collection rate by client
- Skipped underpayment review leaves money on the table
- Weak reconciliation creates deposit mismatches that take days to unwind
End-to-end payment posting process
The steps below are the minimum viable workflow for a multi-client team. Client-specific SOPs sit on top — payer rules, adjustment codes, and who can write off balance.
- 01
Intake remits
Pull ERAs from clearinghouses and payer portals; log paper EOBs and correspondence with deposit date and client tag.
- 02
Match to claims
Auto-post where the PM/EHR supports clean ERA matching; queue exceptions for patient, claim, or line mismatches.
- 03
Post payments and adjustments
Apply payment, contractual adjustment, and patient responsibility per client SOP — never invent codes to force a balance to zero.
- 04
Flag underpayments and denials
Route short pays, unexpected denial codes, and zero-pays into underpayment or denial queues with remit evidence attached.
- 05
Reconcile to deposit
Tie posted totals to bank deposits or lockbox reports by client and date; clear variances the same day when possible.
- 06
Report and hand off
Close the posting batch, report lag and exception volume, and hand underpayment/denial items to the follow-up team.
ERA, EOB, and exception handling
Electronic remits should carry most of the volume; paper and portal EOBs still show up for secondary payers, workers’ comp, and edge cases. The control is not "everything auto-posts" — it is that exceptions have a defined owner and SLA.
ERA auto-post with exception queue
Let the system post clean matches; require human review for unmatched claims, partial lines, and remits with unusual CARCs/RARCs.
Manual EOB posting rules
Document how to handle scanned EOBs, secondary remits, and takebacks so every poster applies the same logic per client.
Denial codes inside remits
A paid remit can still contain denied lines. Capture those into denial management instead of treating the whole remit as done.
Client-specific adjustment maps
Multi-client teams need a map of allowed adjustment codes and write-off authorities so one client's rules do not leak into another's ledger.
Underpayment flags and reconciliation controls
Two controls separate a posting desk from a cash-application factory: systematic underpayment review and deposit reconciliation. Neither requires fancy software — they require a checklist and ownership.
- Compare paid amount to expected allowed (fee schedule or historical allowed) before closing the claim
- Queue material variances for underpayment review with remit reason codes attached
- Reconcile posted cash to bank/lockbox by client and deposit date; age open variances
- Separate takebacks and recoupments so they do not silently erase prior payments
- Require dual review or lead sign-off for large write-offs and manual balance-outs
- Keep an audit trail of who posted what, when, and under which client SOP
Payment posting KPIs to baseline, track, and report
Use these metrics against your own starting point and client mix. We recommend baselining, tracking, and reporting them weekly — not chasing a universal target number, because payer mix, volume, and system automation change what "good" looks like.
Payment posting lag
Time from payment/remit receipt (or deposit date) to fully posted claim. Rising lag means AR and cash reports are stale.
Same-day / next-day post rate
Share of remits posted within your SLA window. Useful for multi-client desks with deposit-driven client reporting.
Exception rate
Share of remits or lines that fail auto-post and need manual work. High rates point to enrollment, mapping, or data-quality issues.
Unreconciled deposit aging
Dollar amount and age of deposits not yet tied to posted remits. This is a control metric, not a vanity KPI.
Underpayment queue volume
Count and dollars flagged for underpayment review. Tracks whether posters are catching short pays, not just clearing the inbox.
Posting accuracy (sample QA)
Percent of audited posts with correct payment, adjustment, and patient responsibility. Sample QA catches systematic mistakes early.
How Salt HealthOps supports posting capacity
Salt HealthOps can add co-managed payment posting capacity for billing companies and RCM teams — working inside your systems, following your client SOPs, with US-based accountability, HIPAA-aware workflows, BAA-ready contracting, ISO-certified parent practices, and SOC 2 in progress. We help you baseline, track, and report posting lag and related controls; we do not guarantee specific posting-speed or collection outcomes.
Payment Posting Services
ERA/EOB posting capacity with reconciliation discipline.
Learn moreBilling Company Support
Multi-client back-office capacity under your brand.
Learn moreRCM KPIs That Matter
How posting lag connects to Days in AR and collection.
Learn moreRelated reading
Frequently asked questions
What is payment posting lag?
Payment posting lag is the time between receiving a payment or remit (often measured from deposit or ERA receipt date) and completing the post to the claim. Longer lag makes AR look older than it is and delays underpayment and denial work that depends on accurate balances.
Should every underpayment go to a specialist?
Not every variance — material ones should. Define thresholds and reason codes so posters flag short pays that look wrong versus routine contractual adjustments. The underpayment queue then belongs to AR or a dedicated review role with remit evidence attached.
How often should multi-client teams reconcile deposits?
Daily or next-business-day reconciliation is the practical standard when client cash reporting depends on posting. Aging unreconciled deposits by client makes ownership clear and stops variances from stacking into month-end fire drills.
Can posting be co-managed without losing control?
Yes, if the partner works in your PM/EHR under least-privilege access, follows your client SOPs, and reports posting lag, exception volume, and QA samples on a fixed cadence. You keep write-off authority, client communication, and admin control of systems.