Accounts payable automation: invoices read, matched and approved without retyping
Accounts payable automation takes supplier invoices from the inbox to the payment run: the invoice is read, matched against the purchase order and goods receipt, routed to the right approver, posted to accounting and queued for payment, and every step is logged. People handle the exceptions, not the routine invoices. We build invoice processing automation around the ERP or accounting system you already use, hosted in the EU, and your company owns the code.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
A purchase invoice, before and after
In many finance teams a supplier invoice still travels like this: it arrives as a PDF in a shared mailbox, someone downloads it, types the supplier, amounts, VAT and order number into the accounting system, emails the budget owner for approval, waits, chases, checks the order by hand when the amount looks wrong, and finally posts it. Duplicate invoices slip through when the same PDF is sent twice, and nobody can say quickly which invoices are waiting and why.
| Step | Manual today | Automated |
|---|---|---|
| Arrival | Shared mailbox, paper, supplier portals | One intake for email, e-invoice and scan, each invoice logged on arrival |
| Data entry | Typed by hand | Read from the e-invoice or extracted from the PDF, with a confidence score per field |
| Checks | When someone has time | Duplicate check, supplier and VAT number check, order and receipt matching |
| Approval | Email threads and reminders | Routed by cost centre, project and amount, with stand-ins and deadlines |
| Posting | Retyped into the ledger | Posted through the accounting system's interface with the coding proposed |
| Payment | Spreadsheet of due dates | Payment proposal by due date and discount, released by the people your policy names |
This is one of the flows covered by our document workflow automation, built out for the rules finance teams work by.
What we build
- Invoice capture. Email intake, scans and structured e-invoices from your operator or a Peppol access point, all in one queue.
- Data extraction. Supplier, invoice number, dates, amounts, VAT lines, order references and line items. E-invoices are read as data; PDFs and scans go through an extraction engine.
- Validation rules. Your rules written down: duplicates by supplier, number and amount; VAT number format; bank account compared with the supplier record; totals that add up; invoice dates inside the period.
- Purchase order matching. Two-way matching against the order, three-way matching against the order and goods receipt, with tolerances per supplier or category that you set.
- Approval routing. Approvers by amount, cost centre, project or category, with substitutes during absences, reminders before due dates and escalation when an invoice waits too long.
- Review queue. Every uncertain field and every failed check goes to a person, who sees the invoice image next to the extracted data and confirms or corrects it.
- Posting and coding. Proposed account, cost centre and VAT code based on the supplier and earlier invoices, posted only after approval.
- Payment proposals. Due dates, early payment discounts and the bank file prepared for release.
- Audit log. Who saw, changed, approved or released what, and when, kept with the invoice for the storage period.
Purchase order automation and the procure-to-pay chain
Three-way matching only works when orders and receipts exist in the system. Where they do not, purchase order automation comes first: requisitions raised in a simple form, approved by budget owner and amount, turned into purchase orders sent to the supplier, and confirmed against what arrives. Orders can be sent as structured messages where the supplier supports them; the Peppol BIS Ordering 3.3 specification describes a buyer issuing an electronic order that the seller may accept, accept with changes or reject, and states that the order agreed upon by acceptance has the commercial and legal status of a contract (OpenPeppol, read on 12 November 2026). With orders and receipts in place, most invoices that match need no human touch at all, and the ones that do not show exactly where the difference is.
Accuracy, honestly
No extraction engine reads every invoice perfectly, and any number quoted without your invoices behind it says little about your case. The quality depends on how many invoices arrive as e-invoices, how many suppliers send clean PDFs and how many send phone photos of paper. So we measure on your own documents: last month's invoices run through the test version, and you see per field how often the extracted value was right, how many invoices needed a person, and the reasons. The threshold for automatic posting is your decision, made on those results.
The design assumes mistakes will happen and catches them: a value below the confidence threshold never posts on its own, every check that fails sends the invoice to review, and every correction is logged and used to tune the extraction. Extraction engines such as Microsoft Azure AI Document Intelligence, Google Cloud Document AI, Amazon Textract, ABBYY and Rossum can do the reading; we choose one that runs in an EU region and can be replaced later without rebuilding the flow.
Controls against invoice fraud
Fake invoices and changed bank details are the attempts accounts payable teams see most. Automation helps only if the controls are built in, not bolted on:
- A bank account on an invoice that differs from the supplier record stops the invoice and alerts finance.
- Changes to supplier bank details need two people, and the second one confirms with the supplier through a contact already on file, not the one in the request.
- New suppliers are approved before their first invoice can be paid.
- Payment release is separate from invoice approval, so no single person can create, approve and pay.
The rules invoices must follow
In the EU, a business can deduct input VAT only if it holds an invoice drawn up according to the VAT Directive's invoicing articles (Directive 2006/112/EC, Article 178(a)), and Article 226 lists the details an invoice must carry, including the date of issue, a sequential number, both parties' VAT numbers where applicable, the quantity and nature of the goods or services and the taxable amount per rate. Those details become validation rules: an invoice without them goes to review instead of to posting.
The VAT in the Digital Age directive changes the format. From 1 July 2030, invoices are to be issued as electronic invoices that comply with the European standard, and Member States may only accept paper or other formats for transactions outside the new reporting obligations; Member States may already require domestic e-invoicing without asking for a derogation (Directive (EU) 2025/516). Payment terms matter too: under the Late Payment Directive, a payment period fixed in a contract between businesses may not exceed 60 calendar days unless expressly agreed and not grossly unfair to the creditor (Directive 2011/7/EU, Article 3(5)). (All read via the EU Publications Office on 12 November 2026.) Our guide to e-invoicing in the EU covers the national mandates.
Ready-made AP software or custom automation?
Accounts payable products such as Basware, Coupa, Tipalti, Medius, Yooz, Bill and the AP modules of the larger ERP systems cover the standard flow well, and for many companies one of them is the right choice. Custom automation pays off when your approval rules, matching tolerances, project coding or system landscape do not fit the product, or when you want the data and the logic in your own account.
| Situation | Ready-made AP product | Custom automation |
|---|---|---|
| Standard approvals, one ERP | Usually a good fit | Rarely worth building |
| Approvals by project, site and contract | Configurable up to a point | Your rules, as written |
| Several ERPs or companies | Connectors where available | Connected to each system you run |
| Pricing model | Per invoice or per user subscription | Fixed price for the agreed scope, then maintenance |
| Data location and ownership | The vendor's platform | Your account, EU data region |
Accounts receivable is the other side of the ledger; see our guide to automated accounts receivable.
How we build it
- Walk the process. Intake, checks, approvals, posting and payment, mapped with the finance team, including the unwritten rules.
- Scope and fixed price in writing. Invoice channels, rules, integrations and what the first phase leaves out, with a fixed price for that agreed scope.
- A test version on real invoices. Last month's invoices run through capture, extraction and matching, with accuracy shown per field.
- Pilot and acceptance. One company or invoice type runs in parallel with the current process, and the phase is accepted against the written scope.
- Roll out and measure. Time from arrival to approval, invoices touched by a person and late payments compared with the numbers recorded at the start.
- Maintenance. Updates, monitoring, new suppliers and rule changes on a monthly plan you can cancel with one month's notice.
As a standard term, the source code sits in a repository in your company's own account, and the database and hosting are in your name in an EU data region. Teams that also want sales orders read from email can see sales order automation; for the wider picture, see business process automation. See prices.
Questions we get
What is accounts payable automation?
Software that takes a supplier invoice from the moment it arrives to the moment it is paid: it reads the invoice, checks it against the purchase order, the goods receipt and the supplier record, routes it to the right approver, posts it to accounting and prepares it for the payment run. People handle the invoices that do not match, not the ones that do.
Is invoice processing automation the same thing?
Invoice processing automation is the first half of it: capture, data extraction and validation of the invoice. Accounts payable automation also covers approvals, posting, payment runs, supplier questions and the audit trail. We build both as one flow, because an invoice that is read well but approved by email has not saved much.
How accurate is the data extraction?
It depends on your invoices, so we measure it on them. Last month's real invoices run through the test version, and you see per field how often the value was right and how many invoices needed a person. Structured e-invoices are read directly with no recognition step. You set the threshold for automatic posting after seeing the results.
Can it pay invoices automatically?
It can prepare the payment run, with due dates, discounts and the bank file ready. The release of payments stays with the people your payment policy names, and changes to supplier bank details always need a second person to confirm through a separate channel. Those two controls are the ones fraud attempts target.
Does it work with our ERP or accounting system?
Yes. It reads purchase orders, goods receipts and supplier data from your ERP or accounting system and posts approved invoices back through their interfaces. Common systems include Microsoft Dynamics 365 Business Central, SAP, NetSuite, Xero, QuickBooks, Netvisor and Procountor. Your ledger stays the system of record.
What about e-invoicing mandates?
Incoming structured e-invoices are received through your operator or a Peppol access point and read without recognition. Under the EU VAT in the Digital Age directive, electronic invoices become the default from 1 July 2030 and Member States can already require domestic e-invoicing. The flow handles PDFs and e-invoices side by side during the transition.
Who owns the system?
Your company. The source code sits in a repository in your own account, and the database, file storage and hosting are in your name in an EU data region. You can keep us for maintenance, run it yourself or hand it to another team.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.