Remittance and posting

“What did the payer pay, did the money arrive, and how do we post it?”

The Remittance and posting workflow turns 835s into postings. Daybook pulls each remit, matches it to your claims and to the bank deposit, and proposes the posting entries for each payment. Unmatched payments are flagged, and every denied line flows into denials and appeals.

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: Remittance and posting
Stage: After payment
Primary users: Payment posters, reconciliation and finance
Core question: What did the payer pay, did the money arrive, and how do we post it?
Transactions: X12 835, bank deposits
In scope: Retrieve · Match · Propose posting · Flag unmatched
Consumption options: API · Webhooks · MCP

What this workflow enables

Receive every 835 as structured data, adjustments and remark codes included.
Match each payment to its claims and to the deposit that carried it.
Get proposed posting entries ready for your PM system.
See payments with no matching deposit, and deposits with no 835.

Typical flow

Remit arrives
From the clearinghouse or a portal. You receive remit.received.
Match
Daybook matches it to claims and to the deposit. You receive remit.matched, or payment.unmatched.
Posting proposed
posting.proposed with payment, adjustment and patient-responsibility entries.
Approve and write back
Approve with POST /v1/remits/{id}/posting/approve. posting.approved is where your write-back picks it up.

Step through it

Step 1 of 4: Remit arrives, sends remit.received

remit.received

{
  "id": "evt_01JBXS9A4C6E8G0J2M4P6R8T10",
  "type": "remit.received",
  "created_at": "2026-10-22T09:15:00Z",
  "mode": "live",
  "data": {
    "remit": "remit_01JBXF8B3C4V",
    "payer": "keystone"
  }
}

Journeys in this workflow

Post a paymentFrom 835 to posted entries without keying.

Reconcile the bankMatch deposits to remits and find what is missing.

Find missing remitsMoney arrived with no 835. Pull it from the portal.

Route denialsDenied lines go straight to denials and appeals.

Use cases

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

835 to posting in your PM systemEvery 835 matched to its claims and deposit, and posted to the PM system once a person approves it.Find a missing remit in the payer portalWhen a payment shows up with no 835, Daybook signs in to the portal and brings the remit back.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.Reconcile deposits to remitsEvery deposit tied to its 835, and finance hears about each one that is not.

APIs powering this workflow

GET/v1/remitsList remits GET/v1/remits/{id}Retrieve a remit POST/v1/remits/{id}/posting/approveApprove a posting

Events you receive

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

Event	Sent when
`remit.received`	A new 835 arrived.
`remit.matched`	The remit matched its claims and deposit.
`payment.unmatched`	A payment or deposit has no match.
`posting.proposed`	Posting entries are ready to review.
`posting.approved`	Posting entries were approved and are ready to write back.

Example event

{
  "id": "evt_01JBXS9A4C6E8G0J2M4P6R8T0W",
  "type": "posting.proposed",
  "created_at": "2026-10-22T09:15:00Z",
  "mode": "live",
  "data": {
    "remit": "remit_01JBXF8B3C4V",
    "payer": "keystone",
    "payment_amount_cents": 31200,
    "entries": [
      {
        "type": "payment",
        "claim": "A-20817-1",
        "amount_cents": 31200
      },
      {
        "type": "adjustment",
        "claim": "A-20817-1",
        "code": "CO-45",
        "amount_cents": 6800
      },
      {
        "type": "transfer_to_patient",
        "claim": "A-20817-1",
        "amount_cents": 3000
      }
    ]
  }
}