What auditors miss in utilities and energy

Utility and energy invoices carry riders, true-ups and demand charges general auditors skip. Here is what a contract-level review actually checks.

Twitter LinkedIn WhatsApp
Ask AI: ChatGPT Claude Gemini Grok
What auditors miss in utilities and energy

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In utilities and energy spend, that gap hides inside riders, demand ratchets and true-up mechanisms that a general AP review was never built to read.

A standard invoice audit checks the math on a bill. It rarely checks the tariff schedule, the rider filing, or the meter data behind the number, which is exactly where utility billing drift lives.

Executive Summary

Utility and energy bills look like a fixed monthly line item, so most audit programs treat them that way: check the total against last month, flag anything unusual, move on. That approach misses drift because utility billing is not one number. It is a rate schedule, a set of riders that change with regulatory filings, a demand charge calculated from a peak interval, and sometimes a true-up reconciliation that lands months after the usage it covers.

The mechanism causing the miss is simple: the people reviewing the invoice do not have the tariff sheet or the interval data in front of them, so they cannot tell a correctly applied rate from a stale one. A general AP reviewer checks the invoice against the prior invoice. A contract-level review checks the invoice against the filed rate schedule and the meter data, which is the only place drift in this category actually shows up.

What changes it is treating the utility bill as a contract compliance object, not a recurring expense. That means pulling the current tariff and rider schedule, reconciling demand charges against actual interval data, and tracking true-up periods separately from the current bill.

1. Why do utility invoices pass review even when the rate is wrong?

Utility invoices pass review because AP checks a total against last month's total, not against the filed tariff. A rate class change, an expired rider, or a demand ratchet applied from the wrong season all produce a bill that looks stable month to month while charging against the wrong schedule. Nothing about the invoice format signals the error; only comparing the line items to the current tariff filing does.

A utility bill's format does not change when the underlying rate changes. The account number, the meter number, the layout of charges: all identical whether the utility applied last year's rate class or this year's. That makes a period-over-period comparison useless for catching a rate error, because the comparison passes even when both months are wrong.

The fix is a schedule comparison, not a trend comparison. The reviewer needs the current tariff sheet filed with the state regulator, the account's assigned rate class, and the rider list active for the billing period. Each line on the invoice gets checked against that document, not against the prior bill.

This is the same mechanical gap that shows up in freight and 3PL billing, where the invoice matches the carrier's own system but not the contracted rate card. See how do you audit freight and 3PL invoices for the parallel process.

2. What are riders and why do they keep charging after they expire?

A rider is a separate charge layered onto the base rate, typically covering fuel cost recovery, infrastructure investment, or a regulatory surcharge, and each one carries its own filing, rate, and expiration or renewal date set independently of the base tariff. A rider that expired or stepped down in a regulatory filing keeps appearing on the invoice at the old value until someone checks the filing date against the billing date.

Riders exist because regulators approve base rates and pass-through costs on different timelines. A fuel adjustment rider might reset quarterly. An infrastructure rider might step up on an annual schedule tied to a capital plan. Each has its own effective date, independent of when the base rate last changed.

Billing systems apply the rider value that was current when the account was last updated. If nobody pushes the new filed rate into the billing system on the effective date, the meter keeps charging the old rider value until someone notices, which nothing in the invoice format prompts.

A checkable item: pull the rider's filed effective date from the regulator's docket and compare it to the date the new rate actually appears on the bill. A gap between those two dates is the exposure window, and it is calculable in dollars once you have both dates and the usage for the period.

3. How do demand charges get miscalculated?

A demand charge bills the account's peak usage interval for the month, not total consumption, and the calculation depends on which interval the meter recorded as peak, which ratchet clause applies, and which season's demand rate is in effect. Errors show up as a peak interval that does not match the facility's actual load profile, or a ratchet minimum applied outside the contract's stated ratchet period.

Demand charges are set by the single highest 15- or 30-minute interval in the billing period, multiplied by a demand rate that itself often varies by season. A summer peak rate applied to a winter bill, or vice versa, is a checkable, specific error: pull the interval data and confirm the peak fell in the period the utility billed it against.

