The platform
The platform behind the pair check
One pair check produces one receipt. This page answers the next question — where does this go — with the checks that run, the legs of a match, and the rungs after the first one.
THE INTERFACE
The working surface.
Three screenshots from our demo tenant. The tenant is synthetic — built so you can inspect the interface before sharing anything — so every number in these images is generated, not a customer’s.
Synthetic demo data — the invoice detail view: variances detected on one invoice, each tied to the PO or contract line behind it
Synthetic demo data — the order hub: every open PO with amount, status, and expected delivery
Synthetic demo data — the vendor view: spend, invoiced volume, and open POs per vendor
WHAT GETS CHECKED
Every tag is a registered detector.
Nothing below is aspirational. Each tag is one anomaly detector registered in the production pipeline — here are 23 of them. The count is the claim: it only moves when a new detector registers.
- Duplicate invoice (exact)
- Duplicate invoice (fuzzy)
- Duplicate invoice (cross-vendor)
- Price variance vs. PO
- Price creep over 90d
- Cross-vendor premium
- Short quantity
- Contract NTE breach
- Expired contract purchase
- Auto-renewal trap
- Clause escalation cap breach
- Clause volume shortfall
- Clause late-delivery penalty
- Freight class mismatch
- Freight FSC formula violation
- Freight FSC variance
- Freight accessorial overcharge
- Freight piece-count mismatch
- BOL/POD weight mismatch
- Carrier insurance expiring
- Carrier credential expired
- Warranty claim expired
- Split-purchase threshold gaming
75+ registered anomaly patterns · growing
MATCHING
Five legs to every match.
Each invoice is checked against five sources. Most tools stop at three — PO, invoice, receipt — and never read the contract or the quote, which is where negotiated terms live and where overcharges hide.
- PO leg
- Line items, quantities, and unit prices on the invoice are checked against the purchase order they bill against.
- Receipt leg
- Billed quantities are checked against what actually arrived — packing slips, BOLs, and goods receipts.
- Contract leg
- Unit pricing is checked against the negotiated rate schedule, price-protection clauses, and not-to-exceed ceilings.
- Quote leg
- PO terms are checked against the original quote, so scope creep surfaces before the invoice does.
- Shipment leg
- Piece counts, weights, and freight charges are checked against the shipment record and carrier terms.
WHERE THIS GOES
The staircase.
Each step is earned by the one before it. You never share more than the last result justified.
- 01
One pair
Forward one invoice and the contract (or PO) behind it. You get a verdict with a receipt.
- 02
One vendor, one quarter
A mini-audit of one vendor's quarter, with a dollar total you can walk line by line.
- 03
Twelve months
The full retrospective audit, paid only on recoveries you confirm.
- 04
Continuous
Every invoice checked before it's paid.
Implementation = forward an email
What the later rungs add.
These run at the continuous rung. None of them are required to start, and none of them are part of a pair check.
- Carrier and OTIF scans
- Rolling on-time-in-full per carrier, lane rate variance, freight invoice matching, and shipment aging — surfaced as actions in a queue, not a separate portal.
- Email automation
- Rules that fire on classified inbound email content. Drafted follow-ups and dispute emails land in the queue for review before anything sends.
- Reports
- Ask in plain English — price variance over 5% in the last 60 days, vendors with declining OTIF, contracts expiring without a renewal thread.
GO DEEPER
The rest of the picture.
Try it on one pair.
Forward one invoice and the contract (or PO) behind it to procurement@kynthar.com. You get a verdict back: matched, or mismatched with the exact line, the billed vs. contracted price, and the clause. One email. No account. No sales call.
Run a pair checkprocurement@kynthar.com