How to prepare utilities and energy data for an audit

Executive Summary

Utilities audits fail before they start, not during analysis. The data sits split across a facilities team that holds the tariff schedules and an AP team that holds the invoices, and neither side has both. In utilities, drift hides in rate schedules, demand charges, and power factor penalties that standard AP review does not touch, because that review was built to check purchase orders, not tariff math.

Preparing the data means pulling twelve months of invoices per meter or account, the current tariff or supply contract for each site, and the meter-to-GL mapping that ties usage back to a cost center. Without all three, a reviewer can see that a bill changed but not why, or whether the change was earned.

What changes the outcome is sequencing: pull the tariff before the invoices, because the tariff defines what a correct invoice looks like. Reversing the order means checking bills against each other instead of against contract, which finds inconsistency but not drift.

1. What data does a utilities and energy audit actually need?

A utilities audit needs three data sets aligned by meter or account number: twelve months of invoices showing every line item, the current tariff schedule or negotiated supply contract for each site, and a meter-to-GL mapping that ties usage to a cost center. Missing any one of the three means a reviewer can see a number changed but cannot determine whether the change was contractually correct. All three together let a reviewer trace a single charge from meter to invoice.

Invoices alone show what was billed. They do not show what should have been billed, so a reviewer working from invoices only can flag inconsistency between months but not drift against contract.

The tariff schedule or supply agreement is the reference document. For regulated utilities this is the published rate schedule filed with the state commission. For deregulated markets it is the negotiated supply contract, which sets the commodity rate, the term, and any demand or capacity charges layered on top of it.

The meter-to-GL mapping matters because multi-site manufacturers often have utility accounts that do not map cleanly to the cost center paying for them. A meter serving two production lines billed to one GL code hides which line's usage is driving the demand charge.

• Invoice detail: Twelve months of line-item invoices per meter or account, not summary totals.
• Tariff or contract: The current rate schedule or supply agreement in force for each site.
• Meter-to-GL mapping: A tie between usage at the meter and the cost center that pays for it.

2. How do you pull twelve months of utility invoices in a usable format?

Export invoices as line-item detail, not summary PDFs: every charge code, its rate, its quantity, and its billing period on its own row. Twelve months is the minimum because demand charges and ratchet clauses are calculated against a trailing peak, so a shorter window cannot show whether a current demand charge is still earned or has carried forward past its trigger. Build the file around the meter number, not the legal entity.

Utility billing portals offer a CSV or itemized statement export in addition to the PDF invoice. Use that export. A PDF invoice rolls several charge types into one subtotal, which is exactly the layer where a stale rate or an expired surcharge hides.

1. Log into each vendor's billing portal or request itemized statements from the account representative.
2. Export twelve consecutive months per meter or account number, not per legal entity.
3. Confirm each row carries: charge code, description, rate applied, quantity or usage, and billing period start and end date.
4. Flag any invoice where the line-item export is unavailable and a PDF must be manually transcribed. These need a second reviewer.

Store the export with a consistent file name convention keyed to meter number and billing month, so a reviewer can trace a single meter's twelve-month history without reopening a portal.

3. How do you organize tariff schedules and supply contracts before matching?

Build one reference sheet per site listing the applicable rate schedule or contract, its effective dates, the demand charge structure, any power factor penalty, and the renewal or expiration date. This sheet is what the invoice gets checked against, so it has to exist and be current before line-by-line matching starts, not assembled alongside it. Treat it as the control document, updated whenever a tariff or contract changes.

A rate schedule changes when a utility files a new tariff with its regulator, which can happen without the customer initiating anything. A supply contract changes on its own renewal date, which the AP team may not track because the contract sits with facilities or procurement.

The reference sheet needs, per site: the current rate schedule name or contract number, effective start date, demand charge basis (kW or kVA, and over what averaging window), any power factor penalty threshold, and the next renewal or rate-review date.

A. Regulated tariffs

Pull the current published schedule directly from the utility's tariff filing, not from memory of what was billed last year.

B. Deregulated supply contracts

Pull the signed agreement, not a renewal notice or a broker summary, because the enforceable rate terms are in the agreement itself.

C. Renewal tracking

Note the expiration date on the reference sheet itself so a lapsed contract that reverted to a higher default rate is visible before invoice matching, not discovered after.

4. How do you match invoice line items against the tariff?

Match each invoice charge code against the corresponding tariff line for the same billing period, checking the rate applied, not just the dollar total. A demand charge, a power factor penalty, and a fuel adjustment each have their own basis in the tariff, and a total that looks stable month to month can still contain one charge that drifted while another offset it. Match charge by charge, never at the invoice-total level.

Three-way matching checks the invoice against the purchase order and receipt of goods. Utilities rarely have a purchase order at all, which is why this category needs a different control: matching the invoice directly against the tariff or contract line, charge by charge.