Ratchet clauses complicate this further. Many demand tariffs set a minimum demand charge based on a percentage of the highest peak recorded over the past 11 or 12 months, regardless of the current month's actual peak. If the ratchet is still applying from a peak recorded a year ago, and the contract's ratchet window has since passed, the account is paying a minimum it no longer owes.

A. Interval data mismatch

Request the utility's own interval data export for the billing period and identify the actual peak 15-minute reading. Compare that timestamp and value to what the invoice states as the billed demand. A mismatch of more than a few percent is a specific, dollar-quantifiable finding, not a general concern.

B. Ratchet window expiration

Find the ratchet clause in the tariff: it will state a lookback period, commonly 11 or 12 months. Confirm the peak the ratchet references actually falls inside that window as of the current bill date. A ratchet still charging against a peak from 14 months ago is billing outside its own stated rule.

4. What does a true-up reconciliation actually correct, and does it correct in your favor?

A true-up is a retroactive adjustment reconciling estimated charges, an interim rate, or a budget billing plan against actual usage or a finalized rate, and it can run months behind the usage period it covers. Because it arrives as a separate, unfamiliar line item long after the original bill, it gets paid on faith rather than checked against the estimate it is replacing.

Budget billing plans, in particular, average a customer's estimated annual usage into equal monthly payments, then true up the difference between what was billed and what was actually used once the year closes. If the estimate embedded a stale rate or an incorrect usage baseline, the true-up carries that error forward at whatever the current, and possibly higher, rate has become.

A checkable step: request the true-up worksheet, not just the invoice line. It should show the original estimated charges, the actual usage, and the rate applied to the difference. Confirm that rate matches the tariff in effect for the period the true-up covers, not the rate in effect on the date the true-up was issued.

True-ups that reconcile in the utility's favor get flagged automatically by billing systems built to collect. True-ups that would reconcile in the customer's favor depend on someone requesting the worksheet and checking it, which is the gap this category lives in.

5. Which contract terms do general auditors skip on utility accounts?

General auditors skip the rate class assignment, the rider schedule, the demand ratchet clause, and any negotiated economic development or curtailment rate, because none of those terms appear on the invoice itself. They live in the tariff filing or a separate contract document the AP team was never given, so the review checks arithmetic on numbers that were never validated against a source document.

Each of these terms sits in a document AP does not typically hold: a tariff filing, a rider docket, or a side letter negotiating a special rate. The invoice presents a total that assumes all of them were applied correctly, and a match-the-total review has no way to test that assumption.

The practical difference from a general indirect spend review is documented in indirect spend audit categories: utility and energy accounts need the source tariff pulled and compared line by line, not just the invoice checked against the prior period.

  • Rate class assignment: Confirm the account is billed under the rate class that matches its actual usage profile and contract terms, not a default class the utility assigned at connection.
  • Rider schedule and effective dates: List every active rider on the account and confirm each one's rate matches its most recently filed value as of the billing period.
  • Demand ratchet clause: Locate the ratchet lookback period in the tariff and confirm any minimum demand charge still falls inside that window.
  • Negotiated or special contract rates: Where an economic development rate, curtailment credit, or negotiated interruptible rate exists, confirm it is still being applied and has not silently reverted to the standard tariff.
  • Power factor and other adjustment clauses: Check whether a power factor penalty or credit clause is calculated correctly against the account's actual reactive power data, not assumed compliant.

6. How does commodity price movement complicate reviewing a utility bill?

Fuel and power cost adjustment riders pass through wholesale commodity movement to the customer bill, so a reviewer has to separate a legitimate cost pass-through from a billing error. Per the US Bureau of Labor Statistics Producer Price Index for industrial electric power (series WPU0543, read 2026-09-06), the July 2026 index value was 341.966, up 1.2% year over year, which sets a reference point for what a commodity-driven increase should look like.

When a utility bill rises, the first question is whether the increase reflects a filed rider tracking wholesale power cost, or whether it reflects a billing error unrelated to the commodity market. Comparing the invoice's period-over-period change to a published cost index gives a reference point: an increase materially larger than the index movement warrants a closer look at the rider calculation itself, rather than being written off as normal commodity volatility.

