The business runs. The books write themselves.
This is the Suma workbench — the secure core every client ships — with a sample trading company loaded. Its owner never types a transaction: every morning a sweep reads the overnight bank feed, matches each line against the company's own rules, posts what's certain and holds what isn't for a one-click yes or no. Invoices settle themselves when the payment lands; a receipt is captured with a tap of confirm, never keyed; anything booked without evidence is flagged on Alerts; and the read-only assistant answers over the books without ever changing them. Press "Run the morning sweep" and watch the books keep themselves.
Bank · HSBC operating
The overnight feed. The sweep matches each line against your company's rules: what's certain posts, what isn't waits for you. Uncertain lines never post on their own.
Transfer out · HK$ 20,000 · ref "K. WONG". No matching rule. Book to the directors' loan account?
Dr Directors' loan account 20,000Cr Cash 20,000
Swipe the table to see In · Out · Status
Journal · May 2026
Every matched bank line, issued invoice and filed receipt lands here as a balanced double-entry line. Nothing books unless it balances.
Swipe the table to see Dr · Cr
Invoices
Issued invoices post to receivables; when the payment lands in the feed, the sweep settles the invoice by its reference. No chasing spreadsheets.
Swipe the table to see amount · status
Expenses
A receipt becomes an expense through the capture pipeline: the assistant proposes, you confirm, Suma books it double-entry and vaults the receipt as evidence. A manual entry with no receipt is allowed too — it just surfaces on Alerts until it's backed.
Send the receipt to the assistant and it proposes the entry below — it commits nothing. You confirm; only then does Suma book it deterministically, vault the image as evidence and record who captured it. The model never holds the pen.
Cr Cash 1,240
Swipe the table to see category · amount
Alerts
Entries with no auditable evidence behind them. A manual entry is allowed — Suma never blocks a booking — but it stays listed here until a receipt or a source record backs it. Everything the sweep matched, an invoice raised, or a receipt filed is evidenced automatically and never appears.
Financial statements
Computed straight from the ledger, never edited by hand. They update the moment anything books.
Income statement
Wah Kee Trading Co. (sample) · May 2026 · HK$
Balance sheet
Wah Kee Trading Co. (sample) · as at 31 May 2026 · HK$
Cash flow
Wah Kee Trading Co. (sample) · May 2026 · HK$
Ask the assistant
Ask about this sample book in plain language — a total, a breakdown, or a list of the actual entries. Every figure is computed server-side, never guessed; when it can't verify one it says so. It's read-only: it can propose a receipt capture for you to confirm, but it never posts, edits or deletes on its own.
How it runs
The pipeline behind what you just clicked.
1 · Your feeds in, books out
Every morning the sweep reads your sources (bank feed, POS, issued invoices, a job calendar) and files each certain line as a balanced journal entry, atomically. Lines with no matching rule are held for a one-click decision; the sweep never guesses. Re-running reconciles instead of duplicating.
2 · A receipt is captured, never keyed
Send a receipt to the assistant and it proposes the entry — it commits nothing. You confirm; only then does Suma book it deterministically, vault the image as evidence and record who captured it and when. The model never holds the pen, so a bad read can't post itself.
3 · Nothing books without evidence — or it's flagged
Anyone may still make a manual entry with no receipt; Suma never blocks a booking. But an unevidenced entry surfaces on the Alerts page and stays there until a receipt or source record backs it. Nothing gets quietly booked with nothing behind it.
4 · Correct by construction
Every entry must balance before it books. Statements are computed from the ledger, never typed. A locked month can't be silently edited: a backdated receipt reopens and re-issues the close instead. And the ledger engine ships with a property-based gauntlet — hundreds of randomized books asserting the trial balance, A = L + E and cash-flow reconciliation hold on every one, in CI, not in your accounts.
5 · Read-only assistant, private by design
The chat computes every figure server-side — the model never sees a row and never does the arithmetic — and its only way to change anything is the confirm-first capture above. Before any text reaches a model, a pseudonymization gate replaces customer and vendor names, and no API key ever lives in the browser.
6 · One core, shaped to you
Every client ships the same secure core — this ledger, the capture pipeline, Alerts, statements, the assistant. A real engagement is a thin client layer on top that wires in how your business actually runs (your POS, your tutor calendar, your clinic diary, your supplier terms) without touching the core's guarantees. Adding a client is adding a folder, not forking the app.
Support
Answers and contact.
Is this the real product?
It's the client workbench's actual interface — the same sidebar, ledger, capture pipeline, Alerts and assistant clients sign into — running a scripted sample company in your browser. The live version adds real feeds, encrypted sync and month-end closes and exports.
Is the assistant here real?
Yes. The chat talks to the same hardened endpoint the product uses, answering over this sample book. It's read-only: it computes figures server-side, refuses any it can't verify, and never posts or edits — its only write path is the confirm-first receipt capture. Every request passes a pseudonymization gate, and no API key ever lives in the browser.
What leaves my computer when I use Suma?
Books mirror to the encrypted store with names encrypted at rest, keyed per client — a stolen database dump is ciphertext. Before any text reaches a model, customer and vendor names are replaced with stable pseudonyms, and structured PII is scrubbed server-side.
Will it fit my business?
The ledger, matching, invoicing, receipt capture, Alerts and statements you just used are the shared core every client gets. The bespoke part is a thin client layer — your feeds, your categories, your approval rules — added without touching the core's guarantees. Tell us what you run on.