Key takeaways

  • Between every two utility billing periods there should be zero days unaccounted for and zero days counted twice. In practice, this almost never happens.
  • Gaps between billing periods inflate consumption estimates; overlaps deflate them. Both are counted as bad days — and one problem meter holds the entire asset to its worst score.
  • The failure is invisible without a system: catching a 1-day overlap requires date-level inspection of every billing record, for every meter, for every asset.
  • The fix is administrative, not technical — a billing date correction with the utility provider, usually returned in 2–4 weeks. Finding it is the hard part.

Between every two utility billing periods, there should be zero days unaccounted for and zero days counted twice. In practice, this almost never happens. Gaps between billing periods inflate consumption estimates. Overlaps deflate them. Both are counted as "bad days" by EDRA — and one problem meter holds the entire asset to its worst score. The financial consequence is real: distorted consumption data leads to incorrect benchmarking, failed certifications, and misinformed capital allocation decisions.

One meter, 12 months of billing — with 15 bad days 15 days
gap + overlap
15 bad days out of 365 drag the whole asset's continuity score below threshold

Why temporal continuity is so hard to see

The source of most temporal continuity failures is surprisingly mundane: utility providers sending incorrect billing dates. A billing period that ends on March 30 and the next starting on April 2 creates a 2-day gap. Over 12 months of monthly billing across 50 meters, these micro-gaps accumulate into material data quality issues. A single meter with 15 bad days can drag an entire asset's continuity score below threshold — even if the other 49 meters are perfect.

What makes temporal continuity particularly dangerous is its invisibility. Coverage gaps are obvious — you either have data or you don't. Completeness gaps are detectable — missing months show up in any review. But a 1-day overlap between billing periods? That requires date-level inspection of every billing record for every meter for every asset. No human reviewer catches these systematically. Most organizations don't even know to look.

0
Days that should be unaccounted for between billing periods
0
Days that should be counted twice between billing periods
15
Bad days on one meter — enough to fail the whole asset

The fix is administrative, not technical

The fix is straightforward but invisible without a system like EDRA to detect it. Once bad days are identified — with the specific meter, billing period, and date range flagged — the resolution is a billing date correction with the utility provider. Most providers will issue corrected statements within 2–4 weeks. The work is administrative, not technical. But finding the problem requires automated, date-level scanning across every meter in the portfolio.

How a continuity failure gets resolved
01
Detect gap or overlap
Date-level scan flags days unaccounted for or counted twice.
02
Reconcile billing periods
Pin the exact meter, period, and date range at fault.
03
Correct & normalize
Provider reissues corrected billing dates; records are normalized.
04
Continuous series
No gaps, no overlaps — the continuity score clears threshold.
EDRA's B3 component runs exactly this scan — every billing record checked against its neighbours, every gap and overlap flagged with a specific meter ID, billing period, and date range.

The portfolio manager doesn't get a vague "continuity issues detected" — they get "Meter EM-0047 at Asset 12 has a 3-day overlap between the February and March billing periods." That level of specificity is what turns a systemic data quality problem into a 4-week fix.

Case Study

A 30-asset portfolio had 14 assets with billing period overlaps averaging 12 bad days each. The overlaps were concentrated in electricity meters from a single regional utility provider. Correcting billing dates with the provider eliminated all continuity failures in 4 weeks — no new meters, no new systems, just corrected records.

Download Case Study (PDF)

Frequently asked questions

What is temporal continuity in utility data?

Temporal continuity is the requirement that, between every two consecutive utility billing periods, there are zero days unaccounted for and zero days counted twice. A clean series moves from one billing period to the next with no break and no overlap. When a period ends on March 30 and the next begins April 2, those two missing days are a continuity failure — and EDRA counts them as bad days.

How do billing period gaps corrupt ESG data?

Gaps between billing periods inflate consumption estimates, while overlaps deflate them — both distort the underlying figure. Over 12 months of monthly billing across 50 meters, micro-gaps of a day or two accumulate into material data quality issues. Distorted consumption leads to incorrect benchmarking, failed certifications, and misinformed capital allocation decisions.

What is a billing overlap?

A billing overlap is when two consecutive billing periods both claim the same calendar days — for example a 3-day overlap between the February and March statements for one meter. The overlapping days are counted twice, deflating measured consumption. Overlaps require date-level inspection of every billing record to detect, which is why no human reviewer catches them systematically.

How are temporal continuity failures fixed?

The fix is administrative, not technical. Once bad days are flagged with the specific meter, billing period, and date range, the resolution is a billing date correction with the utility provider. Most providers issue corrected statements within 2–4 weeks. The hard part is finding the problem — that requires automated, date-level scanning across every meter in the portfolio, which is what EDRA's B3 component does.