Approval, Blanket Agreement and Matching Controls Under Go-Live Pressure
Northwind Components runs purchasing for two business units on one deployment. The US unit buys production components and IT services; the Canadian unit buys components only. Policy says goods are three-way matched (order, receipt, invoice) and services are approved on invoice. Requisitions above $5,000 need the cost center manager, then the controller. Eight blanket agreements exist with commodity suppliers, each capped at $250,000. Three symptoms have appeared since go-live. Buyers changing only a need-by date on an approved order trigger a full re-approval cycle and lose three days. A buyer releasing $500 against a blanket agreement at $249,900 released amount is blocked, and has asked for the cap to be removed entirely. IT services invoices stall at month end because no receipt is ever created, so nothing matches. Separately, a requisition sits unapproved because the cost center manager position is vacant, and the buyer has escalated it.
1. Buyers lose three days when only a need-by date changes, and a requisition is stalled by a vacant manager position. How should the approval design be changed?
Read the worked answer
Separate commercial changes from schedule changes. Set up distinct change order types: a commercial type covering price, quantity, supplier, payment terms, which carries full approval; and a schedule type covering need-by dates only, which requires no re-approval but still notifies the buyer's manager. Restrict which attributes each type can carry, and control which types buyers may select, otherwise buyers will choose the cheap type for a price change and the control is gone.
Keep the re-approval that matters. Re-approval exists to stop spend changes slipping through after the fact. Removing it wholesale would let a buyer raise quantity post-approval; date-only changes carry no spend impact and can safely be exempted.
Fix the vacancy with routing design, not with an override. Use approval groups or a position hierarchy so a vacant manager position resolves to a delegate rather than an empty approver, and configure escalation or time-out on the worklist so stalled items surface instead of sitting invisible. Granting the buyer a super-user bypass is the anti-pattern: it removes the segregation of duties that the escalation exposed.
Verify the transaction type rules apply to requisitions and orders consistently, and test with a date-only change and a $1 quantity change to confirm each routes as intended.
2. The buyer wants the $250,000 blanket agreement cap removed. Evaluate that request and set out the options, including how each affects control and auditability.
Read the worked answer
The cap is the authorization ceiling, not an obstacle. It is how management bounded the commitment made when the agreement was competitively awarded. Removing it converts a controlled agreement into open-ended spend with no further approval, which is precisely what an auditor will test.
Options, best first. (1) Amend the agreement through a change order that raises the cap, routed for approval reflecting the additional commitment. This keeps one agreement, one audit trail and a clear authorization date. (2) If the extra spend is genuinely new scope rather than overrun, run a short competitive event and create a separate agreement - but only with a different scope; a second agreement for the same commodities simply fragments spend and defeats leverage reporting. (3) If the cap is systematically too low across all eight agreements, the real defect is the demand estimate used at award, so correct it at renewal and size caps from historical releases plus forecast.
Check the mechanics before acting. Confirm whether control is by amount or quantity, whether the released amount includes open releases, and whether the block occurs at release or at order creation. A $100 overrun on a $250,000 cap is expected behavior, not a bug.
Do not offer the buyer an informal workaround such as a non-catalog requisition outside the agreement; that hides the spend from the agreement's reporting and is the failure mode to design out.
3. How should matching be configured so services invoices stop stalling, and what governance keeps buyers from improvising match options line by line?
Read the worked answer
Match basis is a setup decision, not a month-end fix. Three-way matching requires a receipt, so any line where no physical receipt will ever occur must not use it. For services, use two-way matching (order and invoice) with acceptance evidenced by requester approval, or a services line type with amount-based billing and progress or milestone payments. Reserve three-way matching for goods where the receipt genuinely evidences delivery.
Set the default from the line type or purchasing options, so the correct match basis is inherited rather than chosen, and restrict buyers' ability to change it on the line. Then audit any exceptions rather than allowing silent per-line overrides.
Do not loosen tolerances to clear the queue. Invoice tolerances exist for rounding and minor price drift; using them to force through an invoice with no receipt masks a control failure and will not scale.
Handle in-flight orders deliberately. Changing the match basis on existing orders requires a change order, so pick a cut-off date, apply new defaults to new orders and change only the live service orders that are actually blocked.
Measure the result: unmatched-invoice ageing and receipt lag by category. If goods categories show the same lag, the problem is receiving discipline, not matching setup.