If your billing team sees an ERA in a work queue, it is looking at payment information—not the money itself. ERA stands for Electronic Remittance Advice: the payer’s electronic explanation of how it processed a claim. EFT, by contrast, is the transfer of funds to the practice’s bank account. An EOB is typically the member-facing explanation of benefits and what the patient may owe.
The distinction matters because receiving an ERA does not finish the billing workflow. Your team still needs to match the remittance to the deposit, post payment and adjustments, update patient or secondary balances, and reconcile the result to accounts receivable.
What is an ERA in medical billing?
An ERA is an electronic record that communicates how a health plan adjudicated a claim. It can show what the payer allowed, paid, adjusted, denied, or assigned to patient responsibility. In the standard electronic workflow, the ERA is commonly associated with the X12 835 Health Care Claim Payment/Advice transaction. CMS and X12 describe the 835 as a way for a payer to send payment and remittance detail to a provider.
In plain language, the ERA answers: “What did the payer do with this claim, and how should the result be applied?” It is a remittance record, not a bank statement and not automatically a patient bill.
ERA vs. EOB vs. EFT: what is the difference?
ERA, EOB, and EFT may appear in the same payment workflow, but they serve different jobs. Payers and software vendors do not always use the terms identically, so treat the table as a practical operating map rather than a substitute for a specific payer’s instructions.
How ERA, EOB, and EFT fit into the billing workflow
The cleanest way to avoid confusion is to follow the claim from adjudication through reconciliation. A remittance is complete only when the information, money, balances, and follow-up work agree.
- The payer adjudicates the claim. The plan determines allowed, paid, adjusted, denied, and patient-responsibility amounts.
- The ERA arrives. The electronic remittance provides the detail needed to understand and apply the payer’s decision.
- The EFT arrives. Funds move to the practice bank account. The EFT and ERA may arrive in different formats or at different times.
- The team reassociates the records. Use the payer’s trace or reference information to match the deposit to the remittance. CMS describes this connection as important for reconciliation and accounts-receivable posting.
- The team posts and updates balances. Apply payment and adjustments to the claim, check secondary coverage, update patient responsibility, and route denials or exceptions.
- The team reconciles the result. The bank activity, remittance detail, and accounts receivable should agree—or a named owner should have the next action.
The key operational distinction is between initiated and completed work. Receiving the ERA initiates review. Receiving the EFT confirms that funds moved. Posting, balance updates, and reconciliation complete the workflow.
What should a biller review on an ERA?
Once the ERA is available, review the details that determine what gets posted and what still needs work. Do not assume that a file’s arrival means every line is ready to close.
- Payment identifiers: Confirm the payer, provider, payment date, trace/reference information, and the batch or deposit the remittance belongs to.
- Claim and service lines: Review billed, allowed, paid, adjusted, denied, and patient-responsibility amounts at the level needed for accurate posting and review.
- Adjustment and remark codes: Use the payer or clearinghouse guidance when an adjustment or denial code needs interpretation. A code is a prompt for the next action, not a complete explanation by itself.
- Secondary and patient balances: Check whether another payer should be billed and whether the patient balance is supported before sending a statement or requesting payment.
- Exceptions: Flag missing, duplicate, unmatched, unexpected, or incomplete transactions with an owner and a follow-up date.
A simple claim example
Consider an illustrative claim line with $200 billed. The payer’s remittance says $150 was allowed, $120 was paid, and $30 was adjusted under the payer’s contract, leaving $0 patient responsibility for that line. The ERA gives the billing team the detail needed to apply the $120 payment and $30 adjustment. The related EFT may arrive as part of a larger deposit that includes other claims, so its total will not necessarily equal the single claim line.
The EOB may explain the same adjudication to the member in a different presentation. The team still needs to match the EFT and ERA, post the line, confirm whether secondary coverage applies, and reconcile the full deposit. The numbers above are illustrative; actual payer terminology, adjustments, and responsibility amounts vary.
What if the ERA and EFT do not match?
Do not force-post an amount simply because a deposit appeared. First check whether the ERA and EFT are on different delivery schedules, whether the deposit is a batch containing multiple claims, and whether the payer’s trace or reference information matches. Then check the payer or clearinghouse status for a delayed, corrected, duplicated, or missing remittance.
If the records still do not agree, hold the exception with a named owner and follow-up date. Document what was checked and what will happen next. An unmatched amount should not quietly become a patient balance or an unexplained adjustment. The goal is a bank record, remittance record, and accounts-receivable record that tell the same story.
How to make ownership clear
A simple ownership map keeps the workflow from stopping between teams. Assign one person or queue to receive and triage new ERA files, another checkpoint for matching deposits, and a defined posting owner for payments and adjustments. Give secondary-coverage and patient-responsibility questions a clear reviewer before a statement goes out. Route denials, missing remits, duplicates, and unmatched EFTs to a queue with a due date and escalation path. This separates communication from consent and collection from verification: a patient can be contacted only after the balance is supported by the posting workflow.
For an office manager, the useful status is not simply “ERA received.” It is “matched,” “posted,” “balance reviewed,” or “exception assigned.” Those labels make handoffs visible and give the team a shared definition of what still needs attention.
Before the ERA arrives: enrollment and delivery
ERA enrollment is the setup step that tells a payer or clearinghouse where and how the practice wants remittance information delivered. It is not the same as proving that a usable remittance was received and matched to a deposit. Enrollment, routing, notifications, and delivery rules can vary by payer, clearinghouse, provider identifier, or account configuration. Confirm the practice’s current instructions, identifiers, and delivery destination, then monitor for the first successful ERA/EFT pair.
If a remittance is missing, duplicated, or routed to the wrong place, treat that as a workflow exception to investigate—not as evidence that the claim was never paid.
Common ERA and payment-posting mistakes
Most ERA problems are handoff problems. The team has information, money, or a balance—but not a shared record of what happened next.
- Treating the ERA as the deposit. The ERA explains the payer’s processing; the EFT is the money movement.
- Treating the EOB as interchangeable with provider remittance detail. The EOB is usually the member-facing explanation, while the billing team needs the provider-side detail used for posting.
- Posting before matching and reconciling. A payment can appear in a bank account without every line or adjustment being correctly applied.
- Billing the patient too early. Patient responsibility should be checked against adjustments, secondary coverage, and the practice’s posting policy.
- Assuming payer workflows are identical. Enrollment, delivery, timing, and terminology can differ by payer or clearinghouse; confirm the workflow when an exception appears.
Related resource: Top Billing Mistakes That Cost Clinics Time & Money
Where practice management software fits
Practice management software is most useful when it keeps the operational work connected after the payer’s response arrives. That can include the patient record, payment activity, invoices, receipts, and follow-up on discrepancies or disputes.
PracticeQ Payments supports patient payments, invoice management, receipt delivery, and payment-dispute workflows inside the practice management system. Those capabilities can support the patient-payment side of the process after the billing team has interpreted and reconciled the remittance. They should not be confused with a claim that the system imports every payer’s ERA or automatically resolves every posting exception.
