What is being tested
Was a service invoice quantity expressed in the same approved unit as the service entry? The boundary for this investigation is service-entry measurement unit mismatch. Begin with the disputed transaction or population, then identify which service entry establishes the observed position and which hours-to-day definition supports the comparison. A difference in totals should not replace this question.
Evidence: service entry
For service-entry measurement unit mismatch, service entry must be linked to hours-to-day definition. 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: hours-to-day definition
For service-entry measurement unit mismatch, hours-to-day definition must be linked to rate card. Retain the applicable wording, effective dates and scope of covered transactions. Identify the event or population that controls the calculation. Do not silently replace a contractual definition with a dashboard label, customary practice or the latest published rule.
Evidence: rate card
For service-entry measurement unit mismatch, rate card must be linked to invoice unit. Keep the dated calculation basis, eligible units and any limits or exclusions. Record the sequence of conversion, threshold selection and rounding. An arithmetic result is only supportable after its inputs and applicable version are independently confirmed for the transaction being reviewed.
Evidence: invoice unit
For service-entry measurement unit mismatch, invoice unit must be linked to service entry. 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
Convert accepted service quantities using the agreed unit definition and preserve mixed-unit line items. Build the comparison at the level identified by service entry and retain the governing version from hours-to-day definition. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A day rate need not equal an assumed number of hourly units. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked service entry, hours-to-day definition, rate card, invoice unit. 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
The service owner validates acceptance units and sourcing validates conversions. Produce a service-unit price bridge with unsupported conversion isolated. 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 service entry or hours-to-day definition 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 service-entry measurement unit mismatch 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
- Purchase-order quantity mismatch with split deliveries
- Restaurant grease-service volume billing
- Equipment maintenance travel fee service zone
- Hotel linen service rejected batch deductions
Procurement resource hub · All guides in this evidence collection