# How to automate accounts payable invoice processing

> Baseline cost per invoice and cycle time, bring every invoice into one intake, extract and validate with AI, match to purchase orders and receipts, route approvals by rule, then post, pay and measure. With the controls auditors expect.

- Author: Pranav Mahaveer, Founder, SBD
- Updated: 2026-10-28
- Level: Intermediate. Time to do: Four to six weeks
- For: Finance managers and controllers handling roughly 200 to 20,000 supplier invoices a month
- You will end with: An invoice flow from inbox to payment with extraction, matching, approval rules, an audit trail and before-and-after metrics
- Canonical: https://smallbaydigital.com/guides/how-to-automate-accounts-payable/

## Steps

1. **Baseline cost, cycle time and exceptions.** Measure cost per invoice, days from receipt to payment, exception rate and duplicate or late payments.
2. **Bring every invoice into one intake.** One inbox or portal per entity, with supplier e-invoicing where available, and nothing arriving by side doors.
3. **Extract and validate.** Read invoices into fields with AI or OCR, validate against the supplier master, and check for duplicates.
4. **Match to orders and receipts.** Two-way or three-way match within stated tolerances, and send mismatches to a named person with the evidence.
5. **Route approvals by rule.** Approval by cost centre and amount, with delegation, reminders and segregation of duties.
6. **Post, pay and measure.** Post approved bills, pay on terms in scheduled runs, keep the audit trail and compare against the baseline.

> **The short answer.** Measure cost per invoice and cycle time first. Funnel every invoice into one intake, extract fields with AI and validate them against the supplier master, match to purchase orders and receipts within agreed tolerances, route approvals by rule, then post and pay on schedule. Keep a person on exceptions and bank-detail changes, log every step, and re-measure after 90 days.

Accounts payable is the most common first automation in finance, and for good reason: high volume, mostly rule-based, measurable, and expensive when done by hand. It is also where fraud and duplicate payments live, so the controls matter as much as the speed.

## 1. Baseline cost, cycle time and exceptions

Measure before you change anything. You will need these numbers for the business case and to prove the result.

| Metric                | How to measure                                                                          |
| --------------------- | --------------------------------------------------------------------------------------- |
| Invoices a month      | Bills posted, from the accounting system                                                |
| Cost per invoice      | AP staff time at the loaded rate, plus systems and any outsourcing, divided by invoices |
| Cycle time            | Days from invoice receipt to payment, from a sample of 50 to 100                        |
| Exception rate        | Share of invoices that need a person to fix, chase or decide                            |
| Duplicates and errors | Duplicate or incorrect payments found in the last year                                  |

For context, APQC benchmarking data reported by CFO.com put the top quarter of organisations at $2.07 or less per invoice processed and the bottom quarter at $10 or more. APQC also reports that top performers pay in about half the days of the average. Where you sit tells you how much there is to gain.

## 2. Bring every invoice into one intake

Automation cannot process invoices it never sees. Set up one intake per legal entity:

- **A dedicated inbox** such as ap@ for PDF invoices, owned by the AP team, not an individual.
- **E-invoicing or a supplier portal** for large suppliers who can send structured data, which removes extraction entirely.
- **A rule that invoices sent anywhere else** (to a buyer, a manager, a personal inbox) are forwarded to intake, not paid on the side.

Write to suppliers with the address and the information every invoice must carry: purchase order number, legal entity, tax ID. Better invoices in means fewer exceptions out.

## 3. Extract and validate

Turn each invoice into structured fields: supplier, invoice number, date, due date, currency, net, tax, total, PO number and line items where needed.

- **Extraction.** AI models now read most invoice layouts without a template per supplier. Use structured output against a fixed schema, and keep the source document linked to every record.
- **Confidence.** Set a threshold. Fields below it go to a person, highlighted on the document.
- **Validation.** Check every invoice against the supplier master: known supplier, matching tax ID, expected currency, bank details unchanged.
- **Duplicates.** Check supplier, invoice number, amount and date against everything already received, including near matches such as "INV-1043" and "1043".

Treat invoice content as untrusted. An invoice is a document from outside the company, and text in it must never be able to change what the process does. Instructions hidden in documents are a known attack on AI systems, listed first in the OWASP Top 10 for LLM applications.

## 4. Match to orders and receipts

Matching is where most AP time goes, and where rules do most of the work.

