ERA/EOB Reconciliation SOP: Matching Payments, Adjustments, and Deposits

ERA/EOB Reconciliation SOP: Matching Payments, Adjustments, and Deposits

ERA/EOB reconciliation is the weekly discipline that makes three records agree: the remittance explanation (ERA/EOB), what your system posted, and what your bank received. When that loop stays tight, a clinic can catch posting gaps, missing ERAs, misallocated adjustments, and deposit mismatches before they turn into noisy A/R.

Reconciliation does not need to be “accounting-heavy.” Instead, it works best as a short, repeatable set of checks with a controlled exception queue.

This SOP is written for outpatient clinics broadly, while using chiropractic-forward operational examples that still translate to PT and behavioral health.

Definitions and scope

What an ERA is

CMS defines an electronic remittance advice (ERA) as an explanation from a health plan to a provider about a claim payment, including how the plan adjusted charges based on factors such as contract agreements, benefit coverage, secondary payers, and expected cost-sharing. See References.

ERA versus EFT deposit

An ERA explains adjudication. However, the bank deposit is a separate event. Therefore, reconciliation must confirm that the EFT deposit (or deposits) aligns to the corresponding ERA amount(s) for the same payment cycle.

Why remittance codes matter

Remittance advice uses standardized codes to explain adjustments. For example, X12 describes Remittance Advice Remark Codes (RARCs) as additional explanation for an adjustment already described by a Claim Adjustment Reason Code (CARC). In addition, CMS provides guidance and manuals that address remittance advice structure and code usage in Medicare remittance processing. See References.

Cadence, roles, and inputs

Recommended cadence

Run this SOP weekly. Weekly timing keeps exceptions small and supports timely correction and follow-up.

Roles

• Billing lead: owns the weekly reconciliation, assigns exceptions, and confirms closure.
• Posting specialist (or cross-trained staff): posts ERAs consistently and flags anything that cannot post cleanly.
• Owner/office manager: reviews the weekly exception summary and approves escalations when needed.

Inputs you need each week

• ERA files or ERA reports for the period (by payer or by batch)
• Posting summary from your billing system (payments, adjustments, and patient responsibility posted)
• Bank activity for EFT deposits (date, amount, and trace/reference details when available)
• Exception tracker with fixed fields (payer, ERA date, deposit date, amount, issue category, owner, due date)

Step-by-step ERA/EOB reconciliation SOP

Step 1: Confirm ERA receipt and completeness

First, list the ERAs you expected to receive for the week and compare that list to what arrived. Then confirm each file is complete enough for posting and for deposit matching.

Next, if your workflow uses EFT/ERA reassociation, confirm that the remittance includes the identifiers your team relies on for matching. CMS also explains that operating rules for EFT and ERA became mandatory on January 1, 2014 and points to CAQH CORE as the source for the published operating rules. See References.

Step 2: Lock the posting window

Before you match totals, lock the posting window. In practice, that means you reconcile ERAs dated in a defined weekly range (or deposits received in a defined weekly range) and you avoid changing postings during the match step.

Consequently, when a late ERA arrives, route it to a “late receipt” bucket and reconcile it in the next cycle.

Step 3: Match ERA payment totals to posted payments

Now match the ERA-reported payment totals to what was posted in your system for the same ERA batch. Do this in two layers:

• Batch level: total paid on the ERA equals total payments posted for that ERA batch.
• Claim level (spot check): a small sample of claims matches line-by-line posted amounts.

If the batch totals do not match, isolate the cause before you chase claim detail. Common causes include an unposted line, a duplicated posting, or a posting rule that misroutes dollars to the wrong bucket.

Step 4: Validate adjustments and responsibility allocation

Reconciliation is not only about payment dollars. Adjustments can distort A/R when they post to the wrong category. Therefore, confirm that contractual adjustments and patient responsibility post consistently and in alignment with how the remittance explains the change.

