PO matching when receiving paperwork is days behind
Two-way and three-way matching with realistic field data: how REQUORDIT AP Flow holds an invoice without blocking the rest of the queue.
Three-way match is a clean idea, invoice, PO, receipt all agree, post and pay. Real receiving paperwork is days behind. Here's how REQUORDIT AP Flow handles the gap without freezing the rest of the queue.
Hold, don't block
Invoices waiting on a receipt enter a hold queue with the missing piece flagged. The rest of the day's coding continues. When the receipt lands, manually keyed, EDI'd, or matched by item and quantity, the hold releases and the invoice flows to approval.
Tolerance bands you can defend
- Quantity tolerance per commodity class, bulk materials run looser than discrete parts.
- Price tolerance with a hard ceiling and an exception path.
- Aging threshold, anything held past N days routes to an AP supervisor instead of sitting silent.
Where it goes wrong
Two patterns we coach against: tolerances set so tight every invoice exceptions, and tolerances set so loose the match becomes ceremonial. The right setting is conservative, reviewed quarterly, and tied to commodity, not to vendor.