What is being tested
Was a retroactive price amendment applied only to the orders explicitly covered? The boundary for this investigation is retroactive price change approved purchase population. Begin with the disputed transaction or population, then identify which retroactive amendment establishes the observed position and which covered order list supports the comparison. A difference in totals should not replace this question.
Evidence: retroactive amendment
For retroactive price change approved purchase population, retroactive amendment must be linked to covered order list. 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: covered order list
For retroactive price change approved purchase population, covered order list must be linked to invoice history. 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.
Evidence: invoice history
For retroactive price change approved purchase population, invoice history must be linked to adjustment memo. 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: adjustment memo
For retroactive price change approved purchase population, adjustment memo must be linked to retroactive amendment. Preserve the source owner, transaction reference, period and accepted version. Explain which field answers the financial question and which facts still require confirmation. Incomplete supporting records should create a named evidence gap rather than an assumed quantity, price or entitlement.
Reconciliation logic
Match orders and periods to the amendment's scope before recomputing historical adjustments. Build the comparison at the level identified by retroactive amendment and retain the governing version from covered order list. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A settlement may exclude already disputed or closed orders. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked retroactive amendment, covered order list, invoice history, adjustment memo. 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
Sourcing validates covered population and finance validates existing adjustments. Return a bounded retroactive adjustment schedule without reopening excluded purchases. 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 retroactive amendment or covered order list 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 retroactive price change approved purchase population 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
- Retroactive purchase orders and evidence limitations
- Supplier price floor after index decline
- Contract price effective date by shipment
- Quote validity expiry before purchase acceptance
Procurement resource hub · All guides in this evidence collection