Electronic funds transfer

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

EFT moves money while ERA explains the result

The CMS EFT and ERA guidance distinguishes the transactions. EFT moves payment funds. An electronic remittance advice, or ERA, explains claim adjudication and adjustments. Payment posting applies the remittance results and matched funds to the practice's accounts receivable and patient ledgers.

These states can arrive at different times:

1. a payer adjudicates one or more claims
2. the payer creates remittance information
3. the payer initiates a payment through the selected method
4. the practice's bank records a deposit
5. the practice receives and validates the ERA
6. staff or software reassociate the EFT and ERA
7. authorized posting updates claims and ledgers

A bank deposit alone does not reveal which claims paid, which adjustments applied, whether patient responsibility changed, or whether the payer later identifies an overpayment.

The adopted health care EFT standard uses ACH

The current CMS adopted-standards table separates the transactions. A standard health care EFT initiated through ACH uses NACHA CCD+Addenda, with the X12 835 TRN segment supplying the addenda record's reassociation data. The associated ERA is a separate X12 835 Version 5010 transaction. CMS's EFT and ERA operating-rules page says the EFT instruction includes the amount, payer and payee identification, bank accounts, routing information, and payment date.

The plan must place matching TRN data in the CCD+ addenda and associated ERA so the practice can reassociate the funds with the remittance. The CCD+ addenda uses the TRN segment, not the full ERA transaction.

Other payment methods can exist. CMS guidance on virtual credit cards and EFT says VCC payments are permitted, but when a HIPAA-covered provider requests the adopted EFT and ERA standards and completes plan enrollment, the health plan must comply whether or not the provider is in network. A plan may use a business associate for its work, but may not condition standard EFT or ERA on the provider accepting that vendor's payment or reassociation services. HHS does not regulate VCC fees under the adopted standards, so record the actual method, fees, terms, enrollment, and reconciliation path.

Enroll bank changes through a controlled workflow

These are practice controls, not universal CMS or payer requirements. Maintain a payer-product enrollment register with:

• payer and payment vendor legal names, identifiers, portal, and verified contact path
• TIN, NPI, payee, contract, location, and bank-account scope
• requested payment method, ERA route, enrollment date, status, and effective date
• submitter, independent approver, confirmation, test, and evidence location
• bank account token or restricted reference, without copying full credentials into a broad work queue
• change request, prior value, new value, reason, request channel, approval, and activation evidence
• termination, merger, ownership, bank closure, payer transition, and revalidation triggers

Use a callback or portal path obtained independently from the change request. Separate the person who requests a bank change from the person who approves it. Alert finance staff to first deposits after any enrollment change, payer migration, or account update.

Medicare supplies one program example. The current CMS-588 page lists the November 2023 EFT Authorization Agreement, with OMB expiration in November 2026. It covers new Medicare EFT enrollment or an account change and states that providers and suppliers must receive EFT at enrollment, revalidation, contractor change, or an enrollment change request. CMS-588 does not itself enroll an entity in Medicare; a separate form is required for each Medicare contractor receiving claims. It does not govern Medicaid, commercial plans, workers' compensation, or other payers.

Reassociate before posting

The CMS reassociation guide explains that EFT and ERA may arrive separately. The health plan includes the same unique TRN in its ACH payment initiation and the ERA. HIPAA does not standardize the bank's Stage 3 deposit notification, so the practice should arrange with its financial institution to receive the CORE-required minimum CCD+ data, including the TRN.

CMS guidance also requires a one-to-one EFT-to-ERA relationship. If one EFT covers several claims, one ERA contains the remittance for all of them. Treat non-one-to-one relationships and missing, duplicate, or altered TRNs as exceptions.

When the operating rule applies, plans must release the ERA no sooner than three business days before and no later than three business days after the EFT effective date for at least 90% of transactions monthly. They must give enrollees written late-or-missing resolution procedures using a maximum four-business-day interval after receipt of either transaction.

For each incoming payment, retain:

• bank-received date, amount, payer label, payment method, full CCD+ addenda TRN from the deposit notification, and any separate bank reference
• ERA received date, payer, payee, payment amount, payment date, and TRN
• claim count, service-line count, paid amount, adjustments, patient responsibility, and zero-pay results
• one-to-one EFT-to-ERA match, amount variance, owner, age, and verified resolution
• posting batch, reviewer, approval, ledger changes, deposit reconciliation, and close date

Place an unexpected deposit, missing ERA, mismatched trace, amount variance, duplicate payment, or unverified bank change in an exception state. Preserve the money and evidence while the authorized finance or RCM owner determines the correct action.

A fictional deposit shows the three layers

A fictional payer sends an EFT deposit of $12,480.50. The provider's Stage 3 bank notification and ERA carry the same TRN. The ERA covers 20 claims: 17 claims have payments totaling $12,480.50, two are denied with no payment, and one has a zero payment with an adjustment and patient-responsibility result.

EFT-to-ERA amount match is $12,480.50 divided by $12,480.50, or 100%. Trace match is 1 of 1. Neither ratio makes all 20 claims “paid.” Claim-level results are 17 paid, two denied, and one zero-pay adjudication. Posting remains open until all 20 results and the deposit reconcile to their source records.

If the trace differs or the ERA totals $12,400.50, the practice holds automated posting and records an $80 variance. Staff should resolve the source rather than force the ledger to balance.

Measure enrollment, matching, and closure separately

Useful measures include:

• EFT enrollment completion: active payer-product routes with verified production enrollment divided by routes due for EFT
• ERA availability: EFT payments with a matched ERA divided by mature EFT payments
• trace-match rate: mature EFT payments with a matching ERA TRN divided by mature EFT payments requiring reassociation
• amount-match rate: matched EFT-ERA pairs with no unresolved amount variance divided by mature matched pairs
• exception aging: median and 90th-percentile days from the defined mismatch event to verified resolution
• posting closure: payment batches fully reconciled and posted divided by mature batches due
• bank-change verification: activated changes with independent verification and approval divided by activated changes

Define the route, maturity window, match unit, amount tolerance, exception, clock, and final disposition. Report unauthorized-change alerts, reversals, recoupments, refunds, fees, and unidentified deposits separately.