Every expense sorted the same way,
not by whoever has time today
Expense categorisation is simple in theory and inconsistent in practice, because the person doing it changes week to week and the rules live in someone's head. We build an agent that reads receipts and bank or card feed lines and assigns the category your chart of accounts expects, every time, the same way.
The process today
Categorising expenses sounds mechanical until you watch how it actually happens: whoever has time that week reads a receipt or a card statement line and picks the category that seems closest, and the rule for what counts as “office supplies” versus “software” lives in that person’s head, not in a document anyone else can check. Two bookkeepers working the same chart of accounts will code the same vendor two different ways.
The second cost shows up at month-end, when a controller has to re-sort a chunk of transactions that were coded inconsistently before they can trust the department-level numbers, which turns what should be a quick close into a reconciliation project.
The third is that nobody flags the genuinely unusual transaction, a one-off that does not fit any existing category, because the categorisation process is built for speed, not for noticing what is different.
What the agent does
The agent reads receipts, invoices and bank or card feed lines, and assigns a GL code from your actual chart of accounts using the rules your finance team defines: this vendor always means this category, this keyword pattern usually means that one, recurring subscriptions get coded automatically once the pattern is confirmed once. The same logic runs every time, on every transaction, regardless of who is on the team that week.
Transactions that match a known pattern are coded and posted or queued for your bookkeeper’s normal review step. Anything that does not match a known vendor or pattern, a new supplier, an unusually large amount, a transaction that could plausibly fit two categories, goes into a flag queue instead of being coded on a guess, with the reason for the flag attached.
A monthly consistency report shows categorisation by category and cost centre, so a controller can spot a pattern shift (a category suddenly growing, a vendor that should probably be reclassified) before it becomes a bigger reconciliation problem.
What stays with humans
The chart of accounts and the categorisation rules are set by your finance team, not the agent. Anything flagged as unusual gets a human decision, and any change to how a recurring vendor is coded needs a person to confirm it before the rule takes effect going forward. The agent applies your rules consistently; it does not invent new accounting policy.
Guards
Every categorisation decision is logged with the rule that triggered it, so a bookkeeper can trace why any transaction was coded the way it was. New vendors and amounts above a threshold you set always route to the flag queue on the first occurrence, so a new pattern gets a human eye before it is trusted to run automatically.
Price and timeline
| Option | Price | What it covers | Timeline |
|---|---|---|---|
| Single automation | from $500 | One chart of accounts, one data source, rule set, flag queue | 3 to 8 days |
| Department package | from $2,500 | Expense categorisation plus bank reconciliation and payroll inputs preparation across your finance team | 2 to 4 weeks |
Running cost is usually $10 to $40 a month in model usage depending on transaction volume, with a budget cap set before launch.
Related
Pair this with bank reconciliation so categorised transactions match cleanly against your ledger, and with accounts receivable reminders to cover both sides of the books. For the inputs that feed the next payroll cycle, see payroll inputs preparation. The full package breakdown is on the AI agents service page and the automation-everything overview; for a real finance system this logic runs inside, see the factory ERP recovery case study and the two-brand analytics hub case study.
Ready for every expense to be coded the same way, every time? Get in touch and we will look at your chart of accounts in the first call.
Tired of doing this by hand? We can take the whole routine off your team, not just this step: Routine takeover, from $400 →
FAQ
What does automating expense categorisation cost?
from $500 for one chart of accounts and one data source; multiple entities or currencies add time, quoted after a short review.
How long does it take?
3 to 8 days once we have your chart of accounts and a sample of recent transactions.
Which tools does it work with?
QuickBooks, Xero, your bank or card provider's feed, and a spreadsheet export if that is still part of your process.
What if the AI codes something wrong?
Anything outside the known vendor and category patterns lands in the flag queue for a bookkeeper to decide, instead of being coded on a guess.
Is our financial data safe?
Transaction data moves between your bank feed and your accounting system through the connections you authorize; we do not keep a separate copy.