One runs an estate and answers for it. The other answers for somebody else’s. The engine is the same; what changes is whose queue the bills sit in.
If you run the estate
Your estate. Your answers.
Finance wants the variance, sustainability wants the number, and the site wants to know why its bill went up. The answers stop being something you reconstruct.
12 permissions over 4 base roles, plus custom roles and per-organisation overrides, so the site manager who needs one report does not also get the contract record.
Every bill answers six questions. In the order one failure causes the next.
Is this bill even yours?
Meter point, supplier and account are matched to a site and a contract you hold. A bill for a meter you left two years ago fails here rather than quietly reconciling.
Ten symptoms never bury one fixable cause: the earliest failing check is tagged as the reason, and everything downstream of it as a consequence.
Everything it rebuilds
Commodity is the easy half.
The rest changes by region, meter, settlement period and charging year. Each of these is modelled from its own published source, for power, gas and water alike.
33 charge types modelled
Two adjustments, not charge types
↑
Line-loss factors
Gross the metered volume up for the charges levied at the grid supply point: transmission, balancing and AAHEDC.
↓
EII exemption and CCA relief
Reduce the levies, and the Climate Change Levy in turn.
A weekday, priced the way the network actually prices it
RedRed
452 kW peak · 16:00 · Red band
00:0006:0011:0014:0016:0019:0023:00
London Power Networks, weekday00:00–07:0007:00–11:0011:00–14:0014:00–16:0016:00–19:0019:00–23:0023:00–24:00
Published LPN time bands. The demand shown is an illustrative weekday shape.
Imbalance prices and gas calorific values are fetched and stored, so a bill that arrives tomorrow is checked against what the market actually published today.
When a rate settles
A bill priced from a draft figure is re-validated the day the final one lands, and the part that was held is either cleared or becomes a query.
When an invoice does not arrive
A supply that should have been billed and was not is noticed, and the chase to the supplier is drafted against the meter and the date it was expected.
On its schedule
The reports somebody asked for are built and delivered, to the people who still work there when the run happens.
None of it needs a person to start it, and none of it is a reason to employ one.
14
GB distribution networks whose DUoS schedules are loaded, band by band
33
charge types the engine dispatches on, across electricity, gas and water
122,688
half-hourly BSUoS rates loaded for the pre-April-2023 regime
6
checks on every run: identity, period, consumption, rates, arithmetic, credits
1
rounding step in the whole system: the final whole penny on each line
0
bills validated by sampling. Every bill, every line.