Why Your ERA and Bank Deposit Don't Match & and What Specialty Clinics Should Do About It

Your ERA shows $12,400 paid by a payer on Tuesday. Your bank statement shows $11,847 landing on Thursday. You are $553 short and have no obvious reason why.

Most billing teams recognize this pattern before they can name it: the ERA says one number, the bank shows another, and the difference sits in the aging report waiting for someone to explain it. It does not show up in denial reports. It is not a coding error or a missing authorization. It is just a dollar figure that does not reconcile — and at specialty practices billing high-cost drug regimens, the gap tends to be larger and harder to trace than at general practices.

This piece covers why that gap exists, which payer patterns produce it most often, and how to build a reconciliation workflow that catches it before it ages into a reporting problem.

Where the gap comes from

ERA-to-bank discrepancies fall into one of three categories. Each one requires a different diagnosis.

1. PLB adjustments offset the deposit amount

Provider Level Balance (PLB) adjustments are payer-initiated financial entries that appear in the ERA but apply at the practice level, not the claim level. Common PLB reasons include recoupments (prior-period overpayment recoveries), interest, capitation, and forward-balance offsets. When a payer issues a recoupment via PLB, they reduce the current EFT deposit by the recoupment amount. Your ERA for this week's claims might correctly show $12,400 in paid claims, but the EFT deposit reflects $11,847 because the payer pulled back $553 from a prior-period overpayment. Without pulling the PLB segments in the 835, you would never know why.

2. Multiple ERAs roll into a single bundled deposit

Payers often process claims across multiple dates and batch the EFT payments into a single bank deposit. A single Tuesday deposit of $18,200 might represent four separate ERA batches from the same payer spanning a two-week window. On the ERA side, those four batches each have their own 835 file. On the bank side, you have one lump-sum deposit. Mapping four ERA totals to a single deposit requires trace numbers (the TRN segment in the 835) and matching ACH reference numbers from your bank. Most practice management systems do not handle this automatically.

3. Third-party administrators route deposits separately from the ERA originator

For commercial payers that delegate claims administration to a TPA — Carelon, MultiPlan, Evicore — the ERA might come from the TPA while the EFT deposit arrives from the health plan itself. The amounts match in theory, but the timing and sender identifiers do not align. The ERA file arrived Monday from one entity. The EFT deposit arrived Thursday from a different entity. Your system cannot link them.

Why specialty clinics see more of this

A general family practice billing mostly E/M codes tends to see clean ERA-to-bank matching. Each payer issues a weekly or biweekly EFT, the ERA matches within a day or two, and the PLB column is small or empty.

Specialty clinics billing GLP-1 medications, TMS therapy, Spravato, or high-cost injectables face a different situation structurally.

GLP-1 practices:

Semaglutide and tirzepatide prescriptions span medical and pharmacy benefit pathways depending on the patient's plan. When the same payer pays the medical portion via one EFT and the pharmacy portion via a separate pharmacy network EFT, your bank receives two deposits that your billing system may attribute to a single ERA. Practices billing GLP-1 compounds frequently see deposit totals that look low because pharmacy benefit payments land under a different TPA identifier.

Beyond the dual-benefit issue: GLP-1 payers including UnitedHealthcare, Aetna, and several BCBS plans issued large-scale PLB recoupments in 2025 and 2026 related to compounded GLP-1 claims. [VERIFY BEFORE PUBLISHING — confirm payer names against platform data.] These recoupments show up in PLB segments and reduce current EFT deposits with no claim-level detail. A practice reconciling at the claim level will not catch them until the PLB data is pulled separately.

TMS practices:

