Accounts payable automation is software that takes a supplier invoice from the moment it arrives to the moment the payment clears and the ledger agrees with the bank, with people stepping in only for exceptions and sign-offs. In 2026 that software reads any invoice layout without templates, codes it from your history, matches it to the PO, routes it for approval and pays it over the rail you choose.
The gap it closes is big. Ardent Partners’ State of ePayables 2025 benchmarks (published January 2026) put the average cost at $9.84 per invoice, 8.2 days to process one, and an 18.4% exception rate. Best-in-class teams in the same study run 79% cheaper and 79% faster.
Below: the 6 stages, which tools fit which company size, what changed since 2024, and the controls that stop an automated AP desk from paying a fraudster faster.
The 6 stages of accounts payable automation
Every AP tool sells the same pipeline with different names. Here’s what each stage does and where a person still signs.
| Stage | What the software does | Where a human still signs off |
|---|---|---|
| Capture | Pulls invoices from an AP inbox, supplier portals, e-invoice networks and scans; reads header and line items | Unreadable or suspicious documents |
| Coding | Assigns GL account, cost centre, tax code and entity from past invoices and PO data | Low-confidence codes, new vendors |
| Matching | Checks invoice against PO and receipt (2-way or 3-way) within tolerances | Price or quantity mismatches |
| Approvals | Routes by amount, department and vendor; reminds and escalates | Every approval above threshold |
| Payment | Schedules ACH, card, wire or check; captures early-payment discounts | Payment release, vendor bank changes |
| Reconciliation | Posts to the ERP, matches bank clearing, archives with an audit trail | Month-end review |
1. Capture
An invoice is semi-structured data (we explain the difference in our piece on structured vs unstructured data), and it arrives 4 ways: email PDFs, supplier portals, structured e-invoices and paper. The software needs to collect all of them into one queue.
Extraction is the part that improved most. Microsoft’s prebuilt invoice model reads invoices in 27 languages, from phone photos to digital PDFs, and returns key fields plus line items as JSON. No template per vendor. We cover how these models work in our guide to invoice automation.
2. Coding
Coding is where AP teams used to burn hours: which account, which cost centre, which tax treatment. Modern tools learn from your past postings. Stampli says its AI, Billy, performs on average 89% of the work across coding, routing, matching and approvals. BILL claims its AI codes multi-line bills and cuts manual time by 20% (its own figure, results vary).
Treat these as starting points. The real test is your exception rate after 90 days.
3. Matching
Two-way matching compares the invoice to the PO. Three-way matching adds the goods receipt. The point of tolerances is to stop a $0.40 freight rounding from waking an approver.
Medius publishes a 97% auto-match rate on invoice lines as its headline figure. Coupa lets you set tolerance levels so reviewers only see what breaks. Non-PO invoices (software subscriptions, utilities, legal) skip matching and lean on coding plus approval thresholds instead.
4. Approvals
Routing rules by amount, department, vendor and entity. The software chases approvers, lets them approve from a phone, and records who did what and when.
Ramp’s approval agent goes a step further: it summarizes vendor history and contract details and recommends approval or rejection. The approver still clicks. That’s the right design, and we’ll come back to why in the controls section.
5. Payment
ACH, virtual card, wire and check, scheduled to hit due dates or discount windows. The rail matters for cost. QuickBooks Bill Pay charges $1.50 per check and offers standard ACH free; Ramp lists about $0.59 for standard ACH and $1.99 per check on its free plan. Virtual cards earn rebates and vendors sometimes refuse them.
6. Reconciliation and close
The tool writes the bill and the payment back to the ERP, matches the bank clearing, and stores the invoice image with the full history. Xero, for example, marks bills as paid and reconciles them automatically once a batch payment file goes through the bank.
Tools by company size
Pricing below is what vendors publish in October 2026. Most mid-market and enterprise tools quote per deal.
| Company size | Good fits | What you get | Published pricing |
|---|---|---|---|
| Under 50 people | QuickBooks Bill Pay, Xero bills, Melio, Dext, Ramp Bill Pay | AI bill capture, basic approvals, ACH and check | QuickBooks $0 to $45 per month; Ramp free tier with per-payment fees |
| 50 to 1,000 people | BILL, Stampli, AvidXchange, Tipalti, Vic.ai, Ramp | Coding memory, 3-way match, multi-entity, vendor portals | Quote |
| Enterprise | Coupa, Basware, SAP Concur Invoice, Medius | Procure-to-pay, global e-invoicing compliance, fraud modules | Quote |
Small teams
QuickBooks has 3 tiers: Bill Pay at $0, Premium at $15 and Elite at $45 per month, with approval controls on Elite. Xero reads emailed bills into drafts ready for approval and flags duplicates. Melio adds pay-by-card where cards aren’t accepted and syncs with QuickBooks, Xero and NetSuite. Dext captures receipts and invoices and, in France, is a state-certified Plateforme Agréée for the new e-invoicing regime.
Mid-market
BILL syncs with QuickBooks, NetSuite, Sage Intacct, Xero and Dynamics. AvidXchange lists over 200 integrations and is a licensed money transmitter. Tipalti pays across 200+ countries in 120 currencies with 50+ payment methods, which matters once you pay contractors abroad. Vic.ai pitches an 85% no-touch rate by month 6 (vendor figure).
Enterprise
Coupa now runs on Rossum’s transactional LLM and promises zero-fee e-invoicing for suppliers. Basware claims 190+ countries covered on its e-invoicing network. SAP Concur Invoice does real-time matching against POs and receipts inside the SAP estate.
For a deeper comparison of the capture engines underneath these suites, read our invoice processing software buyer’s guide.
What AI changed since 2024
Four things moved. One didn’t.
Reading got cheap and layout-proof
Vision-language models read a PDF as an image and return structured fields. Claude accepts up to 600 pages per request (100 under a 1M-token context). Mistral OCR 3, released December 2025, costs $2 per 1,000 pages, or $1 with the batch API, and handles handwritten entries on printed forms. Template maintenance, the chore that killed most RPA invoice projects, is gone.
Agents arrived inside the suites
Tipalti ships agents for invoice capture, PO matching, approver recommendations and ERP sync issues. Medius has Supplier Conversations that answers supplier questions about invoice and payment status. These are narrow, supervised agents, which is the version that works.
Gartner’s warning applies here too: it predicts over 40% of agentic AI projects will be canceled by the end of 2027 and calls out “agent washing”, the rebranding of RPA and chatbots as agents. Its advice fits AP well: agents where decisions are needed, plain automation for routine workflows.
Connectors got standard
The Model Context Protocol lets an AI application connect to data sources and tools through one open standard. In practice that means an agent can read your ERP’s open POs or your bank’s clearing file without a bespoke integration for each.
Structured invoices are becoming law
In France, since 1 September 2026, every company must be able to receive electronic invoices, and large and mid-sized companies must issue them; small companies follow on 1 September 2027. The EU’s VAT in the Digital Age package, adopted 11 March 2025, makes cross-border B2B VAT reporting fully digital by 2030. A structured invoice needs no OCR at all, so the capture stage shrinks and validation becomes the job.
What didn’t change
Exceptions. Ardent’s 18.4% average exception rate is still people reading emails and calling vendors. The software gets the 80% right faster. Your process for the other 20% decides whether automation pays.
Controls and fraud checks
Automating AP without automating the controls just pays fraudsters faster. The numbers say this is the main risk.
In the Association for Financial Professionals’ 2026 survey (465 US treasury practitioners, fielded January 2026), 76% of organizations experienced attempted or actual payments fraud in 2025, and 74% were hit by business email compromise. Only 17% use AI to fight it. BEC rose from 63% of organizations in 2024 to 74% in 2025, with spoofed emails reported by 85%.
The FBI’s IC3 logged 24,768 BEC complaints and $3.05 billion in BEC losses in 2025, second only to investment fraud. The same report notes businesses lost over $30 million to BEC scams that used AI, such as chat-generated emails impersonating executives and voice cloning to request wire payments.
Most of this lands in AP as a “please update our bank details” email. The controls that catch it:
- Verify every vendor bank change through a second channel. The FBI’s standing advice is to use secondary channels or two-factor authentication to verify requests for changes in account information. Call the number on file, never the one in the email. Make the tool block payment until the change is verified.
- Enforce segregation of duties in the software. The person who creates a vendor can’t approve its invoices; the approver can’t release payment. Ramp, Stampli and QuickBooks Elite all expose role permissions for this.
- Catch duplicates and near-duplicates: same amount, same vendor, invoice number off by one character. Xero and BILL flag duplicates by default; enterprise suites add fuzzy matching.
- Scale approval thresholds with risk: 2 approvers above a set amount, a third for new vendors or changed bank details.
- Keep payment release as a separate step. Approving an invoice and releasing money are different clicks by different people.
- Put confidence thresholds on AI extraction. Any field below your cutoff goes to a person. A 71%-confidence bank account number should never auto-post.
- Check AI readers for prompt injection. OWASP lists indirect prompt injection through files as a top LLM risk. A PDF can carry hidden text telling the model to mark itself approved. Mitigation: the model extracts, a rules engine decides, a human approves high-risk actions.
- Keep an audit trail you can export: who changed what, when, from which IP. Your auditors will ask.
Only 17% of organizations use AI against fraud, per AFP. The tools above do, if you turn the settings on.
How to roll it out without a 9-month project
- Measure your baseline: cost per invoice, days to approve, exception rate, number of vendors with no PO.
- Clean the vendor master first. Duplicate vendors and missing bank verifications poison every downstream step.
- Start with PO-backed invoices from your top 20 vendors. They match cleanly and show the touchless rate fast.
- Keep every approval and every payment release human for the first quarter. Loosen thresholds once the exception rate falls.
- Report monthly on the same 4 numbers from step 1.
Where AutomationHero fits
We bolt agents onto the edges of your AP suite, for ecommerce and SaaS teams: a Payments watch agent that flags failed payments, chargebacks and payout blocks before they become a cash problem, and an Inbound desk that sorts supplier and partnership email so bank-change requests and invoice queries land with the right person, drafted but never sent without your approval. We install in one session and keep them running for a monthly fee. The full catalog is here.
FAQ
What is accounts payable automation?
Software that moves a supplier invoice from receipt through coding, matching, approval, payment and reconciliation with minimal manual entry. People handle exceptions and approvals; the system handles the rest and keeps the audit trail.
How much does AP automation cost?
Small-business tools publish prices: QuickBooks Bill Pay runs from $0 to $45 per month plus payment fees, and Ramp offers a free plan with per-payment fees. Mid-market and enterprise suites (BILL, Stampli, Tipalti, Coupa, Basware) quote per customer, usually on invoice volume and modules.
Does AP automation replace the AP team?
It replaces data entry and chasing. Someone still owns exceptions, vendor relationships, bank-change verification and the close. Ardent’s 2025 benchmarks show an average 18.4% exception rate, and that work stays human.
Is it safe to let AI approve invoices?
Let AI extract, code and recommend. Keep approval and payment release with named people, enforce segregation of duties in the software, and verify every vendor bank change through a second channel. The 2026 AFP survey found 74% of US organizations hit by business email compromise in 2025, so the control matters more than the speed.
What is a touchless invoice?
An invoice that goes from capture to posted and scheduled for payment with no human edits. PO-backed invoices from established vendors are the first to go touchless. Ardent reports best-in-class AP teams process more than 1.8 times as many invoices straight-through as their peers.