ERA and EFT enrollment

“Will this payer send us 835s and pay us electronically?”

The ERA and EFT enrollment workflow gets providers set up to receive electronic remits (835s) and electronic payments. Daybook submits the enrollment, tracks it with the payer, and handles the action-required paperwork payers send back, so downstream workflows such as remittance and posting have something to work on.

Build this with AIA brief with this workflow's endpoints, events and docs, ready for your assistant to scaffold the integration in your stack.

At a glance

Workflow: ERA and EFT enrollment
Stage: Onboarding, before remits and payments flow
Primary users: Provider onboarding and credentialing teams
Core question: Will this payer send us 835s and pay us electronically?
In scope: Submit enrollment · Track status · Action required · Approval
Downstream workflows: Remittance and posting · Denials and appeals
Consumption options: API · Webhooks · MCP

What this workflow enables

Submit ERA, EFT or both for a provider with a payer in one request.
Track every enrollment to approval without checking each portal.
Get told the moment a payer wants a signature, a document or a bank letter.
Know when 835s will start, so remittance can pick them up.

Typical flow

Submit
POST /v1/enrollments with the provider, the payer, the transactions and, for EFT, the bank account. You receive enrollment.submitted.
Daybook works the enrollment
It submits through the payer's enrollment channel, portal included, and checks status on a schedule.
Action required
When the payer wants something, you receive enrollment.action_required with what it asked for and by when.
Approval
enrollment.approved when the payer confirms. Remits start flowing into the remittance workflow.

Step through it

Step 1 of 4: Submit, sends enrollment.submitted

enrollment.submitted

{
  "id": "evt_01JBXP3A4C6E8G0J2M4P6R8T10",
  "type": "enrollment.submitted",
  "created_at": "2026-10-29T13:00:00Z",
  "mode": "live",
  "data": {
    "id": "enr_01JBXC7F2D9R",
    "payer": "meridian",
    "transactions": [
      "era",
      "eft"
    ]
  }
}

Journeys in this workflow

Onboard a new providerEnroll a new NPI with every payer it bills.

Clear the paperworkAnswer signature and document requests as they come.

Switch a bank accountRe-enroll EFT when the practice changes banks.

Audit coverageSee which providers are set up with which payers.

Use cases

What teams build on this workflow, each with a prompt you can paste into Claude, ChatGPT or Cursor.

ERA and EFT enrollment at provider onboardingA provider added to your product is enrolled with each payer for 835s and electronic payment, tracked to approval.

APIs powering this workflow

POST/v1/enrollmentsSubmit an enrollment GET/v1/enrollments/{id}Retrieve an enrollment

Events you receive

Subscribe to these with a webhook endpoint. Every event is signed; see Verifying signatures.

Event	Sent when
`enrollment.submitted`	Daybook submitted the enrollment to the payer.
`enrollment.action_required`	The payer wants something: a signature, a document, a letter.
`enrollment.approved`	The payer confirmed. ERA or EFT is live.
`enrollment.rejected`	The payer rejected it, with the reason.

Example event

{
  "id": "evt_01JBXP3A4C6E8G0J2M4P6R8T0W",
  "type": "enrollment.action_required",
  "created_at": "2026-10-29T13:00:00Z",
  "mode": "live",
  "data": {
    "id": "enr_01JBXC7F2D9R",
    "payer": "meridian",
    "transactions": [
      "era",
      "eft"
    ],
    "action_required": {
      "type": "verification_letter",
      "description": "Upload a bank letter confirming the account for EFT.",
      "due_by": "2026-11-12"
    }
  }
}