How to automate accounts payable invoice processing

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 takes invoice volume, handling time and every running cost, including per-invoice AI usage fees.