The real mismatches, found. The small ones, cleared.

01The situation
Supplier invoices arrive all day. Each should match a purchase order and a goods receipt. In practice, quantities differ. The real mismatches hide among the small ones.
02What the agent does
The agent runs a three-way match on every invoice. Line items against the PO. Quantities against the receipt.
Sure matches post to the ERP as drafts, under a spend limit. Three things go to the AP lead first: amounts over the limit, lines outside tolerance, changed bank details. Restarting a stopped run counts as an approval. It is logged as one.
03Where it stops for a person
- SCOPE
Read the AP inbox, purchase orders and goods receipts · write ERP drafts and match results
- ROLE
Match and draft · never post a final payment
- LIMITS
A spend limit on each run, checked before the action
- REVIEW
Over the limit, outside tolerance or a changed bank detail → the AP lead, by name
- SEAL
Each match, draft and hold in the audit trail, with its sources
W/02In brief
- MATCH
- three-way, line level
- POST
- ERP draft, under spend limit
- HELD
- over limit, outside tolerance or bank detail changed → AP lead
- SEAL
- each exception with its sources
04The outcome
Matching invoices post as ERP drafts. The AP lead sees only the exceptions, each with its sources, and decides under their own name.
Every run shows its spend limit. The record shows every exception, its sources and the AP lead's decision.
Run something like this? Start with a teardown. We measure how much comes in and how much goes wrong. You keep the write-up.
More work we run

Every claim checked before a handler opens it.
Every file had to be checked for completeness before a handler could start.
The first pass runs around the clock. Every routing decision carries its reason.

Every answer cites its clause. Or a person answers.
The same easy questions every day. The hard ones waited behind them.
People only get answers the library backs up. Every correction becomes a worked example.