Finance operations
The finance function runs on documents, reconciliations and judgement. We build AI systems for that work, engineered so an auditor can follow every step.
This page is about the finance function, not the financial services industry. Every company has one: a back office that moves invoices, matches transactions, closes the books, answers auditors and produces the numbers leadership acts on. If you are a bank, insurer or payments company looking for AI inside your core business, our financial services page is the better place to start.
Where the work actually sits
Finance work concentrates in a handful of places: invoices and remittances arriving in every format a supplier can invent, bank and intercompany reconciliation, journal entries and accruals, expense and spend policy, billing data spread across systems that disagree, and the reporting pack assembled by hand at every period end. Underneath most of it is a document problem and a matching problem, wrapped in a control. We start by watching the process as it actually runs, including the spreadsheets and shared inboxes that never appear on the system diagram.
Judgement is the hard part, not extraction
Pulling fields off a document is close to solved. The difficulty is what happens next. An exception has to be classified, a threshold applied, an approver chosen, a policy interpreted and a decision recorded in a way that survives review. We design that judgement layer explicitly: what the system decides alone, what it proposes to a person, and what it must never touch. Confidence is not a feeling, so every decision path is measured against an evaluation set drawn from your own historical cases before it goes near a live ledger.
Built to survive an audit
Finance systems get examined, and that changes the engineering. Every action is logged with the inputs it saw, the model and prompt version behind it and the person who approved it, so evidence can be produced later without a reconstruction exercise. Approval limits and segregation of duties are enforced in the system rather than in a policy document. The founders designed payments infrastructure that binds every payment to an auditable spend policy, and built security tooling that reports against SOC 2, ISO 27001, HIPAA and PCI-DSS. That is the standard our finance work starts from.
Working inside the systems you already run
Your ledger is not moving, and it should not have to. We build around the ERP, close management, procurement, billing and banking systems already in place, using their own interfaces and permissions rather than a parallel copy of your financial data. Where a system has no usable interface, we say so early and design for it instead of assuming it away. Finance and IT both sign the architecture before anything is built, because a finance system the platform team will not support is a system with a short life.
One process, all the way through
We would rather take one process the whole way than touch six halfway. A single reconciliation, one invoice queue, one reporting pack: chosen with your controller, instrumented so you can see exactly what it does, and run alongside the existing process until the numbers agree. Your team is trained on it while it is being built, and runbooks, evaluation sets and documentation are deliverables rather than an afterthought. When it holds, the case for the second process is your own evidence instead of our argument.
What you get
- A map of the finance process as it actually runs, including the spreadsheets, email threads and manual steps that sit outside the system of record.
- A working system for the chosen process, integrated with your ERP, close, billing or banking platforms through their own interfaces and permissions.
- An explicit decision boundary that states what the system does alone, what it routes to a person, and what it is never permitted to do.
- An evaluation set built from your own historical cases, so accuracy is measured against your ledger rather than a vendor benchmark.
- An audit trail recording inputs, model and prompt versions and approvals, so evidence can be produced on request rather than rebuilt after the fact.
- Runbooks, documentation and training for your controller and finance systems team, with the code and configuration assigned to you.
Evidence
Pays is a working prototype we built ourselves, a payments system for the case where software agents transact, and the spend policy every payment is bound to sat in the architecture from the first line rather than arriving once somebody asked for evidence.
Pays and the rest of what we have built →
What this is not
This is not an accounting, audit or tax practice. We do not sign off financial statements, issue accounting opinions or act as your auditor, and we do not resell a finance software product. We build the systems your finance team operates, and we work alongside your accountants and auditors rather than in their place.
Talk to a partner
Name the finance process that costs your team the most attention, and we will tell you honestly whether it is worth building for.
