This system map is part of the meter correction disputes guide. It is written for utility billing advisors who want to judge, at metadata level, whether a client's dispute history can be joined into whole cases.
The four systems and what each one sees
Head-end or meter data management (MDM). Holds raw register reads and load profiles by device, plus the change record when a device is swapped. It usually knows nothing about bills, tenants or disputes.
Billing system. Holds premises, service points, occupancy dates, the billing factor with its effective date, calculated bills and corrected-bill transactions with approvers. This is where a wrong mapping or factor does its damage. NB Power's customer guide notes that part of the billing factor for larger services is not shown on the device itself, so billing is often the only place it is recorded.
Customer service tool. Holds the dispute ticket, call notes and the hold decision. Sometimes it is a module of billing; often it is a separate product with its own case numbers.
Field app or metering shop system. Holds work orders, technician notes, test results and photos from the investigation.
The map: system, record, linking key, owner
| System | Record held | Linking key to the next system | Typical owner |
|---|---|---|---|
| Head-end or MDM | Register reads and load profiles by device | Device serial mapped to service point ID | Metering operations manager |
| Head-end or MDM | Device change record at exchange | Service point ID plus exchange date | Metering operations manager |
| Billing system | Billing factor and its history | Service point ID plus effective date | Billing operations head |
| Billing system | Calculated bills | Account number plus bill number | Billing operations head |
| Billing system | Premise, occupancy and move-in or move-out dates | Premise ID linked to service point and account | Billing operations head |
| Customer service tool | Dispute ticket and call notes | Account number plus disputed bill numbers | Customer service lead |
| Field app | Work order, test results, photos | Work order number cited on the ticket | Field operations manager |
| Billing system | Corrected-bill transactions and approver | Original bill numbers cancelled | Billing operations head |
Read down the third column and the dependencies show. Every link after the first relies on the service point ID or the account and bill numbers being stored in structured fields, not typed into notes.
One fully joined case (Illustrative)
This case is deliberately different from the scaling-factor dispute in the worked example. A fictional 340-person billing services company traces a crossed-meter dispute, where two devices were wired to each other's premises. All identifiers are invented.
- Premises P-12A and P-12B, two adjacent suites in one commercial building, each have a service point: SP-4410 and SP-4411.
- The head-end maps device M-1 to SP-4410 and device M-2 to SP-4411, exactly as installed. In the field, M-1 actually measures suite 12B and M-2 measures suite 12A.
- Billing issues eight cycles of bills on accounts A-301 (suite 12A) and A-302 (suite 12B), each charging one tenant for the other's consumption.
- A move-out record shows suite 12A vacant from cycle 7, yet its bills keep showing normal consumption. The building owner, now responsible for the vacant suite, disputes those bills in ticket T-5520, which names account A-301 and cites bills 7 and 8.
- Work order WO-8834 records a shut-off test: with suite 12A's breaker off, M-2 stops; with 12B's off, M-1 stops. The technician confirms the swap.
- Rebills R-201 and R-202 cancel the eight bills on each account, reissue them against the correct device, and the head-end mapping is corrected, with the supervisor's approval recorded.
With all six links intact, a reviewer can recompute every affected bill on both accounts from the stored reads and the corrected device mapping. That recomputation is the best single test of whether an archive holds explainable cases. Notice that the join depends on the service point, the premise and the occupancy record, not on any one system: lose the move-out date and the anomaly that started the investigation disappears.
Where the joins usually break
| Break | Symptom | What it costs |
|---|---|---|
| History stored by device serial only | A new device starts a fresh history at exchange | Reads before the exchange cannot be tied to the case |
| Mapping or factor overwritten, not dated | Billing shows only today's factor | Old bills cannot be recomputed |
| Raw reads purged sooner than bills | Bills exist, reads do not | The original error cannot be shown |
| Ticket cites bills in free text | Joins work by hand only | Large-scale reconstruction fails |
| Photos kept on a shared drive | Evidence not linked to a work order | The cause rests on memory |
| Corrections post as new bills | No link to cancelled bills | Correction looks like extra billing |
Dates matter beyond recomputation. PG&E's Electric Rule 17.1 names crossed meters, alongside wrong factors and misreads, as billing error to be corrected by an adjusted bill or a credit, and correction rules elsewhere often limit how far back a utility may go. A case whose correction period cannot be dated cannot show which rule applied. A platform replacement that migrates only current configurations has the same effect as an overwritten mapping; the CMMS migration guide covers the pattern in maintenance systems.
Ownership and what stays unknown
Ask the billing operations head which identifiers each system stores, how far back each goes and who administers it. Do not request exports, bills or logins. A billing services company may hold records for client utilities under contracts that limit reuse, which the decision tree on who can license these records addresses.
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. Rights, de-identification, buyer interest and any offer stay unknown until SourceX reviews the opportunity.
The worked multiplier case follows a different dispute as a story of decisions. Related chains appear in utility billing disputes, where allocation rather than metering is wrong, and in freight audit exceptions, where a rated charge carries a disputed factor. Field work orders are covered on the maintenance data page, and related companies under energy and utilities.
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 client's systems keep the service point, dated device mapping, ticket and correction links intact across years, register as a partner, check the company against who qualifies and read the program terms before you make the introduction.