Utility billing exception management that stops wrong bills before they post — every held bill with its cause, its corrected bill and the evidence
Held bills cleared in two days, not six, with the cause and the fix attached.
See one case, screen by screen ↓Every bill run parks bills on hold: high or low usage against the account’s history, zero usage on an active account, a third estimate in a row, reads that do not join across a meter exchange, a rate code that does not match the premise. At Lumina Utilities, bill run cycle 14 on Fri 9 Oct put 2,184 of 52,640 bills on hold. Each one means four lookups — the hold reason in the billing system, the reads in the meter data system, the field order result, the tariff — and an analyst works them one at a time.
Often the cause is upstream and nobody sees it. Since field app release 6.2 on 14 Aug, install reads from meter exchanges have stayed on the order and never reached billing, so billing starts the new meter at zero and bills its whole register as usage. This run held 386 bills for it, up from 52 in August. A wrong bill that gets out becomes a high-bill call, a complaint to the commission or a back-bill that the rules cap at 12 months.
Estimated split for a typical held bill, in working days, by hand and with the solution — the 6.2-day baseline is the figure to measure in the pilot.
Six agents find each hold's cause, prove it from reads, field orders and the tariff book, and draft the fix; the analyst releases.
Lumina Utilities bills electricity and water. Ruth Calloway at 18 Fernhill Road, Westbrook, is on residential electricity R-1 and water W-1. Her bill for 9 Sep – 8 Oct 2026 came out of bill run cycle 14 at $1,125.77. Here is what happens next, screen by screen, in the working solution.
The hold classifier reads all 2,184 holds from bill run cycle 14 with each account’s history. Ruth Calloway’s bill is held for high usage: 5,347 kWh against a 12-month average of 856 kWh, 4.6× her usual $244.59. Her last twelve bills stand as columns across the top, the held one in red, with three events pinned where they happened — an estimate in March, the R-1 rate change on 1 Jul and a meter exchange on 22 Sep.
“HELD FRI 9 OCT · 4.6× USUAL — $1,125.77 · High usage”
The read reconciler finds the meter exchange inside the bill period: AX-3318807 out, LU-9920415 in, and billing started the new meter at 0. The field order matcher finds FO-77193, completed by Marco Lindqvist on Tue 22 Sep at 10:41: removal read 61,418, and a reconditioned meter installed with its register at 04,580. The read was keyed on the handheld and never posted to billing.
Technician note: “Refurb unit from stock, register not zeroed. Install read 04580 entered on the handheld.”
The interval reads agree: 1,589 of 1,589 intervals on the new meter sum to 431.2 kWh, which is 5,011 − 4,580. Usage billed drops from 5,347 kWh to 767 kWh. The tariff checker recomputes the bill on R-1 at the rates in force since 1 Jul: energy over 600 kWh goes from $835.47 to $29.39, fuel and purchased power from $65.77 to $9.43, sales tax from $43.30 to $8.80. The water lines do not change.
“7 lines changed · every change cites its source” — corrected bill $228.85, −$896.92
The correction drafter scores the correction 98 out of 100: five sources agree and the corrected bill sits inside Ruth’s usual range of $210–$289. That is above the release line of 95. Dana reads the diff, shows the corrected bill as a green ghost beside the red one, and releases it. It goes out in tonight’s print and e-bill run.
“Corrected bill released · $228.85 instead of $1,125.77 · goes out in tonight’s print and e-bill run”
The pattern finder adds Ruth’s bill to the batch “Meter exchange: install read not posted”: 386 held, 341 corrections drafted, 318 at confidence 95 or more, each start read restored from its own field order. The confidence chart shows the 23 below the line — 7 at 93 and 16 at 94 — which stay with an analyst. A sample of five diffs is drawn for the supervisor.
“Cause. Field app 6.2 does not send install reads to billing (since 14 Aug). Upstream owner: Kwame Asante · meter operations.”
Over 100 bills, so the batch goes to Tomás Ferreira. He opens the sample of five — Ruth Calloway, Gareth Pell, Simone Achebe, Wen Li Harrow, Patrick Doyle-Ames — checks two sources and approves. All 318 go to tonight’s print and e-bill run, and the decision log writes 318 entries with the amounts before and after.
“Approved by Tomás Ferreira · Tue 13 Oct · ‘sample clean, release’”
On Recurring causes, holds per bill run climb from 1,422 in March to 2,184 in October, with a marker at 14 Aug · field app 6.2. Install reads not posted are 17.7% of October’s holds, with release 6.3 not yet booked. One click raises the upstream fix to Kwame Asante in meter operations, so next month’s run holds fewer bills.
“386 holds in October from install reads not posted — up from 52 in August”
Not every hold is a meter exchange. Aoife Brennan’s meter LU-8812207 stopped reporting on 6 Jul with a radio module fault, and August and September went out on estimates. Rule 7.3 holds the third estimate for an analyst. Field order FO-78020 came back on 12 Oct with the module replaced and an actual read of 28,904, so the correction bills 854 kWh on the actual read: $165.26 in place of the $158.61 estimate, at confidence 97.
Rule 7.3: “No more than three consecutive bills may be estimated.”
Okafor Family Dental at 220 Quarry Street was still billed on residential R-1. The tariff checker finds permit BP-26-3318: a change of use to a dental clinic on 3 Aug. Re-rated on small commercial GS-1 with 14 kW of demand, the bill is $467.41, with a back-bill of $186.18 for August and September offered over two months under rule 9.1. Confidence is 93, below the release line, and any rate-code change needs the supervisor — the button reads “Send to Tomás Ferreira”.
Correction drafter: “Confidence 93 · below the 95 release line — kept with an analyst · sent to Tomás Ferreira”
The high-usage rule holds bills above 3.0× the 12-month average, and 61% of those it held in October were right all along. Raising it to 3.5× and replaying it on the last three runs — 157,410 bills, 6,102 holds — removes 412 holds, but 3 real errors would have gone out, including 2 meter exchanges. The replay says not recommended. Helen kept 3.0× on 1 Oct for the same reason.
“A rule nobody can test is a rule nobody can trust.” — Helen Marsh
The same held bill, seen by the five people who own it — what their bill run looked like, and what it looks like now.
Six agents find each hold's cause, prove it from reads, field orders and the tariff book, and draft the fix; the analyst releases.
Reads every bill the bill run holds with the hold reason, the last twelve bills, the account’s events — meter exchanges, estimates, rate changes, moves — and the premise, names the most likely cause and passes the bill to the agents that can prove or disprove it.
Pulls register reads and 15-minute intervals for every meter on the premise in the period and checks that they join: the start read equals the last read or the install read, and the interval sum equals the register difference.
Finds every field order on the premise in the last 90 days, reads its result, reads and photos, and says whether the result reached billing. When the evidence cannot be found, it drafts a field check with the question to answer.
Checks the rate code against the premise class, permits and change-of-use records, and recomputes every bill line from the tariff book in force for each day of the period, including rate changes inside the period.
Writes the corrected bill, the diff against the held bill, the sources behind every changed line and a confidence score, and checks the estimate and back-billing limits.
Groups drafted corrections by cause and confidence for batch release and, across the last eight bill runs, finds causes that are rising, the date they started and what changed then, and drafts the upstream fix for its owner.
Releases each correction. The agents propose; a named person decides.
Ask about a held bill, a batch, a cause or a rule — every answer cites its source. Releasing a bill stays with you; rule changes go to Helen Marsh.
Why was Ruth Calloway’s bill held?
Her October bill came to $1,125.77, 4.6× her usual $244.59. Her meter was exchanged on 22 Sep: the new meter was a reconditioned unit with its register at 04,580, but that install read never reached billing, so billing started it at 0 and charged 5,011 kWh instead of 431. The interval reads add up to 431.2 kWh. Corrected on R-1, the bill is $228.85.
Which corrections can I release in one batch today?
1,128 of the 1,842 drafted corrections are at confidence 95 or more. The biggest batch is meter exchanges with the install read not posted: 318 bills, every one restored from its field order. Over 100 bills, so Tomás Ferreira approves it after opening a sample of five.
What is causing most of this month’s holds?
By count, high usage that turns out to be real (612). The one that is new is install reads not posted: 386 holds in October against 52 in August, since field app release 6.2 on 14 Aug. It is 17.7% of all holds and it is fixable upstream — Kwame Asante owns it.
Can 7 Larch Close go out on another estimate?
No. August and September were estimated; rule 7.3 allows no more than three in a row and holds the third for an analyst. An actual read came back on 12 Oct — 28,904 — so the correction bills 854 kWh on the actual read and the estimates are trued up.
13 screens from the working solution, on its sample data. Pick one to see it large.
The release line, who approves what and the limits every correction is checked against are settings. Changes are saved as a draft and approved by revenue assurance.
| Setting | Default | Choose from |
|---|---|---|
| Batch release line | 95 | the lowest confidence a correction may have to be released in a batch |
| Analyst may release alone | 100 bills | batches up to this many bills; larger batches go to the supervisor |
| Supervisor approves | Tomás Ferreira | batches over 100 bills · any rate-code change |
| Sample shown to the approver | 5 diffs | diffs opened before a batch is approved |
| Consecutive estimates | 3 | rule 7.3 · hold before a fourth |
| Back-billing limit | 12 months | rule 9.1 · customer not at fault |
| Back-bill needing the supervisor | $250 | and the same number of months offered to pay |
| Hold age alert | 2 working days | working days a bill may stay held · field checks run on a 5-working-day target, and a bill re-runs when its field result comes back |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample bill run · “target” = the design goal, measured in the pilot · “estimated” = our estimate: $410K = 2,184 holds × $188 average held bill; the split of a held bill’s days is an estimate against a 6.2-day baseline · “typical” = published figures (CPUC complaint data: high bills 48% of billing complaint contacts). Regulatory context: Missouri 4 CSR 240-13.020 (three consecutive estimates); Ofgem 12-month back-billing ban (2018). Lumina Utilities is a fictional demo utility; the people, accounts, addresses, meters and orders named on this page are characters and sample data in the working solution.
It is the work of clearing the bills a bill run holds — high, low, zero or estimated usage, reads that do not join, rate-code mismatches — before they go to the customer. Billing Exception Management does it with six agents that find each hold’s cause, prove it from the reads, field orders and tariff book, and draft the corrected bill. The billing analyst releases it.
The hold classifier names the likely cause of each held bill. The read reconciler, field order matcher and tariff checker prove or disprove it, and the correction drafter writes the corrected bill as a line-by-line diff with its sources and a confidence score. The analyst sees the account’s last twelve bills with the held one in red, reads the diff and releases it.
No. The agents propose and draft; they never release a bill, edit a read, send a crew without the analyst or apply a rate outside the tariff book. The analyst releases each correction, and batches over 100 bills, back-bills over $250 and any rate-code change need the billing supervisor.
Corrections with the same cause are grouped, and those at or above the release line — confidence 95 in the sample utility — can go out together. The supervisor opens a sample of five diffs and signs the batch once. In the working solution, 318 meter-exchange corrections went out this way; the 23 below the line stayed with an analyst.
Every correction is checked against the limits set in its settings. In the sample utility that means no more than three consecutive estimates, no back-bill beyond 12 months where the customer is not at fault, the supervisor for any back-bill over $250 with the same number of months offered to pay, and no release below the usual range without an actual read or a field check.
Yes. The sample utility bills both, and the agents read water meter data alongside electricity. A water bill held for high usage with continuous flow on the hourly reads is not corrected: the read is right, so the analyst releases it as billed with a leak notice and the leak adjustment form.
That is the point of the recurring causes view. The pattern finder groups holds across the last eight bill runs, finds the cause that is rising and the date it started — in the sample, a field app release that stopped install reads reaching billing — and drafts the upstream fix for its owner. Hold rules can be replayed on past runs to see which holds a change would remove and which real errors it would let through.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your hold reasons, tariff book, billing rules and a sample of held bills from past runs — and it goes live once every quality gate has passed. We will walk you through it on your own held bills first.
Usage, tariff, weather or leak: the real reason, in plain words.
1-min demoRevenue Assurance AnalyticsRecover the 2-4% that leaks between meter and bill.
1-min demoBilling Dispute ResolutionEvery dispute decided on its evidence, inside the clock, with the letter already cited.
1-min demoWe’ll run Billing Exception Management on a sample of your own held bills from a recent bill run.