What ERA posting actually does
An electronic remittance advice, or ERA, carries a health plan's claim-payment details in the standard X12 835 transaction. A practice-management system can use that structured data to match payments and adjustments to claims, service lines and patient accounts instead of requiring staff to key every amount from paper.
The ERA explains the payment or other adjudication result; it is not the funds themselves. When payment is made by ACH electronic funds transfer (EFT), the EFT and ERA generally travel separately and are reassociated using matching trace data. That distinction is the starting point for accurate posting and is covered in more detail in our EOB vs. ERA guide.
A practical ERA posting workflow
- Identify the remit and deposit. Capture the payer, payment date, X12 EFT reassociation trace number, total payment and the claims included in the ERA.
- Match claims and service lines. Confirm that each payment, adjustment and patient-responsibility amount lands on the intended account and date of service.
- Classify every adjustment. Read the Claim Adjustment Group Code with each CARC and applicable RARC, and also review claim status and provider-level adjustment information, to distinguish contractual obligations, patient responsibility, denials, reversals and other exceptions.
- Route exceptions. Move denied, underpaid, unmatched or reversed items into a work queue rather than forcing them through as ordinary payments.
- Reconcile the batch. Tie the ERA total to the related EFT deposit and confirm that posted payments, claim and service adjustments, and any provider-level adjustments account for the remit.
How to read the 835 without losing the business meaning
The 835 is structured for systems, but the posting team still needs to understand what its codes mean. Claim adjustment reason codes explain why an amount differs from the billed charge. Remittance advice remark codes add context. Group codes assign broad financial responsibility.
Those codes and the surrounding 835 data should guide the next action; suspected underpayments must be tested against the payer contract or expected allowed amount. A contractual adjustment may be posted according to the payer agreement. A patient-responsibility amount can move to the patient ledger after coverage, posting and applicable billing rules are checked. A denial or suspected underpayment belongs in follow-up. Treating every adjustment as a write-off hides recoverable revenue and distorts reporting.
ERA-to-EFT reconciliation, step by step
Reconciliation proves that the remittance record and the cash deposit agree. Match each ERA to its corresponding EFT using the X12 reassociation trace number, then confirm the amount, payer and effective date. One ERA/EFT pair can cover many claims; a bank or portal may display transactions in a grouped view, so preserve the transaction-level trace data.
When the totals do not tie, hold the batch open and investigate. Common causes include a missing ERA, a grouped bank or portal display, a reversal or takeback, a provider-level recoupment, a duplicate posting, or an item posted to the wrong account. The goal is not to make the screen balance by adding an unexplained adjustment; it is to identify the reason for the difference.
The exception queues that keep A/R accurate
Auto-posting should produce work, not erase it. Keep separate queues for unmatched claims, denials, underpayments, reversals and takebacks, secondary-billing needs, and patient-responsibility exceptions. Assign an owner and resolution status to each queue so the issue cannot disappear inside a completed batch.
This is where posting connects to denial management and A/R follow-up. The remit supplies the reason; the follow-up workflow determines whether the practice corrects, appeals, rebills, transfers or closes the balance.
Controls worth checking before month-end
- Every EFT deposit has supporting remittance detail, and every paid ERA is matched to cash.
- ERA totals agree with the posted batch after claim, service and provider-level adjustments, with any difference documented and resolved.
- Denials and underpayments are routed to follow-up rather than posted as unexplained write-offs.
- Patient responsibility moves only after payer processing and account posting are verified.
- Reversals, recoupments and takebacks remain visible in reporting.
- Unmatched and suspense items are reviewed on a defined cadence.
Synergy sets up ERA/EFT workflows, posts payments with a published 99% accuracy target, reconciles remittances and works denials within 48 hours. If your deposits, remits and patient balances do not consistently tie, request a free practice audit. There is no long-term contract.
Frequently asked questions
What is ERA posting in medical billing?
ERA posting is the process of importing or entering the payment, adjustment, denial and patient-responsibility details from an electronic remittance advice into the provider's billing system. The ERA uses the X12 835 transaction, which lets software match structured remittance data to claims and service lines.
How do you reconcile an ERA to an EFT?
Match the ERA's X12 reassociation trace number and payment amount to the corresponding EFT, then confirm the included claims and service lines posted correctly and investigate any difference before closing the batch. One ERA/EFT pair may cover many claims.