Choosing AP automation: what actually matters

Most selection criteria lists are vendor marketing

Search for how to choose AP automation software and you will find a dozen checklists. Cloud or on-premise. Number of integrations. OCR accuracy. Mobile approvals. Most of those lists are written by vendors, and they steer you toward the features that vendor happens to sell.

The criteria that fill a shortlist are rarely the ones that decide whether a rollout works. A platform can tick every box and still leave your team keying exceptions six months later. The things that predict success are harder to put in a comparison table, so they get left out.

Take number of integrations, the figure that headlines most comparison pages. A platform that lists hundreds of connectors tells you nothing about the depth of the one you actually need. We connect to 100+ ERP integrations, and the only one that matters to you is yours, done properly. The same goes for a headline accuracy percentage with no note of what it was measured on, or a feature count that treats a checkbox and a working three-way match as equal.

This is a buyer’s guide written from the delivery side. We implement AP automation on the ERP a customer already runs, across 100+ ERP integrations, so we see which decisions hold up once real invoices start flowing. It assumes you already know what AP automation is and are now weighing platforms.

What actually predicts success

Four things separate the implementations that stick from the ones that stall. None of them photograph well in a demo, which is exactly why they get skipped.

Extraction accuracy on your documents

Every vendor quotes an accuracy figure, and it is almost always measured on clean, single-page, English-language invoices in a controlled test set. Your post bag looks nothing like that: scanned images, multi-page invoices, credit notes, handwritten PO references, suppliers who redesign their template every quarter. The number that matters is accuracy on your documents. Ask to run a sample of your own invoices, including the messy ones, and hold the result against the claim. Watch what the platform does with a credit note, a consolidated statement, or an invoice whose line items span two pages. Those are the documents that generate exceptions, and exceptions are where the promised savings quietly leak away. We publish 89% extraction accuracy because it is measured on real customer documents.

Depth of ERP fit

A shallow integration exports a CSV and calls the job done. A deep one validates against live ERP data before anything posts: PO numbers, supplier codes, nominal codes, tax groups, dimensions. It writes invoices back with your coding intact, so nobody re-keys in Sage 200 or Business Central after the fact. Ask exactly how the platform connects to the ERP you run, and what happens to the data on the way in. Ask what it does when a PO is short-shipped, when a supplier bills in a currency you do not usually handle, or when an invoice lands before the goods receipt and sits in GRNI. Those are the moments a shallow integration falls back on a person.

Exception handling

The straight-through invoice is easy. The exception is where the cost lives, and where most tools quietly hand the work back to a person. Look at how the platform routes an invoice that fails to match, how it surfaces the reason, and how much context the approver gets. A good exception queue tells someone what is wrong and what to do about it. A weak one is a list of rejects with no explanation. Ask to see the queue on a real, busy day with genuine exceptions in it, and count the clicks it takes to resolve a price variance, reassign an approval, or chase a missing PO. That click count, multiplied across a month of invoices, is the real running cost of the platform.

UK-based support and BACS awareness

AP is a UK-specific process in ways that matter. Payment runs go out over BACS on a three-day cycle. VAT treatment, CIS deductions and the reverse charge all show up on supplier invoices. Support that understands this, in your timezone, earns its keep the first time a payment run stalls the day it is due. Ask where support sits, who you call when that happens, and whether they know your ERP. Ask how many times the team has implemented the exact ERP you run. Generic AP knowledge is common. Someone who has posted invoices into Sage 200 or NetSuite with your kind of coding is rarer, and it shows the first time something does not reconcile.

What matters less than you think

Some criteria dominate shortlists and deserve less weight than they get.

• Feature-list length. A long feature grid mostly proves the vendor has a big backlog. You will use a fraction of it, and the features you actually need are the unglamorous ones: matching tolerances, approval delegation, clean audit trails.

• Dashboard polish. A clean dashboard is pleasant and easy to demo. It tells you nothing about how the platform behaves when a supplier sends a duplicate or a PO is short-shipped. What decides the rollout is that behaviour, so ask to see it.

• AI buzzwords. Every platform now claims AI. The word carries no information on its own. What counts is what the AI does to your invoice and how accurate it is on your documents. Make the vendor describe the mechanic in plain terms.

None of these are worthless. They are simply poor predictors of whether the platform will still be doing the work in a year, so give them the weight they deserve and no more.

Questions to ask in a demo

Demos are built to show the happy path. These questions pull the conversation off script. Ask them, and watch whether the answers are specific.

1. Can we run a batch of our own invoices right now, including the scanned and multi-page ones? What is the extraction accuracy on that batch?

2. What happens when an invoice does not match its purchase order? Walk me through the exact screens the approver sees.

3. How do you handle a supplier we have never processed before, with a template you have never seen?

4. How does the platform connect to our ERP, and what data does it validate before it posts?

5. What is a realistic exception rate for a team like ours after six months in production, and what drives it?

6. When a payment run is stuck on the day it is due, who do we call, and where are they based?

Choosing AP automation well comes down to refusing to be sold the demo. Bring your real documents, your real ERP and your hardest exceptions to every evaluation. The right platform will welcome it. If a platform is the wrong fit for your setup, a good implementation partner will tell you before you sign.