This worked case is part of the meter correction disputes guide. It is built for utility billing advisors who want to recognize a well-documented exception at a client before suggesting an introduction.
The setup: why one number controls the whole bill
On larger commercial services, the register never sees the full current. Current transformers step it down, and billing scales the register read back up to recover real usage. NB Power's guide to its own bills shows the arithmetic: a 400:5 ratio gives an external factor of 400 divided by 5, or 80, and that number is not printed on the device. If the transformers change, the factor in billing must change on the same date.
Tariffs recognize what happens when it does not. Pacific Gas and Electric's Rule 17.1 counts a wrong multiplier as billing error, with an adjusted bill or a credit to follow.
The case, decision by decision (Illustrative)
A fictional 340-person utility billing and meter services company reads, bills and handles disputes for several client utilities. One commercial customer's service is upgraded.
| Cycle | What happened | Who decided | Record created | Billed usage |
|---|---|---|---|---|
| 1-3 | Normal billing on 400:5 transformers, factor 80 | Billing system, automatic | Register reads, interval profile | About 42,000 kWh per cycle |
| 3 | Device and transformers exchanged; new ratio is 200:5 | Field crew, under a work order | Field work order, device change record | Not billed separately |
| 4 | Billing record still carries factor 80 | Nobody; the change was never keyed | Bill calculation log | 84,000 kWh |
| 5 | Customer disputes the second doubled bill; bill held | Customer service agent, within hold authority | Dispute ticket, call notes | 84,000 kWh, held |
| 5 | Technician photographs the nameplates and confirms 200:5 | Meter technician | Investigation note, photos | Not applicable |
| 6 | Cycles 4-5 reissued at factor 40; configuration corrected | Billing supervisor, approval limit | Approved adjustment, corrected configuration | 42,000 kWh, credit issued |
Step by step: what each record proves
Cycle 4, the silent error. The register read is accurate and the calculation runs correctly; it simply applies yesterday's scaling. Nothing in the bill calculation log looks wrong in isolation. The only signal is the jump from about 42,000 to 84,000 kWh with no change in the interval load shape.
Cycle 5, the dispute. The ticket captures the customer's view and the decision to hold the bill. The hold is a judgment call, and the agent's notes are where the reason sits.
Cycle 5, the field check. The nameplate photos are the evidence that turns a suspicion into a cause. Without them, the reissued bills would rest on someone's memory of a work order.
Cycle 6, the approved fix. The supervisor's approval does two things: it corrects two bills and it corrects the configuration that produced them. A history that keeps only the corrected bills loses every step above.
Why direction and dates change the record
This case ends in a credit. Had the error run the other way, with an old factor of 40 left in place after an upgrade to a 400:5 ratio, the company would have underbilled for months. In Texas customer-choice areas, commission rule 16 TAC 25.126 limits back-billing for a non-compliant meter not affected by tampering to three months when charges go up, with no such limit on credits; whether a given error falls under that rule is a regulatory question. Other states and tariffs differ. A record that captures the direction, the period corrected and the rule applied is far more explainable than one that captures only an amount. This is general information, not legal or regulatory advice.
Spotting similar cases at a client
Ask the billing operations head these questions and note only the answers:
- Are device exchanges recorded against the service point, with a dated factor history?
- Do dispute tickets link to the bills they cover, or only to the account?
- Are field photos and investigation notes kept with the case, or in a separate field app?
- Do reissued bills reference the ones they replace and name the approver?
- Roughly how many scaling, wiring or read errors were corrected per year, and over how many years?
A client that can answer most of these with "yes" holds cases like this one. The system map shows which tool holds each link, and the guide to assessing human review and correction workflows explains how approval trails are judged. For a parallel in another setting, see procurement approvals and exception workflows; field work orders also appear on the maintenance data page.
Qualification and what stays unknown
An introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English. Partners sign the Channel Partner Agreement before submitting introductions and never take bills, reads or account lists.
Until SourceX reviews it, nobody knows whether the company or its client utilities hold the rights, how customer data is de-identified, whether buyers want dispute histories or whether an offer follows. The decision tree for who can license these records identifies the signer, the referral brief template captures the metadata, and energy and utilities lists related candidates.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a billing client can trace cases like this one from exchange to dispute to approved rebill, register as a partner, check the company against who qualifies and read the program terms before you approach the billing operations head.