Invoice matching

The pain

Approving a supplier invoice means proving it against the purchase order, the goods receipt, and sometimes an advance payment, line by line, invoice by invoice. Done by hand, that check is slow enough that teams pay first and reconcile later, and duplicates, over-billings, and price creep surface only after the money is gone.

How it works

• Duplicate detection first: every incoming invoice is screened before matching runs: exact duplicates are caught by fingerprint, and near-duplicates (same vendor and invoice number, different amount or date) are held with both versions presented for comparison.
• Two-, three-, and four-way matching: invoice lines are compared against purchase orders, goods receipts, and advance payments; invoices without a usable PO reference are checked against your price references instead.
• Configurable tolerances: quantity and price variances are judged against the tolerances you set, so immaterial differences pass through and real discrepancies stop for review.
• Exception routing: out-of-tolerance lines create review items for the right approver with the variance spelled out, and billed quantities are tracked so the same delivery is never invoiced twice.

What you get

• Clean invoices matched without a human touch; your team sees only real exceptions.
• Duplicates and double-billings stopped before payment, not discovered after.
• Tolerances that encode your policy instead of a clerk's judgment call.
• Every match attempt recorded with its inputs and variances, an audit trail you can stand behind.