Three Way Invoice Match

Matches one invoice against its purchase order and its goods receipt and decides whether the invoice can be paid: explicit line pairing (declared po_line, then exact sku, then a free same-number PO line; no fuzzy text matching), a fixed first-apply line-verdict order (quantity over received, receipt missing as a two-way flag, quantity over ordered, price outside the declared basis-point tolerance with the boundary passing), integer minor-unit totals with half-up tax from one declared rate, and duplicate-invoice screening against same-vendor priors on the normalized invoice number, same total inside the declared day window, or the same PO. Fractional quantities and sub-minor-unit prices are refused with a named reason, never rounded; one currency per invoice; no tax-jurisdiction logic; day differences come from integer days-from-civil arithmetic with no clock.

Tool URL: https://ainumbers.co/chaingraph/art-701-three-way-invoice-match.html AP2/Policy Mandate export: yes