How do you spot surcharge persistence on a utility bill?

Executive Summary

A utilities invoice is really two documents layered on top of each other: the usage bill and a stack of riders, adjustment clauses and surcharges filed separately with the rate schedule or tariff. Each rider has a trigger. Surcharge persistence is what happens when the invoice keeps charging a rider after its trigger condition has expired, because nobody on either side re-checks the condition once the line item is coded into the billing system.

This is not a pricing error in the usual sense. The rate that was correct in the month the surcharge was filed is still printed correctly. What has gone stale is the condition underneath it: the commodity index reverted, the demand peak rolled out of the ratchet window, the emergency tariff was rescinded.

The line item survives because AP systems match an invoice to a rate, not to the tariff filing that rate depends on.

Finding it requires reading the utility's own tariff or rate filing alongside the invoice, not just the invoice against last year's invoice. The fix is a recurring check against the filing, not a one-time invoice audit.

1. What is surcharge persistence on a utilities invoice?

Surcharge persistence is a rider, adjustment, or surcharge line that continues billing after the condition that justified it has ended. A fuel cost adjustment tied to a commodity index, a demand charge set by one peak billing month, or an emergency tariff filed during a shortage all carry an expiration condition written into the utility's rate filing. The invoice keeps charging the line because the billing system was configured once, when the surcharge was valid, and never re-checked against the.

The distinction that matters is between a rate and a condition. The rate on a surcharge line can be arithmetically correct every month and the charge can still be wrong, because the condition that authorized the rate no longer holds. A demand ratchet is the clearest example: many utility tariffs set a customer's demand charge for a full year based on the single highest month, then keep billing at that level even after usage drops.

That is contractual, not an error, and it is easy to mistake for persistence.

True persistence looks different: a rider that was time-boxed or index-linked in the tariff filing, but never adjusted down, or never removed, once the filing changed. It sits on the invoice at the same dollar amount or the same formula every cycle, disconnected from the condition that was supposed to move it.

2. How do you spot surcharge persistence on a utilities invoice?

Pull the utility's current tariff or rate filing for the account's rate class, then line up every surcharge and rider on the invoice against a clause in that filing. Any line item that has no matching clause, or whose clause states a trigger condition the invoice does not test, is a candidate. Then check the line's history: a surcharge with an identical dollar amount or identical formula output across several billing cycles, despite the underlying index moving, is the strongest.

Start with the rate class, not the bill. Utility tariffs are filed by rate class and change on their own schedule, sometimes annually, sometimes on a regulatory docket timeline unrelated to the customer's billing cycle. Pull the version that was in effect for the billing period under review, because a rider that was valid a year ago may have been superseded.

Next, isolate every non-usage line on the invoice. Usage times rate is one calculation; everything else on the bill, fuel adjustments, power factor penalties, franchise fees, system benefit charges, is a separate clause with its own trigger. Match each one to a clause number or tariff sheet reference.

A line with no traceable clause is not automatically wrong, but it cannot be verified, which is itself the finding worth escalating.

3. Which utility surcharges carry a trigger condition worth checking?

Several standard categories of utility surcharge carry an explicit trigger in the tariff: fuel and commodity cost adjustments tied to an index, demand-based riders tied to a peak measurement window, power factor penalties tied to a load condition, and emergency or interim riders tied to a regulatory docket. Each one has language in the filing describing when the charge applies and when it should stop. None of these is inherently a drift; each becomes one only when the invoice keeps.

Each category below carries its own trigger language in the tariff, and each is checked the same way: locate the clause, read the condition, compare it against current circumstances rather than against last year's invoice.

• Fuel and commodity adjustments: Indexed to a published fuel or power cost benchmark and meant to move with it, up or down, each cycle.
• Demand-based riders: Set by a peak measurement window defined in the tariff, with a stated period after which the peak resets.
• Power factor penalties: Triggered by a load condition at the meter; the tariff states the threshold that removes the penalty once corrected.
• Interim or emergency riders: Filed for a specific regulatory docket or shortage period, with an end date tied to the docket's resolution rather than the calendar.

4. Does the rate filing behind the invoice actually change over time?

Yes. Tariff sheets and rate riders are amended on the regulator's schedule, not the customer's invoice cycle, and the version an AP team filed away at contract signing can be a year or more out of date by the time a surcharge line is reviewed. Commodity-linked components in particular move with published input costs.

The US Bureau of Labor Statistics' Producer Price Index for industrial electric power (series WPU0543) put the August 2026 index at 346.309, up 1.1%.

A tariff filed two years ago is not a static reference document. Riders tied to a commodity index are designed to move, and the index itself moves independently of the customer relationship. When a company's AP team keeps a single PDF of the tariff on file and checks new invoices against it indefinitely, two things can go wrong in opposite directions: a rider that should have gone up with the index stays flat, or a rider that should have expired stays exactly where it was set.

The practical implication is that a surcharge review has to pull the current filing each time, not rely on the version attached to the original contract or the original interconnection agreement. A rate class's filing history is public record with the relevant utility commission, and it is the only document that states, in the utility's own language, when a given rider is supposed to stop.

5. Can three-way matching catch surcharge persistence on its own?

