AuditRes
Revenue Recovery Intelligence
One AuditRes platform

Energy · Demand provisions

Utility coincident versus noncoincident demand basis

What is being tested

Did the bill use the specific coincident or site-peak measure defined by the tariff? The boundary for this investigation is utility coincident versus noncoincident demand basis. Begin with the disputed transaction or population, then identify which site interval data establishes the observed position and which system peak notice supports the comparison. A difference in totals should not replace this question.

Evidence: site interval data

For utility coincident versus noncoincident demand basis, site interval data must be linked to system peak notice. 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: system peak notice

For utility coincident versus noncoincident demand basis, system peak notice must be linked to demand basis clause. 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: demand basis clause

For utility coincident versus noncoincident demand basis, demand basis clause must be linked to utility bill. 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: utility bill

For utility coincident versus noncoincident demand basis, utility bill must be linked to site interval data. 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.

Reconciliation logic

Match measured demand to the explicitly defined timing and eligible interval set. Build the comparison at the level identified by site interval data and retain the governing version from system peak notice. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

The highest site interval may differ from the system coincident interval. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked site interval data, system peak notice, demand basis clause, utility bill. 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

Qualified energy reviewers validate measure semantics. Retain a timing-basis demand calculation without universal tariff assumptions. 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 site interval data or system peak notice 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 coincident versus noncoincident demand basis 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

Energy resource hub · All guides in this evidence collection