Temporal Continuity: The Billing Gap That Costs Millions

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.

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.

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.

EDRA's B3 component runs exactly this scan. Every billing record is checked against its neighbors. Gaps and overlaps are flagged with specific reason codes, meter IDs, and date ranges. 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.