Revenue cycle

EFT and ERA Setup That Supports Payment Reconciliation

Quick answer
EFT moves the money and ERA explains the claim adjudication. A complete setup connects both to the right entity and creates a reliable way to match the bank deposit, remittance file and patient-account posting.

Published · Updated

Treat payment and remittance as separate connections

An electronic deposit can arrive while the billing team is still missing the corresponding remittance. An ERA can reach a clearinghouse that is no longer used by the practice. Map the movement of money and the movement of information separately before requesting changes. Identify the billing entity, payer and product involved in each connection.

CMS describes matching payment and remittance information through reassociation. Use that concept to define the operational result the practice wants: a traceable path from the bank transaction to the payer’s explanation and the accounts updated by the billing team. A submitted enrollment form is only one step toward that result.

Inventory the current payer and entity setup

Create a register of payer identifiers, billing NPIs, tax identities, bank arrangements and remittance destinations. Restrict access to financial details and record the person authorized to approve a change. If a group has multiple entities, do not assume the same destination applies to all of them.

Before changing anything, identify existing remittance access and the person who can retrieve missing files. Record whether files are delivered directly, through a clearinghouse or through another authorized platform. A transition plan should address old and new routes so staff do not accidentally create a period in which neither team receives the remittance. See EFT and ERA enrollment support for the administrative scope.

Use a controlled approval process for financial changes

Follow the payer’s current official process and confirm who is permitted to submit and approve the enrollment. Validate the destination details with an authorized practice contact through an established channel. Treat an unexpected request to change payment instructions as an exception requiring independent verification.

Keep a record of the approved change, submission confirmation and expected next check. Avoid passing bank details through a public contact form or placing them in a general project spreadsheet. If a vendor is helping, establish the access and authorization boundaries in advance. The practice should retain visibility into what was requested and the evidence that supported it.

Define how the team will match deposits and files

Identify the fields the bank and remittance systems expose, including the trace information used for reassociation. Write down where staff find those fields and what they do when a match is missing. CMS’s payment and remittance resources explain the role of matching trace data.

Make the reconciliation process concrete. A bank deposit should have a corresponding remittance or a documented exception under review. A remittance should have a known posting disposition. If the amounts do not reconcile, check for provider-level adjustments and other explanations in the actual file instead of forcing a claim allocation to make the bank total appear balanced. Qualified billing staff should interpret the remittance details.

Create a payment exception queue

Useful categories include deposit without remittance, remittance without identified deposit, delivery to an old destination, duplicate file and unexplained amount difference. For each item, record the payer, date, amount, available references, owner and next action. Keep patient information in the authorized billing system rather than a broadly shared task board.

An exception queue should distinguish a missing file from an adjudication dispute. The person obtaining an ERA is not necessarily the person reviewing a denial or underpayment. Clear routing prevents both teams from waiting on each other. Set an internal review cadence appropriate to the practice’s payment volume and operational risk.

Close setup with evidence from the first payment cycle

After the payer confirms enrollment, monitor the next relevant payment and remittance delivery. Confirm that authorized staff can locate the file, identify the deposit and post or route the claim results. Record the outcome and any unresolved exception. Do not use receipt of an email confirmation as the only closeout criterion.

Repeat the check when the practice changes a bank, clearinghouse, billing vendor or legal entity. Keep the register current so future transitions begin from a known setup. Niyutsa can coordinate enrollment records and payment posting support, with financial approvals remaining under the practice’s designated authority.

Reconcile a deposit and remittance that arrive out of order

A billing team sees a payer deposit on Tuesday and an electronic remittance in its clearinghouse on Wednesday. Compare the payer and receiving entity, then use the information in the payment and 835 files to match the deposit to the correct advice. If there are multiple deposits for the same amount, use the trace and other available matching information instead of applying the first plausible batch.

Ask the posting lead to flag missing payment, missing remittance and amount mismatch as three separate exceptions. Assign different owners where the bank, payer portal or clearinghouse needs a follow-up. Keep banking documentation in an approved system and share only a reference in the routine worklist.

Before an EFT change goes live, document the authorized request and the expected receiving account through your organization’s verification process. Review the first matched settlement and its remittance after the change. If a different group record sends the deposit, route the case to the enrollment and finance owners before releasing the batch.

  • Deposit received. Find the related remittance and verify the transaction reference and billing entity.
  • Advice received. Confirm whether the advice relates to a deposit or an adjustment with no separate payment.
  • Mismatch persists. Keep the batch in the exception queue and save the payer or clearinghouse response.
What should I record when the remittance arrives without a deposit?

Record the advice date, payer, entity, transaction reference and amount. Ask finance to verify the bank record and use the payer’s remittance and financial guidance to decide whether the advice should have an associated payment.

Payment posting exception workflow

Common questions

Does EFT enrollment automatically deliver an ERA?

Do not assume so. Confirm the payer’s processes and verify the money and remittance connections separately.

What is reassociation?

It is the process of matching the payment with its corresponding remittance information. CMS explains the use of matching trace data in that process.

When should setup be considered complete?

Use the payer’s confirmation plus evidence that the practice can retrieve and reconcile the relevant payment and remittance, with exceptions assigned.

Sources and further reading

Put this guide to work

Use the current program or payer instructions to confirm the steps for your own organization. Niyutsa Technologies can help scope application preparation, tracking and the handoff to billing.

Common questions

Can a payer send EFT deposits before ERA is working?

Payment and electronic remittance can have separate setup and routing. When money arrives without an ERA, record the deposit trace and compare it with payer remittance availability and clearinghouse delivery. Verify both connections separately before treating the issue as resolved.

Use the payer enrollment checklist