How a status check runs
On demand, in batches or from your own rules, and you hear only when something moves.
Claim status in the docs →- Step 1Start a check, or let a rule
- Check any claim on the spot, send thousands in one batch, or let a rule start checks, such as every claim with no response after 30 days. A sweep starts about a week after a claim was sent and repeats until the claim is paid, denied or closed.
- Step 2Daybook runs the 276/277
- The 276 goes to the payer through the clearinghouse routes you already use, and the 277 is read into a plain status: paid, denied, pending, in process, returned or not on file. Every raw 276 and 277 is stored encrypted.
- Step 3You hear about changes
- Your system gets an event only when the status differs from the last check, so a quiet claim stays quiet and a moved one gets attention.
- Step 4The next step
- A denied claim flows into denials and appeals. A paid one goes to reconcile and post. A silent claim escalates to a payer call.
For medical billers
Claim status is follow-up that never ends. Daybook asks every payer where each claim is, over EDI with no portal login, and writes the answer on the claim in words with the next step. A clearinghouse rejection is kept apart from a payer's denial, since the two need different fixes, and your billers decide every rework, appeal and write-off.
- Paid, Denied, Closed with no payment, Info requested, Pending at payer, Resubmit or Unable to verify, each with its next step
- A rule such as every claim with no response after 30 days starts the checks, and the Check status button sends a 276 on the spot
- Each payer's profile shows whether it answers claim status over EDI, beside your enrollments with that payer
- A clearinghouse rejection kept apart from a payer denial, since the two need different fixes
- A silent claim escalated to a payer call under your own rules
More for medical billers: the billers page and claim status automation for billing companies.
For dental billers
Every unpaid dental claim gets a 276 through the clearinghouses you use, and the 277 answer lands on the claim in plain words. A dental 277 can say the claim is waiting on an attachment or a narrative, and your biller sees that the day it changes, before any remit arrives. Daybook writes what the payer said and does not change the claim on its own.
- A 276 for every unpaid dental claim through the clearinghouses you use, with no portal login
- A 277 that says the claim is waiting on an attachment or a narrative, read into plain words
- An event to your system only when a status moves
- A payer call when the clearinghouse answer is not enough
More for dental billers: the dental page and claim status for dental offices.
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 claim status that is your follow-up rules: when a claim counts as quiet, when it is checked again, and when it becomes a call.
- Your rule for a claim with no response, such as 30 days
- What each 277 status means for your next step
- When a silent claim becomes a payer call
Where it shows up
- The claim in your PM or EHR
- The status in plain words and the next step
- A signed webhook
- claim.status_changed, only when the status moves
- The Daybook dashboard
- The claims that moved, and the quiet ones re-asked
Run claim status from your own system
Send the check, let a rule re-ask the quiet claims, and hear back only when a status moves. The same operations are MCP tools for your own agents.
Read claim status in the docs →Frequently asked questions
What billing teams ask us about claim status, and our answers.
How does automated claim status checking work?
Daybook sends an X12 276 for each claim and reads the 277 that comes back into a plain status with the next step. Checks start on demand, in batches or from your own rules, repeat until the claim is paid, denied or closed, and your system hears only when the status changes.
Does claim status automation need a login for each payer?
No. The 276 goes over EDI, so there is no portal login. Where a payer will not answer over EDI, Daybook calls the payer instead, under your rules.
How often is each claim checked?
A sweep starts about a week after a claim was sent and repeats until the claim is paid, denied or closed, and a rule of your own, such as every claim with no response after 30 days, can start checks too. Any claim can be checked on the spot.
Does Daybook change the claim or send appeals on its own?
No. Daybook writes what the payer said onto the claim and does not change the claim on its own. A denial gets its cause and a drafted appeal, and your billers send every appeal and make every write-off call.
What is the difference between a clearinghouse rejection and a payer denial?
A rejection means the claim never reached the payer's system, usually over a missing or malformed field, and needs your biller to fix and resend it. A denial is the payer's answer on a claim it accepted, with CARC and RARC codes, and may need an appeal. Daybook keeps the two apart on the claim so the next step is the right one.
Is any of the work offshored?
No. Agents do the payer work, and your team keeps every billing decision. Nothing is offshored.