01What AP automation actually covers
| Stage | Manual version | Automated version |
|---|---|---|
| Capture | Invoices arrive by email, post and supplier portals; someone downloads and files them | One inbox or portal; every invoice lands in a queue with its PDF |
| Data extraction | Someone retypes supplier, date, amounts and tax | Fields are extracted automatically and checked against the supplier record |
| Coding | Someone chooses the GL account and cost centre | Coding comes from the PO, or from rules learned on previous invoices |
| Matching | Someone compares the invoice with the PO and receipt | Three-way matching runs on every line, within tolerances |
| Approval | Invoices are forwarded by email and chased | Only exceptions and non-PO invoices are routed, with reminders and escalation |
| Payment | Payments are keyed into the bank one by one | Payment runs are proposed by due date and approved in one batch |
| Recording | Entries are typed into the ledger | Entries are posted automatically, with the invoice attached |
When people say "AP automation", they often mean only the first two rows. The largest savings and the strongest controls are usually in rows four and five.
02What to automate first
- Centralise capture. One address for all supplier invoices, and an instruction to suppliers to use it. Nothing else works until invoices stop living in personal inboxes.
- Purchase orders upstream. Matching needs something to match against. If fewer than half your invoices have a PO, automating matching will mostly produce exceptions. Start with the purchase requisition and PO discipline.
- Extraction and matching together. Once invoices are centralised and most have a PO, extraction feeds matching directly, and clean invoices pass without being touched.
- Exception routing. Send each exception type to its owner, with a deadline and an escalation.
- Payment runs. Group approved invoices into scheduled runs, approved by someone other than the person who entered the supplier's bank details.
Doing these in the wrong order is the most common reason AP projects disappoint: fast extraction feeding a manual approval process just moves the queue.
03Building the business case with your own numbers
Published benchmarks show a wide gap between the best and the rest. APQC reports that top-performing organizations spend about one fifth as much per invoice as bottom-quartile ones, and take half as many days from invoice receipt to payment. Your own numbers matter more, though. Here is how to build them, with an illustrative company:
- Volume: 800 invoices a month.
- Handling time today: 12 minutes per invoice on average (entry, matching, chasing approval, filing). That is 160 hours a month.
- Loaded cost of AP time: $45 an hour, so about $7,200 a month.
- After automation: suppose 60% of invoices pass without touch, and the remaining 40% take 8 minutes each because the gap is already identified. That is 320 × 8 = 2,560 minutes, about 43 hours a month, or about $1,900.
Monthly time saved: about 117 hours, roughly $5,300, before counting anything else. Replace each assumption with your own measurement: time five people for a week, count invoices with and without a PO, and use your actual touchless rate after a pilot rather than a vendor's promise.
Then add the items that are often larger than labour:
- Early payment discounts. A "2/10 net 30" term means 2% off if you pay within 10 days instead of 30. Paying 20 days early to save 2% is equivalent to an annual return of about 37% (2/98 × 365/20). If $200,000 a month of your spend carries such terms and you capture none today, that is up to $4,000 a month left on the table.
- Errors avoided. Duplicate payments and overbilling blocked before payment rather than recovered after.
- Late fees and supplier goodwill. Fewer invoices paid late because they were stuck in an inbox.
04Controls that automation must keep, or strengthen
Automation removes manual touch points, and some of those touch points were controls. Make sure the new process still has:
- Segregation of duties. The person who creates or edits a supplier cannot approve that supplier's invoices or release the payment.
- Bank detail verification. Every change of supplier bank details is confirmed by a call to a number already on file. In the AFP 2025 Payments Fraud and Control Survey, 63% of organizations named business email compromise as the leading avenue for attempted or actual payments fraud, and 79% reported attempted or actual payments fraud in 2024.
- Duplicate detection across invoice number, amount, date and supplier, including near matches such as "INV-1043" and "INV1043".
- An audit trail showing who approved what, when, and on which version of the document.
- Tolerances with caps, so a small percentage of a large invoice cannot pass unseen.
05Questions to ask any AP automation vendor
- What share of invoices passes with no human touch for customers with a PO coverage similar to ours, and how is that measured?
- Does matching work at line level, with partial deliveries and one invoice covering several receipts?
- How are non-PO invoices coded and routed?
- Can tolerances be set by category and supplier, with absolute caps?
- How is a change of supplier bank details controlled?
- Does it handle our tax rules and currencies (VAT, sales tax, GST, withholding), and our e-invoicing obligations where they apply?
- How does it post to our accounting system, and what happens when the posting fails?
- What does the exception screen look like for the person resolving it?
Ask to see the last question live, on your own invoices. The exception screen is where your team will spend its time.
06A 90-day rollout plan
- Days 1 to 30: centralise invoice capture, clean the supplier master (duplicates, missing tax IDs, unverified bank details), and measure today's baseline: volume, handling time, PO coverage, days to pay.
- Days 31 to 60: go live on extraction and matching for suppliers with POs. Set tolerances. Review every exception daily for two weeks and fix causes at the source.
- Days 61 to 90: route non-PO invoices through approvals, start scheduled payment runs, and compare the new metrics with the baseline. Our guide to procure-to-pay KPIs lists the ones worth tracking.
07Starting before you buy anything
If you are not ready for software, two free templates give you the discipline first. The Supplier Invoice Tracker logs every invoice with computed due dates, partial payments and an aging balance; the Supplier Payment Schedule groups invoices into payment runs by due date. When volume outgrows them, see how invoice capture and matching work in Procura.
08AP automation readiness checklist
- One address or portal receives every supplier invoice.
- Baseline measured: invoices per month, minutes per invoice, PO coverage, days to pay.
- Supplier master cleaned: no duplicates, tax IDs present, bank details verified.
- Most invoices by value carry a PO number.
- Tolerances defined by category, each with an absolute cap.
- Bank detail changes verified by call-back to a number on file.
- Supplier creation, invoice approval and payment release are held by different people.
- Early payment discount terms identified and flagged in the payment schedule.