Piloted a lightweight three-way match module in Q3 and it flagged a 2.3% price creep on our linen contract; we clawed back $14k but AP cycle time slowed two days. Has anyone dialed in a tool or tolerance that catches real variances without straining supplier relationships or clogging approvals?
@OP we saw the same on linens and dialed it in by setting dual tolerances in Coupa: auto-approve within 1% or $150 on contracted SKUs, soft-flag to the buyer at 1–2%, and hard-stop >2% unless the cotton index explains it — kept AP from turning to molasses. We also run a weekly post-audit for credits so suppliers aren’t blindsided; do your terms specify an escalator cap?
Quick example: we moved contracted linens to evaluated receipt settlement in BirchStreet so invoices don’t gate the match; price is locked to the contract, and we only trigger an exception if the receipt qty/UOM mismatches or a vendor provides a price-change reason code. It caught a 1.7% creep without adding a day, but it depends on tight receiving; curious if your module supports ERS or receipt-based settlement so “slowed two days” doesn’t happen, @OP.
We killed the “AP +2 days” drag by auto-short-paying price exceptions and using a cumulative cap: line-level 1%/$100 sails through, but if a supplier’s monthly drift tops 1.5% or $1k we hard-stop and review — caught a 2.3% linen creep without clogging the queue… Pair that with a supplier-facing weekly variance report so they fix catalogs before invoices hit; keeps the relationship sane, . Are you on Coupa or BirchStreet — I can share the rule config we layered on top of @nico_y’s idea.