11 min read |

The Arithmetic of Automation

A bookkeeper earning £28,600 spends 1.5 minutes per transaction. The maths is simple. The decision is harder.

Watercolour illustration comparing manual paperwork with automated digital processing

On a Thursday morning in January, someone at an accounting practice in the Midlands opened Excel and did something unusual: they calculated what manual transaction coding actually costs.

Not the headline number. Not the software subscription or the salary line. The full cost: the time, the interruptions, the rework, the things left undone because the day runs out. They tracked it for a month. Then they sent the spreadsheet to their managing partner with a two-word subject line: "We're haemorrhaging."

The figure was larger than anyone expected. And the uncomfortable truth is this: most practices have never done the calculation at all.

The baseline cost that nobody disputes

Start with the simple version. A bookkeeper in England earns, on average, £28,593 per year. That is roughly £13 per hour before you add employer National Insurance, pension contributions, desk space, software licences, or the cost of someone more senior checking the work.

How long does it take to code a transaction manually? The industry does not publish a single authoritative figure because the answer depends on context. A Tesco purchase with a clear description codes faster than an ambiguous international wire transfer with no reference. But bookkeepers we spoke to estimate between one and two minutes per transaction for routine work, assuming the chart of accounts is familiar and the description is legible.

Call it 1.5 minutes on average. That is £0.33 per transaction in direct labour cost. Before supervision. Before corrections.

The Baseline: Direct Labour Cost Only

Client Size Monthly Transactions Time Required (1.5 min each) Labour Cost (£13/hour)
Small sole trader 100 2.5 hours £32.50
Typical SME 300 7.5 hours £97.50
High-volume client 500 12.5 hours £162.50

This is the optimistic version. It assumes perfect conditions: no interruptions, no ambiguous descriptions, no questions to clients, no corrections.

For a practice managing 30 clients averaging 300 transactions each, that is 9,000 transactions per month. At 1.5 minutes per transaction, you are looking at 225 hours of bookkeeper time just on coding. That is roughly 1.4 full-time equivalents doing nothing but assigning categories to bank feeds.

But here is what the baseline leaves out.

What the baseline leaves out

The figure above assumes the transaction codes correctly the first time, that the description is unambiguous, that the client responds immediately when clarification is needed, and that no one makes mistakes.

None of these assumptions hold reliably in practice.

The Context Tax

A bank feed shows "DD AMZN MKTP." Is that office supplies, inventory, software subscription, or the managing director's personal Kindle purchase. Someone has to find out. That phone call or email thread costs time that the 1.5-minute estimate does not include.

For clients with poor record-keeping, this happens dozens of times per month.

The Error Rate

Manual data entry carries an error rate. Research cited in process automation studies suggests 1-4% for routine tasks, though accounting-specific error rates depend heavily on transaction complexity and staff experience.

At 9,000 transactions per month, even a 2% error rate means 180 corrections. Each correction takes longer than the original coding because you are now investigating why it went wrong.

Then there is the opportunity cost. Advisory work generates higher revenue per employee, higher average fees per client, and better profit margins than compliance-only work. But advisory requires time. Time that is currently spent checking whether a Screwfix receipt belongs in repairs or capital expenditure.

The uncomfortable arithmetic: if a bookkeeper spends 25 hours per week coding transactions at £13 per hour, that is £325 in labour cost producing work billed at compliance rates. The same person spending those hours on advisory work might generate £600-800 in billable value. The difference compounds weekly.

The arithmetic

Consider a realistic scenario. Not an extreme case. Just a practice with normal volume and normal problems.

Real Cost: Practice with 30 Clients (300 Transactions Each)

Cost Component Calculation Monthly Cost
Direct coding labour
9,000 transactions × 1.5 min × £13/hour
225 hours × £13 £2,925
Client communications
Clarifying ambiguous transactions (est. 15% require follow-up)
~35 hours × £13 £455
Error correction
2% error rate, 3 minutes per correction
180 errors × 3 min × £13/hour £117
Supervision and review
Senior review at £25/hour (10% of transactions spot-checked)
~23 hours × £25 £575
Opportunity cost
Advisory work forgone (conservative estimate)
50 hours × £15 margin loss £750
Total Monthly Cost £4,822

This excludes software costs, training time, weekend catch-up work, and client retention issues from errors. It is, if anything, conservative.

That is £160 per client per month just for transaction coding and its immediate consequences. Annually, £57,864 for work that produces no strategic insight, generates no advisory fees, and creates no competitive advantage.

Against this, automated coding tools typically cost between £5 and £50 per client per month depending on transaction volume. Even the higher end is £1,500 monthly for 30 clients. The arithmetic writes itself.

Manual: 30 Clients

Coding labour: £2,925

