Books, invoices & bills
Post/void discipline.
Invoices and bills follow post/void discipline — entries are posted or voided, so the record stays clean.
Adytum Platform — Controller
Live — app at /controller/
The controller's office, as software, on the core.
Books, invoices, and bills with post/void discipline. Bank feeds, reconciliation, reports, payroll accruals, and tax worksheets — every money event posting into a real double-entry core. And it runs on approvals: Controller never moves money and never files anything on its own.
Part of the Adytum platform: everything settles into the ledger. Products post money events through named RPCs, so the double-entry invariant is enforced in one place. See the whole platform →
A full controller's office.
Everything below is live in the app today, and every money event it records settles into the same double-entry core.
Customers & vendors
Both sides of the money.
Manage the people you bill and the people who bill you, alongside the documents that involve them.
Bank feeds via Plaid
Read-only bank data.
Connect accounts through Plaid. The connection is read-only, and transactions are imported settled-only — Controller sees your bank; it cannot touch it.
Bookkeeping
Suggested categories.
Imported transactions come with suggested categories. You review and approve — the suggestion never books itself.
Reconciliation
Match the books to the bank.
Reconcile accounts against imported bank data so the books and the bank agree.
Reports
P&L and balance sheet.
Profit & loss and balance sheet, built from the double-entry books underneath.
Payroll accruals
Payroll, on the books.
Accrue payroll into the books so labor costs land where they belong.
Tax worksheets
Computed, not filed.
Worksheets with computed amounts. Controller is not a filing service — it prepares the numbers; filing is yours.
Approvals & audit gates
Nothing happens by itself.
Approval and audit gates sit in front of the actions that matter, so a person signs off before anything posts.
Practice suite
For firms.
A practice suite for firms that run books for more than one client.
Multi-entity by design
Unlimited entities.
Run as many entities as you have. Multi-entity isn't an add-on tier — it's how Controller is built.
Approvals, not autonomy.
What Controller does not do
It never moves money. Bank connections are read-only. Controller records and reconciles money events; it does not initiate them.
It does not run itself. Controller runs on approvals — suggested categories, approval gates, and audit gates all mean a person decides before anything posts.
It computes, it does not file. Tax worksheets show computed amounts. Controller is not a filing service — the numbers are prepared, not filed.
How it connects to the core
Named RPCs only
Every money event Controller records reaches the books through a named RPC. Nothing in Controller writes the books directly.
One invariant, one place
The double-entry invariant is enforced in the Ledger core — once, for every product on the platform.
The core lives here
The Ledger runs inside Controller today — real double-entry books, immutable once posted, with no separate sign-in.