Billing Cycle vs Last 30 Days: Why the Numbers Are Different

Why two correct reports can show different totals

“Current billing cycle” and “last 30 days” sound similar, but they answer different questions.

• Billing cycle: usage between the provider's opening and closing boundaries for one meter.
• Last 30 days: usage observed during a rolling window counted backward from today.

They match only when the dates and boundary readings happen to match. Usually they do not.

A concrete example

Assume the current date is September 24.

• The meter's billing cycle began September 8.
• The “last 30 days” report begins August 26.
• Current-cycle usage is therefore based on about 16 days.
• The rolling report includes part of the previous cycle and the current cycle.

If MeterPilot shows 77 units for the current cycle and 108 units for the last 30 days, neither number is automatically wrong. The labels describe different windows.

What a selected report period should mean

A clear report needs four pieces of context:

1. Exact start and end dates.
2. Whether boundary readings were observed or estimated.
3. Which properties and meters were included.
4. Whether the number represents total usage, daily pace, or contribution.

Without these, a precise-looking number can still be misleading.

Meter contribution is not another bill total

Contribution answers: How much of this selected report's usage came from each meter?

If a 30-day report contains 100 total units and Meter A contributed 77, its contribution is 77 units or 77%. That does not mean Meter A's current billing cycle is also 77 units. It may be a coincidence if the report window and cycle overlap differently.

Good report design puts the selected period beside the contribution figure so users do not need to remember which filter they chose.

Why sparse readings complicate rolling reports

A cumulative meter only tells you the total at observation points. If there is no reading exactly at the start of a 30-day window, software has three honest choices:

• Start from the first available reading inside the window.
• Use a known official boundary reading.
• Estimate a boundary and clearly label it as estimated.

It should not manufacture an exact-looking observation. More frequent readings improve time-window reports because the boundary gaps become smaller.

Comparing periods fairly

Totals are appropriate when periods have the same duration and meaning. Otherwise compare pace:

Daily pace = units ÷ elapsed days

Example:

Period	Units	Days	Daily pace
Current partial cycle	60	15	4.0/day
Previous complete cycle	120	30	4.0/day

The partial total is half as large, but the pace is unchanged. Saying usage “fell by 50%” would be confusing and wrong in practical terms.

Season and occupancy matter too. Comparing a hot 30-day period with a mild one can accurately show change without explaining its cause.

Which view should you use?

Use current cycle when deciding how you are progressing toward the next provider bill or a cycle-specific threshold.

Use last 7, 30, or 90 days when investigating recent behaviour across cycle boundaries or comparing the same rolling measure over time.

Use official closed cycles for bill reconciliation and long-term like-for-like history.

How MeterPilot keeps the distinction visible

MeterPilot stores billing cycles per meter rather than assuming every property starts on day one of the month. Reports use an explicit selected range, while meter details preserve the actual cycle. Property selection controls which meters contribute without changing their underlying history.

When numbers differ, begin with the labels and dates. Most apparent contradictions disappear once you compare the same meter, same boundaries, same unit, and same calculation method.