Renewal uplift compounded across contract years

What is being tested

Was a multi-year uplift applied once per permitted anniversary rather than compounded early? The boundary for this investigation is renewal uplift compounded across contract years. Begin with the disputed transaction or population, then identify which signed uplift schedule establishes the observed position and which anniversary dates supports the comparison. A difference in totals should not replace this question.

Evidence: signed uplift schedule

For renewal uplift compounded across contract years, signed uplift schedule must be linked to anniversary dates. 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: anniversary dates

For renewal uplift compounded across contract years, anniversary dates must be linked to historical invoices. 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: historical invoices

For renewal uplift compounded across contract years, historical invoices must be linked to renewal amendment. 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.

Evidence: renewal amendment

For renewal uplift compounded across contract years, renewal amendment must be linked to signed uplift schedule. 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.

Reconciliation logic

Build a year-by-year price bridge and compare the timing of each increase with the contractual anniversary. Build the comparison at the level identified by signed uplift schedule and retain the governing version from anniversary dates. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

A newly negotiated base can legitimately differ from the prior uplift formula. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked signed uplift schedule, anniversary dates, historical invoices, renewal amendment. 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 commercial owner confirms which amendment resets the base. Retain the applicable price series and request correction of premature compounding. 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 signed uplift schedule or anniversary dates 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 renewal uplift compounded across contract years 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