Start with the charges that recur every period: the base commodity or delivery rate, and any demand charge. Confirm the rate applied on the invoice equals the rate in the current reference sheet for that billing period, not a prior period's rate carried forward by the vendor's own billing system.

Then check the charges that trigger conditionally: power factor penalties, ratchet demand charges based on a trailing peak, and fuel or purchased power cost adjustments. Nothing in a standard AP workflow re-tests the trigger condition each month, so these charges can persist past the condition that justified them.

5. What role does the BLS Producer Price Index play in checking energy cost movement?

The Producer Price Index for industrial electric power gives an external reference point for whether a rate movement reflects a broad cost trend or a vendor-specific change. Per the US Bureau of Labor Statistics PPI series WPU0543 (read 2026-09-06), the July 2026 index value was 341.966, up 1.2% year over year, which is the scale of movement a reader should expect from underlying cost pressure alone.

If an invoice shows a rate increase well above the year-over-year movement in the underlying index, that gap is worth investigating as a candidate for vendor-specific drift rather than market-wide cost pass-through. If the invoice increase tracks close to the index movement, the increase is more likely a legitimate pass-through of input costs.

This is a sense check, not a substitute for matching against the actual tariff or contract. The index describes an industry-wide commodity trend. It says nothing about whether a specific demand charge basis or power factor threshold was applied correctly on a specific invoice. Use it to prioritize which sites or which months get closer review, not to conclude drift exists on its own.

6. How do you document findings so a utility disputes them successfully?

Document each finding with the invoice line, the tariff or contract clause it should have matched, the dollar difference, and the billing periods affected, in a format the utility's billing department can verify without a phone call. Utilities have formal dispute and rebilling processes, and a claim that cites the exact tariff section moves through that process faster than a claim that only cites the invoice total.

A finding package should include: the meter or account number, the billing period, the charge code in question, the rate the invoice applied, the rate the tariff or contract specifies for that period, and the resulting dollar variance.

Where the discrepancy involves a rate schedule change the utility filed with its regulator, cite the filing or effective date directly rather than describing it generically. This is general information, not legal advice, and a dispute involving a regulated tariff filing may warrant review by counsel before submission, particularly where a back-billing or refund cap under the applicable tariff could limit recovery.

1. Compile findings: One row per finding with all fields above, in a single tracking sheet.
2. Attach evidence: The reference sheet section for the site, as supporting documentation.
3. Route by materiality: Send findings above a materiality threshold to the vendor's billing dispute channel, not a general account line.
4. Track follow-up: Log a follow-up date for each submission, since dispute cycles run on the utility's own timeline.

For the wider pattern this sits inside, start with the margin drift guide. See also the three-way match gap: what your erp structurally cannot see and n-way invoice matching explained.

7. Frequently Asked Questions (People Also Ask)

How far back should we pull utility invoices for an audit?

Twelve consecutive months per meter or account is the minimum. Demand charges and ratchet clauses calculate against a trailing peak, so a shorter window cannot show whether a current demand charge is still earned or has simply carried forward.

What if the utility only issues PDF invoices, not a CSV export?

Flag those invoices for manual transcription and route them to a second reviewer. Transcription introduces error risk that a native line-item export does not, so treat manually transcribed months as lower confidence until checked twice.

Who inside the company usually holds the tariff or supply contract?

It can sit with facilities, procurement, or a site manager rather than AP. Locating the actual signed document, not a renewal notice or broker summary, is often the slowest step in preparation.

Does a stable total invoice amount mean there's no drift?

No. A demand charge, a power factor penalty, and a fuel adjustment each have a separate basis in the tariff. One can drift upward while another offsets it, leaving the invoice total looking flat while a specific charge line is wrong.

Can three-way matching in the ERP catch utility billing errors?

Three-way matching checks the invoice against a purchase order and a receipt of goods. Utilities rarely generate a purchase order at all, so this control has nothing to check against and utility charges pass through unmatched.

What is a demand ratchet clause and why does it matter for review?

A ratchet clause sets a site's demand charge based on its highest usage peak over a trailing window, often 11 or 12 months, rather than the current month's peak. A charge set by a peak from months ago needs the historical data to verify, not just the current bill.

Should legal review a utility billing dispute before it's submitted?

Where the dispute involves a regulated tariff filing or a contractual back-billing cap, yes. This is general information, not legal advice, and a refund cap or filing deadline in the applicable tariff can limit what is recoverable regardless of how clear the finding is.

How do you handle a site where the tariff schedule has changed mid-year?

Split the twelve-month invoice window at the effective date of the change and check each period against its own applicable schedule. Matching the whole year against only the current schedule will misread every invoice before the change as an error.