What is being tested
Were replacement parts separately invoiced despite inclusion in the maintenance coverage? The boundary for this investigation is equipment maintenance parts already included. Begin with the disputed transaction or population, then identify which maintenance coverage schedule establishes the observed position and which parts work order supports the comparison. A difference in totals should not replace this question.
Evidence: maintenance coverage schedule
For equipment maintenance parts already included, maintenance coverage schedule must be linked to parts work order. Record the effective configuration or entitlement rather than only the current state. Explain how it relates to the billed service. Operational availability and commercial scope can differ, so a configuration change alone does not prove that the supplier charge should have ceased.
Evidence: parts work order
For equipment maintenance parts already included, parts work order must be linked to covered asset register. 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: covered asset register
For equipment maintenance parts already included, covered asset register must be linked to parts invoice. Retain stable identifiers and their effective relationships. Current labels are insufficient when assets or accounts changed during the period. Explain one-to-many relationships explicitly and preserve the history needed to distinguish an alias, replacement or reassignment from a genuinely additional item.
Evidence: parts invoice
For equipment maintenance parts already included, parts invoice must be linked to maintenance coverage schedule. 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 asset, part category and service date to coverage, separating excluded consumables. Build the comparison at the level identified by maintenance coverage schedule and retain the governing version from parts work order. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
Coverage may exclude wear items or customer-caused damage. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked maintenance coverage schedule, parts work order, covered asset register, parts 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
Maintenance engineering validates part and failure category. Produce a covered-parts fee review with uncertain exclusions unresolved. 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 maintenance coverage schedule or parts work order 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 equipment maintenance parts already included 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
- Accounts Payable review of reversed service entries
- Equipment maintenance travel fee service zone
- Construction equipment standby authorization
- Facilities on-call retainer included callout-hour allowance
Procurement resource hub · All guides in this evidence collection