Claim status

“Where is this claim, and has anything changed?”

The Claim status workflow keeps track of every claim you have sent. Daybook runs 276/277 status checks in real time and at volume, started by you or by your own rules, such as no response in 30 days. You hear about a claim only when its status changes.

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: Claim status
Stage: After submission, until payment or denial
Primary users: AR follow-up teams
Core question: Where is this claim, and has anything changed?
Transactions: X12 276 / 277
Triggers: On demand · Batches · Your rules
Consumption options: API · Webhooks · MCP

What this workflow enables

Check any claim's status in real time.
Check thousands in one batch.
Let rules start checks, such as every claim with no response after 30 days.
Hear about a claim only when its status changes.
Hand off to a payer call when the 277 is not enough.

Typical flow

Start a check, or let a rule
POST /v1/claim-status/checks, a batch, or a rule.
Daybook runs the 276/277
And reads the 277 into a normalized status: paid, denied, pending, in process, returned or not on file.
You hear about changes
claim.status_changed when the status differs from the last check.
Next step
Denied claims flow into denials and appeals. Silent ones can escalate to a payer call.

Step through it

Step 3 of 4: You hear about changes, sends claim.status_changed

claim.status_changed

{
  "id": "evt_01JBXR4A4C6E8G0J2M4P6R8T0W",
  "type": "claim.status_changed",
  "created_at": "2026-10-29T15:30:02Z",
  "mode": "live",
  "data": {
    "claim": "A-20817-1",
    "payer": "keystone",
    "previous": "in_process",
    "current": "paid",
    "check": "cs_01JBXE4H9M2T",
    "paid_amount_cents": 31200
  }
}

Journeys in this workflow

Chase silent claimsCheck every claim with no response after 30 days.

Confirm a paymentSee the paid amount and EFT number before the 835.

Catch denials earlyReact the day the status changes, not when the remit arrives.

Escalate to a callStart a payer call when the 277 says pending for too long.

Use cases

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

Nightly claim status sweep into your PM systemEvery unpaid claim checked over 276/277 overnight, and only the claims that moved come back to you.A Claude agent that works your AR listClaude checks each claim, reads the payer's last answer and the denial, and drafts the appeal for a person to approve.Recheck silent claims by phone until they moveClaims with no 276/277 answer get a payer call that repeats every few days and stops once the claim is paid.

APIs powering this workflow

POST/v1/claim-status/checksCheck claim status POST/v1/rulesCreate a rule

Events you receive

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

Event	Sent when
`claim_status.completed`	A batched check finished.
`claim.status_changed`	A claim's status differs from the last check.

Example event

{
  "id": "evt_01JBXR4A4C6E8G0J2M4P6R8T0W",
  "type": "claim.status_changed",
  "created_at": "2026-10-29T15:30:02Z",
  "mode": "live",
  "data": {
    "claim": "A-20817-1",
    "payer": "keystone",
    "previous": "in_process",
    "current": "paid",
    "check": "cs_01JBXE4H9M2T",
    "paid_amount_cents": 31200
  }
}