Why the meter exchange is the weak point
Most meter correction disputes turn on something that changed at a specific date: a meter was swapped, a transformer ratio changed, or a multiplier in billing did not change when it should have. Tariff rules treat these as distinct errors. PG&E's Electric Rule 17.1, for example, defines billing error to include incorrect meter reads, crossed meters, an incorrect billing calculation and an incorrect meter multiplier, and provides for an adjusted bill for an undercharge and a refund or credit for an overcharge, without interest.
Dates also limit what a correction can do. In Texas customer-choice areas, 16 TAC 25.126 limits back-billing for a non-compliant meter not affected by tampering to three months when the correction increases the customer's charges, with no such limit when it results in a credit. So the record that explains a settled dispute has to show not only the corrected factor but when each meter and multiplier applied.
Replacement projects often load current meters, active service points and open balances, and leave earlier configurations in the old platform. That is a sensible scope for billing tomorrow's reads. It also means the history on the far side of each meter exchange, which is where a dispute is explained, may be reachable only for as long as the old platform stays up.
Record layers to inventory (Illustrative)
The worksheet below is a fictional example for a 300-person utility billing services company replacing its meter data platform. It records metadata only.
| Record layer | System | Years covered | Administered by | Loads to new platform |
|---|---|---|---|---|
| Register and interval reads | Meter data platform | 2012 to now | Meter operations manager | Last 24 months only |
| Meter change records | Meter data platform | 2012 to now | Meter operations manager | Current meter only |
| Transformer and multiplier records | Billing system configuration | 2014 to now | Billing operations | Current factor only |
| Dispute tickets | Customer service system | 2016 to now | Customer service lead | Not affected |
| Field notes and photos | Field service app | 2018 to now | Field operations | Not in scope |
| Rebill transactions and approvals | Billing system | 2014 to now | Billing operations | Open balances only |
Any layer marked "current only" or "last 24 months" is where an older dispute loses its explanation. Write down the date each old system becomes read-only and the date it is switched off.
Six questions for the billing operations head
Ask these and write down only the answers.
- Which record classes exist? Register reads, interval data, meter change records, transformer and multiplier records, dispute tickets, field notes and photos, rebill transactions, approvals.
- How far back does each go, and does it survive the cutover? Ask what the new platform will receive and what stays in the old one.
- Are meter exchanges recorded against the service point? If not, the history before an exchange may be unreachable after migration.
- Who administers each system? Often the meter operations manager for the head-end, billing operations for the billing system and customer service for tickets.
- What do client contracts say? A billing services company may hold records for utilities under contracts that limit reuse. That changes who can authorize anything.
- When does access end? The decommissioning date of the old platform, or the end of a vendor's read-only period, is the real deadline.
Boundaries for the advisor
Do not take exports, sample bills or logins, and do not advise the company to retain data beyond its policy or authority. Retention decisions belong to the company and its counsel, and customer account data is sensitive even when it is only described. For the wider pattern of a system replacement, see the guide to an ERP replacement; for how approval chains are judged, the guide to procurement approvals and exception workflows; and for the broader dispute workflow, utility billing disputes.
Does the company qualify, and what stays unknown?
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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. Utilities, billing services firms and utility contractors each hold different records; see energy and utilities, utility contractors and the industries hub.
What stays unknown until SourceX reviews the opportunity: buyer interest in dispute histories, the rights review result for customer data and client contracts (see why data rights matter), the de-identification needed, and whether an offer follows. Partners sign the Channel Partner Agreement before submitting introductions.
Go deeper on meter correction disputes
- Meter correction disputes referral brief template: a fill-in brief for company size, platforms, years and owners, with one completed Illustrative example.
- Meter correction dispute examples: one multiplier dispute worked through step by step, with the record each decision produced.
- Meter dispute records across systems: a system map of the meter platform, billing system and field tools, and the keys that join one dispute.
- Who can license meter correction dispute records: a decision tree for record ownership, client contracts and who can authorize a licensing discussion.
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 is replacing its meter platform and its dispute history may not survive the cutover, register as a partner, check the company against who qualifies, and read the program terms before you send the note.