How rate schedule violations happen in utilities

Executive Summary

Utility and energy service contracts, covering contracted energy management, submetering, demand response, and maintenance vendors billing against a rate schedule, rely on a tiered table that changes by season, volume, or time of use. The invoice is supposed to reference that table. The mechanism that causes drift is simple: the schedule changes, or the invoice references an old version of it, and nobody reconciles the two before payment goes out.

Three points in the billing cycle create the opening. The schedule itself gets revised and the vendor's billing system keeps the prior tier. A demand charge or fuel adjustment factor gets applied using a stale index value instead of the current one. Or a contract renewal changes the rate structure and the vendor's invoice template does not.

What changes it is a control that checks the invoice against the current schedule at the line level, not just the total against the PO. Three-way matching confirms quantity and PO reference. It does not confirm that the rate applied is the one the current schedule specifies.

1. What is a rate schedule violation in a utility or energy contract?

A rate schedule violation is an invoice line that charges a rate, tier, or adjustment factor different from the one the current contract schedule specifies. The schedule is the table: a base charge, a demand or capacity charge, a fuel or power cost adjustment, and the tier boundaries that decide which row applies. When the invoice references an outdated row, an expired adjustment factor, or a tier the account no longer qualifies for, the difference between what was billed and.

The schedule usually lives outside the ERP, as a PDF exhibit attached to the master service agreement or a tariff filing referenced by section number. The invoice, by contrast, is a line of numbers in an accounts payable system with no visible link back to that document.

That separation is structural, not accidental. Utility and energy vendors update schedules on their own cycle, often annually or seasonally, and the invoice template does not always update at the same moment. A violation is the invoice and the schedule falling out of sync, then staying that way until someone checks.

2. How does rate schedule violation happen in utilities and energy?

It happens at the handoff between schedule revision and invoice generation. A vendor updates its rate schedule, publishes the new tiers or adjustment factors, and the buyer's copy of the contract is updated. The vendor's own billing system, running on a separate cycle, keeps applying the prior version for one or more billing periods.

Nobody on the buyer side re-checks the invoice against the new schedule, because the AP team's control checks the PO and the quantity, not the rate.

The failure point is rarely dishonesty. It is timing plus a missing reconciliation step. A schedule revision effective the first of a quarter can take a full billing cycle to reach the invoice generation system, and if the buyer's AP process only checks the invoice against the purchase order and the prior period's amount, a stale rate passes without friction.

The same mechanism applies in reverse when a contract renewal negotiates a new schedule. Until someone updates the reference table the AP team checks against, every invoice in that gap carries the old rate forward, correctly formatted and confidently wrong.

3. Where do tariff tier mismatches come from on the invoice?

Tier mismatches come from volume or time-of-use thresholds that move the account into a different row of the schedule without the invoice re-checking which row applies. A schedule with usage tiers, seasonal tiers, or time-of-use windows assigns a different rate depending on when or how much was consumed. If the vendor's billing engine defaults to the account's prior tier instead of recalculating against actual usage each period, the invoice charges the wrong row every time usage crosses a threshold.

This shows up in a few recurring forms. A volume threshold that should move a monthly demand charge to a lower tier stays at the higher tier because the system checks the annual average, not the current month. A seasonal rate window shifts on a calendar date the vendor's billing engine has not been reprogrammed to recognize.

Both are mechanical, not judgment calls: the schedule states the threshold, the invoice either crosses it correctly or does not. That makes a tier mismatch one of the more checkable violations, provided the AP team has the schedule's threshold table in front of it rather than only the invoice total.

4. Can a demand charge drift from the contracted rate schedule?

Yes. A demand charge is billed against peak usage in a defined window, and the rate applied to that peak is set by the schedule's demand tier, not a fixed dollar figure. If the vendor's meter data, the demand window definition, or the applicable tier changes and the invoice does not reflect the update, the demand charge drifts from what the current schedule specifies while still looking like a normal recurring line item on the statement.

Demand charges are structurally harder to audit than a flat rate because they depend on a peak measurement, a window definition, and a tier lookup, three separate inputs that all have to be current for the charge to be correct.

A drift here often starts with the window definition: if the contract redefines the peak-demand measurement period during a renewal and the vendor's meter software is not reconfigured, every subsequent invoice measures the wrong window against the right tier, or the right window against the wrong tier. Either produces a charge the schedule does not actually authorize.

5. How do fuel and power cost adjustments create hidden drift?

