Expense Management software
Expense claims are small amounts of money and large amounts of everybody's time.
A claim is filled in from a folder of crumpled receipts, approved by a manager with no view of the policy, checked line by line by someone in finance, and reimbursed a month later. The amounts rarely justify the process, and the process is what people hate.
What it replaces
- Claim forms in a spreadsheet with receipts stapled to a printout.
- Policy limits that exist in a document and are enforced by whether the approver remembers them.
- Finance re-checking every line because they cannot trust that the approver looked.
- Advances tracked separately from claims, so settlement is a manual reconciliation.
What we build
The parts that make it a system.
Scoped to what you run. A module you do not need is not a discount we withhold — it is work nobody does.
Capture and receipts
Photograph a receipt on the spot and the claim line is created from it — merchant, date, amount, tax — with the image retained as the audit evidence rather than as an attachment nobody opens.
Policy engine
Limits by grade, category, city and trip, per-diem rules, duplicate and out-of-window detection, and violations flagged at submission so the conversation happens before approval rather than after payment.
Approval and advances
Routing by amount, cost centre and exception, delegation that survives holidays, travel advances issued and settled against claims, and clear visibility of what is stuck and with whom.
Reimbursement and accounting
Approved claims posted to the right cost centres with tax treated correctly, payment files or payroll reimbursement, and a per-employee and per-project spend view finance can use.
Where AI actually helps
And where it does not.
This is one of the few categories where the AI is the product rather than a garnish. Reading a photographed receipt into structured fields is reliable now, including the badly lit ones, and it removes the data entry that makes expense claims unpleasant. Duplicate and anomaly detection across claims catches the small persistent leakage nobody has time to look for. The model proposes, finance still approves, and the original image is kept either way.
Integrations
What it has to talk to.
A system that does not reach the ones you already run creates a second place to type things, which is the problem you started with.
- Corporate card and bank feeds for automatic matching against statements
- Payroll or banking for reimbursement
- Accounting for posting, with GST input credit handled where it applies
- Travel booking tools, where trips are booked centrally
The limits
What we do not do here.
Including, on several of these pages, telling you not to buy a build at all. That advice has cost us work. It has also stopped projects that would have failed in month three, which is cheaper for everyone.
- We do not issue cards or move money. We produce approved payment instructions for your bank or payroll.
- Extraction is not perfect and we do not pretend it is. Low-confidence fields are flagged for a human rather than passed through silently, and the receipt image is always retained.
- We do not build fraud investigation tooling. The system flags anomalies; deciding what a pattern means is a management responsibility we will not automate.
In practice
Where this shows up.
Field sales and service teams
High claim volume, small amounts, people who are never at a desk. Mobile capture at the point of spend is the only version that gets used.
Professional services
Expenses are often rebillable to a client, so the categorisation has to be right at capture or the margin quietly leaks into non-billable.
How it runs
Fixed scope, fixed price, working software each sprint.
01
Discovery
A call, then a written read of the problem — what it costs today, what would have to be true for software to fix it, and whether we're the right people.
02
Proposal
Fixed scope, timeline and price. No open-ended discovery phase billed by the hour.
03
Build
Agile sprints with something running at the end of each one. You see progress in the product, not in a status deck.
04
Ship & support
Cloud deployment, production monitoring and a maintenance arrangement that starts before launch, not after the first incident.
Related
Systems that usually come up in the same conversation.
Most of these share data with each other. Where two are in scope we would rather build one system than two that sync.
HR Software
Employee records, attendance, leave, onboarding and appraisals — with payroll integrated rather than reinvented.
ERP
One system across sales, purchase, stock and accounts — scoped to what you actually run, not to a product's feature matrix.
Contract Management
Every contract findable, with its dates, obligations and renewal windows as data rather than buried in a PDF.
Tell us what your Expense Management system would have to handle.
Pick a time that suits you. Tell us the problem, and we'll tell you honestly whether we're the right people to solve it.