Invoice automation for UK businesses
Supplier bills hit an inbox, get captured, coded, approved and paid — without anyone re-typing a PDF. We build the invoice-processing layer between Xero or QuickBooks, Dext or AutoEntry, and your bank.
Your AP team is processing PDFs by hand.
A typical UK SME with 50 staff processes 200–400 supplier invoices a month. Most of that processing is humans: opening PDFs in Outlook, typing line items into Xero, chasing the right manager for approval over Slack, and building a payment file in a spreadsheet at the end of the week.
- OCR that nobody trusts — You bought Dext or AutoEntry. The capture works. But everyone still opens the PDF to double-check because the OCR misreads enough line items to make manual review unavoidable.
- Approval over Slack — Invoices over £500 need approval. The AP clerk DMs the budget owner. The budget owner forgets. Three weeks later supplier emails chasing payment. The relationship deteriorates.
- Payment file built by hand — Every Friday afternoon, someone exports approved invoices from Xero, formats them into a CSV the bank will accept, and uploads it manually. Three times a year someone uploads the wrong file.
Automate the boring 90%. Catch the dangerous 10%.
Invoice automation isn't about hands-off processing. It's about routing the 90% of invoices that are clean and predictable down a fast lane, and reliably surfacing the 10% that need human attention — duplicates, suspicious supplier changes, VAT-rate anomalies, PO mismatches.
- Independent — no AP tool commissions — We have zero financial relationship with Dext, AutoEntry, Bill.com, Tipalti or any of the ledger vendors. The recommendation is whatever fits your stack and volume.
- Audit trail preserved — Every coded invoice carries a stamped trail: who approved, when, on which budget code. MTD digital-link rules preserved. Your auditor can follow every transaction back to the originating PDF.
- Built to be extended — Every automation ships with a runbook. Your AP team can add a new supplier coding rule or change an approval threshold without calling us.
Seven workflows we ship in every project.
These are the stages of a complete invoice processing pipeline. Most projects build five or six of them; the rest get scoped for phase two.
A four-phase engagement, priced flat
No hourly billing. No scope creep. You know what you're paying and what you're getting before we start.
We shadow your AP team through a full week. We measure capture time, coding time, approval lag and payment-file build time. Output: a map of your current invoice flow and the cost-saved estimate of automating each stage.
We pick the highest-ROI stages to automate first — usually capture-to-coding and approval routing. You see the cost saved, the build cost and the timeline for each before signing off.
We build in Make, n8n or Zapier (depending on your stack) plus direct ledger API integrations. Your AP lead pair-builds with us so they understand every step. We run parallel processing for at least a week before switchover.
Full documentation. Training on adding new supplier rules. A 90-day review where we measure capture-to-payment time before and after. After that, fractional CAO retainer or done.
What invoice automation actually means
For a UK SME, invoice automation means removing manual handling from two related workflows: accounts payable (supplier bills arriving and getting paid) and accounts receivable (your sales invoices going out and getting collected). This page focuses primarily on the AP side, because that's where most of the labour is; AR automation has its own dedicated page at /automations/finance/accounts-receivable-automation.
The phrase "invoice automation" gets used loosely. Some people mean OCR (just the capture stage). Some mean an AP SaaS tool like Bill.com or Tipalti (capture + approvals). What we mean is the whole lifecycle: capture, OCR, validation, coding, approval routing, payment-file generation, ledger posting and reporting. A complete invoice automation build is the difference between "the AP team types less" and "the AP team has fundamentally changed shape."
The automated invoice processing workflow, step by step
The sequence below is roughly what we build in every project. The proportions vary — a project-heavy business spends more time on coding rules; a high-volume retailer spends more time on duplicate detection — but the stages are universal.
1. Capture
Every supplier invoice routes to a single inbox. The most common UK setup is invoices@yourcompany.co.uk in Microsoft 365 or Google Workspace, with supplier-portal logins consolidated into a shared 1Password or Bitwarden vault and pulls automated where the portal supports it. Email attachments get extracted; embedded-PDF invoices get OCR'd in place.
The biggest pre-automation problem is invoices in personal inboxes. The accounts manager's predecessor was a CC on five suppliers; nobody told the new manager; those invoices now go to a deactivated mailbox and get missed for a month. Single-inbox capture closes this leak permanently.
2. OCR and extraction
For the OCR step we use whatever's already in your stack — usually Dext (formerly Receipt Bank) or AutoEntry, occasionally Bill.com for larger SMEs, occasionally a custom Google Document AI or Rossum pipeline for high-volume operations. We don't have a preferred vendor and we don't take a commission from any of them.
The critical design decision at this stage is confidence scoring. Cheap automations push every OCR'd invoice into the ledger and expect humans to catch errors downstream. Good automations route low-confidence extractions (below ~85% on key fields) into a manual review queue, where a person validates them once and the OCR model learns from the correction. After 60–90 days of feedback, queue volume drops to 5–10% of total invoices.
3. Validation
Before coding, three checks fire:
- Duplicate detection. Same supplier, same amount, close dates → probable duplicate. The single biggest source of accidental double-payment.
- Supplier bank detail change. If the bank account on an invoice differs from the supplier's known account, the invoice halts and alerts AP. This is by far the most common UK invoice fraud vector — "we've updated our bank, please pay to this new account." Automated change alerts have stopped material losses for multiple clients.
- PO matching. For businesses that run purchase orders, the invoice gets matched against the PO and (where applicable) the goods receipt. Three-way match flags variances.
4. Coding
Rule-based coding applies the account, cost centre, project code and VAT rate. Rules are usually layered:
- Supplier-level rule: every invoice from this supplier codes to this account by default.
- Line-item rule: lines containing "AWS" go to cloud hosting; lines containing "Heathrow Express" go to travel.
- Amount-based rule: invoices under £100 with no project code go to a sundry account.
- VAT rule: standard 20%, reduced 5%, zero-rated, exempt, reverse-charge for EU services post-Brexit.
New suppliers get a one-time human coding decision that becomes the rule for next time. After a few months the coding rule library covers 80–90% of all incoming invoices with zero human input.
5. Approval routing
Approval thresholds typically tier: under £500 auto-approves, £500–£5,000 routes to the line manager, £5,000+ to a director, £25,000+ requires two signatures. The approval happens in the channel the approver actually uses — usually Slack or Teams DMs with a clickable approve/reject — rather than forcing them into the AP tool. Auto-escalation fires if approval is overdue.
6. Posting and payment file
Approved invoices post to the ledger via API — Xero, QuickBooks Online, Sage 50, Sage Intacct, FreeAgent, Brightpearl. Posted invoices queue for the next scheduled payment run.
For the payment file itself we either build a BACS-format CSV that uploads to the bank portal, or push payments directly via Telleroo, Modulr, Bill.com or Wise. The bank statement feed auto-reconciles when the payment clears.
7. Reporting
A live AP dashboard surfaces total open AP, ageing buckets, top 10 overdue suppliers, supplier concentration risk, currency exposure and average time-from-receipt-to-payment. The finance director sees the same view the AP team sees, without having to ask.
Why most UK SMEs underbuild this
Most UK SMEs buy part of the invoice automation stack — usually Dext or AutoEntry for capture — and stop there. The result is that capture is automated, but coding, validation, approval routing and payment-file generation are still manual. The AP team feels slightly faster but fundamentally the same.
The missing piece is the orchestration layer between the AP tool and the ledger. That's what we build. We don't replace Dext or AutoEntry; we wrap an automation layer around them so the whole pipeline runs end-to-end.
UK-specific design considerations
A few things UK SMEs should design for that US-influenced templates often miss:
- HMRC MTD digital-link rules. Every transition between systems must be digital — no manual copy-paste, no exported-then-re-uploaded spreadsheets. Our automations preserve digital links throughout.
- VAT treatment. Standard 20%, reduced 5%, zero-rated, exempt, reverse-charge on EU services. Flat Rate Scheme businesses need an extra coding layer. Partial-exemption businesses (most charities and education providers) need a manual VAT review queue.
- Bank ecosystem. UK SMEs are usually on Tide, Starling, Lloyds or Barclays. Payment file generation needs to work with whichever, plus Wise or Revolut for international suppliers and Telleroo or Modulr for orchestration.
- Companies House and ICAEW conventions. Approval thresholds, audit retention, and chart-of-accounts conventions vary by business form (limited company, LLP, charity, CIC). Our setup respects these.
- GDPR. Supplier data and invoice PDFs contain personal data; retention and access need designing properly. We default to UK or EU data residency and a 7-year retention policy unless your auditor requires otherwise.
Pricing and engagement options
A focused invoice automation build — supplier inbox to coded, approved, paid — is £4k–£8k fixed. A broader engagement that includes customer invoice automation, payment file generation and a live AP/AR dashboard is £8k–£15k fixed.
If you want to scope first, the £1,500 Discovery Sprint is a one-week paid scoping exercise — we map your invoice flow, identify the highest-ROI automation stages, and give you a costed build plan. Many clients use it to take the plan in-house; others use it as foot-in-the-door to a full build.
For ongoing optimisation we offer a fractional Chief Automation Officer retainer at £5k–£15k per month, typically 2–3 days a month of senior automation work. We don't bill hourly and we don't take commissions from any platform.
When invoice automation is the wrong answer
- If you process under ~50 supplier invoices a month, the labour saving rarely covers the build cost. A part-time bookkeeper using Dext is usually the right answer.
- If your chart of accounts is a mess, automate after you tidy. We can do the tidying as part of the Discovery Sprint, but it has to happen first.
- If your suppliers are mostly on direct debit, AP automation has less to bite on — the bigger lever is AR automation. See /automations/finance/accounts-receivable-automation.
- If you're a sole trader or under VAT threshold, you don't need this. A good bookkeeper on a few hours a week is a better investment.
How this fits with the wider Watermelon model
This is one of four dedicated finance automation pages. The parent hub is /automations/finance. Siblings: accounts receivable automation, payroll automation, accounting automation. If you're an accountancy practice rather than an operating business, see /industries/accounting-firms. To estimate ROI before talking to anyone, the automation ROI calculator is the right starting point.
Ready to stop typing PDFs?
If any of the symptoms in the "Where AP teams leak time" section made you wince, the free 30-minute call is the right next step. Bring last month's AP volume. We'll tell you what we'd automate first and what it would cost.
Stop typing PDFs into Xero
30 minutes. No deck. Tell us your AP volume and your current tooling. We'll tell you what we'd automate first and what it would cost.