The books move when the business does. Invoices, receipts and journal entries fire from real events — not month-end memory.
We sit with your business. We find the operational problem costing you the most. We build the system that fixes it.
Sales signed a project on Monday. Finance heard about it on Thursday. The invoice went out the following Tuesday — and only if someone remembered. Retainers were missed. Refunds processed without reversing revenue. The founder spent month-end making decisions against numbers a fortnight stale, and the controller was the last one out every Thursday night.
An event-driven accounting layer. Operational systems emit events — projects signed, milestones shipped, refunds processed, deposits received. The engine writes the right artefact: a deposit invoice, a milestone draw-down, a recurring charge, a journal entry, a bank match. Rules are config, not code. The firm can change VAT treatment or cost-centre splits without engineering work.
Books reconcile to within a day of operations. Month-end takes hours instead of weeks. Every entry traces back to the event that produced it. Auditors get answers in seconds. Revenue stops slipping through cracked spreadsheets.
One example — a 12-person consulting firm on UK VAT. Yours would mirror your chart of accounts, tax rules and project taxonomy.
Fire an operational event on the left. The engine matches a rule, generates the right artefact, and posts the entry to the correct ledger.
Flip a toggle and re-fire the same event to see different entries land.
evt_sign_projectproject.signed → issue-invoice (class X)New project of class X. No VAT. Books AR and revenue.
INV-1042| Account | Debit | Credit |
|---|---|---|
| Accounts Receivable | $50,000 | |
| Revenue · Consulting | $50,000 |
Deposits arriving from the bank. The engine matches each one to an outstanding invoice and posts the receipt — exceptions land in a small queue.
Want one built for your business? The first conversation is free.
Book a discovery callEvery recurring accounting motion — deposit invoice, milestone draw-down, recurring charge, journal entry, bank match — fires from a real operational event, not a calendar reminder.
Every ledger entry carries the event ID and the rule that produced it. Auditors reconstruct the full chain of evidence for any line, any time.
Not the primary focus for this system.
Because the books reflect operations in near-real-time, AR ageing, MTD revenue and project margin are reportable any day of the month — not just at close.
The first conversation is free. And useful either way.