A pharmacy claim response, a remittance advice and a bank deposit answer different questions. The claim record shows the submitted transaction and the response returned to the pharmacy. The remittance explains a payment and its adjustments. The bank record shows the funds posted to the account. To investigate a payment, connect the relevant records instead of treating a claim marked paid as proof that its money reached the bank.
Which payment record do you need?
- “What did the pharmacy submit, and what came back?”
- Start with the claim transaction and response history. Keep the relevant prescription or claim reference, submitted transaction and returned message together in the pharmacy's approved system. A health care claim is a request for payment under the federal transaction definition; it is not the bank's deposit record. [1]
- “Which claims and adjustments explain this payment?”
- Retrieve the payer's remittance advice or payment-detail record. In Medicare fee-for-service, CMS says a remittance usually includes multiple claims and reports itemized adjudication and payment information, with adjustments at the line, claim or provider level. Use the payer's own documentation for the payment you are reviewing. [4]
Federal standards distinguish a provider's request for payment from payment processing information and remittance advice. They also distinguish retail pharmacy drug claims from the electronic payment and remittance transactions. That is the basis for the record map, rather than a promise that every payer, pharmacy system or bank presents the same fields. [1] [2] [3]
This guide helps a pharmacy owner or payment-reconciliation staff member identify the next record to retrieve. It does not calculate what a payer owes, interpret a contract, decide whether a balance can be billed to a patient, or establish a payment deadline. Medicare examples are explicitly labeled; a Medicare fee-for-service explanation is not a Part D plan or commercial PBM payment policy.
Does a paid pharmacy claim mean the money is in the bank?
A claim status alone is not evidence of a bank posting. Preserve the actual response in the pharmacy system, then locate the applicable payment detail and the bank transaction. These are separate records, even if one application displays them together. Federal rules separately describe claims, payment information and remittance advice, while the CORE reassociation rule describes the ERA and EFT traveling through different paths before the provider matches them. [1] [3] [6]
If the claim response and the bank deposit do not appear to agree, first identify which link is missing: the claim in the payment detail, the remittance for the deposit, or the bank posting for the remittance. A missing record is a question to resolve. It does not, by itself, establish an underpayment, a rejection, or an amount owed by the patient.
What is the difference between an ERA and an EFT?
An electronic remittance advice (ERA) explains the payment; an electronic funds transfer (EFT) carries the payment. CMS lists electronic remittance advice and claim payment/EFT as adopted transaction standards, separate from retail pharmacy claim submission. The federal EFT/remittance standards include the X12 835 payment/advice and, for the specified ACH payment-initiation transmission, the CCD+ format with reassociation information. [2] [5]
An ERA is not simply another name for the deposit line visible in online banking. The CORE rule describes the 835 traveling from the payer to the provider, directly or through an intermediary, while the CCD+ goes through the ACH network. The shared information allows those separate deliveries to be matched. [6]
The table below is a record-finding aid. A screen label such as “trace,” “reference” or “batch” does not establish that a field is the required reassociation value; use the bank's, payer's or processor's field definition.
| Information | Why it helps | Boundary |
|---|---|---|
| Payment-related information / reassociation trace | Connects the payment record to its corresponding remittance. | Request the relevant payment-related/addenda information; do not assume any bank transaction ID is interchangeable with it. |
| Payment amount | Checks the payment total against the remittance's payment amount. | A single claim's amount need not equal the remittance total. Medicare remittances usually contain multiple claims. |
| Effective entry date / EFT effective date | Provides another point of comparison between the payment and remittance records. | Do not substitute the claim's service or submission date for the payment date. |
These three categories come from CORE 370, version 3.0.0, June 2012, section 3.3. Its stated scope is the specified X12 835 and healthcare EFT standards; the table is not a universal field mapping for checks, cards or every proprietary PBM report. [6]
What if the bank shows a deposit but the remittance is missing?
Keep the deposit open as an unmatched item while you locate its payment explanation. Retrieve the available payment reference, amount and date from the bank, then ask the payer, processor or remittance-delivery service for the corresponding remittance through your approved channel. If the payment uses the covered CCD+/835 flow, ask whether you receive the payment-related addenda needed for reassociation. CORE 370 section 4.1 specifically addresses arranging delivery of the minimum CCD+ data with the financial institution. [6]
Use that record request to identify the missing connection. Do not assign the deposit to whichever collection of claims happens to produce the same amount. Matching the total is useful corroboration, but an amount-only match can leave the wrong claims marked as settled.
Why might the remittance total differ from the sum of the claims I selected?
First compare the same scope. A selected group of claims may not represent everything in that payment. For Medicare fee-for-service, CMS explains that a remittance usually contains multiple claims and that adjustments may occur at line, claim or provider level. Provider-level adjustments can include recovery of a prior overpayment or payment of interest, rather than an adjustment to one claim in that remittance. [4]
Use the payment's actual remittance to identify the relevant adjustments before describing a difference as missing money. CMS's Medicare examples explain why the record matters; they do not establish the adjustment policy of a Part D plan, Medicaid managed-care plan or commercial PBM.
A fictional Medicare-style remittance lists claim payment amounts of $120, $80 and $50 and a separately identified provider-level deduction of $10. The arithmetic is:
$120 + $80 + $50 − $10 = $240.
A $240 deposit would be consistent with that illustrated payment total, subject to matching the payment identifiers. The example does not establish that any real adjustment is valid, that a payer owes these amounts, or that the bank posting occurred. It illustrates the line/claim/provider distinction described by CMS. [4]
Keep the unresolved question attached to the record
For each unmatched payment, retain the record you have, the record you need, and the specific question for the responsible bank, payer or processor. Useful descriptions include “deposit located, remittance not received,” “remittance located, payment not matched,” and “payment matched, one adjustment needs explanation.” These are suggested work-queue labels, not standard payer status codes or accounting conclusions.
For a claim rejected during processing, begin with the actual returned message and the pharmacy claim reject-code guide. For the payer's current payment and reporting instructions, use the relevant source in the payer-sheet and provider-manual directory. Preserve claim and payment records in your team's approved systems rather than entering patient or bank information into a public lookup.
Source access checked October 29, 2026. The dates below describe the source editions or page updates, not the date of a pharmacy's payment. The record-finding sequence and suggested queue labels are editorial guidance; payer-specific handling remains governed by the relevant agreement, payment documentation and responsible staff.
Sources6 linked sources
- 45 CFR §162.1101: Health care claims or equivalent encounter information transaction. Defines the provider-to-plan request for payment. eCFR title 45 displayed current through October 27, 2026 when accessed; eCFR is an unofficial, continuously updated edition.
- CMS: Adopted Standards and Operating Rules. Page last modified March 16, 2026. Separates retail pharmacy claims, electronic remittance advice and EFT standards. This guide does not restate transaction-version migration dates.
- 45 CFR §162.1601: Health care EFT and remittance advice transaction. Distinguishes payment, transfer/processing information and remittance advice; eCFR title 45 current through October 27, 2026 when accessed.
- CMS: Health Care Payment and Remittance Advice. Page last modified September 10, 2024. Used for the explicitly labeled Medicare fee-for-service explanation of claim/line/provider adjustments and multi-claim remittances, not generalized into a PBM or Part D plan policy.
- 45 CFR §162.1602: Standards for health care EFT and remittance advice transaction. Paragraph (d) specifies the applicable CCD+/TRN and 835 standards for the described transmissions; eCFR title 45 current through October 27, 2026 when accessed.
- CAQH CORE 370: EFT & ERA Reassociation (CCD+/835) Rule, version 3.0.0, June 2012. See sections 2.1, 3.3–3.6 and 4.1. The PDF edition is June 2012; today's access check does not turn it into a 2026 rule. This guide makes no general claim about payment deadlines.