CMS’s remittance advice guidance and the Medicare Claims Processing Manual (Chapter 22) describe remittance advice structure and code usage for Medicare processing. Meanwhile, X12 describes how RARCs provide detail to support CARC-based adjustment explanations. See References.

Operationally, this check prevents two high-friction problems: patient balances inflating because a contractual adjustment was not posted as contractual, and A/R shrinking incorrectly because patient responsibility was posted as a write-off category.

Step 5: Reassociate ERA batch totals to EFT deposits

Next, match ERA batch totals to bank deposits. Two patterns show up frequently:

• One-to-one: one ERA aligns to one EFT deposit.
• Many-to-one: multiple ERAs roll into a single deposit, often based on payer cycles or payment processors.

Start by grouping deposits by payer when possible. Then match by amount and date window. If trace numbers are available in your bank record and in your remittance workflow, use them as supporting evidence for the match.

Because EFT/ERA operating rules exist to improve consistency of these transactions, keep a note of which payers still bundle deposits in ways that complicate matching. CAQH CORE maintains operating rules and publishes updates and compliance dates for rule sets. See References.

Step 6: Create a strict exception queue

When anything fails to match, log it immediately into an exception queue. Use fixed categories so you can trend root causes across weeks:

• Missing ERA: expected remittance not received
• Posting mismatch: ERA totals do not equal posted totals
• Deposit mismatch: EFT deposit does not match ERA grouping
• Adjustment allocation issue: contractual vs patient responsibility posted incorrectly
• Format/import issue: ERA cannot be imported or parsed cleanly

Then assign one owner and one due date per exception. That structure keeps the reconciliation stable while the team resolves issues without reopening the entire week’s match.

Step 7: Close the loop with a weekly summary

Finally, produce a short weekly summary:

• Total ERAs received and reconciled
• Total payments reconciled and total adjustments reviewed
• Number of exceptions opened and closed
• Top exception categories for the week

Because the summary is short, an owner or office manager can review it quickly while still enforcing accountability.

Common failure points and fixes

Deposits bundle unpredictably

If deposits do not map cleanly to a single ERA, document a consistent internal grouping rule (payer + week window) and keep “unmatched deposits” in a dedicated queue until reassociation is supported by deposit details and remittance evidence.

Posting rules change mid-cycle

When posting rules change mid-cycle, reconciliation becomes unstable. Instead, log rule changes and apply them at week boundaries when possible, so each reconciliation cycle reflects one ruleset.

Adjustments inflate patient balances

If contractual adjustments post incorrectly, patient balances can appear larger than they should be. Correct the posting rule at the source, and then run a controlled correction process for affected claims rather than ad hoc edits.

Specialty notes: chiropractic-first, still inclusive

• Chiropractic: add a spot check for recurring cost-sharing patterns and verify that responsibility allocation stays consistent across similar visits, so patient statements remain predictable.
• Physical therapy: keep authorization-related reductions separate from posting mismatches, so the reconciliation queue does not become an authorization queue.
• Behavioral health: monitor place-of-service and modality-related adjustment patterns closely, because small coding differences can shift responsibility allocation.

Conclusion

A weekly ERA/EOB reconciliation SOP protects revenue integrity by ensuring the remittance record, the posting record, and the bank deposit agree. When you confirm receipt, match totals, validate adjustment allocation, and manage a strict exception queue, your clinic reduces rework while improving confidence in A/R and patient balances.

References

• CMS: Health Care Payment & Remittance Advice and Electronic Funds Transfer (What is an ERA?)
• CMS: Health Care Payment and Remittance Advice (remittance advice resources)
• CMS: Operating Rules for EFT and Remittance Advice (mandatory date and rule source)
• CAQH CORE: Operating Rules (rule sets and compliance dates)
• CMS: Medicare Claims Processing Manual, Chapter 22 (Remittance Advice)
• X12: Remittance Advice Remark Codes (RARC definition and usage)
• X12: 835 Health Care Claim Payment/Advice (005010X221 reference)