What automated bookkeeping actually changes in a practice

Most of the writing about software in accounting is written by people who have never prepared a VAT return. This is an attempt at something more useful: what actually comes off your desk, what doesn't, and how to tell the difference before you pay for anything.

Where the hours really go

Ask most practitioners what takes the time and they won't say the accounting. They say chasing clients for paperwork, then keying in what eventually turns up. A shoebox of fuel receipts and till rolls has to become rows in a ledger, and someone has to sit and type them.

That job has two distinct halves. The first is reading a document and pulling out the supplier, the date, the net, the VAT rate and the total. The second is deciding what it means — whether it's allowable, which category it belongs in, whether the client has handed you something they shouldn't have claimed. Only the first half is mechanical. It's also the half that eats the afternoon.

What software can genuinely take

Reading documents is now something software does well. Modern systems don't work by recognising a layout they've been trained on, which is why older tools broke every time a supplier redesigned an invoice. They read the page more like a person does, so an unfamiliar format, a fold across the middle or a photo taken in a van is usually still fine.

The practical effect is that the first half of the job stops being typing and starts being checking. Reviewing a filled-in line takes seconds; keying it from scratch takes minutes. Multiply that across a quarter's worth of documents and it's the difference between an afternoon and a coffee break.

What it can't take, and shouldn't

The second half stays with you, and it should. Software doesn't know that a client's "office supplies" receipt was a birthday present, and it doesn't carry your professional responsibility for what goes on a return. Anyone selling you otherwise is selling you a problem.

This matters for how you judge a tool. The right question isn't "is it always right?" — it won't be. It's "when it's wrong, how quickly do I see it?" A system that shows you the original document beside the figures it pulled out is one you can work with. A system that hides its workings is one you can't.

How to actually test one

Demos use clean documents. Your clients don't send clean documents. So take your worst ones — the faded thermal till roll, the handwritten invoice from the local builder, the statement scanned at an angle — and put those through first. If a tool handles your awkward cases, the easy ones look after themselves.

Be wary of anything that requires a card before you can see output on your own paperwork. Judging this properly takes twenty documents and twenty minutes, and any vendor confident in their product will let you do exactly that.