Three-way Purchase Matching Workbench

How to use Three-way Purchase Matching Workbench

Match cumulative rows by your exact purchase line IDs, retain unknown references, compare every billed unit price and reconcile invoice totals without silently rounding.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Match cumulative rows by your exact purchase line IDs, retain unknown references, compare every billed unit price and reconcile invoice totals without silently rounding.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• 1–100 distinct order lines; up to 300 receipt and 300 invoice rows. Quantities are positive and unit prices/tolerances nonnegative, with decimal-string magnitude at most 1 billion. Each row uses one unchanged unit and currency.
• The snapshot must already include all intended prior receipts/invoices. Partial billing is allowed; excess quantity and absolute per-unit price differences create review flags. Returns, credits, tax, FX, document parsing and payment approval are excluded.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.