Skip to main content
Claim EDI, electronic remittance advice (ERA), and electronic funds transfer (EFT) are different functions. Claim EDI maps an electronic claim route and trading partner; ERA is the X12 835 explanation of adjudication sent to an authorized receiver; EFT is the payment instruction to the enrolled payee’s financial institution.3 A payer may use separate forms, one combined workflow, a clearinghouse authorization, an open payer-ID route, or a delegated enrollment utility. Distinct functions do not imply a fixed number of applications. Dental attachments are another route to configure only where the payer and claim require supporting material.

​
The three, side by side

​
Prerequisites

  • The contract, state enrollment, out-of-network submission authority, or other basis for the specific claim route
  • The applicable billing or payee entity’s W-9 and tax documentation, with consistent legal-business data
  • The billing, rendering, pay-to, location, and NPI/TIN relationships the payer requires; a Type 2 NPI only where the enrolled organization is part of the route
  • Bank evidence for the legally permitted, payer-enrolled payee account
  • A clearinghouse or other trading partner chosen that supports the transactions and payer routes you need, including 837D for routine dental-benefit claims. See Choose a clearinghouse.

​
Steps

1

Get your submitter and receiver IDs from the clearinghouse

Identify the clearinghouse or other trading partner and its submitter and receiver identifiers. A shared submitter can sometimes carry claims for multiple enrolled billing entities; other routes require an entity-specific authorization. Either design needs controls that populate the correct payer ID, product, billing provider, rendering provider, location, and tax identifiers.
2

Configure each intended electronic claim route

For each intended electronic claim route, ask the clearinghouse and payer whether enrollment or authorization is required. Some payer IDs are available through the trading partner without a provider-specific EDI application. Others require a signed form, portal approval, or linkage for particular billing entities or products. Confirm that the route supports the transaction being sent. Routine dental-benefit claims usually use the 837D, while some covered medical or institutional pathways use the 837P or 837I.Track the payer ID, product, enrolled identifiers, submission status, approval if required, and usable effective date. “Submitted” is not “approved,” but do not invent an approval step for an open route that does not have one.
3

Set up the attachment service

A payer may request radiographs, periodontal charts, narratives, photos, or other material for a particular claim, authorization, or audit. The accepted route varies: a payer portal, clearinghouse-integrated attachment, Vyne Dental’s FastAttach (the NEA network), DentalXChange, mail, or another specified channel. An NEA number in a claim is one supported workflow, not a universal dental-claim requirement.1Configure only the routes the target payers accept and test retrieval or receipt. A March 2026 HIPAA rule adopts the X12 275 attachment standard with a May 26, 2028 compliance date; that standard changes covered electronic exchanges but does not by itself guarantee that a current portal or vendor disappears. See Dental attachments.2
4

Configure ERA where requested

For each health plan from which you request standard ERA, identify the authorized receiver and the provider/payee identifiers the plan uses. The receiver may be the current clearinghouse, another vendor, or a direct endpoint.ERA and EFT are separate functions and can route independently. A payment can reach the intended bank while the 835 continues to a former receiver, creating manual retrieval and posting work.When you change clearinghouses, inventory the ERA relationships that point to the former receiver and follow each affected health plan’s change process. Some require a new enrollment; others support a receiver update through a clearinghouse, utility, or portal. Do not assume that changing claim EDI automatically moves ERA.
5

Configure EFT where elected or required

Enroll the account of the legally permitted payee that the health plan recognizes for the product and identifiers. In a conventional dentist-owned PC/MSO structure, that will generally be the professional entity’s account; in another lawful ownership and enrollment model, determine the correct payee from the governing state law, payer record, and contract rather than the acronym “PC.”Options:
  • The health plan’s own portal or form; for Delta, start with the member company identified for the service location and product
  • CAQH EnrollHub, which lets you submit bank details once for participating payers
  • CMS-588, if the group bills Medicare at all
Do not route professional revenue to a support-company account merely because it is the group’s operating account. Match the bank account to the authorized payer payee and the state’s ownership/control rules. An Arizona registered lay-owned dental business, for example, does not share the same structural premise as a dentist-owned PC/MSO arrangement. See Why DSO banking is different.
6

Convert any virtual credit card payer to EFT

If a health plan sends a virtual credit card, identify the card terms and request standard ACH EFT if that is the desired method. CMS states that a health plan must comply when a provider requests the adopted ACH EFT standard, subject to completing that plan’s enrollment process.4 Card acceptance may create merchant fees, but the rate is processor- and agreement-specific. See Paper checks and virtual credit cards.
7

Test before you rely on it

Test the functions actually configured:
  • For electronic claims, confirm acceptance using the acknowledgement the route supports, such as a 277CA, and then verify payer adjudication
  • When a claim or authorization needs an attachment, confirm the receiving party can retrieve or associate it
  • If ERA was elected, confirm the first 835 reaches the authorized receiver and can post
  • If EFT was elected or required, confirm the payment reaches the enrolled payee account
  • For paired ERA and ACH EFT, confirm reassociation using the matching TRN data3
8

Record everything in the enrollment grid

Record each relationship at its actual grain: state/program, health plan or payer, product, payer ID, contract party, billing/pay-to entity, rendering provider, location, trading partner, claim route, attachment route, ERA receiver, EFT payee account, statuses, and effective dates.

​
Multi-entity considerations

Do not use a theoretical three-by-payer-by-PC enrollment count. First determine what the health plan and trading partner key each function to:
Use the completed matrix to evaluate clearinghouse route coverage, payer-ID accuracy, enrollment support, acknowledgement visibility, and ERA migration capability. See Choose a clearinghouse.
A group may use one trading-partner submitter configuration across multiple billing entities if the route permits it, but the claim generator still needs controls that prevent one entity’s TIN/NPI, rendering provider, location, or payer product from leaking into another’s claim.

​
Verify it worked

  • Each intended electronic claim route documented; approval obtained where required; correct 837 transaction confirmed
  • Each required attachment route configured and receipt/retrieval tested
  • Each elected ERA relationship points to the intended current receiver
  • Each elected or required EFT relationship points to the authorized payee account
  • VCC payment methods reviewed and ACH EFT requested where desired
  • First electronic claim accepted through the acknowledgement the route supports and adjudication verified
  • For each elected ERA route, first 835 received and posted
  • For each elected or required EFT route, first payment landed in the correct account
  • For paired ERA and ACH EFT, 835 and deposit reassociate by TRN
  • Relationship grid updated at the applicable program, payer, product, entity/provider, location, and transaction-route grain

​
Common failure modes

​
Sources

  1. Vyne Dental, FastAttach; DentalXChange, attachment service; payer-side example: GEHA, NEA FastAttach instructions.
  2. Administrative Simplification: Adoption of Standards for Health Care Claims Attachments Transactions, 91 FR 14350 (final rule, March 24, 2026; X12N 275 v6020, 277 RFAI; compliance May 26, 2028): Federal Register.
  3. CMS, Health Care Payment and Remittance Advice and EFT and payment/remittance reassociation basics (PDF).
  4. CMS, HIPAA Administrative Simplification FAQs (PDF). Providers may request standard ACH EFT and X12 835 ERA, while health-plan enrollment remains required for the selected transactions.
Last modified on August 21, 2026