The challenge

This one is ours. Built on the system we run ourselves: our own expense module, in daily use, no client involved.

A receipt is a piece of paper in a jacket pocket. Someone has to read it, type the date, the amount, the category and the place into a form, decide whether it is reimbursable, and attach the paper to a report that someone else approves. Every step is small. That is why it slips.

The reimbursement is not the costly part. The costly part is the receipt that belongs to a client project and never reaches the client invoice, because nobody chased it at month end. That money leaves the company quietly and nothing records that it did.

We had the problem ourselves, so we built the module for ourselves first.

What we built

This is the expense module of the treasury platform we run on. We publish it because showing the system we use is the closest thing to a demo we can give you before you sign anything.

You photograph the receipt from your phone. The model reads date, amount, category and place and fills the fields.
Every extracted field arrives with a confidence signal. You check what it read and confirm — you do not key it in. When the model is unsure it says so instead of guessing, and the field waits for a person.
Mileage claims are priced from an official table covering 5,000+ vehicle models: pick the vehicle, enter the distance, the amount is computed.
Expenses attached to a client project are carried into month-end billing as a rebillable line, with the receipts already packaged.
When the transfer shows up on the bank statement, the claim is matched to it and waits for the same one-tap confirmation.

The confirmation tap is the control point, and it is there by design. Nothing reaches the books because a model was confident. It reaches the books because a person looked at what the model read and said yes.

It runs in our own cloud account — the same way it would run in yours: your cloud, your data, your bill.

The results

The honest number first: about twenty receipts a month go through it today. We are a small company and that is the real volume. We would rather publish it than dress it up.

What the volume does not tell you is the shape of the work, and the shape is what you would be buying. One photo becomes one reimbursement line, and the work per receipt does not grow with the count: twenty a month and a few thousand a month are the same pipeline with a longer queue. The system is sized for the second case; we happen to be the first.

The number that matters more to us is the frequency. Of everything in the platform, this is the module we open most — every working day, by everyone who spends anything.

Number	What it measures
1 photo → 1 line	one receipt becomes one checked reimbursement line
~20/month	receipts through the system today, at our size
Daily	the module we open most, across the whole platform
5,000+	vehicle models priced for mileage claims, from an official table

What you get

The same flow on your systems: capture from a phone, extraction with confidence flags, the approval tap, the reimbursement line, and project expenses carried to the invoice with their paperwork attached. Process audit first, scope in writing, and 30 days of support. It runs in your own cloud account. It is packaged as Back-Office Automation.

And because this one is ours, you can watch it work before you commit to anything: we open the module we use every morning and walk you through a real month.

Not sure where your paperwork is leaking? Start with the free AI Audit, or book a call.