What is being tested
Were usage intervals assigned to the dated seasonal periods in the applicable schedule? The boundary for this investigation is utility seasonal rate period classification. Begin with the disputed transaction or population, then identify which seasonal tariff schedule establishes the observed position and which usage dates supports the comparison. A difference in totals should not replace this question.
Evidence: seasonal tariff schedule
For utility seasonal rate period classification, seasonal tariff schedule must be linked to usage dates. 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: usage dates
For utility seasonal rate period classification, usage dates must be linked to interval 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: interval export
For utility seasonal rate period classification, interval export must be linked to utility invoice. 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: utility invoice
For utility seasonal rate period classification, utility invoice must be linked to seasonal tariff schedule. 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
Map intervals to seasonal boundaries and version changes before applying rates. Build the comparison at the level identified by seasonal tariff schedule and retain the governing version from usage dates. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.
Exception conditions
An invoice spanning seasons can legitimately contain multiple prices. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked seasonal tariff schedule, usage dates, interval export, utility 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
Energy specialists validate schedule and meter dates. Return a season-to-usage pricing bridge. 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
The applicable tariff and customer evidence control the result; this method is not a universal utility formula. The authoritative utility calculation producer is not complete. Qualified reviewers must confirm meter interpretation and tariff eligibility before assigning a monetary variance. In this scenario, absence of seasonal tariff schedule or usage 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 utility seasonal rate period classification in the Energy 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 Energy: 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
- Utility unapplied deposit review
- Utility billing days fixed-charge denominator
- Utility time-of-use holiday eligibility
- Utility renewable certificate charge contracted quantity
Energy resource hub · All guides in this evidence collection