MeterPilotMeter Reading Date, Bill Issue Date and Due Date: Why They Are Not the Same
Understand the three dates that commonly appear around a utility bill and use the read date—not the due date—to compare consumption.
The short answer
The meter reading date closes the measured usage interval. The bill issue date is when the provider creates or publishes the statement. The due date is the payment deadline. They can be days or weeks apart and should not be used interchangeably.
To compare meter usage, use the previous and current reading dates and values. To manage payment, use the due date. To track when the provider communicated the bill, use the issue date.
A realistic timeline
| Event | Date | Meaning |
|---|---|---|
| Previous official read | August 12 | Opening boundary |
| Current official read | September 10 | Closing boundary |
| Bill issued | September 14 | Statement generated |
| Payment due | September 27 | Payment deadline |
The measured cycle is August 12–September 10. It is not “September usage,” September 1–30, or the 13 days between issue and due dates.
Why comparisons go wrong
Comparing a calendar month with a billing cycle
Your personal September 1–30 readings include 20 days after the provider's closing read and exclude part of August that the bill includes.
Using the issue date as the closing reading date
This silently adds four days to the example cycle even though no official reading was taken then.
Treating the due date as a consumption boundary
Payment timing does not tell you when energy was measured.
Ignoring estimated status
An exact-looking reading date can still refer to an estimate. Preserve the source label as well as the date.
Which dates belong in your record
For the meter and cycle:
- Previous reading date and cumulative value.
- Current reading date and cumulative value.
- Actual, customer, remote or estimated source.
For the bill:
- Issue date.
- Due date.
- Provider units, amount and adjustments.
This structure lets you answer two different questions: “How much was measured in the cycle?” and “When must this statement be paid?”
If your nearest physical reading is on a different day
Keep it with its real timestamp. A photo taken September 12 can support a reasonableness check around the September 10 official read, but it is not the same observation. Do not backdate or interpolate it silently.
How MeterPilot treats the boundary
When adding an official bill, use the official read date for cycle closure and preserve billed units and amount separately. Reports for “last 30 days” should continue to show their calendar range rather than pretending it matches the bill. Clear labels prevent a correct number from answering the wrong question.
Reserved for a fictional completed bill whose read, issue and due dates are all visible. No unrelated screenshot has been substituted.
Keep provider facts beside the meter that produced them.
Record the official read date, closing value, billed units and amount as distinct facts, then review the cycle boundary.
See the MeterPilot workflow