| Match     | Checks                                                            | Use for                    |
| --------- | ----------------------------------------------------------------- | -------------------------- |
| Two-way   | Invoice against purchase order: supplier, items, price, quantity  | Services and subscriptions |
| Three-way | Invoice against purchase order and goods receipt                  | Physical goods             |
| No PO     | Invoice against a contract or a recurring schedule, then approval | Utilities, rent, one-offs  |

Agree tolerances with finance and write them down, for example price within 2% or $50, quantity exact. Invoices within tolerance pass automatically. Everything else goes to a named owner with the invoice, PO and receipt side by side and the reason for the mismatch stated.

## 5. Route approvals by rule

Replace "email it to whoever ordered it" with an approval matrix.

- **By cost centre and amount.** For example, the budget holder up to $5,000, the finance manager to $25,000, a director above.
- **Delegation.** Absence is the main cause of late approvals. Every approver names a delegate.
- **Where approvers already work.** Approve from email or chat with the invoice attached, rather than a separate login.
- **Reminders and escalation.** A reminder after two days, escalation after four.
- **Segregation of duties.** The person who can change supplier bank details must not be able to approve payments, and no one approves their own purchase.

Bank-detail changes deserve their own rule. Verify every change by phoning a number already on file, flag the next payment to that supplier, and never let an automated step change bank details because an email asked it to.

## 6. Post, pay and measure

- **Post** approved bills to the accounting system through its API, with the source document and approval history attached.
- **Pay** in scheduled runs aligned to supplier terms. Take early-payment discounts where they beat your cost of capital, and do not pay early otherwise.
- **Keep the audit trail.** Who received, changed, matched, approved and paid each invoice, and when. Auditors will ask, and so will you when a supplier disputes a payment.

After 90 days, re-measure the baseline metrics from step 1. Report cost per invoice, cycle time, exception rate and touchless rate (the share of invoices that went from intake to approved without a person) against the starting figures. Then look at the exceptions that remain: each recurring cause is either a supplier to educate, a rule to add or a process to fix.

To estimate the return before you start, the [ROI calculator](/tools/roi-calculator/) takes invoice volume, handling time and every running cost, including per-invoice AI usage fees.

## Checklist

- [ ] Baseline: invoices a month, cost per invoice, cycle time, exception rate, duplicates found
- [ ] Every entity has one intake address or portal, published to suppliers
- [ ] Invoices arriving elsewhere are forwarded, not processed on the side
- [ ] Supplier master cleaned: duplicates merged, tax IDs and bank details verified
- [ ] Extraction confidence threshold set, with low-confidence fields sent for review
- [ ] Duplicate check on supplier, invoice number, amount and date
- [ ] Matching tolerances agreed with finance and written down
- [ ] Mismatches routed to a named owner with the invoice, PO and receipt attached
- [ ] Approval matrix by cost centre and amount, with delegation for absence
- [ ] No one can both change supplier bank details and approve payment
- [ ] Bank-detail changes verified out of band before any payment
- [ ] Every step logged: who, what, when, with the source document
- [ ] Payment runs scheduled to supplier terms and early-payment discounts
- [ ] Metrics re-measured 90 days after go-live against the baseline

## Sources

- APQC, [4 KPIs that set good accounts payable organisations apart](https://www.apqc.org/blog/4-kpis-set-good-accounts-payable-organizations-apart)
- CFO.com, using APQC Open Standards Benchmarking data, [Metric of the month: accounts payable cost](https://www.cfo.com/news/metric-of-the-month-accounts-payable-cost/659393/)
- OWASP, [Top 10 for Large Language Model Applications, 2025](https://genai.owasp.org/llm-top-10/)

## Questions

### What does it cost to process a supplier invoice?

It varies widely. APQC benchmarking data reported by CFO.com put the top quarter of organisations at $2.07 or less per invoice and the bottom quarter at $10 or more, counting staff, systems, overhead and outsourcing. APQC also reports top performers spend about a fifth of what bottom performers do.

### What is three-way matching?

Checking that the supplier invoice agrees with the purchase order (what was ordered, at what price) and the goods receipt (what actually arrived) before it is approved for payment. Two-way matching checks invoice against purchase order only, and suits services where there is no delivery to receive.

### Is AI extraction accurate enough for invoices?

For common layouts, modern models extract header fields reliably, but no extraction is perfect. Set a confidence threshold, validate fields against the supplier master and purchase order, and send anything uncertain to a person. Measure field accuracy on your own invoices before relying on it.

### How do we stop invoice and bank-detail fraud?

Separate duties so the person who can change supplier bank details cannot approve payments, verify every bank-detail change by calling a number already on file, flag new or changed details on the next payment, and never let an automated process change bank details on the strength of an email.