TMS billing changed in early 2026 when Cigna removed the prior authorization requirement for TMS. The coverage change triggered a wave of retroactive adjustments as Cigna reprocessed previously denied claims. These retroactive payments often land as unscheduled EFT deposits from Carelon (Cigna's behavioral health TPA) that do not match any current-period ERA. Reconciling them requires matching retroactive payment dates to original claim dates. [VERIFY — confirm this pattern matches what Foresight has seen with TMS clients.]

Spravato practices:

Spravato billing produces reconciliation complexity from its REMS-restricted dispensing model. Janssen's HUB dispenses the medication to REMS-certified facilities, which means the pharmacy benefit payment for the drug often arrives separately from the professional/administration fee payment. On a single treatment date, a Spravato practice may have two separate payer flows: the professional service adjudicated through the medical benefit, and the drug cost adjudicated through the pharmacy benefit and paid by the PBM. Both flow through different ERA identifiers. The medical ERA may arrive on day T+2 while the pharmacy benefit remittance may come days later or not at all for that period.

The reconciliation workflow that actually works

Clean ERA-to-bank reconciliation at specialty practices requires three matching layers. Most billing software handles only the first two, and many practices skip the third.

Layer 1: ERA to billing system (claim-level) — Match each ERA's claim-level payment lines to the corresponding claims in your PMS. Standard reconciliation. Catches most errors but misses PLB adjustments and anything at the deposit level.

Layer 2: ERA to bank deposit (batch-level) — Match the total payment amount in each ERA batch to the corresponding EFT deposit using trace numbers. The TRN segment in the 835 (specifically TRN03 in loop 1000B) should match the CCD+ addenda reference in your bank activity. This layer catches bundled deposits, PLB offsets, and timing mismatches.

Check for each ERA batch:

• The ERA total (sum of claim-level payments plus PLB adjustments) equals the EFT deposit amount

• The TRN trace number in the ERA matches the ACH addenda reference in your bank activity

• When a single deposit bundles multiple ERA batches, the sum of those batch totals equals the deposit amount

Layer 3: PLB segment reconciliation (provider-level) — Pull the PLB loop data from every ERA and reconcile separately. PLB segments appear outside the claim-level loops in the 835 — most billing systems either ignore them or route them to a catch-all adjustment bucket.

Review PLB reasons by period and payer:

• FD (Forward Balance): advance payment offset applied to this remittance

• WO (Withholding): backup withholding or tax holdback

• FC (Fund Allocation): may appear for TPA-managed payments

• CS (Adjustment): general provider-level adjustment requiring investigation

Common deposit gap patterns by payer

United Healthcare (Optum EFT): UHC deposits often include multiple payer programs bundled under a single Optum Financial Services ACH. Map by TRN trace number; do not assume the deposit total matches any single ERA total.

Cigna/Evernorth: Cigna medical claims and Evernorth pharmacy benefit claims route through separate payment engines. For Spravato and GLP-1 practices, reconcile the Cigna medical ERA and the Evernorth/Express Scripts pharmacy ERA as entirely separate exercises, even when the patient's date of service is the same.

BCBS (Blue Card out-of-area): Blue Card claims for out-of-area patients route EFT payments through a different entity than the local plan's standard payment cycle. The ERA issuer (home plan) and the deposit originator (local plan) may have different identifiers. Build a payer alias table in your reconciliation tracker.

Medicare Advantage vs. traditional Medicare: Medicare Advantage plans adjudicate internally and issue their own ERAs, but some use TRN format conventions that differ from CMS's standard prefixes. Apply MA-specific reconciliation logic separately from traditional Medicare.

What changes when you connect the bank directly

Manual ERA-to-bank reconciliation requires downloading bank statements, parsing 835 files, building a match table, and flagging exceptions. At most specialty practices, this happens weekly or monthly. By then, a PLB recoupment from three weeks ago has already distorted A/R reporting.

Connecting your bank account directly to your RCM platform gives visibility into incoming deposits as they land. When a deposit arrives, the system can:

• Match the EFT amount to the ERA batch total using trace numbers without a manual lookup

• Flag any deposit that has no corresponding ERA in a defined window

• Identify the payer on each deposit by reading the merchant name and payment descriptor in the ACH record

• Surface PLB adjustments that reduce the deposit below the ERA total at the time of posting, not at month-end

Practices running GLP-1, TMS, or Spravato across multiple TPA arrangements see the most from this. The gap that previously took 30 minutes to diagnose becomes a flagged exception with the PLB detail already surfaced — at the time of deposit, not at month-end close.

Field	Example
Payer	UHC, Cigna, BCBS of TX
ERA batch date	2026-04-10
ERA batch total	$12,400
EFT deposit date	2026-04-12
EFT deposit amount	$11,847
Difference	-$553
Root cause	PLB recoupment / Bundled deposit / TPA mismatch / Missing ERA / Timing
PLB reason code	FD (Forward Balance)
Resolution owner	[Biller name]
Due date	2026-04-19
Status	Open / In investigation / Resolved

FAQ

Why does my ERA total not match the EFT deposit for the same day? A PLB adjustment is usually where to look first. Pull the PLB loop data from your 835 for that ERA batch and check for entries.

How do I match a single bank deposit that covers multiple ERAs? Use the TRN segment (loop 1000B, TRN03) from each ERA and match it against the ACH reference number in your bank's CCD+ addenda record. HIPAA operating rules have required payers to include TRN data since 2014.

What does it mean when a GLP-1 or Spravato deposit is smaller than expected? Check whether the missing amount is being paid through the pharmacy benefit. Pharmacy benefit remittances arrive separately with a different issuer on a different schedule.

How often should specialty clinics reconcile ERA to bank? Weekly minimum. For practices with active PLB recoupment history or multiple TPA relationships, daily deposit monitoring prevents month-end surprises.

Is there a way to automate ERA-to-bank deposit matching? Platforms that connect directly to practice bank accounts via bank API can match incoming EFT deposits to ERA batches using trace numbers automatically, surfacing gaps at the time of deposit rather than during monthly close.