Platform module · 03 · Books — built
Know what you're owed before the bank asks.
Books sits on top of the invoice module and answers one question continuously: what is outstanding, how old is it, and where is it drifting? Aging buckets in the app, a CSV your bookkeeper already knows how to open, and nothing to reconcile — because Books never writes, it only reads.
The aging drawing
Four buckets, no surprises.
Specimen — illustrative ledger · fictional payers
| Invoice | Payer | Amount (CAD) | Age | State |
|---|---|---|---|---|
| INV-2201 | Meridian Energy Services | $12,400.00 | 12d | monitoring |
| INV-2198 | Caldera Field Ops | $8,750.00 | 27d | reminder scheduled |
| INV-2183 | Meridian Energy Services | $21,300.00 | 44d | overdue |
| INV-2166 | Stonebridge Industrial | $5,200.00 | 71d | overdue |
| INV-2140 | Caldera Field Ops | $17,900.00 | 104d | escalation review |
Hover a bucket to see which invoices it holds. Read-only, always — Books reports on the ledger, it never edits it.
What it does
We integrate with your accounting. We don't replace it.
Receivables, live
Open total and 0–30 / 31–60 / 61–90 / 90+ aging over every invoice your organization has linked — computed fresh on every view, visible to managers and admins in the field app.
Exports that just open
One CSV, QuickBooks-friendly columns, an open-receivables total in the footer. It opens clean in Google Sheets and Excel too — standard formats, nothing proprietary to break.
The agent reads the books too
Ask “what's outstanding?” and the memory module's agent includes the receivables line with its answer — same numbers, same source.
Read-only by construction
Books has no write path to the invoice ledger — not a permission setting, an architecture. Your ledger cannot be edited by a reporting view.
Founding organizations
Bring one stack of invoices.
Fifteen minutes and we'll tell you honestly what your aging picture would look like in Books.