General operational information only. Payer, state, contractual and regulatory requirements vary. Confirm current requirements with the applicable payer or agency.
Quick answer
What practice leaders need to know
EDI is the electronic transaction framework used to send claims and other healthcare data. ERA explains how a payer processed claims. EFT moves the actual deposit. Practices need the claim acknowledgement, remittance and bank deposit connected for accurate posting and reconciliation.
EDI is the broader electronic exchange
Electronic data interchange is the structured exchange of healthcare transactions between providers, clearinghouses and health plans. Claims, eligibility inquiries, claim-status requests and remittance information can move through standard electronic transactions. In everyday billing conversations, EDI enrollment often refers specifically to approval for electronic claim submission with a payer.
ERA explains how the claim was processed
An electronic remittance advice contains payment and adjustment information that can be posted into the billing system. It may include claim and service-line outcomes, adjustment reason codes, remark codes and patient responsibility. ERA enrollment and routing must connect the correct payer, provider or group, clearinghouse and software receiver.
EFT moves the money
Electronic funds transfer sends the payer's deposit to the enrolled bank account. EFT does not replace the remittance. The deposit shows the amount received, while the ERA explains which claims and adjustments make up that payment. A practice needs both pieces to post and reconcile accurately.
Credentialing approval may not finish electronic setup
A provider can be approved with a payer while claim routing, ERA or EFT enrollment remains incomplete. Treat these as separate readiness steps with their own confirmation. Verify the effective date, billing relationship, payer ID, clearinghouse connection, remittance receiver and bank enrollment before relying on the workflow.
Reconcile the full path
A useful control connects the submitted claim, payer acknowledgement, adjudication, ERA, deposit and posting batch. Unmatched deposits, missing remittances or claims sent under the wrong identifier should have an owner and next action. This turns electronic enrollment from a setup task into an accountable revenue process.
Follow one claim through the full path
The claim transaction moves from the billing system through a clearinghouse or direct payer connection. An acknowledgement confirms transaction status, adjudication produces the remittance, EFT delivers funds and posting connects the payer's decision to the patient account.
Separate electronic enrollment from credentialing
Credentialing or payer participation does not automatically activate claim submission, ERA routing or EFT. Track each enrollment separately and test the connection before treating the payer as fully ready.
Know what each transaction tells you
The 837 carries the professional or institutional claim. A 999 acknowledgement reports whether the electronic transaction met structural requirements. A 277CA can report whether individual claims were accepted or rejected for adjudication. The 835 ERA explains the payer's final claim and line decisions and supports automated posting. A 276 and 277 pair can be used for claim-status inquiry and response. Staff do not need to read raw transaction files every day, but the billing system or clearinghouse should make each response available when a claim stops moving.
Reconcile the ERA and EFT with a traceable batch
One EFT deposit may correspond to an ERA containing many claims, adjustments and patient-responsibility amounts. Use the payer trace information, payment date and amount to match the bank deposit with the remit before posting is considered complete. Investigate a deposit without an ERA, an ERA without a matching deposit, duplicate remits and provider-level adjustments. Do not force a batch to balance by posting an unexplained difference. Record the exception owner and retain the payer or clearinghouse resolution.
Treat bank-change requests as a fraud-sensitive process
EFT maintenance affects where healthcare revenue is deposited, so changes should require independent verification and limited access. Confirm the request through a trusted payer channel, verify the bank documentation and record who approved the change. After activation, compare the first deposit with the expected payer and ERA. An email asking staff to replace banking details should never be accepted as sufficient evidence by itself. This control belongs in the revenue-cycle workflow even when enrollment is handled by another team.
Test every connection before calling setup complete
Send or identify a controlled claim for the new payer route and confirm that the 837 is accepted at both transaction and claim level. Verify that the ERA reaches the intended system, the EFT reaches the approved bank account and the payment posts to the right patient account. Record payer IDs, submitter and receiver IDs, effective dates and confirmation numbers in the setup file. If any step depends on a clearinghouse enrollment, keep that task open until the payer and clearinghouse both show the connection as active.
Use eligibility and claim-status transactions deliberately
The 270 eligibility inquiry and 271 response can support benefit verification, while the 276 inquiry and 277 response can report claim status. These transactions answer different questions and do not replace the payer's complete policy, authorization process or final remittance. Store the response date, payer product and key outcome with the workflow so staff know what was checked. If the system converts the response into a short summary, make the underlying detail available for exceptions. An eligibility response is time-specific and not a guarantee of payment; a claim-status response is not final adjudication unless the payer indicates it is.
Document the trading-partner chain
A claim may pass from the practice-management system to a clearinghouse, another trading partner and the payer. ERA may return through a different receiver, and EFT travels through the banking network. Record each party, payer ID, submitter and receiver identifier, support contact and responsibility. This map helps locate a missing transaction without sending every problem to the payer. It also supports vendor changes and prevents one team from assuming another completed enrollment. Review the chain by payer product because routing can differ even when the insurer's brand name is the same.
Control payer IDs and provider mappings
The payer ID directs an electronic transaction to a particular connection; it does not by itself prove network participation or coverage. Validate the ID against the clearinghouse and payer instructions for the claim type and product. Map billing and rendering providers, tax identifiers, locations and submitter relationships carefully. A correct claim sent through the wrong route can reject or disappear from expected reporting. Restrict mapping changes, record effective dates and test after updates. When organizations merge or payer routes change, preserve the prior configuration long enough to manage older dates of service and remittance history.
Work acknowledgements as daily revenue controls
Review transaction and claim-level acknowledgements on a defined schedule rather than waiting for unpaid accounts to age. Separate file failures from individual claim rejections and assign each response to an owner. Correct the source record, retransmit when appropriate and confirm subsequent acceptance. Track claims with no expected acknowledgement as exceptions because silence is not acceptance. Dashboard measures should include first-pass claim acceptance, rejection dollars, time to correction and acceptance after correction. This workflow protects timely filing and exposes system or routing failures before they become an aged accounts-receivable problem.
Govern automated ERA posting
ERA automation should apply payments, adjustments and patient responsibility according to approved mappings while routing unknown or material exceptions for review. Test claim-level, line-level and provider-level adjustments; reversals; takebacks; interest; and zero-pay remits. Limit access to change reason-code mappings and preserve an audit log. Reconcile the completed posting batch to the ERA and matched deposit, not merely to the expected total in the billing system. Sample posted accounts periodically to confirm that contractual adjustments, denials and patient balances are classified correctly and that automation has not hidden underpayments.
Protect access and sensitive changes
Electronic enrollment portals and clearinghouse accounts can expose claims, remittances, provider details and banking instructions. Use individual accounts, multifactor authentication, least-privilege roles and prompt access removal when staff or vendors change. Keep credential sharing out of email and general task notes. Bank, remit-receiver and submitter changes should require independent verification and documented approval. Review security and business-associate responsibilities with appropriate privacy and compliance advisors. Operational convenience should not allow one compromised login to redirect funds, alter routing or download more protected information than the person's job requires.
Plan for outages and vendor transitions
Define how the practice identifies transactions held during a clearinghouse, payer or system outage and how they will be released without duplication. Preserve submission files, acknowledgements, remits and trace data according to policy. Before changing vendors, inventory active payer enrollments, receiver relationships, open claims, ERA routing and EFT status; then run parallel reconciliation where feasible. Establish a cutoff plan and confirm that older remittances remain accessible. After recovery or migration, compare expected claim volume, acceptance, ERA counts and deposits so missing batches are found before filing or appeal deadlines expire.
Measure the complete electronic pathway
A useful monthly scorecard connects submission volume, first-pass acceptance, unresolved rejections, missing acknowledgements, ERA receipt, unmatched deposits and unposted remits. Add age and dollar value so a small number of material exceptions remain visible. Assign every exception an owner and final status. Measuring each handoff prevents a strong claim-acceptance rate from hiding lost remittances, delayed deposits or posting backlogs farther downstream.
Working reference
Claims-to-payment transaction map
Each step needs a verified connection and an exception owner.
| Step | What it does | Operational check |
|---|---|---|
| EDI claim | Sends structured claim data, commonly through an 837 transaction | Confirm payer ID, sender and billing relationship |
| Acknowledgement | Reports whether the transaction or claim was accepted for processing | Review rejections and route corrections |
| ERA | Explains adjudication, payments and adjustments, commonly through an 835 | Confirm the correct remittance receiver |
| EFT | Moves the payer deposit to the enrolled bank account | Match the deposit to the remittance |
| Posting and reconciliation | Applies outcomes to accounts and identifies differences | Resolve missing, unmatched or incorrect items |
Common questions
Questions practice teams ask
Does EFT include the claim-level payment detail?
No. EFT moves the money, while the ERA provides the remittance detail used for posting and reconciliation.
Can an ERA arrive separately from the EFT?
Yes. The remittance and deposit are separate parts of the payment workflow and may follow different routing.
Does credentialing activate EDI automatically?
No. Claim, ERA and EFT enrollments may require separate setup and confirmation.
What is a payer ID used for?
It helps route an electronic transaction to the intended payer connection.
What should a practice reconcile?
Connect the submitted claim, acknowledgement, ERA, bank deposit and posting batch, then investigate any mismatch.
Primary references
Sources and further reading
Requirements can change. Use these primary sources to confirm the current rule that applies to the payer, service and date of care.
Ready to turn this guidance into action?
Tell us what is happening in your practice, and we will help you identify the most useful next step.