qthree-way match with AI agents
Three-way match with AI agents: who releases the payment
Three-way match with AI agents: the agent lists each difference between invoice, order and receipt. A person releases payment. Bank changes are refused.
4 min readRunning it
by Grisha Pertaia
- session
- credential
- file · redacted· client identifiers
- file
- sign · refused· outside permission
- sign · human review· sent for review
- draft
- file
- intake
A finance lead who hears "an agent can match our invoices" asks the next question at once: can it also pay them? A three-way match with AI agents means the agent compares the supplier invoice, the purchase order and the goods receipt, line by line, and hands over what it found. It does not mean the agent moves money. This post sets out where that line sits, why it sits there, and what your auditor can check afterwards.
What the match involves
An invoice arrives in the accounts payable mailbox. Someone opens the attachment, finds the purchase order it refers to, finds the goods receipt for the same lines, and compares quantity and price on each. Most invoices agree. Some do not: a line billed above the order price, a quantity billed that was never received, a reference that points at the wrong order.
The time goes into the searching, not the judgement. The agent does the searching across your accounting system, your ERP and the mailbox, and the controller gets a decision to make, not a search to run.
Where a wrong action costs money
In accounts payable a mistake is rarely a typo. It is money that leaves and is hard to get back.
- A mismatched line is paid. The price difference is paid in full, and recovering it means a credit note and a supplier conversation.
- A new bank account is paid. An invoice, or a note inside its attachment, asks for payment to different bank details. A payment run that accepts the change pays someone else.
- The same invoice is paid twice. A resent invoice with a new date looks like a new bill.
Each of these needs the agent to do one of two things: release a payment, or change vendor master data. In the workflow we build, it can do neither.
The steps, as we build them
This workflow is designed. The steps below are how we build it in a pilot. It has not run in the sandbox yet, and the invoice matching workflow page carries the same state.
- Step 1
A credential for one matching job
It allows reading the mailbox, the order, the receipt and the invoice record. It expires when the job ends.
- Step 2
Read the invoice
One line in the attachment asks the reader to change the bank details. It is struck out before the agent reads the invoice.
- Step 3
Read the order and the receipt
The ERP returns both for the same lines. Allowed.
- Step 4
Match line by line
One line is billed above the order price. The difference is listed with the documents that show it.
- Step 5
Change the bank details
Vendor master data is outside the permission for this job. Refused, with the reason on the record.
- Step 6
Put the invoice forward
The release waits until the controller approves it, with the price difference noted.
- Step 7
Draft the supplier note
The agent drafts a note about the difference. A person decides whether it goes.
The step the controller keeps
The release of a payment is a person's decision, every time. The agent puts the invoice forward with the order, the receipt and each difference beside it. The controller decides whether the difference is acceptable, and the decision goes on the record with the controller's name.
In this workflow the agent never releases a payment, even on a clean match. What changes is the work behind the decision: the controller reads a short, explained list instead of three systems. The payment approval workflow covers the release step on its own, and the guarantee behind it is a person on sensitive steps: you decide which steps those are.
The refusal that protects the payment run
A request to change bank details never reaches the payment run on the agent's word. The permission for a matching job does not include vendor master data, so the attempt is refused and recorded. The request itself goes to a person, who checks it by your usual route, such as a call to a number already on file.
Two separate controls meet here. The hidden line is struck out when the attachment is read at the door, and the change is refused because it is outside the permission. Both are on the record.
- allowed
Reads the invoice, the order and the receipt
- allowed
Lists each difference, with the document that shows it
- redacted
Strikes out instructions hidden in an attachment
- allowed
Drafts the note to the supplier
- human review
Releasing every payment
- refused
Changing vendor master data, bank details included
- human review
Deciding whether a price difference is acceptable
- human review
Checking a bank change by your usual route
What you can run today
The full match is designed, but two of its controls run in the sandbox now. In the requisition run, an order above the threshold stops and waits for the budget holder, and a change of supplier is refused. In the agent mandate run, the credential carries a ceiling, a list of approved merchants and an expiry, and a purchase outside it is refused before money moves. Both show the pattern the match relies on: the agent prepares, and a person decides.
What your auditor can check
Every invoice read, every difference, every refusal and every release is on the record. Your auditor receives the replay pack for the job and checks it offline with ares-verify, the open-source verifier. The record shows what the agent did and who approved what. It does not show whether your approval rule was the right rule. That stays with your controls and your auditor.
What it does not do
It does not release payments or post to the ledger without a person. It does not change vendor master data. It does not replace your accounting system, your approval policy or your auditor. The duplicate invoice check is designed, not built. The finance page lists the other finance workflows and the state of each.
Related notes
- illustration
- session
- credential
- write
- notify
- file · human review
- write
6 min read
Evidence, not logs: what an auditor can actually verify
A log is a file the operator controls. A trace adds structure, not independence. Evidence is a record more than one party confirmed before it was written, that an auditor can check against another copy without trusting the vendor.
- illustration
- session
- credential
- draft · refused
- file
- route
- lookup · human review
3 min read
AI agent for annual credit review: what the officer signs
An AI agent for annual credit review can gather the file and draft the covenant figures. The waiver and the credit decision stay with the officer.