The committed agreement nobody orders against
Tailspin Components signed a 12-month agreement with a fastener vendor: 250,000 units, a tiered unit price that drops once 150,000 units have been bought, and a 4% rebate for early settlement. Buyers create standalone purchase orders because release orders against the agreement take extra clicks, and the agreement is not flagged as default. Last year 340 purchase orders were raised and none referenced the agreement, so committed quantity never accrued and the volume tier was missed; the discount was clawed back as a manual year-end credit note. Freight of about $0.11 per unit is currently posted as a ledger expense instead of being added to item cost, and the items use standard cost. The vendor is also asking that no purchase order be confirmed before controller approval.
1. How do you configure the agreement so ordering naturally consumes the commitment, and what can still go wrong after go-live?
Read the worked answer
Configuration that makes the easy path the correct path
- Mark the agreement Default for the vendor, so a buyer creating a purchase order for that vendor is prompted to use it. Behaviour improvement comes from the default, not from training slides.
- Set Max is enforced so the commitment cannot be exceeded by accident, and set effective/expiration dates that cover the whole 12-month window - an agreement that expires mid-quarter stops accruing silently.
- Define the commitment as a product quantity commitment of 250,000 units, and define the price and discount on the agreement lines. Orders created as release orders against the agreement take the agreement price, which takes precedence over trade agreement pricing.
- Restrict who can create non-release purchase orders for this vendor, or route purchase order creation through workflow so an off-agreement order is visible before it is confirmed.
- Operationalise it: a weekly review of committed versus fulfilled quantity on the agreement, and a named owner for the tier threshold.
What still goes wrong
- Unit of measure mismatch. Agreement in Eaches, orders in Packs, and the commitment never accrues correctly. Fix the conversion before go-live.
- Site dimension. If the 250,000 is meant to cover three sites, decide whether that is one agreement with lines per site or three agreements, and check the commitment report actually sums what you think it sums.
- Behaviour. A default agreement is a nudge, not a control. Without the restriction or workflow, a determined buyer can still bypass it and you will rediscover the problem at year end.
2. The vendor wants approval before any purchase order is confirmed. How does purchase order change management deliver that, what will buyers experience, and where would you keep it narrow?
Read the worked answer
Enable Change management on the vendor record (or via procurement parameters as a default) and attach an approval workflow.
What buyers experience
- A new purchase order starts in a draft, unconfirmed state and cannot be confirmed until the workflow approves it. The buyer is not blocked from working - they are blocked from committing the company.
- Once a purchase order is confirmed, any change to a controlled field requires a formal request for change. A revised version of the order is created, the buyer edits it, and it must be re-approved before it is confirmed again. There is no silent edit path.
- Everything downstream that creates purchase orders - planned order firming, requisitions, intercompany - flows into the same approval gate, which is exactly the point.
Where to keep it narrow
Approval on every purchase order from this vendor is right if the volume is low and the value is high; applied to all vendors it will create a queue and buyers will learn to batch orders to avoid it. Use conditional workflow logic (vendor group, total amount, specific vendor) rather than switching change management on globally.
Two pragmatics to flag: enabling change management on existing vendors does not retroactively reopen confirmed orders, and any interface or data import that creates purchase orders must be able to leave them in a draft, unconfirmed state or the integration will fail at the confirmation step.
3. Freight is expensed instead of capitalised into item cost. Design the charges setup, and state honestly what it can and cannot achieve given standard cost.
Read the worked answer
Charges configuration
- Create a charges code for inbound freight with the Item posting type and the appropriate debit/credit indicator so the amount is treated as an adjustment to the inventory receipt value rather than an expense account hit.
- Attach it through auto charges at vendor and/or purchase order line level, with a per-unit price so it scales at roughly $0.11 per unit. Manual charges are forgotten; auto charges are not.
- Use a charge code group and item charge group so freight is visible in its own column on the receipt and on the inventory value report rather than being buried in a generic cost bucket.
- If freight is recorded at order header level, verify the allocation across lines, otherwise a mixed pallet sends all the freight to the first line.
- Apply charges before the product receipt and invoice post. Charges added after the receipt have to be corrected through a separate adjustment, and the audit trail gets ugly.
The honest limitation
Under standard cost, an inventory receipt is valued at the item's standard cost. An item charge added to the receipt therefore does not quietly raise on-hand value - it lands in a purchase price or charges variance instead. If finance genuinely wants freight inside inventory value, freight has to be in the standard: add it as a cost group in the cost build-up (a freight or inbound-logistics cost group in the costing sheet, with the percentage or rate maintained in the costing version) and revalue when the freight rate changes.
So the correct answer is two-part: configure the charge so it posts to the item and is reported transparently, and fix the standard cost build-up so the $0.11 is in the standard rather than argued about every quarter.