Systems and records
Energy invoice contract reconciliation: tie each bill line to its terms
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
To connect an energy invoice to the applicable contract terms, take one line at a time, name the tariff component or contract clause that priced it, and confirm that version was in force for the line's service dates. Recompute the line from meter or interval data with its reading quality flags, check any rebill against the dated correction rule, and record the term, inputs and verified outcome so the case can be audited.
License terms
Energy invoice contract
Key takeaways
- Every invoice line needs a named governing term and the version in force for its service dates; a close total is not a reconciliation.
- Bills, meter data and contracts must share identifiers such as service point, billing period, rate schedule revision and confirmation ID.
- Reading quality flags and rebill records are evidence; keep original and revised quantities side by side.
- A useful reasoning task asks one bounded question, freezes its evidence and scores against a closed, verified outcome.
- Confidentiality clauses and counterparty agreements decide what can be shared, and de-identification does not replace that review.
Which version of which document governs each invoice line?
Connect each invoice line to the specific term that priced it, using the version of that term in force for the service dates on the bill. An energy invoice usually draws on several documents at once: a utility tariff or rate schedule for delivery, a supply contract and its transaction confirmations for the commodity, any amendments, and rules for meter errors and billing adjustments. Each has its own effective dates, and a billing period can straddle a change in any of them.
Tariffs live with the utility and its regulator. The U.S. Energy Information Administration says it does not collect or publish electricity rate, tariff or demand charge data, and points readers to utility tariff schedules and to the Utility Rate Database on OpenEI. That makes the dated tariff sheet, not a summary rate, the primary evidence for delivery lines.
The working rule is simple to state and hard to follow without records: for every line, name the document, the clause or rate component, the version date and the service dates it covers. A line with no named term is not reconciled, however close the arithmetic looks.
The evidence bundle: identifiers that let a line be traced
A line can only be traced if the bill, the meter data and the contract share identifiers, so collect those first. The Green Button data model used for utility customer energy data (published by the Green Button Alliance in its OpenESPI code) carries a usage summary with a billing period, the bill amount for the last period, itemized additional cost lines, peak demand, ratchet demand and its period, and a quality of reading flag. Those fields are the natural join points between the invoice and interval data.
| Identifier | Where it comes from | Why the task needs it | Common gap |
|---|---|---|---|
| Account and service point or meter ID | Invoice header, utility portal export | Joins the bill to the meter data and the site | Meter exchanged mid-period under a new ID |
| Billing period start and end | Invoice, usage summary billing period | Selects which tariff and contract versions apply | Bill dates differ from read dates |
| Rate schedule code and sheet revision | Invoice rate line, utility tariff book | Names the delivery terms that priced the line | Only the schedule code is kept, not the revision |
| Contract ID, amendment and confirmation ID | Supply agreement file, confirmations | Names the commodity price and volume terms | Confirmations stored in email, not with the contract |
| Reading type, interval and quality flag | Interval data, usage summary | Shows whether quantities were measured, estimated or revised | Quality flag dropped in the export |
| Adjustment or rebill reference | Corrected invoice, utility notice | Links a correction to the bill it changes | Rebill treated as a new, unrelated bill |
| Work order and approval | Maintenance system, approval log | Explains a meter change, outage or curtailment in the period | Work orders kept in a separate system with no account link |
| Dispute and resolution record | AP system, supplier correspondence | Gives the verified outcome for the case | Disputes settled by phone with no record |
Mapping tariff and contract terms to invoice lines
Every charge type has a governing structure, and the reconciliation checks that structure, not just the total. The Utility Rate Database API documents how tariffs decompose: energy rates with tiers and time-of-use periods driven by 12 by 24 month and hour schedules, flat and time-of-use demand structures, a demand ratchet percentage for each month, a demand window in minutes, and fixed and minimum charges. Supply contracts add their own quantities, prices and delivery periods.
Use the table as a checklist of what each line needs. The point is to make every comparison explicit, so a reviewer can see which input disagreed.
| Invoice line type | Governing term | Data needed to recompute | Typical mismatch |
|---|---|---|---|
| Energy by period or tier | Tariff energy rate structure and schedule, or contract price | Interval kWh mapped to periods by local time | Holiday or daylight saving hours mapped to the wrong period |
| Demand | Tariff demand structure and demand window | Interval kW at the window length the tariff names | Peak taken from 5-minute data when the tariff uses a longer window |
| Demand ratchet | Ratchet percentage and look-back months | Prior peaks for the look-back period | Ratchet applied after a rate change that removed it |
| Fixed and minimum charges | Customer, meter and minimum charge terms | Meter count and service days | Charged for a meter that was removed |
| Commodity volume under a supply deal | Contract quantity and confirmation | Delivered quantity by delivery period | Volume outside the confirmed range priced at the wrong rate |
| Adjustment or rebill | Utility rule on meter and billing errors | Original bill, corrected reads, rule version | Correction spans more months than the rule allows |
Estimated, revised and corrected readings
Treat reading quality as part of the evidence, because a bill built on estimates is a provisional answer. In the Green Button model, each reading is assumed good unless a reading quality record says otherwise, and more than one quality can apply to the same reading. If an export drops that record, an estimated read looks exactly like a measured one.
Corrections are governed by dated rules that differ by utility and customer class. PG&E's Electric Rule 17, for example, sets how far back a bill can be adjusted for a nonregistering meter, with a shorter period for small business customers than for other nonresidential customers. A reconciliation that finds a rebill should record which rule version applied and whether the corrected months fall inside its limit; a reviewer, not the task, decides whether to dispute.
In the dataset, store original and revised quantities side by side with their quality flags and the date each was received. Never overwrite the first value; the sequence of estimate, actual and correction is itself the reasoning a model has to learn.
The rights screened contract and invoice reasoning task
The asset is a task definition: a bounded question, a fixed evidence bundle, a small set of allowed answers and a rights screen that runs before any record enters the set. It is written so an evaluator can score an AI system's answer against a verified outcome rather than against opinion.
- Grade A: gold outcome present, every term version dated, reading quality flags kept.
- Grade B: gold outcome present, one input version inferred from surrounding dates.
- Grade C: no closed outcome; keep for analysis only, never for scoring.
- Split train and evaluation sets by account and by period, so the same meter never appears on both sides.
| Component | Content | Rule | Who confirms it |
|---|---|---|---|
| Question | Is invoice line L correctly priced under the terms in force for its service dates? | One line per task; no open-ended audit | Energy analyst |
| Evidence bundle | Invoice, usage summary and intervals, dated tariff sheet, contract, amendment and confirmation excerpts, work orders | Bundle is frozen at task creation; versions dated | Data owner |
| Allowed answers | Consistent; inconsistent with the named term; cannot determine from the evidence | An inconsistent answer must cite the term and input that disagree | Energy analyst |
| Gold outcome | Resolution recorded in the dispute or AP system | Only cases closed by a rebill, credit or written acceptance | AP or energy manager |
| Rights screen | Confidentiality clause status, counterparty consent where needed, redaction list | Fails closed: no screen result, no inclusion | Contract owner and counsel |
| Redaction | Counterparty names, account numbers, site addresses and personal contacts replaced with stable tokens | Same token across all records of one counterparty | Privacy reviewer |
| Exclusions | Live disputes, cases under regulatory complaint, terms the contract bars from disclosure | Excluded cases are counted, not silently dropped | Contract owner |
Illustrative case: a ratcheted demand charge in a period that spans an amendment
This case is illustrative; the quantities are invented and no prices are shown. A commercial site's bill covers 32 days and crosses the effective date of a supply amendment on day 18. The delivery tariff includes a demand ratchet: billed demand is the higher of the period's own peak and 80 percent of the highest peak in the prior eleven months.
The task asks whether the demand line is correctly priced. The interval data shows a period peak of 410 kW at the tariff's demand window. The highest peak in the look-back months was 600 kW, so the ratchet floor is 480 kW, and the bill shows 480 kW. The demand line is consistent with the named term. The energy lines are checked separately: days 1 to 17 against the original contract price component and days 18 to 32 against the amended one, using local-time interval data.
The exception arrives two months later. The utility issues a rebill because the meter had been reading low; the revised peak for the period is 505 kW, which now exceeds the ratchet floor. The correct answer to the original task does not change, because it was right on the evidence available, but a new task is created for the rebill, with the rule version on meter error adjustments attached and both reading sets kept. A model that learns to revise old answers silently would score badly on this pair, which is the point of including it.
Safety, confidentiality and the edge of the task
The task stays administrative: it compares records and names a disagreement, and it never recommends physical action on meters, equipment or operating schedules. Meter tests, equipment changes and load decisions belong to the utility and qualified site staff under their own procedures. If a case suggests a metering fault, the task output is cannot determine from the evidence, with a note to request a utility review.
Confidentiality is a contract question before it is a data question. The NAESB base contract form for natural gas, for example, includes a confidentiality provision under which transaction terms stay confidential for one year after the transaction expires, with listed exceptions; the existence of the contract itself is not confidential, and parties can elect whether the provision applies. Other supply agreements set different terms. Read each agreement's clause, record the result in the rights screen, and exclude terms the agreement bars from disclosure.
De-identifying counterparties does not by itself create a right to share a contract's terms. Whether a company can license reconciled records depends on its agreements with utilities, suppliers and brokers, which counsel reviews on the specific facts.
When an energy specialist or counsel has to take the case
Stop and bring in a specialist when a case turns on how a tariff is interpreted rather than how it is applied, when a rebill crosses the limit in the applicable rule, when a supply contract has pass-through or change-in-law terms, or when the bill involves interval data that the utility has revised more than once. An energy procurement or rate analyst should confirm the governing terms, and counsel should review any confidentiality or disclosure question.
Narrow the scope rather than widen the task when evidence is thin. A task set built from fewer, fully evidenced lines is more useful than a large set with inferred term versions. Record why each case was excluded, so the set's limits are visible to whoever evaluates a model on it.
Licensing reconciled invoice histories
Reconciled energy invoices are useful evaluation material for document and agent systems because each closed case links a bill, dated terms, measured data and a verified outcome. The rights work comes first: supply contracts, utility agreements and broker terms decide what can be shared, and those are separate from whether the data is accurate.
For a company with years of closed billing disputes, SourceX can run the rights review, contracting, preparation and delivery that turn those invoice cases into a licensed dataset. Buyers usually look for two or more years of consistent history and a large record count in one system, while unusual reconciliation work is judged on its own merits. No energy records move until the scope and terms are approved and signed, and the opening step is a brief assessment without any upload.
Frequently asked questions
How do you match an energy invoice to the contract terms?
List each invoice line, name the tariff component or contract clause that priced it, and confirm the version in force for the line's service dates. Then recompute the line from interval or meter data and compare. A line without a named, dated term is not reconciled.
What is a demand ratchet on an electricity bill?
A demand ratchet sets a floor on billed demand based on a percentage of an earlier peak, so a lower current peak can still be billed at the higher floor. Tariffs define the percentage and the look-back months. The Utility Rate Database stores a ratchet percentage for each month of a rate.
Why does reading quality matter in invoice reconciliation?
An estimated or revised reading changes what the bill can prove. In the Green Button model, readings are assumed good unless a quality record says otherwise, so dropping that record hides estimates. Keep original and revised values with their flags.
How far back can a utility correct a bill?
It depends on the utility's rules and the customer class. PG&E's Electric Rule 17, for example, sets a shorter back-billing period for small business customers than for other nonresidential customers when a meter fails to register. Check the rule version in force for the period in question.
Can energy contracts be shared for AI training?
Only if the agreements allow it. Many supply contracts have confidentiality clauses, and the NAESB gas base contract includes one that covers transaction terms for a year after expiry. Counsel should review each agreement before any terms are licensed.
Sources
- The Green Button (NAESB ESPI) usage summary model carries a billing period, the bill for the last period, itemized additional cost lines, peak demand, ratchet demand and its period, and a quality of reading field. Source
- In the Green Button model, more than one quality can apply to a reading, and each reading is assumed good unless a reading quality record states otherwise. Source
- The Utility Rate Database API describes energy and demand rate structures with periods and tiers, 12 by 24 month and hour schedules, a monthly demand ratchet percentage, a demand window in minutes, and fixed and minimum charges. Source
- EIA does not collect or publish electricity rate, tariff or demand charge data and points to utility tariff schedules and the Utility Rate Database. Source
- PG&E Electric Rule 17 limits back-billing for a nonregistering nonresidential meter to three months for small business customers and three years for other nonresidential customers. Source
- The NAESB Base Contract for Sale and Purchase of Natural Gas keeps transaction terms confidential for one year from the transaction's expiration, with exceptions, and states that the existence of the contract is not subject to that obligation. Source
See if your company qualifies
A short company assessment. No data uploads are needed.