Electricity bill with fixed charge and tax

Why only one line of the bill responds to switching things off

The engine assembles the bill the way a utility does. Units consumed multiply the tariff to form the energy charge — the only part of the bill the meter controls. The fixed service charge is then added whole: it is the price of being connected, levied identically in a month of heavy use and a month away. The tax percentage applies to that subtotal, so it scales both of the other parts at once. Three inputs, three different behaviours, one total.

The decomposition is what makes the tariff an honest number. The rate printed on the bill is a MARGINAL price — what one more kilowatt-hour costs — but dividing the bill total by the units consumed yields a higher figure, because the fixed charge and the tax are smeared across every unit. The gap between those two prices matters in opposite directions: decisions about using less should be priced at the marginal rate, while the felt cost of electricity — the number a household experiences — is the average one.

The fixed charge is also why small consumers pay the most per unit. A frugal household spreads the same standing charge over few units, so its effective rate can sit far above the printed tariff, and conservation savings flatten out: the energy charge can be driven toward zero, the connection charge cannot. Comparing two suppliers on tariff alone misses this entirely — a lower rate with a higher standing charge can cost more at low usage and less at high usage, with the crossover depending on consumption.

The pack also declares the reverse workflow, and it answers the budgeting question the forward one cannot: fix a bill amount you are prepared to pay and let the engine solve for the units that produce it. Because the fixed charge and tax are carried in the relation, the answer is the genuine consumption allowance under a budget — not the naive division of budget by tariff, which overstates it by ignoring the two parts that are owed regardless.

When this calculation is used

• Checking a received bill against your own meter readings, with the fixed charge and tax rate copied from the bill itself.
• Forecasting next month before it happens: projected units in, expected total out, before the utility does the same arithmetic.
• Solving backwards — the declared reverse workflow — from a monthly budget to the units it actually buys once the fixed charge and levy have taken their share.
• Comparing supplier offers whose tariff and standing charge differ in opposite directions, at your own consumption rather than the advertised example.

Worked example

Reconstruct the pack’s own anchor bill: a household that consumed 300 units in the period, on a tariff of 0.20 per kilowatt-hour, with a fixed service charge of 10 and an 8 percent levy applied to the subtotal.

The engine returns the bill amount and, separately, the bare energy charge. Read the gap between them first: that gap is the part of the bill no amount of switching off will ever touch, and its share of the total is the honest measure of how much of this bill is usage and how much is connection.

Now run the declared reverse: hold the tariff, fixed charge and levy, set the bill amount to what you intend to pay, and let the engine find the units that fit under it. The difference between that allowance and last period’s consumption is the size of the behaviour change the budget is actually asking for.

What each input represents

Assumptions and limits

• One flat tariff prices every unit: tiered slabs, time-of-use windows and seasonal rates are outside this relation and need a blended rate to approximate.
• The percentage applies to the whole subtotal, fixed charge included. Jurisdictions that exempt the standing charge or tax it differently will diverge from this structure.
• The model is currency-agnostic — tariff, fixed charge and bill share whatever unit of money you enter, and consistency between them is your responsibility.
• Only three components are modelled. Arrears, meter rent, fuel-price adjustments and other line items some utilities add must be handled outside the relation.

What the guards protect against

• A tax percentage above 100 is refused — the pack ships that refusal as a declared test vector — because a levy that more than doubles the bill is far more likely a fraction entered as a percentage, or two figures transposed, than a real tariff structure.
• Units consumed must exceed zero and are capped at a bound no household meter approaches, which catches an annual total entered where a billing period belongs before it inflates the bill by an order of magnitude.
• The tariff is capped far above any retail price, so the classic slip of entering cents where the unit is currency per kilowatt-hour — a hundredfold error — is refused instead of silently producing an absurd bill.

Provenance

Residential billing relation, bill = (units × tariff + fixed charge) × (1 + tax rate)

The energy charge is formed as units times tariff, the fixed service charge is added, and the declared percentage is applied to the subtotal to produce the bill amount; the declared reverse workflow solves the same relation for the units that produce a target bill.

Screening and reference material, to be checked against the governing standard and a qualified engineer; not a design determination. The signed pack carries its own citation, and the page reports the verification state of the release it mounted.