Touchless match rate
Use it to see how much of the flow runs without exceptions, and read exception causes alongside it.
- Rank exception causes.
- Track days from exception to resolution.
An AI invoice PO matching agent finds the PO an invoice refers to, or proposes one when the reference is missing, and pairs each invoice line with a PO line.
Takes quantities, prices and PO references.
Opens the order and what has been received.
Checks price, quantity and receipt for each line.
Marks full match, partial or exception.
A person resolves differences.
Matched invoices proceed; others wait.
It compares quantity, unit price, tax and total on each pair, and brings in receipt data where your process requires three-way matching.
It labels each line as matched or exception, with the reason and the size of the variance, and routes exceptions to the right owner.
Matching is routine until it is not, and the exceptions consume most of AP's time because the cause lies with someone else.
Invoices quote old, partial or incorrect PO numbers.
One invoice line may cover several PO lines.
Rounding and currency cause noise.
A matched PO can still fail on receipt.
Prior invoices reduce what remains to bill.
Uses the reference, vendor and amounts to locate the matching order, or proposes candidates.
Matches invoice lines to PO lines using items, descriptions, quantities and prices.
Checks quantity, price, tax, currency and remaining open value on each pair.
Brings in receipt quantities for three-way matching where required.
Marks matches and exceptions and sends each exception to the person who can resolve it.
Bring a small sample and watch Flo work through it.
| Aspect | By hand | With the agent |
|---|---|---|
| Lookup | Clerks search for the PO by hand. | The PO is found from the reference or by likely match. |
| Comparison | Lines are compared with price and quantity by eye. | Each line is checked against the PO and the receipt. |
| Tolerance | Small differences are judged case by case. | Agreed tolerances are applied the same way each time. |
| Partial billing | Several invoices on one PO are tracked in notes. | Billed to date is shown per PO line. |
| Exceptions | Failure reasons are vague. | Each exception names the line and the test that failed. |
| If | Then | Who decides |
|---|---|---|
| Invoice lines agree with PO and receipt | Marks as matched and ready for approval | AP team |
| Unit price above the PO price | Flags a price variance | Buyer |
| Billed quantity above the received quantity | Flags a receipt shortfall | Receiver and buyer |
| Invoice quotes a closed PO | Flags the closed status | Buyer |
| Total billed against the PO would exceed it | Flags an overrun | Budget owner |
| Difference sits inside the set tolerance | Passes it and notes the difference | AP supervisor reviews the tolerance |
The agent matches line groups to each PO and shows the split. A specialist confirms the allocation.
The agent flags the added charge as unmatched. The buyer or budget owner decides if it is valid.
The agent keeps the invoice waiting and rechecks when the receipt appears. The receiver is prompted if it stays open.
The agent matches on amount and service period. The budget owner confirms the work done.
Talk it through with the team. We will map it to your steps and show where a person stays in control.
Begin with invoice-to-PO matching in one category.
Include goods receipt checks for physical goods.
Review pass and fail patterns and agree levels with finance.
Extend to service orders and multi-PO invoices.
Use it to see how much of the flow runs without exceptions, and read exception causes alongside it.
Quick answers to what people ask most about invoice PO matching.
Book a demoIt is checking an invoice against its purchase order, and sometimes the receipt, to confirm that what is billed was ordered and received, before the invoice is approved for payment.
Two-way matching compares the invoice with the PO. Three-way matching also compares it with the goods or service receipt, confirming delivery.
The agent can suggest candidate POs from the vendor and amounts, or flag it as a no-PO invoice. A person confirms the link.
A match is evidence for approval. Payment follows your approval and payment process and is carried out by people or approved workflows.
What is invoice vendor matching?
→What is invoice validation?
→What is invoice line item extraction?
→What is invoice tax validation?
→Bring a small sample of real items. We will show what Flo handles on its own and where it hands over to your team.