The invoice with no PO.
The most common AP exception there is. Off-the-shelf tools rarely handle it the way your process really runs. Here is what the manual version costs, and what a governed agent does instead.
The SOP says invoices get matched in the system. Reality disagrees.
In reality, they get matched, 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's coded to general expense and flagged for later. Unless the vendor is new, in which case it waits for master data. Every site has its own version. None of it is in the SOP.
In many AP teams, most invoices still need at least one human touch, and a steady share become formal exceptions. At hundreds of exceptions a month, that is an analyst-week of digging. The digging also stretches the close, because exceptions found in week one get resolved in week two.
Generic AP software automates the four-step process it was designed for. You run a seven-step one. The exceptions, where the cost sits, come back to your team.
Same event. Thirty seconds of human time.
Reads the invoice the moment it lands
Vendor, ABN, amount, dates and line items are pulled from the PDF or e-invoice and checked against the vendor's history before anyone opens the inbox.
Finds the PO on its own
Searches your PO system by vendor, amount and date range, the way your analyst would, including the PO raised under a sister entity, or the one dated after the invoice.
Posts the clean matches
Within the agreed tolerance, the invoice posts straight into SAP under the agent's own scoped credentials. No human touch. Full trace.
Escalates only the real judgement calls
Below the confidence threshold, it sends your analyst the two likeliest POs with everything attached: invoice, history, differences. Fifteen minutes of digging becomes a thirty-second yes or no.
Learns from every decision
Every approve, edit or reject feeds the matching rules. The share that clears straight through climbs week on week instead of sitting flat.
The guardrails are the product.
Scoped permissions
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.
Confidence gate
Every action carries a confidence score. Below the threshold your team set, the agent stops deciding and starts asking.
Human review queue
Escalations arrive with the evidence attached, in the tool your team already uses. Nothing is silently swallowed.
Full audit trail
What it read, what it matched, what it posted, who approved. Every action can be traced for your auditor. "The AI said so" is never the answer.
The four numbers this fix moves.
Share of work in the system: 32% → 76%
Invoice-to-PO digging leaves the inbox and the spreadsheet and becomes governed system actions.
Cost of one invoice
Routine touches go. Your people handle only the cases that need them. The cost is reconciled to the ledger.
Share of elapsed time that is real work: 4% → 14%
The agent acts in minutes, around the clock. Exceptions stop queueing for the close.
Share done once, no correction: 81% → 94%
The rules apply the same way every time, so coding errors and bounced approvals fall away.
Figures are illustrative, not a client result. Your baseline is measured from your own event logs in a Capacity and Cost Review, system alone and with the off-system work added, and measured again after the fix. The method is Portfolio Process Mining.
Start with your AP process.
A Capacity and Cost Review measures your invoice process on the four numbers in about four weeks. It shows what to fix first and whether an agent pays. Fixed fee, agreed on scope.