AI Expense Management
Card lines matched to receipts, the missing ones chased relentlessly and unemotionally, and the private-use and entertainment questions put in front of a person instead of guessed at.
The Problem Was Never the Spreadsheet
Expense management software has existed for twenty years. Firms still have unsubstantiated transactions. Worth asking why.
The industry decided the problem was capture — that people needed a nicer app to photograph receipts with. So we got dozens of them, and firms still arrive at the BAS quarter with a list of transactions nobody can explain. The tools were fine. The diagnosis was wrong. The problem is the chase, and the chase is a social problem, not a software one.
Watch how it actually fails. A transaction appears with no receipt. Someone at the firm notices — maybe. They email the client. Nothing. They email again, because they are conscientious. Still nothing. Now they are on the third reminder to a client who is paying them, about $340, and it feels petty. So it waits. It waits until the quarter, when the person who spent it cannot remember either, and now the choice is between claiming something unsupported and writing it off. Neither is a good outcome, and the whole thing was decided by nobody wanting to send a fourth email.
Nothing about that requires intelligence to fix. It requires persistence and an absence of embarrassment — a system that sends the fourth reminder, and the fifth, with the date, amount and merchant attached, on a schedule, and escalates to your team only when it is not working or the amount is material. Machines are constitutionally excellent at this.
The second half is the part that must not be automated. Was it business or private? Was that meal entertainment? What proportion of the phone bill is deductible? None of that is in the receipt — it is in the client’s head and in your professional judgement. So the AI does the chasing, the reading and the matching, and hands the judgement questions to a person with the client’s answer already obtained.
From Card Swipe to Substantiated Transaction
The chasing loop runs continuously in the background. Your team only appears where judgement is required.
The Gap Appears
A card feed line lands with no matching receipt, or a receipt arrives with no matching transaction. Either way the gap is identified immediately and attributed to a cardholder or client — not discovered as a list of forty items in the last week of the quarter.
Chased Until It Closes
The client or cardholder is asked directly, by email or SMS, with the merchant, date and amount attached — the details that make a person able to actually answer. Follow-ups run on your schedule. No one at the firm has to feel awkward about the fourth reminder.
Read, Matched and Coded
The receipt is read — merchant, date, total, GST, line items where legible — matched to its transaction, and coded against the file’s own history. Documents too degraded to read with confidence are flagged, not guessed at.
Judgement Questions Escalated
Private use, apportionment, entertainment, FBT and anything out of pattern go to your team with the transaction history, the document and the client’s explanation already attached. The treatment decision is a professional judgement and stays with a person.
What the AI Handles
Persistence, reading and matching. Not tax determinations.
Relentless, Unembarrassed Chasing
The single highest-leverage function here. Reminders that actually get sent, with the detail that makes them answerable, on a schedule, until the document arrives.
- Chases by email or SMS with merchant, date and amount
- Follow-up cadence set by you, per client
- Escalates silence and material amounts to your team
- No one at the firm has to send the awkward one
Card Feed Matching
Card lines and receipts matched against each other, with each side chasing the other and neither double-counted while it waits.
- Card transactions matched to their receipts
- Receipts held, not duplicated, until the line appears
- Groups where one receipt covers several lines
- Per-cardholder attribution and follow-up
Receipt Reading
Merchant, date, total, GST and line items read from photos, scans and PDFs — including the crumpled thermal receipt photographed in a dim car park.
- Photos, scans, PDFs and emailed receipts
- Line-level detail where the document allows
- Too degraded to read? It says so and asks
- Never produces plausible numbers from an unreadable image
Coding to the File’s History
Coded against that client’s chart of accounts and established treatment for that merchant — including recurring apportionment splits your team has already set.
- Uses the file’s own merchant history
- Applies your configured apportionment splits
- Tracking categories, jobs and cost centres
- Out-of-pattern items flagged, not coded
Judgement Flags
Categories that commonly raise a treatment question are surfaced with their history and evidence attached — and no AI opinion, deliberately.
- Entertainment, travel, gifts and staff benefits flagged
- Motor vehicle and private-use apportionment surfaced
- Client’s explanation obtained before it reaches you
- Determination stays with your agent or accountant
Documents Kept With Their Transactions
The original stays attached to the transaction it supports, alongside the extracted data and the review trail — findable when it actually matters.
- Original image retained with its transaction
- Extracted data kept alongside the original
- Full trail: proposed, reviewed, changed, by whom
- Retention questions are your agent’s call, not ours
Related Capabilities
Substantiation feeds everything downstream of it.
AI BAS Preparation
Missing substantiation is where BAS quarters come unstuck. See how prep works — and where your registered agent takes over.
BAS preparationAI Invoice Processing
The same reading engine on larger documents — extraction, validation and what happens when an invoice is simply wrong.
Invoice processingAI for Xero
How receipts and coded expenses reach a Xero file, what permissions are required, and what stays under your control.
Xero integrationFrequently Asked Questions
Substantiation, private use, FBT and what the AI deliberately refuses to decide.
Because it is not a few emails — it is a few emails per unsubstantiated transaction, per client, every month, forever, and each one is socially awkward enough that it does not get sent. That is the whole mechanism. Nobody minds sending the first reminder. The fourth reminder, to a client who is paying you and has ignored the first three, is unpleasant, so it gets deferred, and the transaction quietly enters the BAS quarter without support. By the time anyone looks, the client cannot remember what the $340 at a hardware store in March was for either. The value of automating this is not the minutes saved. It is that the fourth reminder actually gets sent, unemotionally, with the date, amount and merchant attached — which is usually what makes the client able to answer at all.
No, and this is one of the clearest cases where it should not try. Whether a purchase was for the business, what proportion of a phone bill is private, whether a meal was entertainment, whether a vehicle expense needs apportioning — these turn on facts that exist only in the client’s head and in the substantiating evidence, and on professional judgement about the tax treatment. A model looking at a card feed line reading "COLES 4471" has no way to know if it was staff amenities or the family shop. What it does instead is useful and honest: it recognises which transactions historically involve an apportionment or a private-use question in that file, flags them with that history attached, and asks the client the specific question — then puts the answer in front of your team to determine the treatment.
Flagged, never decided. Entertainment and fringe benefits are among the most judgement-heavy areas in a small business file: the treatment depends on who was present, what the purpose was, where it happened, and which method the client uses — none of which is visible in a receipt total. What the AI can do is recognise the categories of spending that commonly raise these questions — restaurants, functions, travel, client gifts, motor vehicles, staff benefits — and surface them for your team with the transaction history and the substantiating document attached, rather than coding them to Entertainment and moving on. The determination is a professional judgement for your registered agent or accountant, and the deliberate absence of an AI opinion at that point is a feature.
Card feed lines and receipts are matched against each other, and each side chases the other. When a card transaction appears with no receipt, the AI identifies the cardholder and asks them for it directly, with the merchant, date and amount — repeatedly, on your schedule, without needing anyone at the firm to feel awkward about it. When a receipt is submitted with no corresponding card line, it is held until the transaction appears rather than double-counted. Where a receipt covers several card lines or one card line covers several receipts, it reconciles the group. What matters is that the gap between the two is always visible and always shrinking, instead of being discovered as a list of forty unsubstantiated transactions the week before the BAS is due.
It matters, and we would rather be straight about it. A crumpled thermal receipt photographed in a dim car park is genuinely hard to read, and thermal paper fades to blank within months, which is a records problem no software solves. The AI reads what is readable — merchant, date, total, GST, and line items where they are legible — and where a document is too degraded to read with confidence, it says so and asks the client rather than producing plausible numbers. That behaviour is the important part: a wrong read that announces itself costs thirty seconds, and a wrong read that does not can flow into a BAS. The genuinely useful habit shift is capturing the receipt at the point of sale rather than in a shoebox in July, and continuous chasing is what actually produces that habit.
Digital copies are generally acceptable to the ATO provided they are a true and clear reproduction of the original, and records generally need to be kept for five years — but the specifics of what your clients must retain, and for how long in their particular circumstances, is a question for your registered agent rather than for us or for the software. What we can say about the product is what it does: the original image is retained and attached to the transaction it supports, alongside the extracted data and the review trail. The common failure in firms is not losing documents but severing them from the transactions they substantiate, so that nobody can produce the right one when it is actually needed. Keeping them together is the point.
Never Send the Fourth Reminder Again
Free consultation: bring your unsubstantiated list and we will show you what continuous chasing would do to it. Call +61 3 9999 7398 or email hello@ai-accounting.au.