An invoice for finance: read the PDF, flag the mismatch, do not pay it
By Team Two · Last updated September 23, 2026 · 1 min read
This is an example, not a customer story, and not a measured result.
A supplier PDF lands in #ap-inbox. The subject is a March invoice for warehouse labels. The purchase orders live in a spreadsheet the finance agent is allowed to read. Nothing in this setup is allowed to move money.
What "match" means here
The agent parses the PDF: supplier, invoice number, date, lines, total, currency. It reads the purchase-order sheet and looks for the same supplier and a PO number. One line on the invoice, a rush fee, is not on the PO.
There is no separate accounts-payable product inside Team Two. The match is against the files you gave the agent. If the PO sheet is stale, the flag is stale. The agent says which file it used.
The note finance actually wants
In #ap-inbox it posts: invoice number, total, the PO it matched, the rush-fee line that did not match, and a one-line recommendation to hold that line. The expense policy in the knowledge base says fees over a set amount need a named approver. The note names that rule and stops.
It does not email the supplier. It does not mark the invoice paid. A draft reply, if you ask for one, waits for approval the same way every other customer or vendor email does.
The person who can say yes
The AP owner accepts the matched lines and sends the rush fee back to the buyer. That decision is the human-input step, whether it happens in Slack or on a workflow. See Workflows that wait for a person.
Frequently asked questions
Can it read a pile of receipts?+
Yes. Excel, PDF, Word, and PowerPoint parsing are built in. Categorize against the policy you uploaded, and send the outliers to a person.
Will it log into the bank?+
No. Do not give it a path to payment. The job ends at the exception list.
