Solutions · Receivables & collections
Every receivable balance is derived from an append-only event ledger — corrections are counter-entries, never edits — and it ties out two ways every period. Collections are opt-in and email-only.
Reconciliation
The roll-forward derives the closing balance from the event ledger and compares it with your open-invoice view — with credit memos and write-offs called out as the explained reconciling items.
Because balances are always derived from the events and never stored, the detail can’t quietly drift from the summary.
A residual is a drift detector, not a rounding excuse.
Period Mar 2026
Every figure is a derived balance over an append-only event ledger · corrections post as counter-entries
What's in the box
Append-only events
Every balance is derived from an append-only event ledger. Corrections are counter-entries, never edits — the history stays intact and inspectable.
Two-way tie-out
The event ledger and your open invoices reconcile to the same closing balance every period, with credit memos and write-offs shown as explained items.
Dual-clock aging
Age receivables two ways at once — against the invoice due date and against the date the contract said payment was due — and see the gap between them.
Roll-forward report
Opening + invoiced − collected − credit memos − write-offs = closing, by month, quarter, or year, carried from the earliest event so a windowed opening is right.
Cash-cycle KPIs
DSO, median days-to-pay, and collection effectiveness — derived live from the same event ledger, not a stale nightly snapshot.
Collections that never overstep
Reminders are opt-in and email-only. They stop when a customer pays or promises to pay, and the cadence never initiates a charge.
Every organization gets the full subledger from day one. Watch it tie out before you let it post anything — the accounting judgment stays yours.