This does not replace checking the rider's own filed rate. It is a first screen: if the account's fuel or power cost rider moved far out of line with the published index for the same period, that is a specific, checkable signal to pull the rider filing and confirm the rate applied matches what was actually filed for that period.

For the wider pattern this sits inside, start with the margin drift guide. See also accessorial charge audit: the surcharges nobody validates and duplicate freight billing and the multi-carrier consolidation problem.

7. Frequently Asked Questions (People Also Ask)

What is the single most useful document to request when auditing a utility bill?

The current tariff sheet and active rider schedule filed with the state regulator for that account's rate class. Without it, a reviewer can only compare the invoice to itself month over month, which does not catch a rate class or rider error that has been present since before the comparison period started.

Can a demand charge error be caught without interval data?

No. The demand charge depends on which specific interval the meter recorded as peak, and that timestamp is not printed on the standard invoice. Requesting the utility's interval data export for the billing period is the only way to confirm the billed peak matches the actual peak.

Why does a true-up bill arrive so much later than the usage it covers?

Budget billing and interim rate plans estimate charges monthly and reconcile against actual usage or a finalized rate once the true annual figure is known, which can take several months. The delay is standard utility practice, but the worksheet behind the true-up still needs to be checked against the filed rate for the period.

Does a rider ever apply at the wrong rate without anyone changing it intentionally?

Yes. A rider's filed rate can step up or down on a regulatory schedule independent of the base tariff, and if the utility's billing system is not updated on the effective date, the old rider value continues to be charged until someone compares the billing date to the filing date.

Is a power factor penalty something AP can check without engineering input?

The formula itself typically needs the account's actual reactive power data, which usually requires someone who can read the meter data or interconnection agreement. AP can confirm the penalty or credit clause exists in the contract and flag it for that review rather than skipping it entirely.

How is a negotiated utility rate different from the standard tariff, and how would billing revert without notice?

A negotiated rate, such as an economic development or interruptible rate, is documented in a side agreement separate from the standard tariff. If the account information in the utility's billing system is not flagged correctly, the bill can revert to the standard tariff rate without any explicit notice to the customer.

What is the legal disclaimer that applies to any tariff or regulatory interpretation here?

This is general information, not legal advice. Rate class assignments, rider filings, and ratchet clauses are matters of regulatory filing and contract interpretation, and a specific dispute with a utility should be reviewed against the actual filed documents and, where needed, counsel familiar with the relevant public utility commission.

Does the diagnostic cover utility and energy accounts specifically?

The Margin Drift Diagnostic covers indirect spend categories broadly, including utility and energy billing as part of its invoice-to-contract review, checking invoices against the underlying rate schedules and contract terms rather than against prior invoices alone.

How far back should a utility billing review look?

Riders, ratchets, and true-ups can carry forward errors for many months before they surface, so a review that only checks the most recent bill will miss a stale rider or ratchet that has been running for a longer period. Pulling the tariff history alongside recent invoices is what surfaces how long an error has been present.

Executive Summary

Utility and energy bills look like a fixed monthly line item, so most audit programs treat them that way: check the total against last month, flag anything unusual, move on. That approach misses drift because utility billing is not one number. It is a rate schedule, a set of riders that change with regulatory filings, a demand charge calculated from a peak interval, and sometimes a true-up reconciliation that lands months after the usage it covers. The mechanism causing the miss is simple: the people reviewing the invoice do not have the tariff sheet or the interval data in front of them, so they cannot tell a correctly applied rate from a stale one. A general AP reviewer checks the invoice against the prior invoice. A contract-level review checks the invoice against the filed rate schedule and the meter data, which is the only place drift in this category actually shows up. What changes it is treating the utility bill as a contract compliance object, not a recurring expense. That means pulling the current tariff and rider schedule, reconciling demand charges against actual interval data, and tracking true-up periods separately from the current bill.

1. Why do utility invoices pass review even when the rate is wrong?

