Nexus Grid ProEnterprise ERP & Freight TMS
Implementation

Eight AP Automation Mistakes That Keep Invoices Out of the Touchless Lane

Touchless rates usually stall because of supplier data, tolerances, receipts and non-PO spend, not the software. Here are eight common mistakes and the configuration fix for each.

By the Nexus Grid Pro editorial team · November 2026 · 8 min read

Where Touchless Rates Stall and How to Find the Cause

Say your AP automation software went live with a straight-through target, and months later a stubborn share of invoices still lands in someone's queue. Don't blame the software first. Touchless invoice processing depends on four inputs the vendor doesn't control: how clean your supplier master is, how your match tolerances are set, how quickly receipts reach the ERP, and how much of your spend runs without a purchase order. When a project plateaus, the cause is almost always one of those.

Before you change any settings, pull 90 days of exception data. Tag every held invoice with one primary reason code: vendor not found or ambiguous, price variance, quantity variance, missing receipt, missing or invalid PO, capture error, tax or compliance failure, suspected duplicate, or approval routing. Platforms such as Coupa, Basware, Medius, Esker, Tipalti, Stampli and SAP Concur Invoice, along with the payables modules in SAP S/4HANA, Oracle NetSuite and Microsoft Dynamics 365, generally record some form of exception reason, though the labels and depth differ. If yours lumps everything into a generic "needs review" status, fix that first. You can't tune what you can't see.

Advertisement

Next, rank the reason codes by two measures: invoice count and handling hours. A frequent reason that takes 30 seconds to clear matters less than a rarer one that eats a buyer's afternoon. The eight mistakes below are the causes that usually top those rankings, each with the fix that raises straight-through processing.

A Supplier Master Nobody Owns, and Invoices That Arrive From Everywhere

Mistake: duplicate and stale vendor records

Picture one supplier under three vendor IDs, each with a different remit-to address and only one carrying a valid tax ID. The capture engine can't resolve the vendor with confidence, so the invoice stops. Missing or wrong tax identifiers do extra damage in markets where invoices are validated against them, such as EU VAT numbers, India's GSTIN, Mexico's RFC or a Gulf state TRN.

What to do instead: Deduplicate before go-live, not after. Make tax ID plus legal entity a unique key. Normalize names ("Ltd" vs. "Limited," "GmbH" vs. "Gmbh"), and give ownership of the master to a master-data or procurement operations role rather than AP clerks under deadline pressure. Require a call-back to a contact already on file for every bank-detail change. That's your main defense against payment-redirection fraud, and it doesn't hurt touchless rates because bank changes are rare. Supplier records often hold personal data for sole traders and contacts, so align retention with whichever rules apply to you, such as GDPR in Europe, India's DPDP Act or Brazil's LGPD.

Mistake: letting invoices arrive through any channel

Invoices emailed to a buyer's personal inbox, forwarded three days late, or mailed on paper to a regional office will never be touchless. They arrive late, without context and often without a PO number.

What to do instead: Publish one intake address per legal entity and push high-volume suppliers onto a portal or e-invoicing network. Add a contract and PO clause requiring the PO number on every invoice. Then phase in a "no PO, no pay" rule with a defined grace period, and return non-compliant invoices to the supplier rather than hunting for the PO yourself.

Match Tolerances and Receipt Timing That Manufacture Exceptions

Mistake: one global tolerance for everything

A rule like "0% price variance" holds every invoice with a rounding difference. A loose rule like "5% everywhere" quietly approves overbilling. Both are common, and both suggest nobody tied tolerances to actual risk.

What to do instead: Use tiered tolerances that combine a percentage with an absolute cap (whichever is lower), set by spend category. The table shows illustrative starting points to adjust against your own variance history. They are not benchmarks.

CategoryPrice toleranceQuantity toleranceWhy
Direct materials, contracted price0.5% or $500% over, partials allowedHigh value; contract price should hold
MRO and indirect goods2% or $25Small over-ship allowedLow value, frequent small variances
Bulk commodities by weight or volume1% or $1001–3% either wayScale and meter variance is normal
Freight and surchargesRate-table match, not PON/AFuel and accessorial charges vary by shipment

A hypothetical worked example: a manufacturer buys resin at a contracted $1.84/kg and receives an invoice for 20,000 kg at $1.85/kg. The variance is about 0.54%, or $200. Under the tiered rule above it's held, which is correct, because the contract doesn't allow that price. A $3 rounding difference on a $600 MRO order passes. Get the tolerance policy approved by the controller, and review it every quarter against the variances it actually let through.

Mistake: three-way match against receipts that aren't there yet

Many three-way match failures are really timing failures. The invoice arrives before the goods receipt is posted, or the invoice is in cases while the receipt is in eaches.

