Skip to content

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.

1

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.

2

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.

3

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.

4

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 preparation

AI Invoice Processing

The same reading engine on larger documents — extraction, validation and what happens when an invoice is simply wrong.

Invoice processing

AI for Xero

How receipts and coded expenses reach a Xero file, what permissions are required, and what stays under your control.

Xero integration

Frequently Asked Questions

Substantiation, private use, FBT and what the AI deliberately refuses to decide.

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.