ERA enrollment service for billing companies
An ERA enrollment service for billing companies sets up every provider you bill for to receive electronic remits (ERA) and electronic payments (EFT) from every payer, and tracks each enrollment until the money arrives. Daybook Health works out which ERA, EFT and EDI enrollments each provider needs from what it actually bills, ranks the gaps by the dollars behind them and files them through Availity, Stedi or the payer's own form. An enrollment counts as live only when its first EFT matches its first 835. Your team keeps the signatures and the decisions.
On this page
Customer story: How Ease Health automated ERA enrollments and claim follow-up in four weeks.
What is ERA and EDI enrollment?
ERA enrollment tells a payer to send a provider's remittance advice electronically, as an X12 835 file, instead of on paper. Some teams call it 835 enrollment. EFT enrollment tells the payer to deposit payments straight into the provider's bank account instead of mailing a check. EDI enrollment is the wider term. It covers ERA, EFT and claim submission (the 837), each set up per provider, per payer and per transaction.
A provider needs ERA and EFT with each payer before remits can post without anyone keying paper. Enrollment is filed through a portal, a clearinghouse or a signed form. One detail trips teams up when they change routes. Stedi, a clearinghouse, notes that "ERA enrollment is exclusive to one clearinghouse" and that switching a provider to Stedi "stops ERA delivery through the previous clearinghouse." So moving a practice to a new clearinghouse means redoing its ERA enrollments.
Why enrollment is hard for a billing company
A single practice has a handful of enrollments. A billing company has every provider at every client, times every payer each one bills. Each new client brings its own list, some enrollments half done by a previous biller, and some payers still mailing paper.
The hard part is keeping track. Each enrollment sits in a different state at a different payer, and the same questions come up every week:
- Which providers are still getting paper remits, and from which payers?
- Which submissions went in, and which ones did the payer accept?
- Which ones are waiting on a signature from the practice?
- When does the new ERA start, and will the old route stop before it does?
When nobody can answer those quickly, remits arrive on paper, posting slows and money sits unmatched. For the steps in a sound workflow, see what belongs in a payer enrollment workflow and how to track ERA enrollment across many clients.
How Daybook runs ERA enrollment services
Daybook's agents run enrollment from the first form to the first ERA. This is ERA enrollment automation with your team on every decision.
Find the gaps from what each provider bills
Daybook reads each provider's claim history by TIN, NPI and payer, and works out which ERA, EFT and 837 enrollments it needs. It compares that with the enrollment record and ranks the gaps by the dollars at risk. A payer Daybook cannot route is listed for your team, not guessed.
Each provider is onboarded once: legal name, TIN, NPIs checked against NPPES, the signer, the payer mix and a letter of authorization for ERA and EFT. No enrollment asks your billers for the same thing twice.
Every enrollment in one tracker
Enrollments are added by hand, or start on their own when a new payer appears for a provider. Each one lands in a queue for a biller to accept. Every enrollment shows a plain state: live, stuck, not yet checked or not required. Not required always says who checked.
Portal, API and form steps done by the agent
- Availity. The agent signs in, handles two-factor codes and fills the ERA/EFT enrollment wizard, up to 10 payer ids per request. It runs bulk uploads of up to 5,000 rows, reads the error file and stages the resubmit. It downloads a payer's enrollment form and attaches the signed one.
- Stedi. Enrollments go through Stedi's enrollment API, and their status is read back.
- Form-only payers. The form is filled from the onboarding record, signed by e-signature or ink, then sent by fax, mail or portal upload and followed up.
Each live portal run waits for a named person on your team to approve it. A run that cannot finish stops with a plain reason, such as a pending two-factor code or a portal error, and a screenshot.
Status checked on a schedule
The agent reads each payer's enrollment instructions and says whether it can finish alone or needs a person, and for what. It checks status on a schedule, and every submission is reconciled onto the tracker. Where a payer reports status only by phone, Daybook calls, no more than once a week per enrollment. Activation dates are set so ERAs are not cut off early.
Live only when the money arrives
An approved enrollment counts as live only when its first EFT matches its first 835, at the right destination, on or after the effective date. After that, Daybook watches for decay. It opens a case when a check arrives where EFT should be live, an 835 goes to the wrong destination, a remit is overdue or a payer switches to virtual card. A bank change, new TIN or new NPI becomes a planned set of re-enrollments, in order, without breaking the ones that work.
What your team still decides
Agents do the payer work, and your team keeps every billing decision. Your billers accept each enrollment into the queue and approve parked submissions in a batch. The practice or biller signs wherever a payer wants a wet signature. Anything only the customer can do goes to them as one request, with reminders. Billers make every call on appeals, write-offs and posting.
Nothing is offshored, so there is none of the data-handling, quality or compliance exposure of large offshore teams.
ERA posting automation once enrollment is live
Enrollment is the first half. Once ERAs flow, every 835 is proven to the cent and matched to its claims line by line. Each settled deposit is matched to its 835 on the trace number, so you can see per claim whether it was paid, posted and deposited.
For remittance posting automation, Daybook turns each 835 into the lines a biller would post: paid, contractual write-off, patient responsibility, still owed and next payer. The lines always add up to the claim payment, and each claim is marked post, review or refuse. Daybook never posts a payment without your click. Payments post through the path your system already has, and anything that does not balance is held for your posting lead. See how to balance and match every remit.
How it connects to your systems
Nobody switches software. Daybook connects to the PM systems, EHRs and clearinghouses your clients use. Where a system has no API, it builds a browser automation and wraps it as an integration. A whole portal action (signing in, two-factor authentication, then the task) is exposed as a single API call.
Daybook is not a clearinghouse and does not replace yours. It files enrollments through Availity, Stedi, payer forms and portals, and reads remits from the routes your clients already use.
Daybook can also run inside your own tools so it looks native to your team, and your clients never need to know which infrastructure is behind it.
Proof from a live deployment
Ease Health runs Daybook for status checks, remit balancing and payer enrollment. Enrollment work went from 20 hours to 13 hours per batch of 50 enrollments, with review on. It took 4 weeks from kickoff to code in Ease's repository.
"Daybook came in, mapped how our claims move across our systems, and built what was missing inside of what we already have. Status checks, remit balancing and payer enrollment now run on their own, and the team works the exceptions instead of the queue." Raymond Wang, CTO, Ease Health
Who this is for
This page is for medical billing companies and RCM firms onboarding many practices, tracking enrollment across many clients rather than one office. Daybook works through billing companies, RCM firms and software vendors. It does not bill for providers and will not compete with the RCM companies it works with.
Dental billing companies and the billing offices of dental groups get the same enrollment work across dental clearinghouses. See Daybook for dental billers and how dental ERA and EFT enrollment works. EHR and practice management vendors can run it inside their own product, under their own name. See Daybook for EHR vendors.
How pricing works
Pricing is usage-based, with no subscriptions and no seats. Customers pay only for what Daybook processes. A forward-deployed engineer can handle onboarding, starting from the rules, scripts and data you already have.
After the BAA, Daybook starts on one practice, or one payer and one system, with milestones agreed up front. It expands to your other practices once they are met. More on the model: how usage-based pricing works for claims automation.
Other ways to get enrollment done
Daybook is not the only route. For some teams, another one fits better.
| Option | Who it is for | ERA/EFT enrollment | Pricing |
|---|---|---|---|
| Daybook Health | Billing companies, RCM firms, EHR vendors, dental billing teams | Found from each provider's claims, tracked payer by payer until the first ERA | Usage-based, no seats |
| Your clearinghouse (Stedi as the example) | Anyone already on it | "Stedi handles the entire enrollment process for you", one clearinghouse's payers | "free on every Stedi production plan" |
| Zentist Remit AI | DSOs with 5 or more locations | "enrollment services for ERA. and EFT", up to 30 payers | Quote only, no public price |
| Lassie | Independent dental practices | "Enrolls electronic payments", with reconciliation and posting | "Lassie gets paid when it does work", no public price |
- Best for one clearinghouse and few clients: your clearinghouse. If every client already sends claims through one that handles enrollment for free, as Stedi does on its production plans, start there. It may be all you need.
- Best for a DSO buying remit automation: Zentist. It includes ERA and EFT enrollment with Remit AI, but it requires a minimum of 5 locations and caps enrollment at 30 payers. See Zentist alternatives.
- Best for a single dental office: Lassie. It sells to independent practices and pairs EFT enrollment with reconciliation and posting.
- Best for a billing company with many clients, payers and clearinghouses: Daybook. Enrollment for every provider at every client sits in one queue, alongside claim status, remits and underpayments.
Phone-call vendors such as SuperDial list "Credentialing & Enrollment," but there it means payer panel status, effective dates and missing documentation, not ERA or EFT setup. Daybook's EDI enrollment services cover ERA, EFT and 837 setup, not credentialing or getting a provider in network.
Is this right for you?
It likely fits if:
- You onboard new practices often and each one arrives with its own enrollment backlog.
- Your clients use more than one clearinghouse or PM system.
- Your posting team still keys paper remits from payers that could send 835s.
- Nobody can say, today, which enrollments are waiting on a signature.
It likely does not fit if you bill for one practice through one clearinghouse that already manages enrollment. It does not fit an individual practice either: Daybook works through billers and software vendors, not practices directly.
Related: claim status automation for billing companies, underpayment detection software and the best AI medical billing software for billing companies.