What is being tested
Did tenant migration reset a usage counter without duplicating its already billed cumulative value? The boundary for this investigation is usage counter reset after tenant migration. Begin with the disputed transaction or population, then identify which old and new tenant counters establishes the observed position and which migration timestamp supports the comparison. A difference in totals should not replace this question.
Evidence: old and new tenant counters
For usage counter reset after tenant migration, old and new tenant counters must be linked to migration timestamp. Document the observation window, units, inclusion criteria and export version. Identify gaps and corrected events before using the total. Keep raw observations separate from derived quantities so a reviewer can reproduce the population without assuming every logged event is independently chargeable.
Evidence: migration timestamp
For usage counter reset after tenant migration, migration timestamp must be linked to meter reset definition. 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: meter reset definition
For usage counter reset after tenant migration, meter reset definition must be linked to usage invoices. 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: usage invoices
For usage counter reset after tenant migration, usage invoices must be linked to old and new tenant counters. 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
Reconcile counter increments on both sides of migration using stable workload identifiers and documented reset handling. Build the comparison at the level identified by old and new tenant counters and retain the governing version from migration timestamp. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
A new tenant may have a legitimately separate minimum. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked old and new tenant counters, migration timestamp, meter reset definition, usage invoices. 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 migration owner validates counter lineage. Produce a migration counter bridge with duplicated carryforward isolated. 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 old and new tenant counters or migration timestamp 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 usage counter reset after tenant migration 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
- SaaS spend software proof-of-value without assumed integrations
- AI tool-call fees separate from model usage
- AI cached-input price classification
- AI embedding refresh versus incremental indexing costs
Technology Spend resource hub · All guides in this evidence collection