Communications: £455

Corrections: £117

Supervision: £575

Opportunity cost: £750

Monthly: £4,822

Automated: 30 Clients

Software (£20/client avg): £600

Review (10-20% flagged): £390

Corrections (minimal): £50

Advisory time unlocked: +£1,200

Placeholder

Net Position: +£160

But that is not the whole story.

The case for doing it manually anyway

There are legitimate reasons to code transactions by hand, and pretending otherwise would be dishonest.

For very small volumes, the overhead of learning new software outweighs the time saved. A sole trader with 50 transactions per month spends roughly 75 minutes coding them manually. The breakeven point for automation is measured in months, not weeks, once you account for setup time and the learning curve.

Some businesses have genuinely unusual transactions that pattern-matching systems struggle with. A property developer with complex joint venture accounting, or a business operating across multiple VAT jurisdictions, may find that automated tools create more work through false positives than they save through correct classifications.

And there is a subtler point: coding transactions manually forces you to look at every line. That scrutiny sometimes catches problems that an automated system would miss. An unexpected large payment. A duplicate invoice. A supplier charging VAT when they should not. These things matter.

When Manual Makes Sense

Automation is not universally optimal. It pays for itself fastest when:

Below these thresholds, the case weakens. A practice with five clients and 400 total monthly transactions might reasonably stick with manual processes.

The question is not whether automation is always right. It is whether most practices are making a conscious decision based on the actual numbers, or simply continuing with manual processes because that is what they have always done.

What this means for the profession

The shift is already happening, though not uniformly. Practices that have embraced technology-enabled workflows report using compliance automation as a catalyst to move clients onto year-round advisory relationships, turning what was once a January scramble into a continuous service model.

But the broader implication is uncomfortable: if manual transaction coding is economically indefensible at scale, then the profession's relationship with compliance work is changing faster than many practitioners realise. The work that once filled the gaps between advisory engagements is being compressed into minutes instead of hours. The firms that recognise this early have time to build advisory capabilities before the compression accelerates. The ones that do not may find themselves defending hourly rates for work that clients increasingly believe should be instantaneous.

There is a parallel in legal services. Twenty years ago, junior solicitors spent billable hours manually reviewing contracts for standard clauses. Software now does that work in seconds. The firms that adapted early built new service lines around the capacity that freed up. The ones that insisted clients should keep paying for manual review lost those clients to competitors who offered flat-fee automation.

The same dynamic is unfolding in accounting, though more quietly. The practices making the shift are not talking about it loudly because there is no competitive advantage in advertising that you have stopped doing something inefficiently. But the arithmetic remains the same for everyone.

The Choice

The question facing most practices is not whether to automate eventually. It is whether to do it before or after competitors use the efficiency gain to undercut on price or expand into advisory work that you cannot match.

The maths has already been done. The decision is what remains.

That spreadsheet from the Midlands practice, the one with the two-word subject line? The managing partner read it on a Friday evening. By Monday morning, they had signed up for a trial of three different automation tools.

Not because they believed automation was perfect. Because they had finally calculated what manual was actually costing.

See what the maths looks like for your practice

Upload a bank statement. Get your first automated coding done in under two minutes. No credit card, no obligations, no sales call.

Try The IQ Suite Free

Frequently Asked Questions

How long does manual transaction coding actually take?

Industry estimates suggest 1-2 minutes per transaction for an experienced bookkeeper, though this varies significantly based on transaction complexity and available context. A simple ALDI purchase codes faster than an ambiguous international transfer. The 1.5-minute average used in this analysis represents routine transactions under normal conditions, excluding time spent on client communications or error correction.

What does a UK bookkeeper actually cost per hour in 2026?

The average UK bookkeeper salary is £28,593 per year, or roughly £13 per hour according to PayScale and Indeed data. This is the base cost before employer National Insurance contributions (13.8%), pension contributions (minimum 3%), workspace costs, software licenses, or supervision time. The fully-loaded cost is typically 25-40% higher than the base hourly rate.

When does automation actually pay for itself?

For a practice handling 30 clients with 300 transactions each (9,000 monthly), manual coding at 1.5 minutes each costs approximately 225 hours of labour, or roughly £2,925 in direct costs before adding communications, corrections, and supervision. Even modest automation that reduces this by half pays for itself within weeks, not months. For lower volumes (under 200 transactions per month), the payback period lengthens but typically remains under six months.

Does automated coding mean no human review is needed?

No. Automated systems handle pattern-based classification, but typically 10-20% of transactions require human judgment for unusual items, VAT treatment, or context the system cannot infer from the transaction description alone. The question is not whether you review, but what percentage of transactions requires your attention. Manual coding requires 100% human time. Automation reduces that to the genuinely ambiguous cases.