What is being tested
Did a release use the price version authorized under its blanket agreement? The boundary for this investigation is blanket po release price-version mismatch. Begin with the disputed transaction or population, then identify which blanket agreement establishes the observed position and which release date supports the comparison. A difference in totals should not replace this question.
Evidence: blanket agreement
For blanket po release price-version mismatch, blanket agreement must be linked to release date. 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: release date
For blanket po release price-version mismatch, release date must be linked to price amendment. 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: price amendment
For blanket po release price-version mismatch, price amendment must be linked to release invoice. 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: release invoice
For blanket po release price-version mismatch, release invoice must be linked to blanket agreement. 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 each release to the governing price version rather than apply the current blanket header price to all history. Build the comparison at the level identified by blanket agreement and retain the governing version from release date. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
An approved release can preserve a prior price. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked blanket agreement, release date, price amendment, release 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
Sourcing validates release precedence and amendment scope. Retain a release-to-price authority map. 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 blanket agreement or release date 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 blanket po release price-version mismatch 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 substitute SKU price equivalence
- Blanket PO amount ceiling versus quantity ceiling
- Procurement card merchant split transaction approval
Procurement resource hub · All guides in this evidence collection