The invoice with no PO
Playbook · Accounts payable

The invoice with no PO.

The most common AP exception there is. No off-the-shelf tool handles it the way your process actually runs. Here's what the manual version costs — and what a governed agent does instead.

Systems: SAP · Oracle · Coupa · your inbox Runs: continuously, as invoices land Build-ready
Today

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.

Industry-wide, roughly two-thirds of invoices still need at least one human touch. About one in seven becomes a formal exception. 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 the digging 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 lives — come back to your team.

With an agent on the process

Same event. Thirty seconds of human time.

1

Reads the invoice the moment it lands

Vendor, ABN, amount, dates, line items — pulled from the PDF or e-invoice and checked against the vendor's history before anyone opens the inbox.

2

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.

3

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.

4

Escalates only the genuine judgment call

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.

5

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.

15 min → 30 secof human time per exception — and the clean ones need none at all
Governance

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 reconstructable for your auditor — "the AI said so" is never the answer.

Measurement

The numbers this play moves.

▼ down

Work done by hand

Invoice-to-PO digging leaves the inbox and the spreadsheet, and becomes governed system actions.

Measured as DWR · Digital Work Ratio
▼ down

Cost per invoice

Routine touches disappear. Your people handle only the cases that need them.

Measured as CTS · Cost to Serve
▼ down

Time invoices sit waiting

The agent acts in minutes, around the clock — exceptions stop queueing for the close.

Measured as CTE · Cycle Time Efficiency
▼ down

Rework

The rules apply the same way every time, so coding errors and bounced approvals fall away.

Measured as FTR · First Time Right

Baselined in week one from your own event logs, re-measured in week six. The methodology is our Portfolio Process Mining framework.

Run this play as your build.

One agent on your AP exceptions. Live in six weeks. Fixed price. The before-and-after measured in your own numbers.

Book a build scoping call Back to the playbook