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 five documents every match is verified against, and the steps from one checked pair to continuous coverage.
THE INTERFACE
The working surface.
The three core views, drawn as idealized compositions, not captures. Every number in them is synthetic and internally consistent, so you can inspect how the interface answers before sharing anything.
Synthetic numbers. The invoice check: two flagged lines, each tied to the PO or packing-slip line behind it, summed to the dollar.
Synthetic numbers. The order hub: every open PO with amount, status, and expected delivery.
Synthetic numbers. The vendor view: spend, invoiced volume, open PO value, and OTIF per vendor, each with its window.
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
100+ registered anomaly patterns · growing
MATCHING
Five legs to every match.
One order produces five documents: the quote, the purchase order, the vendor's acknowledgment, the receipt, and the invoice. Each is checked against the chain before it.
- Quote
- The prices and terms the vendor put in writing before anything was ordered. The PO is checked against it, so scope creep surfaces before the invoice does.
- Purchase Order
- The line items, quantities, and unit prices your team actually ordered. Every document downstream is read against this record.
- Order Confirmation
- The vendor's confirmation of the PO. Substituted items, changed quantities, changed prices, and pushed dates surface here, before anything ships.
- Receipt
- What actually arrived: packing slips, BOLs, and goods receipts. Billed quantities are checked against received quantities, line by line.
- Invoice
- The bill. Every line is checked against the four documents above it, so a price or quantity that drifted anywhere in the chain is caught before payment.
Then the contract.
Most tools stop at three documents (PO, invoice, receipt). Kynthar matches all five, then checks the settled price against the contract behind them: the negotiated rate schedule, price-protection clauses, and not-to-exceed ceilings. That is where overcharges hide.
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.
- 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 check