Procurement Contracted Lead Time Master-Data Accuracy

A planning system assumes a component arrives 14 days after ordering, but the active supplier agreement says four weeks before shipment, so procurement contracted lead time master-data accuracy checks whether stored planning values reflect the right agreed timing. Define lead-time components, namely supplier preparation, manufacturing, shipping, customs, receiving and inspection, because a single number may represent only one component.

Microsoft describes purchase requested ship dates calculated from receipt date, lead time, transport days and vendor calendar, which shows why a wrong supplier lead time can distort order timing. Identify the controlling contract, quote or purchase agreement and its effective period, since historical actual deliveries can inform review but do not automatically replace an agreed term.

Link the value to supplier legal entity, item, plant and purchasing unit, because the same supplier may quote different lead times for standard and custom variants. Check whether days are calendar days, business days or supplier working days, as a number without its calendar rule is incomplete data.

Where the supplier quotes a range, define whether planning uses the minimum, typical or reliable upper bound, and record the choice and its service-risk rationale. For a first order, tooling or qualification may add a one-time lead time that should not be permanently added to every repeat order, while a seasonal or capacity clause should be reflected at the proper effective dates because a generic year-round number can make peak planning unrealistic.

Check transport route and destination separately, since a supplier preparation time for shipment from Spain does not include every possible final delivery point, and for Incoterms or freight arrangements ensure the planning endpoint is clear as ready at supplier dock, shipped, delivered or accepted at receiving. Compare the master value with recent supplier acknowledgments, because repeatedly longer confirmed dates may indicate the commercial term is stale and needs renegotiation.

If the agreement is amended, preserve prior effective values for orders placed earlier, since overwriting the master in place can make old planning decisions hard to explain. Where multiple suppliers serve one item, avoid applying the fastest supplier lead time to all sources, and check minimum order quantities and batch cycles because a valid lead time may depend on ordering a full production lot or meeting a recurring cut-off.

Distinguish data accuracy from supplier reliability, since a perfectly accurate contractual value cannot guarantee that every shipment arrives as promised, and define the checkpoint at master review or planned-order generation because a contract that changed yesterday may need an agreed update deadline before being counted as missed. If the contract is silent on timing, mark the field as an estimate with its source and approval rather than labelling it contracted.

Define the denominator as active supplier-item-site records with contracted lead times applicable to current purchasing, retiring inactive records under a stated rule, and classify wrong value, wrong calendar, wrong effective date, wrong destination and missing contract separately because each has a different remedy. Audit selected records from source agreement to purchasing master and sample planned orders, as a correct field in one table may not be the value the planning engine uses.

For urgent orders, seek current supplier confirmation, because a master lead time is planning data, not a live promise that a specific order will arrive, and report exposed planned orders and critical materials alongside the accuracy percentage since one wrong lead time on a sole-source component can matter greatly. Use the measure to keep planning assumptions aligned with supplier commitments; it should improve purchase timing, not make every actual delivery variation look like bad data.