Electronic Remittance Advice: Match the Deposit to the Claims

An electronic remittance advice, usually called an ERA, explains how a payer processed one or more medical claims. An electronic funds transfer, or EFT, moves money to the pharmacy's bank account. The ERA explains the payment; the EFT delivers it.

A pharmacy billing team reconciles the batch by connecting three records: the EFT or check, the ERA, and the affected medical claims. This article shows that match with one trace number, a three-claim example, and a payment-batch record that keeps unexplained adjustments out of the wrong claim or patient balance.

The deposit and the ERA answer different questions

CMS defines an EFT as the payment instruction that moves money. It identifies the payer, payee, amount, accounts, and payment date. The electronic remittance advice is the explanation that assigns the payer's decision and amounts to claims and service lines. Searchers sometimes call that an electronic remittance notice, but ERA is the standard health care term.

One ERA can contain several claims. It can show billed amounts, allowed amounts, payer payments, patient responsibility, contractual adjustments, reason codes, and remarks. It can also include a provider-level adjustment such as interest or recovery of a prior overpayment. That batch-level amount may change the deposit without belonging to one current claim.

A retail prescription claim may start as an NCPDP D.0 transaction while its later payment and remittance use an X12 835. The real-time response at the pharmacy counter is not the later ERA, so keep the adjudication response, remittance, and cash posting as separate records.

Use the trace number to match the batch

A health care EFT and its ERA use reassociation data to connect the payment and explanation, but two different trace labels can appear. The ACH trace number identifies the bank-network transaction. The X12 TRN02 reassociation trace identifies the payment in the ERA and in the CCD+ addenda record sent with an ACH payment. These are not interchangeable numbers.

CMS and the CAQH CORE reassociation rule use the X12 reassociation trace to connect the EFT with the correct ERA. Ask the bank for the full CCD+ addenda data when the ordinary deposit view does not expose it. A match is strongest when the reassociation trace, payer and payer ID, payee, amount, effective date, and payment method agree. If any of those facts conflict, preserve the mismatch and investigate instead of forcing the records together.

One $965 deposit, three paid claims

Assume a pharmacy receives an illustrative EFT for $965. The matched ERA lists three professional medical claims with net payer payments of $450, $300, and $250. Those claims total $1,000, so posting only the three claim payments would leave the bank deposit $35 short.

The provider-level section explains the difference: the payer recovered $40 from a prior overpayment and added $5 of interest. The complete batch is $1,000 minus $40 plus $5, which equals the $965 EFT. The recovery and interest stay separate from the three current claims unless the ERA supplies a supported reference to allocate them elsewhere.

The ERA can still contain separate contractual adjustments or patient-responsibility amounts inside each claim. Those amounts explain the individual claim balance; they do not change the $450, $300, and $250 payer payments used in this example. Use the claim remit-code guide when a group code, adjustment reason, or remark controls the remaining balance.

When the two records do not arrive together

The deposit arrives first

Record the payer, payee or pharmacy location, amount, date, and bank trace. Then search the payer portal, clearinghouse, or remittance connection with those facts. If the ERA is still unavailable, ask the named payer or trading partner where it sent the 835 and provide the trace, amount, date, tax identifier or NPI, and connection details. Keep the cash unallocated until the payer supplies enough evidence to identify the claims and adjustments.

The ERA arrives first

Read the payment method, amount, date, and trace in the ERA. Check the bank, outstanding checks, and the payer's current payment instructions. A claim marked paid inside the remittance proves the payer's adjudication result; it does not prove that the corresponding cash reached the correct account. Escalate with the trace and payee details when the money is missing or misdirected.

Payers use different enrollment processes, portals, trading partners, and exception timeframes. Practitioner reports show that missing-remittance and missing-payment problems happen in both directions, but those anecdotes do not establish a universal waiting period or contact route. Use the named payer's current written instructions and keep its response with the batch.

Keep one payment-batch record

A payment-batch record should let another teammate prove the cash, remittance, and claim allocation without starting over. Keep the record free of unnecessary patient details when the same information already lives on the protected claim.

• Payment identity: payer and payer ID, pharmacy location or payee TIN or NPI, aggregation level, payment method, EFT or check date and amount, bank ACH trace, full CCD+ addenda data, ERA TRN02 reassociation trace, BPR02 amount, ERA control or file identifier, and the source and retrieval time for each record.
• Claim allocation: internal and payer claim identifiers, service date, billed amount, allowed amount, payer payment, patient responsibility, and relevant group, reason, and remark codes. Record duplicate, reversal, or replacement status before suppressing or reposting a repeated file.
• Batch adjustments: PLB code and identifier, amount and sign, interest, recoupment, withholding, incentive, or other provider-level reason, with its payer reference, date, source, and supported allocation if one exists. Do not move a provider-level balance into a patient account merely because the ERA lacks a claim reference.
• Interpretation: the payer's stated result, the unresolved fact, evidence checked, likely route, confidence, owner, payer-specific deadline, and stop or qualified human-review trigger.
• Patient-balance review: stated patient responsibility, secondary coverage, Medicare QMB indicators or other program protections, contract restrictions, advance-notice evidence when applicable, and the qualified reviewer who confirmed that billing the patient is allowed.

Stop automatic posting when the full reassociation trace is missing or mismatched, the amount or effective date differs, the payee is wrong, several records remain plausible, claims appear twice, the same TRN arrives with changed claim content, a provider-level adjustment lacks a verified payer reference, or the claims plus or minus PLBs do not balance to the deposit. Use a separate path for a check or virtual card instead of treating it as ACH. Require human review before any patient bill when secondary coverage, Medicare QMB protections, contract terms, notice requirements, or other program rules remain unresolved.

Post only what the batch proves

Match the total payment first, then allocate each claim, then preserve any provider-level difference as its own line. The claims-adjudication guide explains how the claim reaches the ERA, while the pharmacy revenue-cycle guide shows where payment ownership and follow-up continue after posting.

DocStation displays incoming remittances with check numbers, amounts, associated locations, payment dates, and payers. Claim history and notes remain available for follow-up. The pharmacy still verifies that the bank payment, remittance, claim allocation, and payer evidence agree before closing the batch.

Public reconciliation platforms advertise automatic deposit matching, missing-deposit detection, and posting controls. That confirms the capability category exists, but software output does not prove that two records belong together or that a balance may be assigned to a claim or patient. Preserve the evidence and require review when the match is uncertain.