Why invoice vs PO matching matters

Retail AP teams lose money on quiet unit-price jumps: the same SKU on a Sysco or Grainger invoice that was $24 on the PO now bills $29. Duplicate detection stops you from posting the same invoice twice. Price variance catches the other leak — paying more than the PO or more than the last time you bought that item from the same vendor.

DocuMesh runs this check after extraction, on invoices in your account only. Flagged lines show in red in Scan & Edit. When you push to QuickBooks, you get a warning you can confirm. It never blocks the Bill.

How DocuMesh matches prices

• Match the invoice PO number to a purchase order you already scanned
• Compare unit cost by SKU, then by unique line description
• If there is no PO, compare to that vendor’s last invoice unit price
• Flag overcharges only — undercharges and unmatched SKUs stay quiet
• Ignore penny OCR noise (about two cents or 0.5% of the baseline)

Warn, then still push to QuickBooks

Price variance is a review aid, not a lock. You can export a QuickBooks Online Bill or a Desktop IIF after you see the red lines. That matches how duplicate warnings already work: you decide, the payload does not change.

No matching PO and no vendor history means no flag. Setup and freight lines are included when they match. Start free with 25 documents per month and scan a PO, then the vendor invoice, to see overcharges before they post.