Payment posting is where the payer’s explanation becomes operational truth. In practice, speed matters, but an auto-posted batch is not finished until the deposit, adjustment, patient responsibility and follow-up queue agree. This is the control sequence we use with practices.
Match the remittance to the deposit
Confirm payer, trace number, service date range and total deposit before posting. Keep a reconciliation note for any difference between the ERA, bank activity and batch total.
Post line-level outcomes
Apply allowed amount, paid amount, contractual adjustment, denial code and patient responsibility at the service line. Never bury a partial payment inside a generic adjustment.
Separate true balances from work queues
Route underpayments, missing lines, recoupments and coordination-of-benefits issues to owners. Patient balances should be sent only after insurance responsibility is resolved.
Close the loop with A/R aging
Use posting results to refresh payer, provider and age-bucket reporting. Pair this workflow with our A/R aging guide to prioritize the next action.
Frequently asked questions
How quickly should ERAs be posted?
Set a service-level target that protects follow-up time, then monitor unposted days and exceptions rather than chasing a single speed number.
What is a posting quality check?
Sample batches for deposit reconciliation, correct adjustments, complete denial codes and accurate patient responsibility before statements are released.