Commercial and industrial utility bill audit that checks demand charges and multipliers before the bill goes out
Demand charges and multipliers checked before the bill goes out.
See one case, screen by screen ↓A large business bill is not a meter read times a price. It is a 15-minute peak demand scaled by a CT/PT multiplier, compared with a ratchet from the last eleven months and a contract minimum; a power factor taken from reactive energy and turned into an adjustment; and energy split into the time-of-use windows written in a special supply agreement. When one input is wrong — a multiplier changed mid-cycle, a contract amendment not loaded, an estimated interval used as the peak — every number on the bill is still consistent with every other, so the billing system's validation passes it.
The error then repeats. A wrong multiplier is on every bill until someone notices; a wrong peak sets the ratchet floor for the next eleven months. Inside the utility, a key-account team checks a sample of the biggest bills in spreadsheets next to an interval export, and the bill it did not sample is the one the customer's energy manager finds. Then it is a refund, a cancelled and reissued bill, and a difficult call with the accounts that carry the most revenue.
Estimated split for one demand-billed key-account bill, in hours, checked by hand in a spreadsheet and with the solution (where a person reviews what the agents rebuilt).
Six agents rebuild every key-account bill from its 15-minute data, contract and meter records; the billing specialist stops or releases it.
Lumina Utilities builds its September key-account run, KA-2609, on the night of 10 October: 1,860 demand-billed draft bills, with the release window closing Tue 13 Oct at 18:00. One of them is Saltmarsh Cold Stores LLC, an 11 kV cold store at Kestrel Logistics Park that added a blast-freezer line in September. Here is what happens to its bill, screen by screen, in the working solution.
The run is built at 22:00 on the 10th and every draft is checked against its own 15-minute data, contract and meter records. By morning the release run shows each bill as a dot by money at stake: 1,812 passed every check (AED 401.6M), 39 are for review with an explained variance inside the stop rule, and 9 are stopped with AED 193,795 of errors — from a PT ratio keyed wrongly to a winter on-peak window used for a summer month.
Stop rule: more than AED 1,000 or 0.5% of the bill
Nadia opens KA-40217. On the left is the September bill as Saltmarsh will see it, line by line, marked DRAFT · NOT RELEASED: AED 531,919.53. In the middle are the month's intervals, with the billed demand of 2,480 kW drawn as a dashed line across them. The true interval peak is 2,140 kW on 29 Sep at 14:45. The gap is 340 kW, AED 13,940.00 on the demand charge.
“Recommended: stop · AED 14,783 over · Nadia decides. A stopped bill is held until its correction is released.”
Nadia runs the checks again to watch them. The draft bill reader finds 7 lines and billing demand taken from the maximum-demand register. The contract and tariff reader reads SSA-2019-0412 and its second amendment: 7 billing terms, each cited. The meter configuration checker finds field order FO-88213. The interval recalculator rebuilds demand from 2,880 intervals, none estimated. Each step takes between 1.4 and 2.1 seconds.
“FO-88213: CTs 200/5 → 300/5 on 22 Sep 10:40 · multiplier 4,800 → 7,200 · billing applied 7,200 to the whole month’s register”
Tariq Salem's crew replaced the CTs on 22 Sep for the new blast-freezer feeder; with the 11,000/110 PTs, the multiplier went from 4,800 to 7,200. The register's highest value was set on 16 Sep at 14:15, under the old CTs — 1,653 kW at ×4,800. Billing read the register once at month end and applied ×7,200 to it: 2,480 kW. The account's history shows twelve months billed at their interval peak; September is the first above it.
“CTs replaced 200/5 → 300/5 · FO-88213 · Tariq Salem · multiplier 4,800 → 7,200 · for the new blast-freezer feeder”
The special supply agreement opens with each billing term highlighted and cited in the margin: peak as the highest of the month's fifteen-minute intervals (5.1), a contract demand of 1,500 kW (5.2), a 75% ratchet over 11 months (5.4), on-peak 12:00–18:00 from May to October (6.2), the power-factor adjustment below 0.90 (7.1) and a written note for any correction (9.1). Clause 8.3 is marked “Not followed on the September draft”.
Clause 8.3: “the billing determinants shall be computed separately for each part of the period, using the ratio in force for that part.”
Capacitor bank 2 was out from 9 to 15 Sep, and the month averages a power factor of 0.89 from 1,102,670 kWh and 564,890 kVArh, so clause 7.1 adds 1%. But the 1% was taken on a demand charge built from 2,480 kW: on the true demand it is AED 4,154.33, not AED 4,293.73. Time-of-use energy agrees with the intervals inside 0.01%, split at the CT change as clause 8.3 asks — no change.
“The 1% adjustment is right; what it is 1% of is not.”
The reason is drafted from the evidence: billing demand 2,480 kW is the 16 Sep register peak scaled with the post-change multiplier 7,200 (FO-88213); the interval peak is 2,140 kW on 29 Sep 14:45; clause 8.3 was not applied. Nadia signs the stop with her Lumina account. Releasing the bill as drafted would have needed a written reason too.
“I, Nadia Kareem, stop this bill. Signed with my Lumina account.”
The bill is held, and the customer sees nothing until the corrected bill goes out. The variance explainer shows why stopping it matters beyond September: under clause 5.4, a 2,480 kW peak would hold a ratchet floor of 1,860 kW until Aug 2027. The true floor is 1,605 kW. On the winter load forecast that is 1,105 kW-months over-billed from November to April.
“1,105 kW-months over-billed, Nov–Apr · AED 45,305”
The correction and note writer has drafted the corrected bill beside the draft, line by line: demand 2,480 → 2,140 kW (−AED 13,940.00), power-factor adjustment −AED 139.40, VAT −AED 703.97. Total due AED 517,136.16, AED 14,783.37 less. The next 11 bills are listed with the wrong and the true ratchet floor. Nadia signs and releases it in place of the draft.
“Corrected bill released · Nadia Kareem · 09:47”
The note goes to Omar to approve and send to Daniel Okoro, Saltmarsh's energy manager, with the finance controller copied. It says what was found, in plain words: the larger current transformers for the blast-freezer line, the 16 September peak scaled with the new ratio, the 2,140 kW peak in the 15-minute readings. The bill and the interval readings are attached. No agent sends anything to a customer.
“Your September bill is AED 517,136.16, AED 14,783.37 less than it would have been, and the correct peak will be used for your demand floor over the next eleven months.”
The same bill, seen by the four people who own it — what their month looked like, and what it looks like now.
Six agents rebuild every key-account bill from its 15-minute data, contract and meter records; the billing specialist stops or releases it.
Reads every draft key-account bill and its billing determinants — account, tariff, bill period, each line with its quantity and rate, register reads, multipliers and billing demand — from the billing system the night the run is built, recording where each number came from.
Turns each special supply agreement, its amendments and the tariff sheet into billing rules — contract demand, ratchet, power-factor terms, time-of-use windows by season, metering-change rules and credits — each cited to its clause.
Compares CT and PT ratios, multipliers and change dates in field orders and installation records with the billing system's meter record and with what the draft used, for each part of the bill period.
Rebuilds peak demand, the ratchet floor from the last 11 months, the contract minimum, average power factor from kWh and kVArh, and energy in each time-of-use window from the 15-minute intervals, each scaled with its own multiplier; projects the ratchet floor for the next 11 months on the load forecast.
Explains every difference between the draft and the recalculation in one sentence a key account manager can repeat — the cause, the evidence, the money and its direction — and recommends stop, review or pass.
Drafts the corrected bill lines from the recalculation and a short note to the customer's named contact in Lumina's voice: what was found, the corrected amount and what changes next.
Stops or releases each bill. The agents propose; a named person decides.
Ask about any bill in the run, a contract term or a meter — or say what to change. Answers point to the interval, clause or field order behind them.
Why is the Saltmarsh demand 340 kW too high?
An old reading was scaled with a new multiplier. The CTs were changed from 200/5 to 300/5 on 22 Sep, so the multiplier went from 4,800 to 7,200. The maximum-demand register kept its 16 Sep peak, set under the old CTs; billing multiplied it by 7,200 = 2,480 kW. Clause 8.3 asks for each part of the month to use its own ratio. The 15-minute data peaks at 2,140 kW on 29 Sep 14:45.
Which other accounts had a CT or PT change this cycle?
Four meters now differ from their field records: KA-40217 Saltmarsh Cold Stores — CTs 22 Sep, bill stopped; KA-29315 Brightwater Data Hall 2 — PT ratio keyed as 11,000/120, bill stopped (AED 61,340 under-billed); KA-51107 Northgate Sports Arena — CT 400/5 on site, 300/5 in billing, next run; KA-33450 Verdant Bottling — new meter not yet linked, next run.
What would the wrong peak have cost them over the next 11 months?
Clause 5.4 sets a floor of 75% of the highest billing demand in the last 11 months. At 2,480 kW the floor is 1,860 kW; at the true 2,140 kW it is 1,605 kW. On the winter forecast that is 1,105 kW-months, AED 45,305 (AED 47,570.25 with VAT) over Nov–Apr, on top of the AED 14,783.37 on September.
Add a check: stop any bill whose register peak falls before a meter change
Done. New check: “If a CT, PT or meter changes during the period, rebuild demand from the intervals for each part and stop the bill if the register-based demand differs.” It runs from the next run; on the last 6 runs it would have caught the same 5 bills the multiplier check did, and 1 more in June (KA-37702, AED 3,410). It is now in Settings.
13 screens from the working solution, on its sample data. Pick one to see it large.
When a bill is stopped, what the audit checks and who decides are settings, chosen by the billing team. A change applies from the next run; the run in progress keeps its rule.
| Setting | Default | Choose from |
|---|---|---|
| Stop a bill when the difference is more than | AED 1,000 or 0.5% of the bill | Any amount in AED, or a percentage of the bill |
| Demand tolerance | 0.5% or 5 kW, whichever is larger | A percentage or a number of kW |
| Energy tolerance | 0.2% | A percentage of the billed energy |
| Checks | 9 on | Demand against the interval peak · ratchet, from the last 11 months · contract minimum demand · multiplier for each part of the period · power-factor adjustment and its base · time-of-use windows by season · estimated intervals at the peak · contract amendments loaded · tariff assigned to the supply voltage — each on or off |
| Stop or release one bill | Key-account billing specialists | Nadia Kareem · Yusuf Rahim · Mei Lin Tan |
| Release the run | Billing operations manager | Priya Menon — signs the release; also changes the stop rule |
| Approve and send a customer note | Key account manager of the account | 14 key account managers, including Omar Farouk |
| Clock | Built 22:00 on the 10th · window closes 18:00 on the 13th | Checks finish by 06:00 on the 11th; a bill still stopped at the close stays held and is reported to Priya Menon |
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 data · “target” = the design goal, measured in the live solution · “estimated” = our estimate: AED 2.4M = 22,320 key-account bills a year (1,860 × 12) × 0.5% with a material error × AED 21,100 average error, the 0.5% to be replaced by the pilot's own rate; the hours split is also our estimate · “typical” = published figures (vermontbiz.com on Burlington Electric Department's billing errors, 2014 — $357,794 over-billed to the University of Vermont, including a CT multiplier error; PG&E Electric Rule 17.1 — an incorrect meter multiplier is a billing error and over-charges are refunded for 3 years). Lumina Utilities and the people, customers, sites, accounts and records named on this page are fictional — characters and sample data in the working solution.
Software that checks a utility's commercial and industrial bills before they are released. C&I Bill Audit puts every demand-billed draft bill beside its own 15-minute data, special contract and meter records; six agents rebuild demand, ratchet, power factor and time-of-use energy and explain every difference. A key-account billing specialist stops or releases each bill.
The monthly key-account run is built at 22:00 on the 10th and every draft is checked overnight, not a sample. Bills inside the tolerances pass; bills with an explained variance inside the stop rule go for review; bills above the stop rule — AED 1,000 or 0.5% of the bill in the demo — are recommended for a stop, with the corrected bill drafted. People decide each one before the release window closes.
The meter configuration checker compares the CT and PT ratios in field orders and installation records with the billing system's meter record, for each part of the bill period. The interval recalculator scales every 15-minute interval with the multiplier in force at that moment. In the sample case, an old register peak scaled with the new multiplier after a CT change showed up as 340 kW of billed demand above the true interval peak.
Yes. It rebuilds the ratchet floor from the last 11 months and the contract minimum, the average power factor from kWh and kVArh and the adjustment on its correct base, and the energy in each time-of-use window by season. It also projects what a wrong peak would do to the ratchet over the next 11 bills.
It is held and the customer sees nothing. The specialist signs the stop with the reason on the record, reviews the corrected bill drafted beside the original, and signs and releases it in place of the draft. A note explaining the correction goes to the key account manager to approve and send.
Yes. The agents have read-only access to the billing, interval, contract and meter systems; they recommend and draft but never release a bill or send to a customer. Specialists stop or release bills, the billing operations manager signs the release of the run, and key account managers send customer notes.
Yes. The stop rule, the demand and energy tolerances, each of the nine checks, who may stop or release a bill, who releases the run, who sends customer notes, who fixes meter records and the run's clock are all settings. A change applies from the next run.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your tariffs, a sample of special contracts, interval data and past bills — and it goes live once every quality gate has passed. We will walk you through it on your own demand-billed accounts first.
Held bills cleared in two days, not six, with the cause and the fix attached.
1-min demoHigh Bill InvestigationUsage, 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 demoWe'll run C&I Bill Audit on a sample of your own demand-billed accounts and their interval data.