Minimum consumption shortfall true-up

What is being tested

Was a minimum-consumption shortfall calculated after all eligible usage and adjustments? The boundary for this investigation is minimum consumption shortfall true-up. Begin with the disputed transaction or population, then identify which minimum-spend commitment establishes the observed position and which eligible usage export supports the comparison. A difference in totals should not replace this question.

Evidence: minimum-spend commitment

For minimum consumption shortfall true-up, minimum-spend commitment must be linked to eligible usage export. 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: eligible usage export

For minimum consumption shortfall true-up, eligible usage export must be linked to adjustment ledger. 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: adjustment ledger

For minimum consumption shortfall true-up, adjustment ledger must be linked to shortfall invoice. Use the opening position, dated movements and closing position together. Preserve the distinction between requested, authorized and posted changes. The reconciliation should explain how the source item moved through the account, not simply assert that the final total agrees.

Evidence: shortfall invoice

For minimum consumption shortfall true-up, shortfall invoice must be linked to minimum-spend commitment. 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 the committed floor against the eligible consumption base without netting excluded purchases. Build the comparison at the level identified by minimum-spend commitment and retain the governing version from eligible usage export. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

Excluded products may not satisfy the commitment. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked minimum-spend commitment, eligible usage export, adjustment ledger, shortfall 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

Finance validates base completeness and procurement validates eligibility. Return a commitment-to-consumption bridge and supported shortfall disposition. 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 minimum-spend commitment or eligible usage export 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 minimum consumption shortfall true-up 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