What is being tested
Did a change in contractual delivery responsibility remove freight already included in supplier pricing? The boundary for this investigation is delivery-term change duplicated logistics scope. Begin with the disputed transaction or population, then identify which old and amended delivery terms establishes the observed position and which price breakdown supports the comparison. A difference in totals should not replace this question.
Evidence: old and amended delivery terms
For delivery-term change duplicated logistics scope, old and amended delivery terms must be linked to price breakdown. 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: price breakdown
For delivery-term change duplicated logistics scope, price breakdown must be linked to transport 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: transport invoice
For delivery-term change duplicated logistics scope, transport invoice must be linked to effective shipment list. 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.
Evidence: effective shipment list
For delivery-term change duplicated logistics scope, effective shipment list must be linked to old and amended delivery terms. Retain stable identifiers and their effective relationships. Current labels are insufficient when assets or accounts changed during the period. Explain one-to-many relationships explicitly and preserve the history needed to distinguish an alias, replacement or reassignment from a genuinely additional item.
Reconciliation logic
Compare responsibility and price scope across the amendment without assuming a standard trade label decides all charges. Build the comparison at the level identified by old and amended delivery terms and retain the governing version from price breakdown. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
Supplemental agreement terms can override a general delivery label. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked old and amended delivery terms, price breakdown, transport invoice, effective shipment list. 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
Procurement and logistics validate the actual signed responsibility split. Return a responsibility-to-price bridge without providing legal interpretation. 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 old and amended delivery terms or price breakdown 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 delivery-term change duplicated logistics scope 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
- Supplier invoice freight allowance reconciliation
- Supplier quote optional-scope inclusion
- Retroactive price change approved purchase population
- Quote validity expiry before purchase acceptance
Procurement resource hub · All guides in this evidence collection