Remittance and posting

Daybook pulls every 835, matches it to its claims and to the deposit that carried it, and proposes the posting lines for your posting lead to approve.

How a remit is posted

From the 835 to approved posting lines, balanced to the cent, with nothing posted without your click.

Remittance and posting in the docs →
Step 1The remit arrives
From the clearinghouse routes your clients already use, from a portal pull when the 835 never came, or dropped in by a biller as an 835, .rmt or PDF.
Step 2Match
Daybook matches the remit to its claims line by line and to the settled deposit on the trace number, and proves it to the cent, provider-level adjustments included. A payment with no deposit, or a deposit with no 835, is flagged.
Step 3Posting proposed
Each 835 becomes 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.
Step 4Approve and write back
Your posting lead approves, and the approved lines go to your system through the path it already has. Anything that does not balance is held for a person. Daybook never posts a payment without your click.

For medical billers

Posting is where a billing company's day goes. Daybook receives every 835 as structured data, adjustments and remark codes included, from the routes your clients already run, and turns each one into posting lines your posting lead approves. Each paid line is also checked against the contract, and a short payment comes flagged with why.

  • 835s from the clearinghouse routes your clients already use, Stedi, Optum or Waystar, or pulled from a portal when the 835 never came
  • Each settled deposit matched to its 835 on the trace number, so you see per claim whether it was paid, posted and deposited
  • Each payment carrying its source, an ERA, an import or a manual entry
  • Each paid line checked against the contract rate on file, and a line paid under the expected amount flagged with the expected amount, the paid amount, the gap and how it was reached
  • Claims with no answer sent to the top of the status check, so a missing remit does not sit unnoticed

More for medical billers: the billers page and underpayment detection software.

For dental billers

Dental remits arrive through more than one clearinghouse. Daybook connects to each one, downloads the raw EDI files, parses the 835s and matches each payment to its claims, balanced to the cent before anyone posts it. A remit that does not balance is held for a person, and your posting lead approves every posting.

  • Every remittance pulled, matched to its claims and balanced to the cent before anyone posts it
  • The raw EDI files downloaded from the clearinghouse and parsed, with the adjustment and remark codes kept
  • A remit that does not balance held for a person
  • Nothing posted without your click

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 posting that is the way your posting lead works a remit today, and what your team does with one that does not match.

  • Your contract rates and fee schedules on file
  • How your posting lead wants each line marked
  • Who looks at a remit that does not balance

Where it shows up

Your PM or EHR, through its posting path
The approved posting lines, through the path your system already has
A signed webhook
remit.matched, payment.unmatched, posting.proposed and posting.approved
The Daybook dashboard
Each remit matched to its claims and deposit, and the ones held for a person

Post from your own system

Every 835 arrives as structured data, matched to its claims and deposit, with the posting proposed. Approve it in one call, and the approved lines come back as a signed webhook for your write-back.

Read remittance and posting in the docs →

Frequently asked questions

What billing teams ask us about remittance and posting, and our answers.

Does Daybook post the payments?

Daybook proposes the posting lines and your posting lead approves them. The approved lines go to your system through the posting path it already has, and nothing posts without your click.

How does Daybook get the 835s?

Through the clearinghouse routes your clients already use, Stedi, Optum or Waystar among them, or by pulling the remit from the payer's portal when the 835 never came. A biller can also drop in an 835, .rmt or PDF and bulk-apply the lines after review.

What happens when a remit does not balance?

It is held for a person. Every 835 is proven to the cent, provider-level adjustments included, and matched to its claims line by line, so a remit that does not add up never reaches posting until someone has looked at it.

Does Daybook match deposits to remits?

Yes. 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. A payment with no matching deposit and a deposit with no 835 are both flagged.

How does Daybook know a payer paid short?

Each paid line is re-adjudicated against the contract rate on file, from your contracted rates, published fee schedules, state rules and the patient's plan, or, before a contract is loaded, against the rate the same remit paid on matching lines. A line paid below the expected amount is flagged with the expected amount, the paid amount, the gap and how it was reached. The rules are fixed code, and lines with no rate on file are counted and shown, never guessed.

Who makes the write-off calls?

Your billers. Daybook turns each 835 into paid, contractual write-off, patient responsibility, still owed and next payer lines and marks each claim post, review or refuse. Your team decides every write-off and every posting.