What is being tested
Did open orders move to a successor supplier with documented transfer authority? The boundary for this investigation is supplier transition open-order novation. Begin with the disputed transaction or population, then identify which novation consent establishes the observed position and which open-order schedule supports the comparison. A difference in totals should not replace this question.
Evidence: novation consent
For supplier transition open-order novation, novation consent must be linked to open-order schedule. 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: open-order schedule
For supplier transition open-order novation, open-order schedule must be linked to successor acknowledgment. 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: successor acknowledgment
For supplier transition open-order novation, successor acknowledgment must be linked to successor invoice. 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: successor invoice
For supplier transition open-order novation, successor invoice must be linked to novation consent. 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 transferred order identifiers and remaining scope to the accepted novation rather than supplier name similarity. Build the comparison at the level identified by novation consent and retain the governing version from open-order schedule. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
Some legacy orders may remain with the original supplier. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked novation consent, open-order schedule, successor acknowledgment, successor 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 successor authority and AP validates remaining liability. Produce a transferred-order schedule excluding unauthorized reassignment. 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 novation consent or open-order schedule 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 transition open-order novation 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 transition unused advance payment
- Procurement card merchant split transaction approval
- Off-contract purchase emergency authorization
Procurement resource hub · All guides in this evidence collection