The most common AP exception there is, and the one no off-the-shelf tool handles the way your process actually works. Here's what the manual version costs, and exactly what a governed agent does instead.
In reality, they get matched in the system — except when the PO was never raised. Then someone emails the department head for a retroactive one. Unless it's under the threshold, in which case it gets coded to the department's general expense line and flagged for later. Unless the vendor is new, in which case it waits for master data. Every site has its own version of this, and none of it is in the SOP.
Industry-wide, roughly two-thirds of invoices still need at least one human touch, about one in seven becomes a formal exception, and a fully manual invoice costs somewhere north of ten dollars to process. At hundreds of exceptions a month, that's an analyst-week of pure digging — and it's the digging that stretches the close, because exceptions found in week one get resolved in week two.
This is why generic AP software disappoints: it automates the four-step process it was designed for, not the seven-step one you actually run. The exceptions — where all the cost lives — get kicked back to your team.
Vendor, ABN, amount, dates and line items extracted from the PDF or e-invoice and checked against the vendor's history — before anyone has opened the inbox.
Searches your PO system by vendor, amount and date range, exactly the way your analyst would — including the PO raised under a sister entity, or the one dated after the invoice.
Where the match clears the agreed tolerance, the invoice is matched and posted straight into SAP under the agent's own scoped credentials. No human touch, full trace.
Below the confidence threshold, it sends your analyst the two likeliest POs with everything attached — invoice, history, deltas. Fifteen minutes of digging becomes a thirty-second yes or no.
Each approve, edit or reject feeds back into the matching rules, so the share of invoices that clear straight through climbs week on week instead of sitting flat.
The agent can match and post within agreed tolerances — and nothing else. No payment runs, no master data changes, no exceptions to its own rules.
Every action carries a confidence score. Below the threshold your team set, the agent stops deciding and starts asking.
Escalations arrive with the evidence attached, in the tool your team already uses. Nothing is silently swallowed.
What it read, what it matched, what it posted, who approved. Every action reconstructable for your auditor — "the AI said so" is never the answer.
Invoice-to-PO digging leaves the inbox and the spreadsheet, and becomes governed system actions.
Routine touches disappear; your people handle only the cases that genuinely need them.
The agent acts in minutes, around the clock — exceptions stop queueing for the close.
The rules apply the same way every time, so coding errors and bounced approvals fall away.
Baselined in week one from your own event logs, re-measured in week six. The methodology is our Portfolio Process Mining framework.
One agent on your AP exceptions, live in six weeks, for one fixed fee — with the before-and-after measured in your own data.