An AI price variance agent compares each invoiced unit price with the PO price and the current contract rate, and calculates the gap per line and in total.
The agent extracts unit prices from invoice lines.
It looks up the PO, contract or price list.
It compares each line and explains the gap.
The buyer accepts, disputes or updates the price.
A dispute draft goes to the buyer for sending.
The decision and any corrected price are saved.
It suggests likely causes, such as a lapsed discount, a price list update, a currency difference or an uplift clause, based on what the contract says.
It routes variances above your tolerance to the buyer with the evidence, and tracks whether the outcome was acceptance, a credit request or a corrected invoice.
Small price differences repeat across hundreds of lines, so they are rarely noticed individually and add up over a year.
The invoice shows a number, but the agreed rate is deep inside a PDF.
Indexation, tiers and expiring discounts change what the right price is.
Conversion and rounding create gaps that are not real overcharges.
A cent on a bolt is not the same as a cent on a licence.
Overcharges are spread thin and are easy to approve.
The agent finds the price on the PO and in the contract or price list that applies on the invoice date.
It computes the difference per unit, per line and in total, in the invoice currency.
It tests common explanations such as an uplift clause, expired discount or tier change.
It separates variances inside tolerance from those that need a decision.
It sends the case to the buyer and records whether it was accepted, credited or corrected.
Bring a small sample and watch Flo work through it.
| Aspect | By hand | With the agent |
|---|---|---|
| Detection | Price differences surface only when someone checks a line. | Every priced line is compared with its agreed source. |
| Source of truth | Analysts pick between PO and contract prices by guess. | The agent states which source it used and why. |
| Cause | The reason for a gap is unclear. | Gaps are labelled as price rise, wrong tier, expired discount or typo. |
| Disputes | Disputes start from memory of the agreed price. | Dispute drafts cite the agreed price and its source. |
| Patterns | Repeat overcharging by a supplier is invisible. | Variance is summarised by supplier and item. |
| If | Then | Who decides |
|---|---|---|
| Invoice price equals agreed price | Passes the line | None |
| Invoice price is above agreed price | Holds the line and shows the gap | Buyer decides |
| Invoice price is below agreed price | Flags it as unusual in case of a missing line | AP analyst checks |
| Contract has a price escalation clause | Checks whether the rise fits the clause | Contract owner confirms |
| Discount expiry date has passed | Notes that the discount may have lapsed | Buyer confirms |
| No agreed price exists | Marks the line unverifiable | Buyer provides the price |
The agent compares in the contract currency and flags conversion effects separately. Finance decides which rate applies.
The agent applies the tier for the quantity bought and shows the working. The buyer confirms the tier.
The agent looks for the notice and links it. The buyer decides whether to accept.
The agent shows both and flags the conflict. The buyer or contract owner says which governs.
Talk it through with the team. We will map it to your steps and show where a person stays in control.
Start with items bought often at fixed prices.
Bring in contract schedules.
Add cause labels for reporting.
Use summaries in supplier meetings.
This shows how often suppliers charge above what was agreed. Track which suppliers appear repeatedly, since a pattern suggests a rate that was never updated or enforced.
Quick answers to what people ask most about price variance.
Book a demoIt is the difference between the price on an invoice and the agreed price on the PO or contract. It can be favourable or unfavourable.
It reads the invoiced price, finds the PO and contract rates, calculates the difference and explains likely causes. A buyer decides what to do.
No. It prepares the evidence and the draft query. A buyer or AP team member raises the dispute with the supplier.
Price variance concerns the unit price. Quantity variance concerns how many units were billed against ordered or received, and each has its own tolerances.
Two-way match is the check that compares an invoice with its purchase order only, confirming that supplier, items, quantities and prices agree with what was ordered.
→Quantity variance is the difference between the number of units billed on an invoice and the number ordered or received.
→Three-way match is the control that compares an invoice with the purchase order and the goods receipt before payment, confirming that what was billed was ordered and received.
→Invoice approval routing is the step of sending each invoice to the person or people with authority to approve it, based on amount, cost center, category and policy.
→Bring a small sample of real items. We will show what Flo handles on its own and where it hands over to your team.