Utility invoices pass review because AP checks a total against last month's total, not against the filed tariff. A rate class change, an expired rider, or a demand ratchet applied from the wrong season all produce a bill that looks stable month to month while charging against the wrong schedule. Nothing about the invoice format signals the error; only comparing the line items to the current tariff filing does. A utility bill's format does not change when the underlying rate changes. The account number, the meter number, the layout of charges: all identical whether the utility applied last year's rate class or this year's. That makes a period-over-period comparison useless for catching a rate error, because the comparison passes even when both months are wrong. The fix is a schedule comparison, not a trend comparison. The reviewer needs the current tariff sheet filed with the state regulator, the account's assigned rate class, and the rider list active for the billing period. Each line on the invoice gets checked against that document, not against the prior bill. This is the same mechanical gap that shows up in freight and 3PL billing, where the invoice matches the carrier's own system but not the contracted rate card. See how do you audit freight and 3PL invoices for the parallel process.

2. What are riders and why do they keep charging after they expire?

A rider is a separate charge layered onto the base rate, typically covering fuel cost recovery, infrastructure investment, or a regulatory surcharge, and each one carries its own filing, rate, and expiration or renewal date set independently of the base tariff. A rider that expired or stepped down in a regulatory filing keeps appearing on the invoice at the old value until someone checks the filing date against the billing date. Riders exist because regulators approve base rates and pass-through costs on different timelines. A fuel adjustment rider might reset quarterly. An infrastructure rider might step up on an annual schedule tied to a capital plan. Each has its own effective date, independent of when the base rate last changed. Billing systems apply the rider value that was current when the account was last updated. If nobody pushes the new filed rate into the billing system on the effective date, the meter keeps charging the old rider value until someone notices, which nothing in the invoice format prompts. A checkable item: pull the rider's filed effective date from the regulator's docket and compare it to the date the new rate actually appears on the bill. A gap between those two dates is the exposure window, and it is calculable in dollars once you have both dates and the usage for the period.

3. How do demand charges get miscalculated?

A demand charge bills the account's peak usage interval for the month, not total consumption, and the calculation depends on which interval the meter recorded as peak, which ratchet clause applies, and which season's demand rate is in effect. Errors show up as a peak interval that does not match the facility's actual load profile, or a ratchet minimum applied outside the contract's stated ratchet period. Demand charges are set by the single highest 15- or 30-minute interval in the billing period, multiplied by a demand rate that itself often varies by season. A summer peak rate applied to a winter bill, or vice versa, is a checkable, specific error: pull the interval data and confirm the peak fell in the period the utility billed it against. Ratchet clauses complicate this further. Many demand tariffs set a minimum demand charge based on a percentage of the highest peak recorded over the past 11 or 12 months, regardless of the current month's actual peak. If the ratchet is still applying from a peak recorded a year ago, and the contract's ratchet window has since passed, the account is paying a minimum it no longer owes. ### A. Interval data mismatch Request the utility's own interval data export for the billing period and identify the actual peak 15-minute reading. Compare that timestamp and value to what the invoice states as the billed demand. A mismatch of more than a few percent is a specific, dollar-quantifiable finding, not a general concern. ### B. Ratchet window expiration Find the ratchet clause in the tariff: it will state a lookback period, commonly 11 or 12 months. Confirm the peak the ratchet references actually falls inside that window as of the current bill date. A ratchet still charging against a peak from 14 months ago is billing outside its own stated rule.

4. What does a true-up reconciliation actually correct, and does it correct in your favor?

A true-up is a retroactive adjustment reconciling estimated charges, an interim rate, or a budget billing plan against actual usage or a finalized rate, and it can run months behind the usage period it covers. Because it arrives as a separate, unfamiliar line item long after the original bill, it gets paid on faith rather than checked against the estimate it is replacing. Budget billing plans, in particular, average a customer's estimated annual usage into equal monthly payments, then true up the difference between what was billed and what was actually used once the year closes. If the estimate embedded a stale rate or an incorrect usage baseline, the true-up carries that error forward at whatever the current, and possibly higher, rate has become. A checkable step: request the true-up worksheet, not just the invoice line. It should show the original estimated charges, the actual usage, and the rate applied to the difference. Confirm that rate matches the tariff in effect for the period the true-up covers, not the rate in effect on the date the true-up was issued. True-ups that reconcile in the utility's favor get flagged automatically by billing systems built to collect. True-ups that would reconcile in the customer's favor depend on someone requesting the worksheet and checking it, which is the gap this category lives in.

