What is being tested
Did prepaid services hours expire under the agreed rule or remain available for future use? The boundary for this investigation is professional-services unused prepaid hours expiry. Begin with the disputed transaction or population, then identify which prepaid-hours order establishes the observed position and which timesheet approval supports the comparison. A difference in totals should not replace this question.
Evidence: prepaid-hours order
For professional-services unused prepaid hours expiry, prepaid-hours order must be linked to timesheet approval. 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: timesheet approval
For professional-services unused prepaid hours expiry, timesheet approval must be linked to expiry provision. 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: expiry provision
For professional-services unused prepaid hours expiry, expiry provision must be linked to remaining-hours statement. 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: remaining-hours statement
For professional-services unused prepaid hours expiry, remaining-hours statement must be linked to prepaid-hours order. Use the opening position, dated movements and closing position together. Preserve the distinction between requested, authorized and posted changes. The reconciliation should explain how the source item moved through the account, not simply assert that the final total agrees.
Reconciliation logic
Reconcile purchased, approved-consumed and remaining hours before applying the expiry date. Build the comparison at the level identified by prepaid-hours order and retain the governing version from timesheet approval. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
Unapproved work may still be commercially chargeable under the agreement. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked prepaid-hours order, timesheet approval, expiry provision, remaining-hours statement. 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 project sponsor validates consumption and extension approvals. Document usable hours, expired entitlement or a supported balance query. 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
Do not infer license removability from activity alone or describe a proposed configuration change as confirmed savings. The authoritative spend, license and contract producer is not complete; customer evidence and processing validation are prerequisites to production conclusions. In this scenario, absence of prepaid-hours order or timesheet 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 professional-services unused prepaid hours expiry in the Technology Spend 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 Technology Spend: 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
- Professional services contractor licensing
- Auto-renewal notice delivery evidence
- Software cancellation request authority
- Early termination fee remaining-term basis
Technology Spend resource hub · All guides in this evidence collection