Complete EDI enrollment for ERA and EFT with a payer to enable electronic remittance delivery and direct deposit
domain: x12.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the enrollment pathway for each payer: most commercial payers offer ERA/EFT enrollment through CAQH EnrollHub (formerly CAQH CORE); some payers have proprietary portals; Medicare requires CMS-588 form submission through Palmetto GBA, Noridian, or the applicable MAC
For CAQH EnrollHub: register your organization, submit banking information (routing number, account number marked as YOUR_ROUTING_NUMBER/YOUR_ACCOUNT_NUMBER in test), select the payers you wish to enroll, and choose transaction types (ERA 835, EFT CCD+ or CTX format)
Provide your clearinghouse receiver ID or your own ISA ID so the payer knows where to route the 835 ERA files; if using a clearinghouse as an intermediary the clearinghouse will provide their receiver ID for you to enter
Await enrollment confirmation from each payer (1–30 business days depending on payer); some payers issue a test ERA file and require you to confirm receipt before activating production delivery
Verify EFT activation by confirming a small test deposit (if the payer sends one) or monitoring for the first live 835 remittance correlated with a submitted claim; reconcile the BPR EFT trace number against your bank statement
Maintain enrollment records and resubmit ERA/EFT enrollment when banking information changes or when onboarding to a new clearinghouse, as the receiver ID in payer systems must be updated
Known gotchas
ERA enrollment and EFT enrollment are separate processes even through CAQH EnrollHub; completing EFT enrollment alone does not result in electronic 835 files — both must be enrolled independently
Some payers require a voided check or bank letter for EFT setup rather than accepting routing and account numbers entered online; initiate paper-based banking verification early as it adds significant processing time
After activation, the first 835 ERA from a new payer enrollment may arrive on a different schedule than subsequent remittances; monitor the first 30 days closely for any enrollment-related routing issues before assuming the workflow is stable
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?