Apply a supplier price-list change by establishing its commercial scope first, mapping its rows to the correct purchasing records, and testing the effective-date rule before an authorized update. Then verify the first affected orders and invoices. A successful file import proves that data moved; it does not prove that the right purchases received the right prices.
Use the price-list change review and verification template (Excel) to track the incoming version, row dispositions, approvals, intended changes, and post-update checks. This guide concerns the operational handoff from a supplier notice to purchasing data. It does not establish whether a supplier is entitled to change a contract price.
Establish which commercial position the file represents
Record who supplied the file, when, its version, and the supplier account and buying entities it covers. Preserve the original attachment and any explanatory message. A spreadsheet named “new prices” may contain a proposal, a published catalogue, or an agreed amendment; those should not be treated as interchangeable instructions.
Ask the commercial owner to identify the applicable agreement and whether the change has been accepted under the team's process. If negotiation is still open, classify the file as proposed and prepare an impact review without updating live agreed prices. If only part of the list is accepted, record that scope at row or material-group level.
Clarify the trigger for the new price: orders placed, supplier acknowledgements, shipments, receipts, or another stated event. Obtain a date and any relevant time-zone boundary where timing matters. A date printed at the top of a file does not necessarily mean every open PO should change on that day.
Keep any grandfathering or order-specific exceptions with the change record. The person preparing the import should not have to interpret contract wording from memory.
Preserve the old and new versions before comparing
Keep a read-only source copy of each supplier file and a separate working comparison. Record the extraction date and previous accepted version. If the supplier sends a correction, add a new version rather than silently replacing the evidence behind an earlier review.
Define the comparison key before matching rows. It may include supplier account, supplier item, internal material, unit, currency, quantity tier, and site. An item number alone can be insufficient when the same item has several pack sizes or commercial conditions.
Retain row identifiers from the source file so questions can point to an exact location. A reviewer should be able to move from a proposed system update back to the supplier's row and the commercial approval that supports it.
Check for duplicate keys, blank prices, missing currencies, and inconsistent date formats. A blank may mean “unchanged,” “not offered,” or missing data. Ask rather than converting it to zero or deleting the current price.
Normalize units before calling a change an increase
Compare the same price basis. Keep supplier units and normalized units alongside each other. A price per carton, reel, hundred pieces, or kilogram requires a documented conversion that applies to the actual material and pack.
For an illustrative item, the old list says $48 per carton of 12. The new list says $4.10 each. The old equivalent is $4 each, so the increase is $0.10 per piece, or 2.5% relative to the old $4 price. Comparing 48 with 4.10 would show a dramatic apparent reduction created entirely by units.
If the carton changes from 12 pieces to 10, record both price and pack changes. The purchase quantity or order multiple may also need review. Do not update only the unit price while leaving an obsolete pack conversion in the material record.
Keep currencies distinct unless finance supplies an evaluation rate and basis. A comparison-rate conversion helps assess impact; it does not change the currency in which the supplier offers to transact. Identify discounts and surcharges separately where their scope changes.
Assign every row a disposition
Classify each row as unchanged, accepted change, proposed change awaiting decision, new item, discontinued item, mapping unresolved, or invalid source data. These are review outcomes, not automatic instructions to create or delete materials.
A new supplier item may map to an existing internal item, but similarity of description is not enough. Have the responsible material owner confirm identity and specification. A discontinued row needs a supply and sourcing decision; its absence from a new file is not sufficient evidence that an existing order should be cancelled.
For accepted changes, record the old and new normalized values, scope, effective-date rule, approval, and intended target record. For unresolved rows, identify the precise missing fact and owner. Continue processing independent accepted rows if the team's controls permit it; do not force guessed mappings to make the file appear complete.
Reconcile counts. The total source rows should equal the rows assigned to documented dispositions, accounting explicitly for headers, duplicates, or excluded records. A smaller imported count without explanation can hide dropped items.
Test existing pricing rules before planning an update
Ask the systems owner where the purchasing price comes from and which agreement takes precedence. Test the applicable item, supplier, entity, quantity, and date conditions in the actual configuration. A generic assumption about “the latest price list” can conflict with the rules already in the ERP.
For example, Microsoft documents that Dynamics 365 purchase-agreement prices can override trade-agreement prices and that agreement validity uses receipt dates. Those are product-specific behaviors to check in the implementation, not universal contract rules. Microsoft purchase agreements.
Create test scenarios for a transaction before the effective boundary, one on it, one after it, an excluded entity, a different quantity tier, and an explicitly protected open order. Record the expected value before running the check. If a test produces a different price, investigate the source or configuration rather than editing the expected result to match it.
Where the commercial rule cannot be represented safely by the current setup, identify the manual control or system change required. Do not load a simplified rule that knowingly prices the wrong population.
Review open orders separately from future purchases
Split the affected population into future requirements, unreleased orders, issued orders awaiting acknowledgement, confirmed open orders, receipts awaiting invoice, and already invoiced purchases. The same notice may have different implications at each stage.
For open orders, preserve the issued price and applicable agreement. Ask the authorized buyer to decide whether an amendment is required and obtain the supplier's response through the normal change process. Updating a purchasing master record should not be treated as evidence that a supplier accepted a PO amendment.
For earlier invoices, a retrospective review may be warranted only if the agreement supports it. Use the contract-price review guide to establish the applicable terms. A future price reduction does not automatically create a credit entitlement for historical purchases or existing stock.
If a price-protection clause or other recovery right may apply, hand that question to the responsible claims owner with its agreement and transaction scope. Keep that possible recovery separate from the forward price update.
Worked example: one notice, three different order outcomes
In this illustrative example, an accepted supplier notice reduces the price of a covered component from $12 to $11.40 for orders placed on or after November 1. The agreement explicitly keeps earlier orders at their accepted price. There are no additional tiers or charges in this example.
- PO A was placed October 29 for 500 units, arriving November 5. It remains at $12, totaling $6,000, because the rule uses order date rather than receipt date.
- PO B will be placed November 2 for 300 units. Its expected price is $11.40, totaling $3,420. At the old price it would be $3,600, a $180 difference to check in the new order.
- PO C was placed October 30 for 200 units, but has not yet been acknowledged. Lack of acknowledgement does not by itself move its order date into November. The buyer must establish its applicable terms rather than automatically repricing it.
The authorized update should support B's new price without treating A or C as automatically eligible. After release, the reviewer checks B's PO and supplier acknowledgement, then the eventual invoice. If B is invoiced at $12, the $180 becomes a supported investigation candidate once the applicable terms and quantity are verified; it is not recovered money merely because the comparison found it.
Now change the notice to use receipt date. The expected classifications change. This is precisely the rule that must be resolved before import. A technically correct upload cannot repair a misunderstood commercial trigger.
Verify the update and handle failures visibly
Have the authorized systems owner record the intended changes, actual update result, rejected rows, and evidence of review. Use the organization's established import, approval, and recovery process. This guide does not replace system-specific procedures for posting or reversing price records.
After the update, check representative accepted rows against the approved source, including the boundary-date and exception scenarios. Include an unchanged control row to ensure the update did not alter more than intended. Verify the first affected purchasing documents rather than relying only on a success message from the upload.
If a problem appears, pause dependent changes within the owner's authority and record the affected scope. Ask the systems owner how to restore or correct the record while preserving history. Do not overwrite issued documents to make them agree with the new master data.
Supplier corrections arriving after the update need a new review. Identify which transactions used the earlier version and assign any resulting order or invoice work. Keep those actions linked to the price-list change so the same issue does not have to be rediscovered downstream.
Close the change with a measurable result
Close when every in-scope row has a disposition, accepted changes are authorized and verified, rejected rows have owners, and affected downstream orders have a defined follow-up. A partially applied list can have a clear status without pretending the whole change is complete.
Measure time from accepted supplier change to verified purchasing update, separating time spent awaiting commercial agreement. Report accepted rows applied and verified divided by accepted rows due for update. Keep proposed and unresolved rows outside that denominator, but show their counts separately.
Review downstream price discrepancies associated with each version. Distinguish source mapping errors, date-rule errors, missed updates, and supplier billing differences. Count each affected invoice line once. These measures help improve the handoff; they are not savings percentages to multiply across all spend.
Mandel's invoice discrepancy work connects purchasing terms with the documents and supplier follow-up that come afterward. A well-controlled price-list change gives that work a clear answer to the first question: which price actually applies?
