How an enrollment runs
From the gap in a provider's enrollments to the first 835 and the first EFT.
ERA and EFT enrollment in the docs →- Step 1Submit
- One request names the provider, the payer, ERA, EFT or both and, for EFT, the bank account. Gaps are found from each provider's own claims by TIN, NPI and payer, so you know which enrollments are missing.
- Step 2Daybook works the enrollment
- It submits through the payer's channel, an enrollment API, a portal or a form, and checks status on a schedule. Each portal run waits for a named person on your team to approve it.
- Step 3Action required
- When the payer wants a signature, a document or a bank letter, you hear what it asked for and by when. The practice or the biller signs, and the agent picks the enrollment back up on its own.
- Step 4Approved, then proven
- The payer confirms. Daybook counts the enrollment as done only when the first EFT matches the first 835 at the right destination, and opens a case when a paper check arrives where EFT should be running or an 835 goes to the wrong place.
For medical billers
Enrollment is where a new client stalls. Daybook finds the gaps from what each provider bills, submits through the payer's channel, works the Availity wizard and its bulk uploads, and tracks every enrollment in one place across your clients. Your enrollment lead approves each portal run.
- Gaps found from each provider's own claims by TIN, NPI and payer, ranked by the dollars behind them
- Availity's enrollment wizard filled by the agent, and bulk uploads of up to 5,000 rows with the error file read and the resubmit staged
- A form-only payer's form filled from the onboarding record, signed, sent by fax, mail or portal upload and followed up
- Where a payer reports status only by phone, Daybook calls, no more than once a week per enrollment
- A bank change, a new TIN or a new NPI turned into a planned set of re-enrollments
More for medical billers: the billers page and the ERA enrollment service for billing companies.
For dental billers
Dental ERA and EFT enrollment runs across clearinghouses and dental payer portals, and each one asks for something different. Daybook tracks every enrollment from the first form to the first ERA. When one waits on a bank check or a signed letter, it goes to the person who owns that step, and the next step queues up once it is done.
- Enrollment across clearinghouses and dental payer portals, tracked from first form to first ERA
- A bank check or a signed letter routed to the person who owns that step, with the next step queued behind it
- Every enrollment in a plain state: in place, stuck, not yet checked or not required. Not required always says who checked
- ERA, EFT and 837 setup covered for every office you bill for
More for dental billers: the dental page.
Starts from your knowledge base
Your billing company's own rules, appeal workflows, payer quirks and call scripts are what Daybook runs. You send the documents, Daybook imports them as payer guides, shows you what it produces, and you adjust it together on a call. Each solution runs on its own, so you start with one and add the next.
For enrollment that is your onboarding record for each provider and payer, and who on your team signs what.
- The onboarding record each form is filled from
- Who owns each signature, document and bank letter
- Which payers take a wizard, an API or a form
Where it shows up
- The Daybook dashboard
- Every provider's enrollment with every payer, what each one is waiting on, and reminders to the person who owns the step
- A signed webhook
- enrollment.submitted, enrollment.action_required, enrollment.approved and enrollment.rejected
Enroll from your own system
Submit an enrollment in one request. Daybook works it with the payer and tells you, by signed webhook, when a signature or a letter is needed and when the payer approves.
Read ERA and EFT enrollment in the docs →Frequently asked questions
What billing teams ask us about ERA and EFT enrollment, and our answers.
What is the difference between ERA enrollment and EFT enrollment?
ERA enrollment asks the payer to send its electronic remittance advice, the 835, to the clearinghouse you choose. EFT enrollment asks the payer to pay by bank transfer instead of a paper check. Payers enroll the two separately, so a provider can have one without the other, and Daybook submits either or both in one request.
Who signs the enrollment forms?
The practice or the biller signs wherever a payer wants a wet signature. Daybook fills the form from the onboarding record, routes it for an e-signature or ink, sends it by fax, mail or portal upload and follows up. Anything only the customer can do goes to them as one request, with reminders.
Does anything go to a payer portal without our approval?
No. Each portal run waits for a named person on your team to approve it. Status checks run on their own, and a submission goes through only after that approval.
When is an enrollment counted as done?
When the money proves it. Daybook counts an enrollment done when its first EFT matches its first 835, at the right destination, on or after the effective date. A paper check where EFT should be running, an 835 at the wrong destination, an overdue remit or a payer switching to virtual card each opens a case.
How are enrollment statuses kept current?
Daybook checks status on a schedule and reconciles every submission onto the tracker, and statuses your team sets by hand are kept out of those updates. Activation dates are set so ERAs are not cut off early, and where a payer reports status only by phone, Daybook calls, no more than once a week per enrollment.
Is Daybook a clearinghouse?
No. Daybook is not a clearinghouse and does not replace yours. It is one door to every clearinghouse and payer channel your clients already use, and an enrollment it submits points the payer's remits and payments at the clearinghouse you choose.