What is being tested
Did the supplier invoice use the price returned to the approved purchase request? The boundary for this investigation is punchout returned price versus checkout price. Begin with the disputed transaction or population, then identify which punchout cart return establishes the observed position and which approved requisition supports the comparison. A difference in totals should not replace this question.
Evidence: punchout cart return
For punchout returned price versus checkout price, punchout cart return must be linked to approved requisition. Preserve the transaction identity, measured or accepted quantity and who confirmed the event. Distinguish physical evidence from later system posting. Where condition affects acceptance, retain the authorized disposition instead of using a raw observation as an automatic commercial conclusion.
Evidence: approved requisition
For punchout returned price versus checkout price, approved requisition must be linked to order transmission. Keep the accepted version, covered scope and relationship to earlier documents. Identify whether it adds, replaces or transfers an obligation. A newer document should not be assumed to govern an earlier transaction unless its scope and effective period support that conclusion.
Evidence: order transmission
For punchout returned price versus checkout price, order transmission must be linked to supplier invoice. Document the observation window, units, inclusion criteria and export version. Identify gaps and corrected events before using the total. Keep raw observations separate from derived quantities so a reviewer can reproduce the population without assuming every logged event is independently chargeable.
Evidence: supplier invoice
For punchout returned price versus checkout price, supplier invoice must be linked to punchout cart return. 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
Compare captured cart price and approved order price with subsequent supplier acknowledgment and amendment. Build the comparison at the level identified by punchout cart return and retain the governing version from approved requisition. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A later authorized order change can supersede the cart. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked punchout cart return, approved requisition, order transmission, supplier 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
Procurement validates transmission history and approved changes. Return a cart-to-order-to-invoice price trace. 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 punchout cart return or approved requisition 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 punchout returned price versus checkout price 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
- Manufacturer price protection distributor stock
Procurement resource hub · All guides in this evidence collection