Meter readings

How to Calculate Electricity Units Between Two Meter Readings

Understand the simple current-minus-previous calculation, meter multipliers, rollovers, replacements, and why dates matter.

Published · 7 minute read

The core calculation

For a normal cumulative electricity meter:

Units used = current reading − previous reading

One electricity “unit” usually means one kilowatt-hour (kWh). A cumulative register never resets each month under ordinary operation; it keeps increasing, while the bill calculates the difference for a defined interval.

Simple example

Observation Reading
Previous reading 12,640 kWh
Current reading 12,718 kWh
Difference 78 kWh

The meter used 78 units between those two observations.

That answer is meaningful only when the readings belong to the same meter and register. Write down both dates as well as both values.

Why the dates change the interpretation

Imagine two intervals that both used 78 units:

  • 78 units over 30 days is about 2.6 units per day.
  • 78 units over 10 days is about 7.8 units per day.

The total is identical, but the pace is nearly three times higher in the second interval. This is why a report should never present a number without its date range.

For a fair pace comparison:

Average units per day = interval units ÷ number of elapsed days

You do not need this average to maintain the meter ledger; it is simply useful for comparing periods of different lengths.

Meter multipliers

Some commercial or industrial installations use a current-transformer or provider-defined multiplier. In that situation:

Billable units = (current register − previous register) × multiplier

Example: a register difference of 42 with a documented multiplier of 20 produces 840 units. Never invent a multiplier from the size of the bill. Use the meter documentation or official bill and keep the multiplier attached to that meter's history.

What if the current reading is lower?

Do not automatically turn a negative result into zero. Check for:

  1. A transposed or missing digit.
  2. A reading from another meter or register.
  3. A decimal-point mismatch.
  4. A newly installed replacement meter.
  5. A mechanical rollover after the highest display value.

A replacement meter creates a boundary between two registers. Preserve the final old-meter reading, replacement date, new meter's opening reading, and any provider documentation. Treating the new meter as if it were the old one destroys the audit trail.

Reading intervals that cross a bill date

If your own readings were taken on June 10 and June 20, while the official bill closed on June 15, the full ten-day difference is not the official cycle consumption. You lack a physical observation exactly at the boundary.

You may use the provider's official closing reading for the billing cycle, or label any time-based split as an estimate. Do not present an interpolated number as an observed reading.

Consumption is not the payable amount

Multiplying units by one advertised rate rarely reproduces a complete electricity bill. Tariff slabs, fixed charges, taxes, adjustments, subsidies, minimum charges, time-of-use registers, and provider rules may all affect the amount.

MeterPilot therefore separates three ideas:

  • Cumulative reading: what the register displayed.
  • Cycle consumption: the validated difference for the cycle.
  • Official bill: the provider's issued amount and bill details.

Keeping these separate makes discrepancies visible instead of hiding them inside a homemade total.

A low-error workflow

  1. Select the correct property and meter.
  2. Confirm the displayed unit and register.
  3. Enter the current cumulative reading and actual observation time.
  4. Review the calculated difference.
  5. Investigate warnings before saving.
  6. When the official bill arrives, record its official dates and readings against the same meter.

Common calculation mistakes

  • Subtracting the current value from the previous value.
  • Entering interval consumption as the next cumulative reading.
  • Comparing a 30-day total with a 17-day total as if the periods were equal.
  • Mixing readings from different tariff registers.
  • Applying a multiplier twice.
  • Rounding every reading, allowing small errors to accumulate.
  • Assuming the app's date range exactly matches the provider's billing cycle.

The arithmetic is easy. Preserving identity, dates, precision, and provenance is the real work.

MeterPilot reading history showing cumulative values and interval changes
The ledger keeps cumulative readings and their calculated changes visibly separate.
Make the next reading useful

Turn one observation into a trustworthy history.

MeterPilot keeps the previous value, timestamp and meter identity together so the next comparison has a reliable starting point.

See the MeterPilot workflow