The Question That Prompted This
“I am really struggling to work out what I can get Claude to do, accounting-wise, that is actually saving time and not accessing confidential data I don’t want it to access.”
A common concern raised by accountants adopting AI for the first time
The answer is not what most accountants expect. Claude does not save time by doing accounting work faster. It saves time by building the tool that does the work — forever — while you do something else.
The Client
Client Profile
- 🏪 European speciality artisan bakery
- 📈 ~£2m annual turnover
- 👥 45+ employees across production, delivery, and admin
- 🗂️ 130+ wholesale customers on recurring weekly orders
- 🚚 Daily delivery routes across multiple drivers and vehicles
The Problem
- ×No-code automation tools failing under growing order volumes
- ×Google Sheets and Excel used as makeshift operational databases
- ×Xero receiving invoices but blind to everything before that point
- ×Orders, production, logistics, and HR running in complete isolation
- ×Manual handoffs at every step — daily risk of errors and missed orders
A Note on Data and Confidentiality
What Claude Built — and What It Permanently Eliminated
| What Claude built | The recurring work it eliminated |
|---|---|
| Daily auto-invoicing A scheduled job runs every day at noon, reads yesterday’s confirmed deliveries from the operations database, applies each customer’s pricing and grouping rules, and creates draft invoices in Xero — automatically. | The entire weekly invoicing run a bookkeeper used to do |
| Three-way reconciliation page A single live screen joining deliveries made, invoices raised in Xero, and payments received — so for any delivery you can see at a glance whether it’s invoiced and whether it’s paid. | Stitching three reports together every time anyone asked “did this get paid?” |
| Same-day revenue gap report A live page listing every delivery in the operations system with no matching Xero invoice — surfaced the same day, not at month-end. | The month- and quarter-end hunt for un-invoiced deliveries |
| Client approval portal When a backlog accumulates, the app generates a unique single-use URL per client listing their pending invoices. The client clicks approve; consent is timestamped and stored as an auditable record before any invoices are raised. | The multi-week email chain to get a client to OK a catch-up invoice plan |
| Webhook → instant client email A listener fires the moment an invoice moves from draft to authorised in Xero, fetches the PDF, and sends a branded email to the client — all within seconds, with no one in the loop. | A bookkeeper clicking “send” on every authorised invoice |
| Bulk catch-up workflow The invoicing pipeline and client-approval portal combine so any accumulated backlog can be raised, client-approved, and emailed in a single run — on demand, whenever needed. | Periodic write-offs of un-invoiced revenue deemed “too painful to chase”, and weeks of bookkeeping to clear historical backlogs |
| Smart standing orders A dedicated UI for managing recurring delivery patterns — Mon/Wed/Fri schedules, automatic bank-holiday skips, seasonal menu swap-outs — feeding directly into the daily invoicing pipeline. | Weekly manual exception handling on recurring orders |
The Lesson
Every row above is work that used to happen every week, every month, or every quarter. None of it happens now, because a small piece of software does it. Claude wrote each tool in hours to days. The tools then run indefinitely.