What is being tested
Was a replacement invoiced as a new purchase despite an agreed no-charge replacement obligation? The boundary for this investigation is supplier replacement without new purchase authorization. Begin with the disputed transaction or population, then identify which warranty replacement approval establishes the observed position and which replacement receipt supports the comparison. A difference in totals should not replace this question.
Evidence: warranty replacement approval
For supplier replacement without new purchase authorization, warranty replacement approval must be linked to replacement receipt. Preserve the authorized sender, accepted scope and event timestamp. Distinguish a request from its acceptance and check whether the approver had authority for this change. Later approval should remain visible as a separate event rather than rewrite the original sequence.
Evidence: replacement receipt
For supplier replacement without new purchase authorization, replacement receipt must be linked to original order. 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: original order
For supplier replacement without new purchase authorization, original order must be linked to replacement invoice. 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: replacement invoice
For supplier replacement without new purchase authorization, replacement invoice must be linked to warranty replacement approval. 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
Match replacement purpose and covered failure to the original entitlement and separate uncovered consumables. Build the comparison at the level identified by warranty replacement approval and retain the governing version from replacement receipt. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A customer-requested upgrade may be legitimately chargeable. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked warranty replacement approval, replacement receipt, original order, replacement 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
Quality and procurement confirm replacement coverage. Retain a coverage-to-charge explanation and request correction of unsupported new-sale billing. 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 warranty replacement approval or replacement receipt 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 supplier replacement without new purchase authorization 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
- Receipt reversal after supplier replacement delivery
- Supplier invoice receiving cutover after warehouse transfer
- Goods receipt posted after supplier invoice cutoff
Procurement resource hub · All guides in this evidence collection