Supplier invoices are captured from every channel, matched to the purchase order, the goods receipt and the contract price, and posted touchless inside tolerance.
Tuesday 22 September 2026, 08:10. J. Harrison, finance lead, opens the exception desk. Overnight Juno matched 1,180 supplier invoices against purchase orders and receipts in SAP S/4HANA and Oracle Fusion. 1,062 posted inside tolerance. 118 wait in her queue, grouped by cause: price, quantity, missing receipt, suspected duplicate.
Forty-one price blocks come from Brightline Metals SA: the invoice follows price list version 3, the purchase order still carries version 2. Beside each block Juno shows both prices, the contract clause and a drafted release. She approves the 41 in one action, sends 27 quantity blocks to D. Okafor with the receipts attached, and holds six suspected duplicates for the accounts payable manager.
SAP returns a document number for each release. The audit trail keeps the rule version, her login and the acknowledgement, so the internal auditor who samples released blocks at period end reads the same record she did. The morning is the showcase estate; the roles it uses are designed and yet to be built.
The cost of an invoice is the best-measured number in the chain. The average invoice costs $9.40 to process against $2.78 at the top performers, takes 9.2 days against 3.1, and 22% of invoices become exceptions against 9% (Ardent Partners 2025, via WEX, 20 July 2026) 8. The gap between the two columns is people: keying, e-mailing the buyer, waiting for a credit note.
Accounts payable is where AI in procurement has gone first. 58% of accounts payable organisations are using or piloting AI, and 65% expect a significant or transformational effect within three years (Ardent Partners, The State of AP in 2026, via Medius) 9.
Every suite ships a named agent. SAP’s Invoicing Assistant handles capture, duplicate detection and payment proposals (SAP, 14 May 2026) 14; Oracle’s Payables Agent ingests invoices from e-mail, portals and e-invoicing networks with an exception hub (Oracle, 9 August 2026) 26; Coupa’s Invoice Attachment Validation Agent is generally available (Coupa, 20 August 2026) 28; GEP, Basware, Esker and Ivalua ship matching agents as well 45 52 53 46.
The named results are large. Molex reached 87% touchless invoices across 70,000 parts (IT Brief UK, 16 April 2026) 38. McKinsey’s invoice-to-contract reconciliation found over $10M of leakage at one pharma company (McKinsey, 27 October 2025) 10, and agents cut leakage by 4% (McKinsey, 5 February 2026) 11. The top performers’ 9% exception rate is the practical ceiling for touchless posting, and the reason the exception desk stays a desk 8.
An invoice arrives by e-mail, portal, e-invoicing network or EDI. An accounts payable clerk checks the company code and keys the header and lines into SAP or Oracle Payables, or corrects what the scanner read. The ERP proposes a match against the order and the receipt; inside tolerance it posts, outside it the invoice is parked or blocked on price, quantity or date.
The clerk e-mails the buyer. The buyer opens the purchase order, the contract price list and the receipt, asks the supplier for a credit note or raises a price change; the receiving clerk posts a missing goods receipt; a suspected duplicate is checked by hand against the supplier’s history. The clerk releases the block, and an approver signs above the delegation limit.
The payment run picks up due items, and at period end the controller reconciles the GR/IR account and books the accruals. Six roles touch one blocked invoice: the clerk, the team lead, the buyer, the receiving clerk, the controller and the supplier. Elapsed: 9.2 days per invoice, 22% of invoices in exception, $9.40 each (Ardent Partners 2025, via WEX, 20 July 2026).
The manual path as the research note describes it: 9.2 days per invoice on average, 22% of invoices in exception, $9.40 per invoice (Ardent Partners 2025, via WEX, 20 July 2026).
The six stages below are the ones the PO cancellation agent went through in chapter 5, applied to invoices. Everything here is a design: what would be registered and mapped, what a person would ask, what the team would teach, what the agent would do and at which level, and what would improve with feedback.
| Row | Kind | What it would test or do | Data it would read | Then |
|---|---|---|---|---|
| 01 | Check | Price within 2% or $50 of the order price | invoice line price, order line price, currency | carry on |
| 02 | Check | Quantity within the quantity received | invoice quantity, goods receipt quantity | carry on |
| 03 | Check | Supplier, amount and date match an earlier invoice | invoice header, supplier invoice history | hold for the manager |
| 04 | Action | Post the invoice | company code, posting date | the document number is kept |
| 05 | Action | Draft the release with the cause and its basis | both prices, the contract clause, the receipt | row 06 decides the route |
| 06 | Limit | Release value against $10,000 | invoice amount | under: the analyst · at or above: the manager |
A policy sentence the finance lead would state in plain language, and the planning table the Planner Agent would draft from it. The rows are designed; the thresholds are illustrative.
The market runs matched invoices inside rules and drafts the exceptions for a person: Oracle describes near-touchless processing with people on the flagged exceptions (Oracle, 9 August 2026). The blueprint designs capture and matching at A4 and the exception roles at A3. The badge reads A2 because the decision this page is about, releasing a blocked invoice, would start there: the agent drafts, a named person releases. Six weeks of releases would be the evidence for moving the routine causes to A3, as the PO cancellation agent moved.
| Element | Setting | Set by | Changes |
|---|---|---|---|
| Objective | Post every matched invoice inside tolerance and clear each blocked one by cause before it ages ten days | J. Harrison, finance lead | New version |
| Data scope | Invoices, order lines, receipts, price lists, the supplier master and tolerance groups in SAP S/4HANA and Oracle Fusion Payables | A. Novak, data lead | New version |
| Rules | The matching policy and its planning table: price within 2% or $50, quantity within the receipt, a duplicate test on supplier, amount and date | J. Harrison with the Planner Agent | New version, simulated first |
| Trigger | Each invoice arrival · a matching run every 15 minutes, 07:00 to 19:00 · once overnight · the payment calendar | J. Harrison, owner | At once |
| Actions permitted | Post or park · draft a release · create a credit memo request · route a dispute to the buyer | J. Harrison, owner | New version |
| Limits | Release value under $10,000 to the analyst, at or above to the AP manager · daily release budget 300 · confidence floor 0.85 | J. Harrison and the AP manager | New version |
| Escalation | A suspected duplicate, to the AP manager · a bank-detail change, to P. Sharma and a second approver · a failed post, to the owner | J. Harrison, owner | At once |
| Level | A4 Autonomous for matched invoices · A2 Supervised for each release, with J. Harrison as the named approver | The controller | Up on evidence, down in one step |
| Feedback | Every release, edit and hold is recorded with its cause and used in the next cycle | Always on | Fixed |
Every row is a setting or a versioned rule; the level and the limits are the ones a manager signs.
Lima’s agent blueprint is a design of 960 agent roles across five end-to-end chains. It is the map of what Juno can be configured to do, and the first agents are built from it one at a time, the way the PO cancellation agent was.
Additional capability in Procure-to-Pay lists the rest of the map for this chain.
| Measure |
|---|
| touchless rate (Molex 87%) |
| exception rate (22% average, 9% top performers) |
| cost per invoice ($9.40 to $2.78) |
| invoice cycle days (9.2 to 3.1) |
| blocked-invoice ageing |
| late-payment share |
| duplicate payments found |
| discount captured |
| overrides per 1,000 releases |
Baseline the exception rate first, by cause, because it decides everything else: the touchless rate is its complement, the cost per invoice follows it, and the causes tell you which tolerance to write first. Take one quarter of blocked invoices from both ERPs and count them by cause and by supplier before the first rule is drafted; the simulation on the Friday is then a test you can mark.
Yes, after the fact. At A4 the controller audits a sample each period, and every posted invoice carries its match record, the tolerance it passed and the document number the ERP returned.
It is held and routed to the accounts payable manager with the earlier invoice beside it. Payment waits for the decision, and the decision goes on the audit trail with the manager’s name.
Every tolerance is a limit in a versioned rule. Juno would propose a change from the release history; the accounts payable manager approves it as a new version, simulated on last quarter first.
Matching catches an invoice that disagrees with the order. What about the order itself, when a tail requisition was priced by one e-mail to one supplier?
Autonomous sourcing and tail-spend negotiation: the request built from the last award, three bids normalised, and an award drafted for the buyer.
Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.
