Invoice matching: How to reduce mismatches and speed up approvals

Invoice matching should be one of the most straightforward controls in accounts payable (AP). You check a supplier invoice against the purchase order and goods receipt, confirm everything lines up, and approve the payment. In practice, it's where a surprising amount of time goes. When invoices arrive without PO numbers and quantities don't match delivery notes, your team ends up having to investigate discrepancies instead of closing the books.

According to Ardent Partners, the average organisation flags roughly 14% of invoices as exceptions requiring manual intervention. Best-in-class AP teams hold their exception rate to 9%, while all others average 22%. That gap comes down to upstream process discipline, and if you’re a mid-market finance team looking to close it without enterprise-scale investment, this article should give you a starting point.

However, this is only a guide for UK finance teams, not legal or tax advice, so consult your accountant or HM Revenue & Customs (HMRC) for your specific circumstances.

What causes invoice mismatches?

Small, repeated process breakdowns cause most invoice mismatches.

Missing or invalid PO data. Ardent Partners research has consistently found that over 60% of invoices are linked to a purchase order, meaning around four in ten arrive without one. When there's no PO to match against, someone on your team has to track down who placed the order, confirm the amount was agreed, and get retroactive approval before the invoice can move forward. That investigation can add days to the cycle for a single invoice, and at volume it compounds quickly.

Pricing and quantity discrepancies. Invoice unit prices may differ from the agreed PO price, or suppliers may invoice for the full PO quantity while delivering in partial shipments. The UK Government's small business plan identifies administrative errors in processing invoices as one of the key drivers of the UK's late payment problem, alongside deliberate poor practice.

Partial deliveries and split shipments. When a supplier delivers against one PO in multiple shipments, each with its own goods receipt note (GRN), the invoicing doesn't always map cleanly. Your team may receive one invoice covering three deliveries, or three invoices against a single PO. Without a way to track cumulative quantities against the original order, these partial matches create exceptions that need manual reconciliation.

Coding errors and missing information. An invoice arrives with the wrong cost centre, an incomplete description, or a mismatched VAT code. These can be time-consuming to fix, and they always seem to arrive during close when your team has the least time to spare. The corrections should have been right at source, and when they're not, the rework falls on the people already handling the highest volume of payables.

Duplicate invoices and unapplied PO amendments. Suppliers sometimes submit the same invoice more than once, or a PO is updated after issuance but the supplier invoices against original terms. Without automated duplicate detection, these can slip through and result in overpayment.

UK Government research estimates that businesses across the UK are owed a combined £26 billion in late payments at any given time, a figure that weighs particularly heavily on mid-market companies managing high invoice volumes. None of these mismatches are individually complicated. The challenge is that they arrive together, every month, and your team has to resolve each one before anything gets paid.

Under the Procurement Act 2023, suppliers bidding on major public sector contracts worth more than £5 million per year must demonstrate they pay their own invoices within an average of 45 days, with at least 95% paid within 60 days. This threshold took effect on 1 October 2025. If mismatches slow your approval cycle, those requirements could cost you eligibility for significant public sector work.

Choose the right matching type

Which matching type you apply depends on the spend category and the level of verification your team needs. Two-way matching compares the purchase order and invoice only. It's the fastest option for services and subscriptions where no goods receipt exists.

Three-way matching adds the goods receipt note and confirms delivery before payment. This is the standard control for physical goods. Four-way matching adds an inspection or quality acceptance report, reserved for high-value or regulated procurement such as pharmaceuticals, defence supply chains, or healthcare equipment.

Most mid-market teams default to three-way matching for physical goods and two-way for services and subscriptions. The choice determines how many documents your team compares on each invoice, which directly affects the tolerances and exception workflows you'll need to configure.

Five upstream fixes to lower your exception rate

If your exception queue keeps growing despite your team working through it diligently, the pattern is usually the same. The problems originate upstream of AP, in how purchase orders are created, how suppliers are onboarded, and how receiving is documented. These are the areas you can actually fix.

Set tolerance thresholds

Many mid-market teams start with auto-approval for invoices within 1% to 2% of the PO value or below a fixed threshold such as £100, fast-track review for variances up to 5%, and full investigation above that. The most common frustration is a threshold that's either too tight (flagging everything, overwhelming your team) or too loose (letting real problems through), so getting the starting point right matters. Your team will tell you quickly which direction you got wrong.

If your average invoice value is £50,000, a £100 fixed threshold is 0.2%, which may flag more exceptions than your team can usefully review. How do you know where to set it? Start by looking at your current exception volume. If your AP team is clearing low-value flags without finding real problems, raise the threshold. If genuine mismatches are slipping through, tighten it. Review quarterly as your invoice mix changes.

Enforce "No PO, No Pay" discipline

A written policy requiring a valid PO before any invoice is processed addresses the matching problem at source. This can feel like a big cultural shift, especially if teams are used to placing orders informally and sorting out the paperwork later. But the alternative is a permanent stream of invoices your AP team can't match.

So how do you get buy-in from teams who've never needed a PO before? The honest answer is that the first few weeks will be uncomfortable. Budget holders will push back when their orders get held up. Sales teams will call it bureaucracy. The friction is real, and it's worth naming it up front rather than pretending the policy will land smoothly.

