Procurement most easily loses control on price: contract price, RFQ price, last-deal price, and verbal special-approval price exist at the same time. Orders pick whichever is handy; inbound receipt and reconciliation do not match. Email price lists expire and nobody takes them offline.
Email spreadsheets split the right to set prices
The same item has a “latest price” in attachments across different mailboxes. An RFQ never closed the old agreement; a special approval mentioned once on WeChat is treated as a standing price; volume-tier prices are matched to the wrong quantity band. Each plant maintains its own price list; at group reconciliation the same supplier and same item show three settlement prices. Finance books to the invoice; procurement explains from memory; disputes pile up until they explode at month-end.
The loss is more than paying a little extra: orders placed before an agreement takes effect, expired agreements still cited, special-approval scope copied onto other items. Audit needs “which price version this order line locked at the time.” A spreadsheet cannot produce that snapshot.
| Comparison | Email + spreadsheet | Systematized price list |
|---|---|---|
| Validity window | Date in the file name | Auto-match the valid agreement by date |
| Special approval | Hard to trace on WeChat | Special-approval number bound to the order line with a cap |
| Volume-tier pricing | Easy to pick the wrong band | Band selected automatically by quantity |
| Reconciliation | Many disputes | Locked-price snapshot for three-way matching |
| Audit | Not auditable | Price changes, withdrawals, and special approvals are traceable |
| Multi-plant | Definitions split | Group agreement + plant add-on layers |
System objects: agreement, special approval, locked price, tolerance
Every PO must cite the currently effective agreement. Breaking the price goes through special approval, which states the item, quantity cap, validity period, and reason. Goods receipt and invoices read the locked price on the order line, not the latest email. Objects include agreement price, tiers and surcharges, version, special-approval document, locked-price snapshot, and invoice tolerance. Surcharges (tooling amortization, freight, packaging) belong in the price-list structure; do not open a side column for “communication fees.”
When one item has many codes and unit conversions are not unified, price-list matching misaligns. Clean item master data first, then onboard high-frequency strategic suppliers; do not dump every spot-buy item into the agreement library to pad the count. When group and plant agreements conflict, hard-code the rule: group wins, plant wins, or take the lower price—no ad-hoc choice on the floor.
Rollout sequence and control points
Suggested sequence: versioning and validity rules → lock price at order → invoice tolerance and three-way matching → supplier portal shows our effective price. The portal is read-only for effective prices; price changes still go through internal approval. Split tolerance into absolute amount and percentage. Over tolerance, freeze matching and raise a dispute ticket. Procurement must not rewrite historical locked prices during reconciliation.
Watch special-approval rate, price-break amount, reconciliation dispute duration, and how often expired agreements are still cited. A persistently high special-approval rate means coverage is thin or negotiation is unfinished—not a reason to loosen special-approval rights. Pilot on categories with high spend and relatively standard price terms. Spot buys may keep RFQs, but results must become a short-term agreement or a one-time locked price, not remain in chat history.
Pull price authority back onto the order line
Price-list governance is not a prettier quote sheet. It is locking the price version on every purchase-order line at the moment it is released. Reconciliation then checks quantity, tax, and residual difference within tolerance—not which attachment “counted” at the time. When the supplier’s commercial contact or the buyer changes, the locked-price snapshot remains.
How special approvals and locked prices avoid becoming a new spreadsheet
If special approval only says “you may go cheaper,” without quantity, validity, or whether it can be copied to later orders, in three months it becomes a second price list. Default special approvals to one-time, bound to a specific purchase request or order line. To become a standing price they must go through an agreement version upgrade and retire the old version. A locked-price snapshot must include currency, unit, tax-included flag, volume band, and surcharges. Miss any one, and invoice matching still fails.
FX and index prices such as copper and aluminum need their own model: base agreement + index formula, with the agreed timestamp captured at settlement and the source retained. Do not hand-type the index result into remarks. After a supplier changes commercial staff, old email prices may still be waved around; the system recognizes only the locked-price ID. When a buyer leaves, open special-approval lists must be reassigned so the price bypass does not outlive the authorized person.
Tolerance and disputes in three-way matching
Compare three things: order locked price, received quantity, and invoice unit price. Quantity gaps go to receipt adjustment; unit-price gaps go to tolerance or dispute; tax gaps are listed separately—do not mash them into one “does not match.” Auto-match within tolerance saves finance time, but keep sampling reports so systematic price increases cannot hide inside tolerance. Over tolerance requires a dispute ticket: procurement explains, finance rules, supplier confirms. Close the books only when all three steps are done.
Do not force VMI or consignment onto ordinary purchase price lists. Settlement may trigger on consumption or on invoicing; the price list still needs versions, only the trigger differs. Sample and pilot-run orders should use a one-time locked price and, by default, must not be cited by later mass production. If mass production keeps using sample prices, margin is punched through unnoticed. A procurement monthly report that only shows savings is not enough: put special-approval rate and dispute duration beside it, or savings can be stacked with special approvals.
When annual tender prices and day-to-day agreement prices coexist, the tender result should create a new version with a cutover date; in-transit orders before cutover still use the old locked price. Do not write intended prices into the orderable price list before the tender is complete. Separate procurement authorization amounts from special-approval amounts so “within authorization” is not read as a license to bypass the agreement. Related-party prices must be flagged and take a higher approval path, so internal prices are not mistaken for external agreements. Import duties and inspection fees belong in the surcharge structure—do not wait to allocate them when the invoice arrives. Sample prices expire by default after 30 days; overdue ones require a new RFQ. Consignment consumption reconciliation should not exceed one week; stretch it and disputes are guaranteed. Write the month-end supplier reconciliation cutoff into the agreement; late invoices go to dispute automatically.
XYN Tech has custom delivery experience on supply-chain and procurement collaboration systems. Learn more at https://www.xynadmin.com. Company profile: XYN Tech About Us. Legal entity: Shandong XYN Information Technology Co., Ltd. (XYN Tech).