What is being tested
Was a cancellation submitted by a person authorized under the supplier agreement? The boundary for this investigation is software cancellation request authority. Begin with the disputed transaction or population, then identify which cancellation request establishes the observed position and which authorized-contact schedule supports the comparison. A difference in totals should not replace this question.
Evidence: cancellation request
For software cancellation request authority, cancellation request must be linked to authorized-contact 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: authorized-contact schedule
For software cancellation request authority, authorized-contact schedule must be linked to supplier acknowledgment. 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: supplier acknowledgment
For software cancellation request authority, supplier acknowledgment must be linked to post-request 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: post-request invoice
For software cancellation request authority, post-request invoice must be linked to cancellation request. 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
Compare the sender and requested scope with the permitted termination authority before dating cessation of charges. Build the comparison at the level identified by cancellation request and retain the governing version from authorized-contact schedule. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
An internal ticket may not be a supplier-accepted cancellation. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked cancellation request, authorized-contact schedule, supplier acknowledgment, post-request 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 verifies authority and the supplier response. Identify valid notice or request corrected authorization without assuming retroactive cancellation. 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 cancellation request or authorized-contact 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 software cancellation request authority 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
- Evaluate software spend review for reseller pass-through pricing
- SaaS implementation change-request price authority
- Auto-renewal notice delivery evidence
- Early termination fee remaining-term basis
Technology Spend resource hub · All guides in this evidence collection