What are the best practices for accounts payable automation?

What are accounts payable automation best practices?

Accounts payable automation best practices are the habits that let software pay most supplier invoices without a person: purchase orders raised before buying, receipts recorded on the day, clean supplier data, structured invoices from suppliers, exceptions removed at their cause, firm fraud controls and monthly measures. Without them, automation only moves problems faster.

What accounts payable automation is, and what it changes at each step from invoice to payment, is explained in what is accounts payable automation. How to design the routes, the rules and the tests for your own invoices is explained in the accounts payable automation process. This page is about running it well: which practices to apply, the problem each one fixes, and the figure that shows it works.

A common situation shows why the practices matter. A company buys an invoice capture tool and expects most invoices to pass alone. Three months later, the accounts payable team still touches two invoices out of three. The software works; the invoices arrive with no order number, before the goods are booked in, or at a price nobody put on the order. The practices below deal with those causes.

Where do most accounts payable automation problems start?

Most accounts payable automation problems start before the invoice reaches accounts payable. An automated match compares the invoice with the purchase order and the goods receipt. If the order was never raised, if the receipt is recorded a week late, or if the order price is out of date, the invoice stops, however good the software is.

• Buying before ordering. An employee asks a supplier for a service by email, and the invoice is the first document the system sees. The purchase order, if any, is raised afterwards to make the invoice payable.
• Late receipts. Goods arrive on Monday; the warehouse records them on Friday. A correct invoice that arrives on Tuesday waits four days.
• Prices that differ from the order. A contract price changed in January, but buyers still copy last year’s price into orders. Every invoice at the new price fails the match.
• Poor supplier data. The same supplier exists three times in the system, one record with an old bank account. The invoice is matched to the wrong record or blocked.
• Unstructured invoices. PDFs and scans need to be read by capture software. New layouts and poor scans produce misread fields that a person corrects.

These causes sit with buyers, receivers, requesters, the supplier data team and suppliers, not with accounts payable. That is why the practices that work are shared between procurement and finance. How the purchase order and the receipt prepare a match is explained in three-way match.

Which practices matter most, and how do you measure them?

The table lists twelve practices in the order most teams need them: before the software goes live, during the rollout, and once it runs. Each line names the problem it fixes and the measure that shows whether it works.

What should be ready before the software goes live?

Four things should be ready before the first invoice is processed automatically: a baseline, purchase orders raised before buying, a cleaned supplier file and one intake channel. Each one takes weeks, not days, so start them while the software is still being chosen.

1. Measure the baseline over at least three months: invoices by channel, share with a purchase order, days from receipt to payment, invoices touched by a person, exceptions by cause, and cost per invoice. The definitions of these measures are in what is accounts payable automation.
2. Agree the purchase order rule with procurement and budget holders. Announce “no PO, no pay” to suppliers with a date and a short list of exceptions such as rent, utilities and taxes. For repeat services, set up a blanket purchase order so each monthly invoice has an order to match.
3. Clean the supplier file: merge duplicates, close suppliers with no invoice for 18 months, check tax numbers and confirm bank details through a known contact. How to keep this data clean afterwards is explained in supplier master data management.
4. Choose one intake channel per invoice format: one e-invoicing route, one supplier portal, and one email address for PDFs. Write to suppliers with the address and the content each invoice must carry, such as the purchase order number.

Watch for orders raised after the invoice. They satisfy the rule on paper but skip the check on price and supplier. The City of York Council, reporting to its audit committee in November 2024, defines retrospective orders as those “where the purchase order date comes after the invoice date” and monitors them by department. A rising share of retrospective orders means the rule is being worked around.

How do you get suppliers to send invoices you can automate?

A structured invoice arrives as data, so there is nothing to read and nothing to misread. Moving suppliers to structured channels is often the largest single gain in accounts payable automation, and laws now push in the same direction.

• E-invoicing networks. Peppol BIS Billing 3.0 is built on the European standard EN 16931. In Germany, every business must be able to receive structured e-invoices from domestic businesses since 1 January 2025. Belgium has required them between VAT-registered businesses since 1 January 2026, and France began phasing them in from 1 September 2026.
• Cross-border invoices in the EU. Under the VAT in the Digital Age package, adopted by the Council of the EU on 11 March 2025, e-invoicing and near real-time reporting for intra-EU transactions will be mandatory from 1 July 2030.
• Supplier portal. Suppliers that cannot send e-invoices can turn a purchase order into an invoice in a supplier portal, so the order number, lines and prices are copied, not retyped.
• PDFs by email. For the rest, one email address, one invoice per PDF, and a clear list of required content keep capture errors low.

Start with the suppliers that send the most invoices. Sort last year’s invoices by supplier: in many companies, a short list of suppliers sends a large share of all invoices. Contact them first, agree a date, and check the first structured invoices with them before switching off paper. Suppliers ask “when will I be paid?”; showing invoice and payment status in the portal answers that and gives them a reason to join. Working with suppliers on their invoices is covered in vendor invoice management.

How do you bring the exception rate down after go-live?

The exception rate comes down when exceptions are counted by cause and the largest causes are fixed where they start. The example is a fictional wholesaler that receives 3,000 supplier invoices a month. Six months after go-live, only 1,050 pass with no manual action, a touchless rate of 35% (1,050 ÷ 3,000). The team counts the 1,950 exceptions of one month by their main cause, then works on the largest causes for the next six months.