What makes the difference is showing those teams that the PO isn't about slowing them down. It's about making sure their invoices don't sit in an exception queue for a week while your team tracks down who approved what.

You'd typically set a threshold above which a PO is mandatory, define explicit carve-outs for utilities, payroll, and genuine emergency spend, and require the PO number on every supplier invoice. Including this requirement in your standard terms and supplier management onboarding documentation sets expectations before the first invoice arrives.

Design workflows that match rigour to risk

Route approval workflows by value. Auto-approve low-value matched invoices, require department budget holder sign-off for mid-range amounts, and escalate high-value invoices to the finance director or CFO. This way, your team isn't reviewing every £200 stationery order, but nothing material gets through without the right eyes on it.

As a matter of internal control, many teams also separate PO creation from final invoice approval, which adds a layer of oversight that can prevent errors before they reach the payment queue.

All supplier invoices should also flow into a single AP inbox or invoice management portal so your team isn't chasing documents across shared mailboxes. That reduces duplicate handling and gives you one place to monitor exceptions.

Standardise supplier data at onboarding

It's worth producing an "Invoice Requirements" document listing every mandatory field and distributing it through the supplier onboarding pack and the footer of every PO. Verify the supplier's legal entity name, VAT number, and bank account details before processing their first invoice.

Contact the supplier directly via an independently verified phone number before recording bank details. Restricting access to the vendor master to authorised AP staff and logging all changes protects against both errors and fraud.

Measure your exception rate

Tracking four metrics monthly gives you the clearest picture of where matching is working and where it isn't. These are your invoice exception rate, average receipt-to-approval time, average approval-to-payment time, and exception resolution time. When an exception occurs, log the specific reason.

The real value comes from reading the patterns. If the same supplier shows pricing mismatches six times in a quarter, the root cause is in contract management or procurement upstream of AP. If one cost centre generates a disproportionate share of missing-PO exceptions, the purchasing behaviour in that team needs attention. A monthly review of exception categories by supplier, budget holder, and error type shows you exactly where to intervene.

Over time, this approach shifts your team's focus toward prevention. When finance can show procurement exactly which suppliers or cost centres are generating exceptions, the fixes happen upstream, and the finance function earns a seat in operational conversations it previously wasn't part of.

Automate the matching process

Those five fixes work. They also take sustained effort from a team that's already stretched thin at month-end. Automation doesn't replace the upstream discipline, but it does take the mechanical matching work off your team's plate so they can focus on the fixes that actually prevent exceptions.

With AI-powered optical character recognition (OCR), your team no longer manually keys in supplier names, amounts, PO numbers, VAT details, and line items. Machine learning suggests general ledger codes based on vendor identity and transaction history, growing more accurate over time as it processes more of your invoices. And instead of pulling up each PO to compare manually, algorithmic matching runs the comparison against your tolerance thresholds automatically. When something doesn't match, the right reviewer gets an alert at the point of mismatch rather than discovering it days later.

Spendesk's AP automation, for example, handles the extraction, links each invoice to its corresponding purchase order and delivery notes, and runs three-way matching automatically. If there's a discrepancy, the relevant controller receives an immediate alert. Duplicate invoices are flagged before they reach the payment queue.

Matched invoices export to your accounting system through native integrations with Xero, QuickBooks, or NetSuite. The manual re-keying step disappears.

For growing teams especially, scaling invoice volume without adding headcount to the finance team is where automation delivers the most value.

From matching invoices to preventing exceptions

The 22% to 9% exception rate gap in Ardent Partners' best-in-class research comes down to whether upstream issues are identified and fixed systematically. PO discipline, supplier data quality, and tolerance configuration are where exception rates are won or lost, not at the point of matching itself. If your team can trace each recurring mismatch back to its root cause and close it at source, the exception rate drops and the payment deadlines that affect procurement eligibility become routine to meet. The work isn't glamorous, but it's the kind of operational improvement that compounds quietly and gives your finance team the hours back for forecasting and strategic planning.

Spendesk's accounts payable automation connects the full matching workflow in one process, from automated invoice processing through exception routing to final approval, so your team can fix the upstream problems that generate exceptions.

Frequently asked questions about invoice matching

How long do you need to keep invoice matching records in the UK?

Under the Companies Act 2006 (Section 388), private companies must retain accounting records for at least three years and public companies for six years. VAT records must be kept for at least six years under HMRC rules, or ten years for VAT One Stop Shop schemes. Most companies default to six years to cover both requirements.

What is the UK e-invoicing mandate and how does it affect invoice matching?

Structured e-invoicing transmits invoice data in machine-readable format, which eliminates OCR interpretation errors and manual re-keying. Following a public consultation, the UK government confirmed in November 2025 that mandatory e-invoicing will apply to all VAT invoices from 2029. Even if your business operates entirely within the UK, preparing early for these requirements can reduce your matching exceptions ahead of the deadline.

How does invoice matching connect to the procure-to-pay process?

Invoice matching is one stage within the broader procure-to-pay process. It sits between goods receipt and payment execution, acting as the verification checkpoint that confirms you're paying for what you ordered and received. Stronger matching discipline feeds directly into faster payment cycles and a cleaner month-end close.