What is being tested
Was a tool relocation fee within the approved transfer scope and cost basis? The boundary for this investigation is customer-owned tool relocation fee approval. Begin with the disputed transaction or population, then identify which tool asset record establishes the observed position and which relocation approval supports the comparison. A difference in totals should not replace this question.
Evidence: tool asset record
For customer-owned tool relocation fee approval, tool asset record must be linked to relocation approval. 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.
Evidence: relocation approval
For customer-owned tool relocation fee approval, relocation approval must be linked to quoted move cost. 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: quoted move cost
For customer-owned tool relocation fee approval, quoted move cost must be linked to supplier relocation 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: supplier relocation invoice
For customer-owned tool relocation fee approval, supplier relocation invoice must be linked to tool asset record. 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 the owned tool and approved origin-destination move to the billed work and extras. Build the comparison at the level identified by tool asset record and retain the governing version from relocation approval. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
Rigging or certification work may be separately authorized. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked tool asset record, relocation approval, quoted move cost, supplier relocation 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
Engineering validates tool continuity and procurement validates extras. Produce a tool-move authorization and price bridge. 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 tool asset record or relocation approval 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 customer-owned tool relocation fee approval 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 supplier invoices for customer-owned manufacturing materials
- Procurement card merchant split transaction approval
- Off-contract purchase emergency authorization
- Unauthorized supplier provisional master record
Procurement resource hub · All guides in this evidence collection