Work / Accounting
Approvals, reconciliation and close run on spreadsheets and email threads. We build the AP and close systems that run them for you — inside Xero, QuickBooks or your ERP.
- 0 hrsof weekly processing, before
- 0 hrsafter — same volume
- 0% → 0.8%error rate in reporting
Right now, your close runs on email threads and one person's checklist.
Approvals chase through email, expense tagging is manual across tools, and the close is a checklist someone keeps in their head.
Invoices approved by email thread
Reconciliation by hand
Close checklist in someone's head An approval lost in a thread
A payment run built by hand An exception nobody flagged
A journal drafted at midnight
The close that finished a week lateSame week. Same team. A different set of problems.
The decisions behind approvals, reconciliation and the close.
- Invoices in the inboxCaptured by hand, coded by guess, approved by reply-all.
- Expenses tagged by handThe same supplier lands in three categories.
- Reconciliation by eyeHalf a day a week per entity, exceptions found late.
- A checklist in someone's headA different close every month.
- Invoices in the inboxInvoices captured and routed
- Expenses tagged by handExpenses categorised
- Reconciliation by eyeReconciliation by agent
- A checklist in someone's headA close that runs itself
An AP and close operating system: capture, code, route, reconcile, and a close that runs itself.
Accounts payable
- Invoice capture & codingParsed, coded, matched to PO or contract
- Approval routingBy amount, entity and department, with an audit trail
- Payment runsPrepared for one-click approval
Close
- Reconciliation agentsBank, card and intercompany against the ledger
- Close checklistRuns itself, flags what's blocked
- Management packDrafted from the ledger, reviewed by you
Agents we deploy
Approvals stay with the controller; the chasing doesn't.
- Invoice & payments
- Expense tagger
- Reconciliation
- Close runner
What the studio has shipped as a product, not a project. Each opens in its own site.
- Constraint
- Seventeen hours a week of invoice parsing and entry, an eight percent error rate in reporting, and approvals lost in email.
- System
- Invoice capture and coding, approval routing with an audit trail, and reconciliation agents against the ledger.
- Result
- Two hours a week for the same volume; error rate under one percent; every approval logged.
“Invoice reconciliation used to eat half my Monday morning. Now I review exceptions over coffee. (Simulated quote — see PLACEHOLDERS.md.)”
Tell us about one workflow. We'll come back within a working day with what a system would look like — then you pick a time.
- Map the workflow to the agents and systems that would run it
- Build inside the tools you already use — no new platform
- Move from a first increment to a system your team runs — in fortnights