Invoice approval workflow: a practical guide for UK finance teams
- KeystoneFA
- 1 day ago
- 13 min read
An invoice approval workflow is the structured sequence of steps your business follows to verify, authorise, and post a supplier invoice before payment is released. If you do nothing else today, confirm that the person who approves an invoice is never the same person who authorises the payment — that single segregation of duties control underpins every other fraud and error prevention measure in your accounts payable function. HMRC’s procure-to-pay guidance and a complete audit trail sit directly behind it as the next two essentials.
Key takeaways
A well-designed invoice approval workflow reduces payment errors, strengthens fraud controls, and produces an audit trail that satisfies HMRC requirements without additional year-end effort.
Point | Details |
Fix the intake point first | A single, controlled invoice inbox removes the most common cause of lost and duplicated invoices. |
Enforce segregation of duties | The approver and the payment authoriser must be different people; in small teams, use a periodic review as a compensating control. |
Log every override | HMRC requires manual overrides to be documented with a reason, approver name, and date to protect VAT integrity. |
Pilot automation on PO invoices | Start with high-volume, PO-backed suppliers to get the fastest return and lowest risk from AP automation. |
KeystoneFA for workflow design | KeystoneFA assesses, designs, and implements audit-ready AP workflows for UK founders and small businesses. |
This article is general information, not a substitute for advice from a qualified financial advisor. Consult a qualified financial professional about your own circumstances before acting on anything here.
Table of Contents
What is an invoice approval workflow and where does it fit in P2P?
A formal invoice approval workflow sits between invoice capture and payment release in the purchase-to-pay (P2P) cycle. Invoices arrive through several entry points: supplier email, a dedicated AP inbox, an EDI feed, a supplier self-service portal, or as scanned paper documents. Each entry point carries its own risk of data loss or duplication. This is why a single, controlled intake channel matters.
The structured workflow follows this sequence:
Capture — receive and digitise the invoice (OCR/IDP or manual keying)
Validate — check supplier details, VAT number, invoice number, and required fields
Match — compare against purchase order (PO) and goods receipt note (GRN) where applicable
Route — send to the correct approver based on cost centre, value, or category rules
Approve — authorised sign-off within agreed SLA
Post and pay — write to ERP, schedule payment run
Archive — store with full audit trail attached
At the approval stage, the approver typically needs the original invoice, the matched PO, the GRN confirming goods or services were received, and any supporting contract or statement of work. Without those artefacts, approval is a rubber stamp rather than a genuine control.
Why a formal approval process matters for AP accuracy and control
A documented, policy-driven accounts payable approval process does three things at once: it cuts operational waste, strengthens financial controls, and protects cash flow.
On the operational side, a defined workflow removes the ambiguity that causes invoices to sit unanswered in inboxes for days. When every invoice has a clear owner, a required evidence set, and a deadline, rework drops and cycle times shorten. Finance teams that have moved from ad-hoc email approvals to a rule-based process typically report fewer duplicate payments and lower headcount effort per invoice processed.
The control benefits are harder to see until something goes wrong. Segregation of duties prevents a single employee from both approving spend and releasing funds, which is the most common vector for payment fraud in small and mid-sized businesses. Duplicate detection catches the same invoice submitted twice, whether by accident or design. An immutable audit trail means that when your auditors or HMRC ask how a payment was authorised, the answer is already attached to the journal entry rather than scattered across email threads.
Cash flow improves too. When you know exactly where every invoice sits in the approval cycle, you can schedule payment runs accurately, capture early-payment discounts, and avoid late-payment penalties under the UK’s Late Payment of Commercial Debts Act.
How does a step-by-step invoice approval workflow actually run?
A practical invoice management process needs clear role ownership at every step, not just a flowchart on a wall.
Ordered steps from capture to archive
Capture and validate — AP clerk receives the invoice at the designated intake point, checks that mandatory fields are present (supplier name, VAT number, invoice date, net/VAT/gross amounts, payment terms), and logs it in the system.
Two- or three-way match — AP clerk matches the invoice against the PO (two-way) and, where goods or services have been received, against the GRN (three-way). Discrepancies outside tolerance trigger an exception.
Route for approval — the system or AP clerk routes the invoice to the correct approver based on cost centre, value band, or category. Routing rules should be documented in an approval matrix.
Approve or escalate — the budget holder or approver reviews the invoice, confirms the spend is authorised, and approves within the agreed SLA. If they are absent, a delegated approver takes over. Invoices above a threshold escalate to a finance manager.
Post to ERP — once approved, the invoice is posted to the correct nominal code, cost centre, and VAT code in the accounting system.
Reconcile and archive — the AP team reconciles the supplier statement, confirms the payment run, and archives the invoice with the full approval trail attached.
Role matrix
Role | Responsibility |
AP clerk | Capture, validate, match, route, archive |
Goods receiver | Confirm GRN and sign off delivery |
Budget holder / requester | Confirm spend is authorised and within budget |
Approver | Review and sign off invoice within SLA |
Finance manager | Escalation approvals, override sign-off, policy owner |
Approval path design
Serial approval (one approver after another) suits high-value or sensitive invoices where each sign-off adds a distinct control. Parallel approval (multiple approvers simultaneously) speeds up routine spend where no single approver owns the full budget. A hybrid path uses parallel routing for standard invoices and serial escalation for exceptions or high-value items.
Set approval thresholds in writing: for example, invoices up to £1,000 approved by the budget holder alone; £1,001–£10,000 require finance manager co-approval; above £10,000 require director sign-off.
What goes wrong with manual or ad-hoc invoice approvals?
Manual processes fail in predictable ways, and knowing the failure modes helps you target fixes rather than redesigning everything at once.
The most common breakdown is the lost or stranded invoice. An invoice arrives in a shared inbox, nobody claims ownership, and it sits until a supplier chases payment. By then, the early-payment window has closed and the AP team is scrambling to reconstruct approval evidence. Related to this is unclear ownership: when any of five people could approve an invoice, none of them feel urgency, and the invoice ages.
Duplicate payments are a direct cost. Without a duplicate-detection check, the same invoice submitted twice — or once by email and once by post — can be paid twice. Recovering an overpayment from a supplier takes time and damages the relationship.
Missing or incorrect VAT details create a different problem: a VAT-registered supplier who omits their VAT number, or an AP team that codes the wrong VAT rate, produces a record that will not survive an HMRC inspection. Manual coding is where this error most often originates.
The data is stark. UK finance professionals report spending 40% of their time resolving errors and around 32% chasing approvals, with a further 31% on reconciling payments and 30% fixing mismatched POs. That is the operational cost of a workflow that relies on email, spreadsheets, and individual memory rather than defined rules.
UK-specific controls, HMRC guidance, and governance for your workflow
UK finance teams face a specific compliance layer that generic workflow advice often skips. Getting this right protects your VAT position and keeps you audit-ready.
Segregation of duties in AP
AccountingWEB’s guidance is direct: the person who approves an invoice must not be the person who later authorises the payment. In larger teams, you can enforce this through system roles. In smaller teams where strict role separation is impractical, a compensating control works: a second person performs a periodic review of approved invoices and payment runs, looking for anomalies. Document the review and keep the log.
HMRC guidance on manual overrides and tolerance limits
HMRC’s procure-to-pay compliance guidance is clear that manual overrides to system-calculated values must be narrowly tolerated and subject to formal approval controls. Every override should be logged with the reason, the approver’s name, and the date. Tolerance limits — the acceptable variance between a PO price and an invoice price before a manual override is needed — should be set in policy and reviewed at least annually. Overrides that fall outside tolerance without documented approval are a VAT compliance risk.
Audit trail and record retention
HMRC requires VAT records to be kept for at least six years. A digital approval workflow that attaches the full trail (approver comments, timestamps, matched documents) to the posted journal entry converts your day-to-day AP process into audit-ready evidence rather than something you have to reconstruct at year end. Paper-based or email-only trails rarely survive that test intact.
Bank-detail change checks
Changing a supplier’s bank details is the most common vector for authorised push payment (APP) fraud. Any request to update bank details should require independent verification with the supplier by phone (using a number from your records, not the email) and a second authoriser before the change is made in the supplier master.
Pro Tip: Before approving any invoice, run through this short SoD check: (1) Did I raise or receive the goods/services on this invoice? If yes, escalate to a colleague. (2) Will I also authorise the payment run? If yes, a second approver must co-sign. (3) Has this supplier’s bank account changed recently? If yes, verify independently before posting.
How does automation change the invoice approval workflow?
Automation does not replace the controls described above — it enforces them consistently, at scale, without relying on individual discipline.
The core capabilities to prioritise, in order of impact:
Intelligent capture (OCR/IDP) — extracts header and line data from PDFs and scanned documents, removing manual keying and the transcription errors that come with it
PO matching — automatically compares invoice lines against the PO and GRN, flags discrepancies, and routes clean invoices straight to approval without AP touching them
Duplicate detection — checks invoice number, supplier, amount, and date against the ledger before the invoice enters the approval queue
Rules-based approval routing — applies your approval matrix automatically, sends reminders, and escalates when SLAs are breached
Immutable audit trail — records every action (view, comment, approve, override) with a timestamp and user ID, attached to the posted transaction
ERP posting — writes approved invoices back to Xero, Sage, QuickBooks Online, or your chosen platform with the correct nominal code and VAT treatment
Integration priorities matter as much as features. Two-way posting to your ERP prevents the duplicate-entry problem that arises when AP tools and accounting systems are not synchronised. Supplier master validation checks that the supplier on the invoice matches your approved supplier list. VAT code handling ensures the right rate is applied automatically rather than left to manual coding.
Piloting automation on high-volume, PO-backed suppliers gives you the fastest return with the lowest risk. New suppliers and any invoice involving a bank-detail change should stay on a manual check path until the supplier relationship is established. Test with live invoices before rolling out to the full supplier base.
How to improve your invoice approval workflow today
Quick wins require no new software. Medium-term changes do, but they pay back quickly.
Quick wins (this week)
Designate a single invoice intake email address or portal and redirect all supplier invoices there. Remove AP team members’ personal inboxes from supplier communications.
Require a PO number on every invoice above a minimum threshold. No PO, no pay is a policy, not a technical feature — enforce it now.
Write down your approval matrix: who approves what, up to what value, and within how many working days.
Set an escalation rule: if an invoice is not approved within the SLA, it automatically goes to the approver’s manager.
Standardise the required fields on every invoice (supplier name, VAT number, invoice number, date, line items, payment terms) and communicate them to your top 20 suppliers.
Medium-term changes (next 90 days)
Implement an IDP or AP automation tool and pilot it on your highest-volume, PO-backed suppliers first, per Wise’s automation guidance
Build a formal approval matrix document and get sign-off from the finance director
Set up delegated sign-off rules so that an approver’s absence never stalls a payment run
Run a duplicate-payment audit on the last 12 months of transactions to establish a baseline
KPIs to track
Time-to-approve — average days from invoice receipt to approval sign-off
Touchless rate — percentage of invoices processed without manual intervention
Exception ageing — average days an exception sits unresolved
Duplicate detection rate — number of duplicates caught before payment
Involve procurement, operations, and your approvers when redesigning routing rules. Workflows that are designed without the people who use them tend to get worked around rather than followed.
Sample invoice approval workflow template
The template below gives AP teams a ready starting point. Adjust SLAs and thresholds to match your business size and risk appetite.
Step | Owner | SLA | Required evidence | Post-action |
Capture and validate | AP clerk | Same day | Invoice with all mandatory fields | Log in AP system |
Two/three-way match | AP clerk | 1 working day | PO, GRN (if applicable) | Flag exceptions |
Route for approval | AP system / AP clerk | Automatic | Matched invoice, PO, GRN | Notify approver |
Approve (≤£1,000) | Budget holder | 2 working days | Invoice, PO confirmation | Post to ERP |
Approve (£1,001–£10,000) | Finance manager | 3 working days | Invoice, PO, GRN, contract | Post to ERP |
Approve (>£10,000) | Director | 5 working days | Full evidence pack | Post to ERP |
Exception handling | AP clerk + approver | 5 working days | Exception form, supplier correspondence | Resolve or reject |
Archive | AP clerk | Same day as posting | Full approval trail attached | Retained 6+ years |
Any override outside tolerance requires finance manager sign-off and a logged reason.
Exception form fields: invoice reference, supplier name, exception type (price mismatch / missing PO / VAT error / other), description of issue, action taken, resolved by, date resolved.
Which tools do UK AP teams typically use?
The typical UK AP software stack combines an invoice capture tool, an approval engine, an accounting platform, and a payment or expense layer. Here is what to look for in each category and which platforms are commonly used.
Invoice capture and IDP: tools like Dext (formerly Receipt Bank) extract data from supplier invoices and receipts, removing manual keying. Dext integrates directly with Xero, Sage, and QuickBooks Online, which makes it a natural first layer for small and mid-sized UK businesses.
Accounting platforms: Xero and Sage are the dominant choices for UK SMEs, with QuickBooks Online a close third. All three support approval workflows to varying degrees, though dedicated AP tools extend their native capabilities significantly.
Expense and card management: Pleo provides smart company cards with real-time spend visibility and receipt capture, which complements invoice approval by covering employee-initiated spend that would otherwise bypass the AP workflow entirely.
Dedicated AP automation platforms: purpose-built tools add rules-based routing, multi-level approval, duplicate detection, and ERP posting on top of what accounting platforms provide natively.
Must-check integration points when selecting any tool:
Two-way posting to your ERP (not just one-way export)
Supplier master synchronisation to catch bank-detail changes
VAT and tax code handling that maps to your chart of accounts
Reconciliation reports that match AP sub-ledger to the general ledger
UK data residency and GDPR compliance
For sector-specific VAT handling, such as the construction reverse charge, confirm that your chosen platform supports the correct VAT treatment before committing to a rollout.
Vendor selection checklist:
Does it integrate natively with your current ERP/accounting platform?
Can it enforce your approval matrix without custom development?
Does it produce an immutable, timestamped audit trail?
Is UK VAT handling (including Making Tax Digital) supported?
What is the pilot or onboarding process, and can you test with live invoices?
What most finance teams get wrong about invoice approval
The conventional wisdom says the biggest problem with invoice approval is speed — that the goal is to approve invoices faster. That framing is wrong, or at least incomplete.
Speed without control is how duplicate payments and fraud happen. The teams that genuinely improve their AP function are not the ones who cut approval time by removing steps; they are the ones who remove the friction that adds no control value while keeping the friction that does. Chasing an approver for a third time because they missed an email is waste. Requiring a GRN before approving a goods invoice is not.
The second thing teams consistently underestimate is the bank-detail change risk. Most AP fraud in UK small businesses does not come from sophisticated external attacks. It comes from a convincing email that asks you to update a supplier’s sort code. A workflow that automates everything but leaves bank-detail changes on an informal email process has a large, unguarded door.
The third oversight is treating audit readiness as a year-end task rather than a by-product of good daily process. When your approval workflow attaches every document, comment, and timestamp to the posted journal entry, your auditors can test a transaction in minutes rather than hours. That is not a compliance luxury for large businesses — it is a practical time-saver for any business that faces a year-end audit or an HMRC enquiry.
KeystoneFA helps you build an audit-ready AP workflow
Most founders and small business owners know their invoice approval process has gaps. The harder part is knowing which gaps matter most and how to close them without disrupting day-to-day operations.
[
](www.keystonefa.co.uk)
KeystoneFA works with UK startups and growing businesses to assess their current AP process, identify the controls that are missing or inconsistently applied, and design a workflow that is both audit-ready and practical to run. That means helping you select and configure the right tools from the UK AP stack — Xero, Sage, Dext, Pleo, and others — and ensuring your approval matrix, SoD controls, and HMRC-compliant audit trail are in place before your next year-end or VAT inspection. The work covers everything from a one-off workflow health-check to ongoing bookkeeping and compliance support for businesses that want a finance function they can rely on. To find out where your current process stands, get in touch with the KeystoneFA team for a workflow review.
Sources
FAQ
What is an invoice approval workflow?
An invoice approval workflow is the structured sequence of steps a business follows to verify, authorise, and post a supplier invoice before releasing payment. It typically runs from invoice capture through matching, routing, approval, ERP posting, and archiving.
What are the key steps in an AP approval process?
The core steps are: capture and validate, two- or three-way match against the PO and GRN, route to the correct approver, approve within SLA, post to the accounting system, and archive with a full audit trail. Each step has a defined owner and evidence requirement.
How do you approve an invoice correctly?
The approver should confirm the invoice matches the PO and GRN, that the spend is within their authorised limit, that VAT details are correct, and that they have not also raised the original order or authorised the payment run. Any discrepancy outside tolerance should be escalated rather than overridden without documentation.
How does automation improve invoice approval?
Automation handles data extraction, PO matching, duplicate detection, and approval routing automatically, reducing manual keying errors and chasing time. UK finance professionals report spending around 40% of their time resolving errors in manual workflows — automation redirects that effort to higher-value tasks.
Can KeystoneFA help redesign an invoice approval process?
Yes. KeystoneFA works with UK founders and small businesses to assess their current AP workflow, design audit-ready approval controls, and support tool selection and configuration across platforms such as Xero, Sage, and Dext.
Recommended