Product sunset conversion price protection

What is being tested

Was a forced product conversion billed under the agreed sunset protection rather than a new list price? The boundary for this investigation is product sunset conversion price protection. Begin with the disputed transaction or population, then identify which sunset notice establishes the observed position and which conversion amendment supports the comparison. A difference in totals should not replace this question.

Evidence: sunset notice

For product sunset conversion price protection, sunset notice must be linked to conversion amendment. 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: conversion amendment

For product sunset conversion price protection, conversion amendment must be linked to protected price 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.

Evidence: protected price schedule

For product sunset conversion price protection, protected price schedule must be linked to replacement invoice. 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: replacement invoice

For product sunset conversion price protection, replacement invoice must be linked to sunset notice. 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 replacement scope and protection expiry with billed price components. Build the comparison at the level identified by sunset notice and retain the governing version from conversion amendment. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

Optional new features may fall outside the conversion protection. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked sunset notice, conversion amendment, protected price schedule, replacement 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 the accepted transition package. Separate protected base charges from approved replacement additions. 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 sunset notice or conversion amendment 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 product sunset conversion price protection 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