No. Three-way matching checks the invoice against the purchase order and the receipt, confirming quantity and a general rate agree with what was ordered and received. It does not test a surcharge's expiration condition, because that condition lives in a tariff filing outside the purchase order entirely.

A utilities invoice frequently has no PO line for a rider at all, since rider items are billed by the utility unilaterally under its filed rate schedule rather than negotiated per shipment or.

Standard AP controls are built around the purchase order as the source of truth. For a freight or MRO invoice, that works because the PO carries the negotiated rate and quantity. A utility rider has no equivalent PO line: it is set by regulatory filing, applies to the account's entire rate class, and changes on the utility's timeline rather than a purchase agreement's.

That means the control gap is structural, not a matter of AP staff missing a step. A surcharge review has to be a separate process that pulls the tariff filing and checks it against the billed rider, run on its own cadence rather than folded into the routine three-way match.

6. What does a recurring surcharge persistence review look like in practice?

A working review pulls the current tariff filing for each utility account's rate class on a fixed cadence, maps every non-usage line on the invoice to a specific clause, and flags any line whose dollar amount or formula output has not moved despite the underlying trigger condition changing. Flagged lines get sent back to the utility with the clause citation attached, not disputed generically. The output is a short list of lines to challenge, plus a record of which lines.

The process holds together only if the clause map and the trigger recheck are treated as two separate steps, built once and then run on a schedule rather than redone from memory each time a bill arrives.

A. Build the clause map once

The first pass, mapping every rider to its tariff clause, is the expensive step. Once built for a given rate class, it is a reference document that gets updated when the utility refiles, not rebuilt from scratch each billing cycle. This is the step most AP teams skip because it takes longer than paying the bill on time.

B. Recheck triggers, not totals

A month-over-month comparison of invoice totals will not surface persistence, because a persistent surcharge produces a stable, unremarkable number. The check has to compare the trigger condition stated in the clause against current conditions: has the index moved, has the peak window reset, has the docket closed. That is a different question than whether the bill looks normal.

7. Where does surcharge persistence fit in a broader utilities invoice audit?

Surcharge persistence is one drift type within a wider utilities and energy invoice review that also checks usage rates, tax and fee schedules, and meter-level billing accuracy. It sits alongside accessorial and surcharge issues found in other indirect spend categories, since the underlying mechanism, a billed line outliving the condition that justified it, is not unique to utilities. Treating it as part of a full category review, rather than a one-off surcharge check, is what keeps the clause map current.

A surcharge review done in isolation, once, catches whatever is stale at that moment and then goes quiet. The more durable version sits inside a recurring audit of the whole utilities and energy category, where usage rates, tax lines, and surcharge clauses are all checked against current filings on the same cadence.

The same mechanism, a billed line that outlives its trigger, shows up under a different name in other categories: an accessorial charge that survives past the shipment condition that justified it, or a software true-up that keeps billing a tier the account no longer uses. Recognizing the pattern once makes it faster to spot in the next category.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and accessorial charge audit: the surcharges nobody validates.

8. Frequently Asked Questions (People Also Ask)

What is a surcharge persistence finding, in plain terms?

It is a line item on a utility invoice, such as a fuel adjustment or demand rider, that keeps billing at the same rate or formula after the condition that justified it in the tariff filing has changed or expired. The charge itself may be calculated correctly; the condition underneath it is what has gone stale.

Is a demand ratchet the same thing as surcharge persistence?

Not usually. A demand ratchet is a tariff term where one peak month sets the demand charge for a full year by design. That is a contractual feature, not drift. Persistence is when a rider continues past the specific condition its own clause defines for ending it.

Where do I find the trigger condition for a given surcharge?

In the utility's rate filing or tariff sheet for the account's rate class, filed with the state or regional regulatory commission. The invoice itself will not state the trigger; it only shows the resulting charge.

Why doesn't three-way matching catch this?

Three-way matching checks the invoice against a purchase order and receipt. Most utility riders have no corresponding PO line because they are set unilaterally under the filed rate schedule, not negotiated per order, so the control has nothing to match the surcharge against.

How often should a company recheck utility tariff filings?

On a fixed recurring cadence tied to when the utility typically refiles for that rate class, rather than only at contract renewal. A filing that changes annually needs at least an annual recheck against every rider currently on the bill.

Can a fuel adjustment surcharge go down as well as up?

Yes, by design, since it is meant to track a commodity or power cost index in both directions. A rider that has only ever moved in one direction across several cycles despite index movement is a signal worth checking against the current tariff clause.

Is this the same issue as an accessorial charge that never gets removed?

The underlying mechanism is similar: a billed line that outlives the condition that justified it. The context differs. Accessorial charges are typically shipment-triggered freight fees, while utility surcharges are triggered by tariff conditions like an index level or a load measurement.

What should I ask the utility when I find a persistent surcharge?

Cite the specific tariff clause and its stated trigger condition, then ask the utility to confirm whether that condition still holds for the billed period. A general dispute without the clause reference is far less likely to get a substantive response.

Does this apply to both electric and gas utility accounts?

The mechanism applies to any utility that bills under a filed rate schedule with conditional riders, which includes electric, gas, and in some jurisdictions water and sewer accounts. The specific rider names differ by utility type, but each has its own tariff-defined trigger.