Fuel and power cost adjustment clauses let a base rate move with an underlying index, which means the invoice is only correct if the index value applied matches the current published figure. The US Bureau of Labor Statistics Producer Price Index for fuels and related products, industrial electric power, stood at 341.966 in July 2026, up 1.2% year over year (read 2026-09-07). A schedule tied to a similar index drifts whenever the invoice lags that movement or applies.

An adjustment clause exists so the base rate does not have to be renegotiated every time input costs move. That flexibility is also where drift hides: the clause states which index to reference and how often to reapply it, and both are easy for a billing system to get slightly out of step with.

A lag of one billing cycle in applying an updated index value is invisible on the invoice. The line item still looks like a normal adjustment charge. Confirming it is correct means pulling the index value the vendor should have used and comparing it to the one actually applied, not just checking that an adjustment line exists.

6. What should an AP team check against the rate schedule before paying?

An AP team should check four things against the current schedule before releasing payment: the base rate matches the schedule version in effect for the billing period, the tier applied matches actual usage against the schedule's stated thresholds, any demand charge reflects the correct window and tier, and any adjustment factor matches the index value published for that period. Three-way matching checks the invoice against the PO and receipt; it does not test any of these four against the schedule.

A. Version control. Keep the current rate schedule, dated, as a reference document the AP system can be checked against, not just filed with the signed contract.

B. Line-level comparison. Compare the base rate, tier, and adjustment factor on the invoice to the schedule's corresponding row, not just the invoice total to the prior period's total.

C. Renewal triggers. Flag every contract renewal or amendment as a prompt to refresh the reference schedule the AP team checks against, since a stale reference table is itself a source of missed violations.

For the wider pattern this sits inside, start with the margin drift guide. See also the Margin Drift Diagnostic and our insights.

7. Frequently Asked Questions (People Also Ask)

What counts as a rate schedule violation on a utility invoice?

Any line where the rate, tier, or adjustment factor charged does not match the schedule currently in effect under the contract. This includes an outdated base rate, a demand charge computed against the wrong tier, or an adjustment clause applied with a stale index value. If the schedule's current version would produce a different number than the invoice shows, that line is a violation.

Is a rate schedule violation the same as being overcharged?

Not always. A rate schedule violation is a mismatch between the invoice and the current schedule, and it can run in either direction. Most cases found in practice favor the vendor, because a stale higher tier or an unremoved surcharge tends to persist once billed, but the definition itself is about mismatch, not direction.

Why does three-way matching miss rate schedule violations?

Three-way matching checks the invoice against the purchase order and the goods or service receipt: quantity, price per unit as entered in the PO, and confirmation the service happened. It does not compare the rate applied to the current version of the rate schedule, because the schedule is a separate document the ERP was never configured to reference.

How often do utility and energy rate schedules change?

This varies by vendor and contract type, so no single figure applies across accounts. What matters operationally is that schedules do change on their own cycle, independent of the invoice generation cycle, and every revision is a point where the two can fall out of sync until someone checks.

What is a demand charge and why is it hard to audit?

A demand charge bills against peak usage in a defined measurement window, using a rate set by the schedule's demand tier. It is harder to audit than a flat rate because it depends on three separate inputs, the peak measurement, the window definition, and the tier lookup, all of which have to be current for the charge to be correct.

What does a fuel or power cost adjustment clause actually do?

It lets a base rate move with an underlying published index so the parties do not have to renegotiate the base rate every time input costs shift. The clause specifies which index and how often it reapplies. The invoice is correct only if the index value actually used matches the current published figure for that period.

Can a contract renewal cause a rate schedule violation?

Yes. A renewal or amendment often changes the rate structure, the tier thresholds, or the demand window definition. If the vendor's billing system and the buyer's reference documents are not both updated at the same time, every invoice issued in that gap can carry forward terms the current contract no longer specifies.

How do I check my own utility invoices against the rate schedule?

Pull the current, dated rate schedule from the contract file rather than relying on the last invoice as a reference point. Compare the base rate, the tier applied, any demand charge window and tier, and any adjustment factor line by line against that schedule, not just the total against last period's total.

Does this apply to consumer electric bills or only business contracts?

This addresses contracted energy and utility service vendors billing a business account under a negotiated schedule, including energy management, submetering, and demand response contracts, not residential consumer electric billing, which runs under separate consumer tariff rules.

What is the legal status of disputing a rate schedule violation?

Disputing a billed rate against a contracted schedule is a commercial and contractual matter between the parties. This is general information, not legal advice, and any dispute involving a regulated tariff or contract terms should be reviewed with counsel familiar with the specific agreement.