What is being tested
Did a changed supplier price apply by dispatch date when the agreement uses shipment as the trigger? The boundary for this investigation is contract price effective date by shipment. Begin with the disputed transaction or population, then identify which effective-date clause establishes the observed position and which dispatch timestamp supports the comparison. A difference in totals should not replace this question.
Evidence: effective-date clause
For contract price effective date by shipment, effective-date clause must be linked to dispatch timestamp. Retain the applicable wording, effective dates and scope of covered transactions. Identify the event or population that controls the calculation. Do not silently replace a contractual definition with a dashboard label, customary practice or the latest published rule.
Evidence: dispatch timestamp
For contract price effective date by shipment, dispatch timestamp must be linked to old and new price schedules. Record the date convention and timezone where relevant. Separate occurrence, notification and posting times. A later administrative entry may describe an earlier event; the review must use the event specified by the governing record rather than whichever date is easiest to extract.
Evidence: old and new price schedules
For contract price effective date by shipment, old and new price schedules must be linked to invoice. Keep the dated calculation basis, eligible units and any limits or exclusions. Record the sequence of conversion, threshold selection and rounding. An arithmetic result is only supportable after its inputs and applicable version are independently confirmed for the transaction being reviewed.
Evidence: invoice
For contract price effective date by shipment, invoice must be linked to effective-date clause. Keep the issued document version and line-level quantity, currency and service period. A header total cannot establish which component is being tested. Retain later corrections as linked versions, so a replacement does not create a second liability.
Reconciliation logic
Assign deliveries to the stated dispatch-based price version instead of using receipt or invoice date. Build the comparison at the level identified by effective-date clause and retain the governing version from dispatch timestamp. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
Late invoicing may legitimately retain the earlier dispatch price. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked effective-date clause, dispatch timestamp, old and new price schedules, invoice. Document the conflicting input or rule. A plausible operational explanation requires validation, but it should not be discarded to maximize an apparent financial difference.
Human review and outcome
Logistics validates dispatch and procurement validates trigger. Retain a shipment-to-price-version reconciliation. Keep the reviewer's reason and source references with that disposition. A supported correction should be followed to the revised record or settlement; an accepted explanation can close the question with no adjustment. Missing authority or evidence should remain an open task rather than a confirmed recovery.
Limitations and processing boundary
A PO, acceptance record or supplier credit request alone cannot prove a complete recovery. The authoritative supplier, contract, PO, invoice and receipt processor is not complete. Treat commercial interpretation, authorized acceptance and final credit application as separate validation steps. In this scenario, absence of effective-date clause or dispatch timestamp limits whether the comparison can be completed. The review method describes what people should validate, not a promise that AuditRes automatically detects or executes this specific outcome.
AuditRes pathway
Discuss contract price effective date by shipment in the Procurement workspace. Review current plans, the shared platform and secure evidence requirements; use the existing contact path to confirm the sources and validation this scope requires.
AuditRes Procurement: Available for onboarding. Public previews use synthetic demonstration data; production processing remains gated until applicable customer sources and authoritative processors are connected and validated.
Neighboring financial questions
- Review index-linked supplier price adjustments
- Supplier price floor after index decline
- Manufacturer price protection distributor stock
- Catalog item configuration price components
Procurement resource hub · All guides in this evidence collection