Key Findings

  • If the reading behind a bill came from someone else's cloud, your chain of custody starts on their server, not your meter
  • A vendor outage is an unbillable gap: no local record means the interval data for that window cannot be reconstructed
  • API pricing, rate limits and authentication are the vendor's to change, on the vendor's timetable
  • A tenant disputing an estimated charge is on strong ground, because an estimate is not a measurement

The Seductive Promise of "Easy" Billing

Software-as-a-Service (SaaS) billing platforms make an attractive pitch: "We handle everything. Just connect to your meters and start billing."

What they don't tell you is that "connecting to your meters" often means relying on a fragile chain of third-party APIs that you don't control, can't audit, and have zero legal recourse against when they fail.

The Chain of Custody Problem

When your billing platform reads meter data from a third-party hardware vendor's cloud API, the reading behind each bill takes a long trip before it reaches you:

1 Meter Hardware
→
2 Manufacturer Cloud Public Internet
→
3 SaaS Vendor API Translation Layer
→
4 Your Bill Final Output

If any link in that chain breaks, you cannot bill your tenant. Worse, in a legal dispute, you cannot prove the data is accurate because you do not own the source.

How This Fails In Practice

When the upstream platform goes dark

A vendor cloud takes an extended maintenance outage. Every dashboard that reads from it shows "No Data Available" until the vendor is finished, and billing software with no local fallback has nothing to fall back to.

The result: the usage for that window is gone unless something on site recorded it. You either estimate it, which is exactly the practice a tenant can dispute, or you absorb it.

When API access gets repriced

API terms are the vendor's to change. Access that launched free can acquire a per-meter monthly fee, or a rate limit, or an authentication change that requires re-integration on the vendor's timetable rather than yours.

The result: the cost lands on whoever built on top of it, and historical data is only as portable as the vendor's export allows.

The Legal Exposure You Didn't Know About

California Weights & Measures law requires that utility billing be based on "direct measurement" using certified equipment. When a tenant disputes a bill, you must be able to produce:

  1. Proof that the meter is certified (ANSI C12.20 or equivalent)
  2. A complete, unbroken record of interval data
  3. Evidence that no third party could have modified the readings

If your data passed through two cloud platforms before reaching your billing system, can you really certify that chain of custody? In court, the answer is increasingly "no."

The "Direct-Read" Standard

Blueline Electric builds every system on direct Modbus/BACnet connections. The billing computer talks to the meter over a hard wire, with no vendor cloud in between.

  • No cloud dependencies
  • No data loss during internet outages
  • Complete chain-of-custody for legal defense
  • No third-party pricing surprises

Questions to Ask Your Current Provider

Before signing (or renewing) with any billing platform, demand answers to these questions:

  1. Where does the meter data originate? (If the answer involves a manufacturer's cloud, that's a red flag.)
  2. What happens to billing if the internet goes down for 48 hours? (The correct answer is "nothing changes.")
  3. Can I export all my historical data in a standard format? (If not, you're hostage.)
  4. Who owns the data—me or you? (This should be in your contract. Read it.)

Get a Free Infrastructure Audit

Not sure if your current setup is at risk? We can assess your metering infrastructure and identify API dependencies you might not know about.

Request a Risk Assessment →