Early termination fee remaining-term basis

What is being tested

Was an early termination charge based on the correct remaining committed period? The boundary for this investigation is early termination fee remaining-term basis. Begin with the disputed transaction or population, then identify which termination agreement establishes the observed position and which commitment end date supports the comparison. A difference in totals should not replace this question.

Evidence: termination agreement

For early termination fee remaining-term basis, termination agreement must be linked to commitment end date. 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: commitment end date

For early termination fee remaining-term basis, commitment end date must be linked to fee formula. Record the date convention and timezone where relevant. Separate occurrence, notification and posting times. A later administrative entry may describe an earlier event; the review must use the event specified by the governing record rather than whichever date is easiest to extract.

Evidence: fee formula

For early termination fee remaining-term basis, fee formula must be linked to termination invoice. 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: termination invoice

For early termination fee remaining-term basis, termination invoice must be linked to termination agreement. 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

Recompute the remaining period using the agreed effective date and distinguish unpaid accrued service from future commitment charges. Build the comparison at the level identified by termination agreement and retain the governing version from commitment end date. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

Outstanding prior invoices may be payable in addition to a termination fee. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked termination agreement, commitment end date, fee formula, termination 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 validates the settlement scope and approved termination date. Produce a fee-component schedule and dispute only unsupported remaining-term charges. 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 termination agreement or commitment end date 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 early termination fee remaining-term basis 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

Technology Spend resource hub · All guides in this evidence collection