If one exception takes about 12 minutes to resolve, an assumption for this example, 1,100 fewer exceptions save about 220 hours of work a month (1,100 × 12 ÷ 60). Most of the gain came from procurement and the warehouse, not from accounts payable. That is the point to make to budget holders when asking for their help.

Two cautions. First, an invoice often has more than one problem; counting only the main cause keeps the table simple but understates the work on mixed cases. Second, do not raise tolerances to make the touchless rate look better. A wider tolerance lets more invoices through unchecked; it hides the cause instead of fixing it.

Which fraud controls must stay in place when invoices move faster?

Automation pays invoices faster, so a fake invoice or a diverted payment also goes out faster. Fraud aimed at payments is common. In the 2025 Payments Fraud and Control Survey of the Association for Financial Professionals, answered by 521 corporate practitioners, 79% of organisations were victims of attempted or actual payments fraud in 2024; 63% cited business email compromise as the main route, and 45% cited vendor impostor fraud, where a criminal poses as a known supplier. The FBI’s Internet Crime Complaint Center recorded reported losses of about $3.05 billion from business email compromise in 2025.

• Verify every bank detail change by phone, on a number already on file or published, never the one in the request. The UK National Crime Agency gives this advice and lists “a regular supplier’s bank details have changed” among the warning signs.
• Separate duties in system roles. The person who changes a supplier record does not approve its invoices or release its payments. The US Government Accountability Office’s internal control standards describe this separation; small teams that cannot separate tasks add a review by someone else.
• Hold the first payment to new bank details for a short review, and send it only after the callback is recorded.
• Keep a second person on payment release, especially for high values and first payments to a new account.
• Check duplicates on supplier, amount and date, not only on the invoice number, so that the same invoice with a slightly different reference is caught.

Write each of these controls as a rule with an owner and a review date. The register that holds the rules, and the tests that prove they work before go-live, are explained in the accounts payable automation process.

How do you keep tolerances and touchless rules under control?

Tolerances and touchless rules are controls: each one lets some invoices through with no person looking at them. Keep them under control with a short quarterly review owned by finance, not by the software team.

1. List every tolerance and touchless rule, with its value, owner and approval date.
2. For each tolerance, pull the invoices that passed under it in the quarter and add up the difference paid. A 2% price tolerance on €4 million of invoices can let up to €80,000 of price differences through without review.
3. Look for patterns: the same supplier always 1.9% above the order price, or one buyer whose orders always need a price change.
4. Lower a tolerance, or remove a supplier from touchless approval, when a pattern appears. Record the change and who approved it.
5. Check that the rules still match the delegation of authority, so that nobody approves above their limit through a rule.

How tolerances work in a match, and what happens to an invoice outside them, is explained in three-way match.

When should automated invoices be paid?

Automated invoices should be paid on their due date, earlier only when an early payment discount is worth more than keeping the cash, and never later. Automation makes this possible because matched invoices are approved within days instead of weeks; the payment run then follows a rule instead of the order in which invoices were found.

Paying late has a direct cost. In the EU, statutory interest on late commercial payments is the reference rate plus at least eight percentage points, with a fixed minimum of €40 for recovery costs. US federal agencies pay a late payment interest penalty automatically when they pay a proper invoice after its due date, generally 30 days after receipt of the invoice or acceptance of the goods, whichever is later. Paying too early has a cost too: the cash leaves the company weeks before it had to. How to value an early payment discount, with a worked “2/10 net 30” example, is shown in what is accounts payable automation.

Which measures show that the practices work?

Review a short set of measures every month, against the baseline, in a meeting with procurement and the main budget holders. The figures matter less than the trend and the actions taken on them.

• Touchless rate: invoices approved for payment with no manual action, divided by invoices received.
• Exceptions by cause and by owner: the table of the worked example above, updated each month.
• Days from invoice receipt to payment: the median, so that a few disputed invoices do not distort it.
• Cost per invoice and invoices per full-time employee: two of the four core accounts payable measures APQC, a benchmarking body, uses. In its 2018 benchmarks, top performers spent one-fifth as much per invoice as bottom-quartile organisations.
• Share of invoices by channel: structured, portal, PDF and paper.
• Orders raised after the invoice, by department: the sign that the purchase order rule is being worked around.
• Late payments and discounts captured: whether the faster process turns into money.

Count each measure the same way before and after, or the comparison means nothing. Published benchmarks count costs and invoices in different ways, so compare your own figures over time first. A wider dashboard for procurement is in procurement KPIs.

Which mistakes undo accounts payable automation?

• Buying software before fixing purchase orders and receipts: the tool then moves the same exceptions faster.
• Automating every entity at once: problems appear everywhere and nobody has time to fix the causes.
• Leaving every exception to accounts payable: clerks chase buyers and receivers by email, and the causes stay where they are.
• Raising tolerances to reach a touchless target: the rate looks better while more differences are paid unchecked.
• Accepting bank detail changes by email: the fastest route to a diverted payment.
• Reporting only cost savings: without the touchless rate and exceptions by cause, nobody sees why the figures move.
• Cutting the team before the process is stable: exceptions, disputes and supplier questions still need skilled people.

Choosing the tool comes after these practices, not before. The method, the criteria and the questions to ask vendors are in accounts payable automation software.