Intelligence
The part that tells you something
The name of this product is a claim, so here is what backs it: a ledger that is continuously checked rather than periodically trusted, and reports that are computed from postings every time they are asked for.
What is in it
What the intelligence layer covers
An integrity engine, always running
Twenty-one rules over the whole ledger: unbalanced vouchers, orphaned allocations, negative stock, control accounts that disagree with their subsidiary, periods that should be closed, gaps in a numbering series. Each returns the rows that failed, not a red light.
A tamper-evident audit trail
Every recorded event is hashed with the hash of the event before it. Change one row in the database and every subsequent hash stops matching — and the Operations screen says so. Verified over 12,050 events in the load test.
Ageing and collections
Receivables aged into bands from the bill dates, then grouped by customer into a collections view with a stage worked out from how overdue the oldest bill is. The stage is derived on every load, so it cannot be stale.
Statements, computed not cached
Trial balance, profit and loss, balance sheet, cash flow and day book, all derived from postings. Forty-one milliseconds for a trial balance over a year of 100,000 vouchers on PostgreSQL — fast enough that there was never a reason to store a second copy.
Checkable
What backs each claim
Where in the product, or in the repository, you can go and see it for yourself.
- 21 checks over 100,000 vouchers in 343 ms
- scripts/load-test.ts
- Audit chain verified across 12,050 events
- Operations → Audit trail
- Trial balance in 67 ms, balance sheet in 170 ms
- scripts/load-test.ts
Try the intelligence layer against real books.
The demo company is seeded with a year of transactions, so there is something to actually work with rather than an empty screen.