- Before
- Runs monthly exception reports on billing and meter data, with no network map, and spends most of a day building the evidence for one back-bill.
- Now
- Opens the buckets that moved this week and the premises behind them on the map, such as the 186 that changed this week, each with its proof.
A tower energized with no accounts, found and billed back inside the rule
The sample utility supplies electricity and water to 1,004,600 premises and billed $9,860.0M in the last 12 months. One Monday the weekly run finds a new ring of premises on one residential tower. Here is what happens next, screen by screen, in the working solution.
A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.
- 01Monday, 06:51
The year, drawn as one waterfall
Six agents · the weekly runThe run takes 06:10 to 06:51. The network tracer traces 1,004,600 premises to 9,412 transformers; the meter data reader reads 1,762,100 meters and finds 3,860 silent for 30 days; the account matcher runs 9 checks and files 17,607 gaps in 8 buckets. The waterfall runs from $9,922.3M delivered to 9,893.4M metered, 9,860.0M billed and 9,821.5M collected, each step down a named bucket.
“$62.3M delivered in the year never reached a bill” · root cause finder: “New: one residential tower, 186 premises”
- 02Morning
Consuming, no account: up 186 this week
Revenue assurance analystThe analyst opens the bucket that moved: 1,240 premises, $3.1M a year at tariff, $2.2M back-billable under rule BR-7. Each premise is a dot on the map of the utility’s eight districts, and a new ring sits on the tower: 186 premises, $612k a year. Beside it, how the gap is found: network map connected and energized, meter data at least 30 kWh, or the set water volume, in 30 days, billing with no active account.
Top root cause in the bucket: “Developer handover file rejected silently” · $1.1M
- 03One premise
One apartment: connected, consuming, not billed
Network tracer and meter data readerThe trace runs from the substation through the feeder, the tower’s transformer and its rising main to one apartment, energized under a service order seven months ago. Its electricity meter has recorded 7,940 kWh since, and both meters show 100% actual reads. Billing shows no account, premise status “installed, not billed”, and the developer’s handover file rejected two days after the tower was energized.
Priced at the tariff version in force: $3,228 to date. “No month went above the first tier, so no higher rate applies.”
- 04The case
The case, with the three-way join for each apartment
Case writerThe case opens on the join, premise by premise: each of the 186 on the tower’s transformer, 158 consuming and 28 near zero (unlet), none with an account. Reads run from energization to the run date, priced at 29.5 cents/kWh and the water tariff, with the unbilled value by month for electricity and water.
“186 premises · $612,000 a year at tariff · back-bill $370,600 from energization to date”
- 05The money
Priced at tariff, inside the rule
Revenue estimatorElectricity, 919,700 kWh: $271,300. Water: $99,300. The back-bill is $370,600, $352,070 of it recoverable at 95% collectable, and $612,000 billed each year from now. The developer is billed from energization, because clause 9.2 of its connection agreement makes the developer the account holder until a tenant takes over the supply.
Rule BR-7: developer-held supply, “from energization” · field check not needed: the largest premise is $3,228
- 06How it leaked
A handover file, rejected silently
Root cause finderDay one: the tower is energized, 186 premises. Day two: the meters start reading daily. Day three, 11:42: the developer’s handover file is rejected, because the tenant reference is blank on 186 of 186 rows, and the rejection notice goes to a mailbox nobody reads. No account is created. The same cause sits behind 412 premises across 6 developments.
“Proposed fix: a rejected handover file raises a work item for billing operations within the hour.”
- 0707:18 · approved
Approved, with the checks on the same screen
Revenue assurance managerThe analyst sends the case for approval. The revenue assurance manager signs for a back-bill of $370,600 to the developer, and 186 accounts in its name until tenants take over. Before the signature, three checks show: inside rule BR-7, evidence pack complete with trace, reads, account history and tariff version, and prepared by someone else.
Agents find, price and draft; only named people approve a back-bill.
- 0807:24 · co-signed
Two signatures, 186 accounts open
Finance controllerAbove $250,000 a back-bill needs two signatures, so the finance controller co-signs after the manager. The back-bill is posted to the developer, billing operations reloads the handover file with the tenant references, and 186 accounts open, billed from the run date. The bucket falls back to 1,054 premises.
“Billed. Back-bill of $370,600 posted to the developer; 186 accounts open, billed from the run date. The bucket is back to 1,054 premises.”
- 09The cause
The cause behind the bucket, with its owner
Billing operations leadFixing a case recovers the money once; fixing its cause stops the bucket refilling. The root causes screen ranks 31 causes from 312 clusters by value a year and shows how much each refills a week. “Developer handover file rejected silently” refills 31 premises a week, worth $1.1M a year, and billing operations owns it.
Root cause finder proposes causes and owners; it does not close a cause.
- 10Month end
Found is not recovered
Finance controllerRecovery reconciles each case to billing for the audit committee: $49.7M found a year, $26.9M billed back this year from 2,960 closed cases, $18.4M collected (61% of the $30M target), and $21.7M billed each year from causes that were fixed.
Wrong multiplier cases brought in the most: $7.4M paid.