Reconcile Insurance Payments From Bank Statements

An insurer deposit on a medical practice’s bank statement proves that cash arrived. It does not identify every claim in the payment, show why a line was adjusted, establish the contracted allowance, or prove that a payer owes more.

For US electronic payments, the useful control is EFT-to-ERA reassociation: match the electronic funds transfer to the corresponding electronic remittance advice, then reconcile the remittance to the practice-management ledger. Other countries and payers use different documents, so adapt the workflow to the local standard.

The four records have different jobs

Record	What it establishes	What it does not establish alone
Bank statement	posted deposit date and amount	claims, billed charges, adjustment reasons
EFT detail	payer, trace reference, settlement information	full claim adjudication
ERA/835 or paper remittance	claim and line payments, CARCs/RARCs, provider-level adjustments	whether the bank posted the cash correctly
Practice ledger and payer contract	billed services, patient account, expected contractual treatment	actual bank receipt

CMS explains that a Medicare ERA or paper remittance contains claim and service-line adjudication details and adjustment reasons. See Health Care Payment and Remittance Advice.

The bank is therefore a control point, not the primary claims record.

Step 1: build a deposit control list

Start with the relevant practice bank account and isolate deposits that appear to be insurer EFTs. Keep the bank’s original statement and, if available, its native CSV export.

Use a control table:

Bank posted date	Bank description	Bank amount	Payer	Trace reference	ERA found	Status
2026-05-07	HEALTH PLAN EFT	1,540.00	Example plan	004812	Yes	Matched

A description keyword is only a starting clue. Confirm payer and trace information from the EFT detail or treasury record.

If a statement exists only as a supported PDF or image, a conversion can make filtering easier. Check the extracted dates and amounts against the original before using the rows.

Step 2: reassociate the EFT and ERA

For HIPAA-standard US EFT and ERA transactions, the trace information in the payment addenda is designed to match the payment to the remittance. CMS calls this process reassociation and explains that the matching TRN segment helps connect the EFT with its ERA in its EFT and remittance operating-rule guidance.

Match:

• payer identity;
• payment or effective date;
• trace or reassociation reference;
• ERA payment amount;
• bank deposit amount;
• bank account receiving the funds.

If one ERA relates to one EFT, the bank variance control is:

Bank deposit - ERA payment amount = 0

If a payer batches or splits payments differently, document the many-to-one or one-to-many relationship instead of forcing a single-row match.

Step 3: reconcile the ERA internally

The ERA may include multiple claims and adjustments. In the US standard:

• CARCs explain why a claim or service-line amount changed;
• RARCs add detail;
• group codes assign financial responsibility;
• PLB entries describe provider-level adjustments not assigned to one claim.

CMS notes that provider-level adjustments can include prior-payment recoupments, interest, or incentive adjustments. A PLB entry is not automatically correct merely because it balances the remittance; review its code, reference, payer notice, and appeal or dispute rights.

Use an ERA worksheet:

ERA trace	Claim control	Billed	Payer paid	Patient responsibility	Contractual/other adjustment	Code	Ledger posted
004812	C-1001	900.00	700.00	50.00	150.00	See ERA	Yes

Do not infer the “expected” amount from billed charges. The payer contract, fee schedule, benefit rules, and adjudication details determine the expected treatment.

Step 4: post the payment to the practice ledger

Post the ERA at claim or service-line level according to the practice system:

1. payer payment;
2. patient responsibility where applicable;
3. contractual and other coded adjustments;
4. provider-level adjustments;
5. unresolved exceptions.

Then compare the practice’s payment batch with the ERA total and the bank deposit. An unexplained difference remains on an exception log; it is not assigned to a random patient account.

Worked example: a deposit smaller than claim payments

Suppose an ERA contains these payer payments:

Component	Amount
Claim A payment	700.00
Claim B payment	500.00
Claim C payment	595.00
Claim payment subtotal	1,795.00
Provider-level prior-period adjustment	(255.00)
ERA payment amount	1,540.00
Bank deposit	1,540.00

The bank and ERA match: cash variance is zero. The 255.00 difference from the claim-payment subtotal is not proof that Claim A, B, or C was short-paid. It is a provider-level adjustment that must be validated against its code, reference, prior ledger history, and payer notice.

If the bank showed 1,510.00 instead, the 30.00 would be a bank-to-ERA exception. That still would not identify a specific underpaid claim.

How to investigate a possible underpayment

Only begin an underpayment review after the EFT, ERA, and ledger reconcile. For the claim in question, compare:

• submitted procedure and units;
• payer contract or applicable fee schedule;
• allowed amount;
• deductible, coinsurance, or other patient responsibility;
• CARC, RARC, and group codes;
• coordination-of-benefits information;
• prior adjustments or recoupments;
• timely filing, appeal, and reconsideration deadlines;
• the amount posted in the practice system.

Then classify the outcome: correct adjudication, posting error, missing information, contractual issue, payer error, or unresolved. A spreadsheet variance is a work item, not a legal conclusion that money is due.

Denials are not visible in the bank

A claim that produces no payment leaves no bank transaction. To identify denials or unprocessed claims, use:

• ERA and paper remittance records;
• claim-status responses;
• clearinghouse reports;
• practice-management aging and denial worklists;
• payer portals and correspondence.

Bank deposits can confirm received cash but cannot define the complete population of submitted claims.

Accounting and tax treatment is context-specific

Do not equate all deposits with taxable income or all billed charges with revenue. Treatment depends on the entity, accounting method, jurisdiction, payer arrangement, patient collections, and period cut-off.

Reconcile the cash deposit to the remittance and ledger, preserve the source documents, and let the accountant apply the correct recognition and tax rules. In the US, the IRS recordkeeping guidance emphasizes supporting documents in addition to account statements.

Protect patient and payment information

ERA, claims, billing ledgers, and related payment records can contain protected health information. For a US covered entity, HHS says the HIPAA Security Rule requires safeguards for electronic PHI, and a cloud provider that creates, receives, maintains, or transmits ePHI on the entity’s behalf may be a business associate requiring an appropriate agreement. Review HHS cloud-computing guidance.

Before using any conversion or spreadsheet service:

• determine whether the file contains PHI;
• use only vendors approved by your privacy and security team;
• confirm any required contract or business associate agreement;
• minimize the data shared;
• restrict access and maintain an audit trail;
• follow the organization’s retention and deletion policy.

A vendor’s general privacy statement is not proof that a healthcare workflow is compliant.

Monthly sign-off checklist

• Every insurer deposit has an identified payer.
• Each EFT is associated with the correct ERA or paper remittance.
• Bank amount and remittance payment total agree, or the variance is open.
• Claim and provider-level adjustments have codes and references.
• Ledger postings agree with the remittance.
• Possible underpayments are tested against contracts and adjudication details.
• Denials are reviewed from claim systems, not inferred from the bank.
• A qualified reviewer signs off exceptions.
• PHI is handled only through an approved workflow.

Related articles

• Bank Statements to Excel and CSV for Doctors
• How to Prepare Bank Statements for Your Accountant
• How to Reconcile Bank Statements at Month End

For approved statements without regulated patient data, extract the bank-deposit control rows with BankStatementLab