How I'd End the January Receipt Chase at an Accounting Firm

A carrier bag on the reception desk

It is the last Monday in January, 09:05, and there is a supermarket carrier bag on the reception desk of a small accounting practice in Leeds. Gary, a plumber, has brought a year of receipts for his tax return. Some are folded into a petrol station envelope. Some are stuck together. One till receipt has faded to a white strip.

Priya, who has done the practice's bookkeeping for six years, signs for the bag and puts it on the shelf behind her desk. It is the fourth since Friday. Online Self Assessment returns are due by 11:59pm on 31 January, and every client who has sent nothing all year sends everything now.

The practice is invented for this story: seven people, around 230 clients, mostly sole traders and landlords plus a handful of limited companies, with the books in Xero and a few in QuickBooks. January is not only tax returns. The monthly clients' December paperwork is late as well, because nobody sends receipts at Christmas, and the same four people chase both.

Five receipts, one photo

The carrier bags are the visible part. Most of January arrives on a screen.

• A hairdresser sends a photo to Priya's own mobile at 22:14: five receipts laid out on a kitchen table, one of them upside down.
• A landlord answers the request for his December bank statement with a screenshot from his banking app. It shows twelve transactions and no balance.
• An electrician sends his July statement instead of November's, plus a second copy of an invoice he already uploaded in October.
• The owner of a small online shop forwards an order confirmation instead of the invoice.

Each one needs a person to open it, work out what it is, find the transaction it belongs to and write back. Behind all of them sits the spreadsheet: 230 rows, a column per month, cells shaded by hand. Its reminders read the way reminders read when nobody has time to be specific: "Hi, please could you send over your outstanding paperwork." And clients reply with the question the email should have answered: "What's missing?"

The list is already in Xero

Helen, who owns the practice, calls me in September, with the next January four months away. She has a second reason to call now. Making Tax Digital for Income Tax has put many of her sole traders and landlords on quarterly updates since April 2026, so for them the January chase is becoming a chase every quarter. "I can do this once a year," she says. "Not four times."

I ask her to open Gary's bank feed in Xero and filter for transactions without an attachment. There it is: the list of what he owes the practice, computed by the ledger, with dates, amounts and payees. The spreadsheet tracks by hand what the books already know. What nobody has is the time to turn that list into a message a plumber can act on from his van.

The other half of the list has no transaction to hang on. The fuel card statement comes every month, the van leasing invoice every quarter, and each bank statement's opening balance must equal the previous closing balance, so a missing statement shows up even when no transaction does. None of that needs a model. It is a count over twelve months of the client's history, confirmed once by the accountant. The model gets the language jobs only: writing the reminders and the questions, and reading what comes back.

A reminder a plumber can answer from his van

The old reminder asks for "outstanding paperwork". The new one, on WhatsApp, reads like this:

Hello Gary, this is the automated document reminder from your accountants. For the quarter just ended we are still missing three things: the receipt for £486.00 paid to the tile supplier on 3 November, the van insurance renewal from October, and the November statement for your second account. You can reply here with photos or PDFs.

Every item in it comes from the checklist and the bank feed. The model turns them into a short message in the firm's tone and adds nothing else: no amounts it made up, no deadlines or penalties the firm has not written into its own templates, no threats.

WhatsApp runs only for clients who opt in, on the WhatsApp Business Platform, and never again on Priya's own phone. Outside the 24-hour window after a client's last message, reminders go out as approved utility templates, which Meta bills per message. Messages name items and amounts, never balances or account numbers. Clients who prefer email get email. Frequency caps and quiet hours are the firm's settings, and after two unanswered reminders there is no third message, only a task for the accountant to call.

The photo from the kitchen table

Now take the hairdresser's photo, the one that reached Priya's phone at 22:14, and send it through the business number instead. Before anything is read, the photo is cut into one document per receipt and each is turned the right way up. Then:

The reply goes back within a minute: thank you, that covers the wholesaler and the train ticket, and here is what is still missing. The café receipt waits for Priya, because whether a coffee is a business expense is her call, not a model's. And the split is the step I trust least. When receipts overlap or the cut is uncertain, the whole photo goes to Priya rather than half of it being filed. The reading works the way my guide to AI document extraction describes, and the full design is in the blueprint for accounting document chasing.

What the dry run asks for

Before one reminder reaches a client, the checklists run over a quarter of real bank feeds, and the accountants read what the system would have asked each client for. Nothing is sent. This is where the design gets corrected, and two corrections come straight away.

The first is a landlord's buildings insurance. He pays it by monthly direct debit, so twelve months of history say a document is due every month. But the insurer sends one schedule a year. A system that asks him for it every month teaches him, by March, to ignore every reminder the practice sends. So each learned checklist is confirmed by the accountant before it goes live, and "not due this month" becomes a status in its own right, as important as "missing".

The second is the landlord's screenshot from January. In the dry run it would have ticked off his December statement, because it shows the right account and the right month. But a screenshot has no opening or closing balance, so it proves nothing about completeness. From then on a screenshot counts as evidence for the single transactions it shows, the statement is still requested, and a screenshot never counts as a statement.

What stays with Priya and Helen

The system asks, sorts and files. Everything that touches the books stays with people, and the line is drawn by consequence.

• The rules of the chase. Helen sets the tone, the frequency caps and the quiet hours, and an accountant confirms each client's checklist before its first reminder.
• The questions. Payments nobody can explain become a question list in plain words, such as what the £480 to an online marketplace in August was for. Priya sends each question as it is or rewrites it.
• The books. Which account a cost goes to, how it is treated for tax and every posting stay with the accountant, approved from one dashboard that shows per client what is complete, what is missing and what arrived but could not be matched.
• The clients who go quiet. After two reminders the system stops, because a client who ignores two specific messages has a relationship problem, not a reminder problem. Priya knows whether he needs a call, a visit or patience. The system does not.

Every message and every document is logged, and every provider that touches client data works under a data processing agreement. Gary can still bring his carrier bag. Reception scans it into the same pipeline as everything else.

The next January

The practice's clients do not become tidier. What changes is the shape of the month. December's gaps are known on the first working day of January, and every client who owes something has a message naming it. The quarterly clients were asked in October and again in January, one quarter at a time. The spreadsheet is gone, and so is the WhatsApp thread on Priya's own phone. What reaches her desk is the part that needs her: unmatched documents, the question list, and a short list of people to call.

If your clients already use a portal and one checklist fits all of them, buy rather than build: Karbon, TaxDome and Canopy send client requests with automatic reminders, and Dext and Hubdoc capture receipts into Xero and QuickBooks. A build earns its cost in the gap between those tools: checklists that differ per client and come from their history, a chase that reads the ledger instead of a portal, and clients who will never log in anywhere but do answer WhatsApp. It usually fits the multi-step tier of AI workflow automation, and the full blueprint covers the flow, the failure modes and what each part costs to run.

Frequently asked questions