AI Accounting for Retail
One net deposit on Tuesday. Behind it: three days of sales, two processors, merchant fees, and two refunds. Automate the unpicking — and get the GST-free versus taxable line right the same way every single time.
Retail Bookkeeping Fails in Two Specific Places
The settlement that never matches, and the GST treatment that changes depending on who coded it. Both are consistency problems, and consistency is what machines are for.
Start with the settlement, because it is the one that makes people think their books are broken. Your POS says you sold $5,140 on Saturday. Your bank shows a deposit of $4,812.37 on Tuesday. Neither number is wrong. The deposit is several days of gross sales, batched by the processor, net of merchant fees, net of two refunds, and it arrived on the processor’s schedule rather than yours. Meanwhile the buy-now-pay-later provider settles on a completely different cycle with a completely different fee structure.
Reconciling that properly is a daily job, so in practice it becomes a monthly job, and then a shortcut: just book the net deposit. That shortcut is far more expensive than it looks. Your turnover is now understated by the fees. Your merchant fees never appear as an expense, so the GST on them is never claimed. Your profit is approximately right through two offsetting errors, and your revenue — the number every other metric is built on — is simply wrong.
The second failure is the GST mix, and it is worth being precise about where the actual damage comes from. Australian food GST rules are genuinely fiddly: basic food is generally GST-free while prepared food, confectionery, savoury snacks and most bakery lines are taxable, and the boundary produces real head-scratchers — the same bread roll is treated differently once something is put in it. But most retailers know their rules. What kills them is that the same product gets coded two different ways six months apart because two different people made the call. That is not a knowledge problem. It is a consistency problem.
Both of these are exactly what automated processing is good at: doing the same unglamorous thing identically, every day, without getting tired in December. What it does not do is decide your GST treatment for a novel product — that determination belongs with your accountant or registered BAS agent, and the AI’s job is to apply it consistently once made, and to flag anything it has not seen before rather than quietly assuming.
What It Does in a Retail Business
Daily, across every store, at whatever volume December throws at it.
Settlement Reconciliation, Daily
Your bank shows one net deposit. Behind it sits three days of gross sales from two processors, minus merchant fees, minus refunds, plus a buy-now-pay-later batch on its own schedule. The AI unpicks it every day and books the gross and the fee separately, as actually happened.
- Gross sales and merchant fees recorded separately, never netted
- Handles batching, weekend holds and delayed settlement
- Buy-now-pay-later and card processors reconciled on their own cycles
- Refunds matched rather than silently absorbed into a deposit
GST Mix Applied Consistently
The damage from the GST-free versus taxable line is rarely the hard call — it is the same product being treated one way in March and another in September. Your determined treatment, applied identically across every store and every period.
- Your treatment decision applied consistently, everywhere
- New and unseen products flagged rather than assumed
- Mixed-supply invoices surfaced for apportionment
- Treatment determinations stay with your accountant or BAS agent
Store-Level Reconciliation, Group Reporting
Every store reconciled on its own takings, banking and float, then rolled up. A variance at one store is a store-level signal — averaging it across the group is how it stays invisible for eight months.
- Per-store takings, banking and float reconciliation
- Consistent small variances flagged as the signal they are
- Group roll-up without losing store-level detail
- Comparable store performance without a manual rebuild
Supplier Invoices at Retail Volume
Hundreds a month, arriving as email, PDF and photographs from a phone on the loading dock. Read, extracted, matched to deliveries where you record them, and coded to your chart.
- Email, PDF and photographed invoices all handled
- Matched against deliveries where receipting exists
- Duplicate detection across near-identical monthly invoices
- Low-confidence items queued for a human, not guessed
Supplier Price Movement, Noticed
Not an accounting function at all — it falls out of the same processing for free. When a supplier’s price on a line item moves, you find out from the invoice rather than from your margin three months later.
- Line-item price changes surfaced as they arrive
- Quiet increases on high-volume lines flagged first
- Compare invoiced price against your agreed price
- Margin protection from work you are doing anyway
Peak Volume Without a Peak Backlog
December triples the transactions and does nothing for your bookkeeping capacity, so the backlog builds through the peak and clears in February — after the decisions were needed.
- Processing scales with volume, not with headcount
- Ledger stays current through the peak trading period
- Margin visible in December, during December
- No February archaeology on the busiest month of the year
Start With One Store and One Month
Preferably a month with a public holiday in it, so you see the settlement mess properly.
Connect One Store, One Processor Set
Pick a single store and connect its POS, its payment processors and its ledger. One store is enough to prove the settlement reconciliation works, and it is small enough that you can check the AI’s working line by line — which you should, at least once, before you trust it with six stores.
Lock Down the GST Treatment Table
Your accountant or BAS agent determines the treatment for your product categories, including the awkward ones. That determination gets configured once and applied identically from then on. This is the step that ends the March-versus-September inconsistency, and it is a professional decision — the AI applies it, it does not make it.
Extend Across Stores Before Your Peak
Roll out to remaining stores well before your peak trading period, not during it. The whole point is that the ledger stays current through December — which only works if the configuration was settled in October. Retailers who start this in late November get the backlog anyway, plus the rollout.
Related Pages
AI for Bookkeepers
Retail files are volume files — the exact category where fixed fees bleed.
Learn moreFrequently Asked Questions
From retailers and hospitality operators, and the people who do their books.
It handles the consistency problem, which is most of the real-world damage, but it is not a substitute for a considered view on the hard categories. Australian GST treatment of food is famously fiddly: basic food is generally GST-free, but prepared food, confectionery, savoury snacks and most bakery products are taxable, and the line between them produces genuinely difficult calls. A plain bread roll and the same roll with a filling are not treated the same way. What goes wrong in practice is rarely that a retailer does not know the rule — it is that the same product gets treated one way in March and another way in September because two different people coded it. The AI applies your determined treatment consistently across every store and every period, and flags new products it has not seen before rather than assuming. The determination itself should come from your accountant or BAS agent.
Because they are measuring different things, and the gap is structural rather than a mistake. Your POS records gross sales on the day of sale. Your bank records a net deposit some days later, after the payment processor has taken its merchant fee, batched multiple days together, or held funds over a weekend. Buy-now-pay-later settles on its own schedule with its own fee. Refunds net against the deposit rather than appearing separately. So a deposit of $4,812.37 on Tuesday might represent three days of gross sales, minus fees, minus two refunds, from two different processors. Reconciling that manually is a job nobody has time to do daily, so it gets done monthly, badly, or not at all. The AI does the unpicking every day and surfaces only the genuine variance.
It is one of the most common and most damaging shortcuts in retail bookkeeping, and it is worth being blunt about. Booking only the net deposit understates your turnover by the amount of the fees, which distorts every metric built on revenue and can matter for thresholds and reporting. It also means the merchant fees never appear as an expense — so your cost base is understated too, and the GST on those fees is never claimed. The business ends up with a profit figure that is roughly right by accident, built from two offsetting errors, and a revenue figure that is simply wrong. Automated settlement reconciliation books the gross sale and the fee separately because that is what actually happened.
Both, and the distinction matters more than most retailers expect. Each store is reconciled on its own — its own takings, its own banking, its own float, its own variances — because a discrepancy at one store is a store-level issue and averaging it across the group is how it stays hidden for eight months. Reporting then rolls up, so you get a group position without losing the store-level detail underneath it. The pattern worth knowing about: takings variances are rarely random. When one store shows a consistent small variance in one direction, that is a signal, and it is one that only shows up if you were reconciling per store rather than per group.
It is the normal case for retail and hospitality, and it is exactly the shape of work automation suits — high volume, low complexity, high tedium. The AI reads invoices from email, PDF and phone photos, extracts the detail, matches against the supplier and against deliveries where you record them, and codes to your chart. The two things it does that a human at volume genuinely cannot: catch duplicates reliably across a month of near-identical invoices from the same supplier, and notice that a supplier’s price for a line item has moved. The second one is not an accounting function at all — it is margin protection — but it falls out of the same processing for free.
This is where the capacity argument for automation is strongest in retail, because the December problem is not a December problem. Your transaction volume might triple in the lead-up to Christmas while your bookkeeping capacity stays exactly the same, so the backlog builds through the peak and gets cleaned up in February — which means you are flying blind on margin during the single period where it matters most. Automated processing scales with volume without a hiring conversation, so the ledger stays current through the peak. You get to see what is actually happening to margin in December, in December.
Make the Settlement Match, Every Day
Bring one store and one messy month. We’ll unpick the settlements in front of you and show you exactly where the gross, the fees and the refunds went.
Or call +61 3 9999 7398 — or email hello@ai-accounting.au