What to do instead: Set a receiving SLA, for example posting within one business day of physical receipt, and report on it by site. Configure scheduled auto-rematch runs so an invoice without a receipt waits and retries for a set number of days before it goes to a person. Maintain unit-of-measure conversions on the item or supplier record. For stable, high-trust suppliers, consider two-way match or evaluated receipt settlement, where you pay from the receipt and skip the invoice match altogether.

Capture Tuned for One Invoice Format in a Multi-Country Supplier Base

Mistake: piloting with your easiest invoices

Pilots tend to use domestic suppliers in one language with clean PDFs. Go-live then brings DD/MM dates, decimal commas, several tax lines, Arabic or Thai script and scanned images, and field accuracy drops for whole supplier groups.

What to do instead: Before you sign, build a test set of a few hundred real invoices stratified by supplier country, language, format (native PDF, scan, structured file) and volume tier. Measure accuracy field by field for vendor, invoice number, date, net, tax and total in each group, not as one blended number. Set confidence thresholds per field, so a shaky tax amount triggers review while a confident invoice number doesn't. For your top 50 suppliers by volume, confirm the vendor will tune extraction or apply supplier-specific rules.

Mistake: treating structured e-invoices as just another PDF

A growing number of countries require structured or clearance-model e-invoicing. Examples include Italy's SDI, Mexico's CFDI, India's IRN regime for larger taxpayers, Saudi Arabia's ZATCA phases and Malaysia's phased MyInvois rollout. Belgium and other EU states are moving toward Peppol-based B2B exchange, and the EU's ViDA package points the same way. If your workflow OCRs the PDF copy of an invoice that already exists as validated XML, you're adding errors to data that was already clean.

What to do instead: Ingest the structured file (UBL, CFDI XML or the local format) as the system of record, check its clearance or validation status, and keep the PDF only as a visual copy. Thresholds, scope and deadlines change and differ by country, so confirm your obligations with a qualified tax advisor in each jurisdiction.

Non-PO Spend and Exception Queues Without Owners

Mistake: routing all non-PO invoices to manual coding

Utilities, rent, software subscriptions, telecom, freight and professional services can make up a large share of invoice count. If every one waits for someone to pick a GL account and cost center, your ceiling is fixed no matter how well matching works.

What to do instead: Split non-PO spend into three groups and treat each differently:

  • Recurring, fixed amount (rent, leases, subscriptions): match to a contract or schedule and auto-approve within a narrow band.
  • Recurring, variable amount (utilities, telecom, cloud usage): apply default coding by vendor and auto-approve when the amount falls within a set range of the trailing three- or six-month average.
  • One-off or discretionary (consulting, events, equipment): move these to a PO through procurement policy instead of trying to automate approval after the fact.

Freight works best against carrier rate tables or a freight audit tool, not purchase orders.

Mistake: exception queues nobody owns

When every exception goes to AP, clerks spend their time chasing buyers and warehouses, and the same supplier fails the same way every month.

What to do instead: Send each exception to whoever can fix the root cause, give each queue an SLA, and review the top ten failing suppliers every week.

Exception reasonOwnerFix at source
Vendor ambiguous or not foundMaster dataMerge duplicates, enforce tax ID
Price varianceBuyerCorrect PO or contract price, or dispute with supplier
Missing receiptReceiving siteEnforce posting SLA
Missing PORequester and procurementNo PO, no pay; catalog or blanket PO
Capture errorAP systems leadSupplier-specific tuning or e-invoicing

Here's a rule for the next 30 days: take the single reason code costing the most handling hours, fix it at the source, then measure again. Only when clean reason codes still show capture or matching limits your configuration can't solve should you look at another platform. Until then, switching vendors usually just moves the same dirty data to a new system.

Quick answers

What touchless invoice processing rate should we realistically target?

Your ceiling is roughly the share of invoices that are PO-backed with timely receipts, plus the recurring non-PO invoices you can auto-code. Work that number out from your own invoice mix before accepting any vendor's target. A company with heavy services and utility spend will plateau lower than a distributor buying catalog goods on blanket POs, and that isn't a software failure.

How much does AP automation software cost, and do exceptions affect it?

Typical 2026 market ranges run from roughly $0.50 to $5 per invoice on volume-based plans, or from about $1,000 to well over $10,000 a month for mid-market subscriptions, plus implementation fees. These vary widely by contract, region and invoice volume, so confirm them with vendors. Exceptions rarely change the license fee, but they drive the real cost: staff hours, late-payment penalties and missed early-payment discounts.

Will loosening match tolerances create audit or control problems?

It can, if the change isn't documented or controlled. Auditors generally expect a written tolerance policy approved by finance leadership, absolute caps alongside percentages, segregation between whoever sets tolerances and whoever approves payments, and periodic review of what got through. Requirements differ by jurisdiction and by internal-control framework, so review proposed changes with your external auditor before go-live.

Written by the Nexus Grid Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.