Skip to content

Matching invoices

Matching invoices helps you compare an incoming purchase invoice with the records you already expected to see, especially the related purchase order and its line details. This is useful when you want a quick way to catch missing order references, price differences, quantity differences, and totals that do not line up before you finish processing a document.

Use invoice matching when:

  • your team expects invoices to relate to purchase orders
  • you want invoice totals checked against expected totals
  • you want line items compared instead of relying only on the document total
  • you want small differences separated from larger exceptions
  • you want users to review problem invoices before trusting the imported result

From the user perspective, the matching flow is:

  1. process an invoice with an analyzer that has matching turned on
  2. let Sifterra find the expected open purchase order
  3. review the header and, if enabled, line-level comparison results
  4. check whether differences are matched, within tolerance, outside tolerance, or not matched
  5. use Match Results when the invoice outcome needs explanation

For matching to work consistently:

  1. turn on matching in the matching setup
  2. turn on matching for the analyzer that processes the invoice
  3. decide how purchase orders should be found
  4. set tolerance values for price, quantity, and amount
  5. decide whether line matching and partial matching should be used
  6. test with a few real invoices before relying on the results in daily processing
  • Start with wider tolerance values, then tighten them after you review a few real invoices.
  • Use line matching when item-level accuracy matters more than total-only checks.
  • Review the Match Results page whenever users report unexpected approval, review, or mismatch behavior.
  • If matching fails often, focus first on invoice reference quality and purchase order reference consistency.