Catch Vendor Overcharges Before You Pay

Detect Price Inflation at the Line-Item Level

When a vendor invoices $140/case but the PO says $130 — you want to know before approving payment. The engine compares every line, flags overcharges, and quantifies the leakage.

3-Way Match Engine
247 Matched12 Exceptions
Invoice
$12,500.00
INV-2024-4891
Purchase Order
$12,500.00
PO-4501
Goods Receipt
1,000 qty
GR-7892
3-Way Match: PASS
Price, quantity, and terms verified
98.7%
Confidence
Exception: Qty Variance
INV-4892 · Invoiced 500 · Received 480
-$2,100
Overbilled

Every line compared against agreed pricing — variance quantified in currency.

1–5%

Typical Revenue Leakage

$500K–$3M

Annual Recovery Potential

2%

Default Tolerance

Per-Line

Detection Granularity

How It Works

01

Extract invoice unit prices

AI reads every line item from the invoice — unit price, extended amount, quantity. Works on any format without templates.

02

Compare against PO price

Each invoice line price is compared against the corresponding PO line. Variance calculated as percentage deviation.

03

Apply tolerance rules

Default 2% tolerance. Configurable per vendor, category, or commodity. Variances within tolerance auto-approve.

04

Quantify leakage

Over-charges are calculated: (invoice price − PO price) × quantity = leakage per line. Aggregated by vendor, period, and category.

Capabilities

Per-Line Comparison

Not header-level totals — actual unit price comparison at the line-item level. Catches padding hidden in individual lines.

Expected Cost Check

Compares against both PO terms AND expected cost (product master). Detects cases where POs were issued at inflated rates.

Trend Analysis

Tracks price changes over time per vendor and commodity. Flags gradual creep that stays within single-invoice tolerance but compounds over months.

Contract Price Enforcement

When contracts define pricing tiers or fixed rates, the engine validates invoices against contracted prices — not just POs.

Frequently Asked Questions

What if we don't have PO data?

Without POs, the engine uses historical pricing baselines — comparing this invoice against the same vendor's past invoices for the same items. Statistical outliers are flagged.

Can I set different tolerances per vendor?

Yes. The rules engine supports tolerances at global, category, vendor, and individual item levels. More specific rules override general ones.

How is this different from duplicate detection?

Duplicate detection catches the same invoice submitted twice. Price variance catches legitimate invoices that overcharge versus the agreed price.

No-risk assessment

See what we find before you commit.

Read-only connection. We review a sample of your invoices, agreements and supplier spend, then hand back a findings report with specific figures. If there is nothing to recover, there is nothing to pay.

Read-only accessNo commitmentNothing found, nothing owed
Request an assessment