5. Which contract terms do general auditors skip on utility accounts?

General auditors skip the rate class assignment, the rider schedule, the demand ratchet clause, and any negotiated economic development or curtailment rate, because none of those terms appear on the invoice itself. They live in the tariff filing or a separate contract document the AP team was never given, so the review checks arithmetic on numbers that were never validated against a source document. Each of these terms sits in a document AP does not typically hold: a tariff filing, a rider docket, or a side letter negotiating a special rate. The invoice presents a total that assumes all of them were applied correctly, and a match-the-total review has no way to test that assumption. The practical difference from a general indirect spend review is documented in [indirect spend audit categories](/guides/indirect-spend-audit-categories): utility and energy accounts need the source tariff pulled and compared line by line, not just the invoice checked against the prior period. - Rate class assignment: Confirm the account is billed under the rate class that matches its actual usage profile and contract terms, not a default class the utility assigned at connection. - Rider schedule and effective dates: List every active rider on the account and confirm each one's rate matches its most recently filed value as of the billing period. - Demand ratchet clause: Locate the ratchet lookback period in the tariff and confirm any minimum demand charge still falls inside that window. - Negotiated or special contract rates: Where an economic development rate, curtailment credit, or negotiated interruptible rate exists, confirm it is still being applied and has not silently reverted to the standard tariff. - Power factor and other adjustment clauses: Check whether a power factor penalty or credit clause is calculated correctly against the account's actual reactive power data, not assumed compliant.

6. How does commodity price movement complicate reviewing a utility bill?

Fuel and power cost adjustment riders pass through wholesale commodity movement to the customer bill, so a reviewer has to separate a legitimate cost pass-through from a billing error. Per the US Bureau of Labor Statistics Producer Price Index for industrial electric power (series WPU0543, read 2026-09-06), the July 2026 index value was 341.966, up 1.2% year over year, which sets a reference point for what a commodity-driven increase should look like. When a utility bill rises, the first question is whether the increase reflects a filed rider tracking wholesale power cost, or whether it reflects a billing error unrelated to the commodity market. Comparing the invoice's period-over-period change to a published cost index gives a reference point: an increase materially larger than the index movement warrants a closer look at the rider calculation itself, rather than being written off as normal commodity volatility. This does not replace checking the rider's own filed rate. It is a first screen: if the account's fuel or power cost rider moved far out of line with the published index for the same period, that is a specific, checkable signal to pull the rider filing and confirm the rate applied matches what was actually filed for that period. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. See also [accessorial charge audit: the surcharges nobody validates](/guides/accessorial-charge-audit-the-surcharges-nobody-validates) and [duplicate freight billing and the multi-carrier consolidation problem](/guides/duplicate-freight-billing-and-the-multi-carrier).

Questions & Answers

What is the single most useful document to request when auditing a utility bill?

The current tariff sheet and active rider schedule filed with the state regulator for that account's rate class. Without it, a reviewer can only compare the invoice to itself month over month, which does not catch a rate class or rider error that has been present since before the comparison period started.

Can a demand charge error be caught without interval data?

No. The demand charge depends on which specific interval the meter recorded as peak, and that timestamp is not printed on the standard invoice. Requesting the utility's interval data export for the billing period is the only way to confirm the billed peak matches the actual peak.

Why does a true-up bill arrive so much later than the usage it covers?

Budget billing and interim rate plans estimate charges monthly and reconcile against actual usage or a finalized rate once the true annual figure is known, which can take several months. The delay is standard utility practice, but the worksheet behind the true-up still needs to be checked against the filed rate for the period.

Does a rider ever apply at the wrong rate without anyone changing it intentionally?

Yes. A rider's filed rate can step up or down on a regulatory schedule independent of the base tariff, and if the utility's billing system is not updated on the effective date, the old rider value continues to be charged until someone compares the billing date to the filing date.

Is a power factor penalty something AP can check without engineering input?

The formula itself typically needs the account's actual reactive power data, which usually requires someone who can read the meter data or interconnection agreement. AP can confirm the penalty or credit clause exists in the contract and flag it for that review rather than skipping it entirely.

Margin Drift Resources