Electricity Monitoring System Guide for Multifamily Owners

A tenant emails a photo of her January bill and asks why it's nearly double December's. You open the consumption report, find three days of missing intervals, and realise the invoice went out anyway. Nothing is wrong with the meter. The process wrapped around it failed.

That gap is what separates an electricity monitoring system that a building can defend from a set of meters that merely produce numbers. The chain runs from current transformers through the meter, the communications path, the headless data store, the monthly reconciliation, the invoice, the dispute desk and the arrears policy. Break any link and the data stops being trustworthy at precisely the moment someone depends on it, usually a resident holding a bill they don't believe.

The sections below are the decisions I'd make in order: what to meter, who to buy from, how to commission it, how to move data into billing, which numbers prove the system is working, and how to protect residents when a reading is estimated or a payment is late. Most of the failures show up in the last two.

Table of Contents

• Match the Monitoring Level to Your Building Type
• Select and Verify a Vendor Before You Sign
  • Accuracy means field accuracy
• How to Deploy and Commission the Metering System
  • The sequence that survives an audit
• Connecting Meter Data to Billing and Operations
• KPIs That Show the System Is Working
• Protecting Residents From Billing Errors and Arrears

Match the Monitoring Level to Your Building Type

Ask three questions of every electrical load in the building before anyone quotes you hardware.

Billing. Which circuits must appear on a named resident's invoice? Allocation. Which ones get split between tenant classes or recovered as a shared cost? Diagnostics. Which ones only need to be understood when something misbehaves?

Pick the lowest monitoring level that answers all three. Everything above that line is capacity you'll maintain and nobody will open.

Take a 30-unit walk-up with a single common-area meter. Unit submeters plus that one common meter cover billing and shared-cost recovery completely. Putting floor-level interval data into the same building adds a communications design to a riser that never needed one, and buys analytics nobody on staff has time to read. Condominiums and strata run the opposite risk: unit submeters are only an option where the bylaws permit them, so where they don't, a building master meter divided by an agreed formula is the honest answer, and extra hardware doesn't change the legal position. Mixed-use buildings need separate meters for residential, commercial and shared loads, because a retail tenant billed on a demand profile shouldn't inherit corridor lighting, and residents shouldn't inherit a kitchen exhaust fan.

Larger rental towers change the economics. Buildings of 50 units or more earn their keep from 15 to 60 minute interval data by floor, the resolution at which a short-cycling rooftop unit or a drifting corridor load becomes visible. EV chargers and amenity loads each want a dedicated circuit meter at 15-minute intervals for load management and clean cost recovery. Student and affordable housing portfolios get more from a resident portal and usage alerts layered on monthly reads than from faster intervals, because a predictable bill prevents more disputes than a better chart resolves.

The utility side already operates at that granularity. Natural Resources Canada's smart grid report counted approximately 13.3 million smart meters deployed nationally, an increase of 1.2 million from 2018, and those devices record interval usage and transmit readings remotely rather than waiting for a reader to walk the route. Tenants live with that precision at the utility, so a building still reconciling quarterly estimates sits behind the standard the people paying the bills already expect.

The table is what I'd hand a property manager in week one, before any vendor gets airtime.

Building type

Recommended metering

Data interval

Main purpose

Low-rise multifamily (under 50 units)

Unit-level electricity submeters and a common-area meter

Monthly reads, optional hourly

Tenant billing and cost recovery

High-rise rental (50+ units)

Unit submeters on a shared network, plus common-area and amenity meters

15 to 60 minutes

Billing and load analysis by floor

Condominium or strata

Unit submeters where bylaws allow, with a building master meter

Monthly for units, hourly for common areas

Allocation of shared costs and reserve planning

Mixed-use (residential above retail)

Separate meters for residential, commercial and shared loads

15 minutes

Allocation between tenant classes and diagnostics

Student or affordable housing

Unit or room-level submeters with a resident portal

Monthly reads plus usage alerts

Predictable bills and fewer disputes

EV charging or amenity loads

Dedicated circuit meter on each load

15 minutes

Load management and separate cost recovery

Whatever row you land on, design the data path once. The same registers and intervals feed the dashboard, the invoice and the building management system; a project that buys those as three separate things ends up with duplicated meters and three versions of the truth. And when intervals vanish, the fault usually sits in the integration layer rather than the meter, which is the same trace-the-request discipline set out in this guide to enterprise application monitoring and debugging.

Select and Verify a Vendor Before You Sign

A portal demo can look polished while leaving a practical question unanswered: what happens when a meter stops reporting just before billing closes? Select a vendor for how it handles exceptions and disputes, not just how its dashboard looks.

Score each shortlisted vendor from 1 to 5 on the seven criteria below. If the vendor cannot provide evidence for a criterion, score it zero. Compare three vendors, and agree on what evidence will count as acceptance before signing a portfolio agreement.

Accuracy means field accuracy

Ask what accuracy the installed system can maintain in the field, not only the meter's nominal resolution. California Public Utilities Commission materials on submetering report that available third-party submetering equipment can reach approximately 1% laboratory accuracy and 2% field accuracy. That leaves roughly 2% measurement uncertainty before wiring, transformer-ratio, installation or data-processing errors are considered. Resolution describes the smallest increment a meter can display; it does not establish the accuracy of the billed reading.

Criterion

What to ask the vendor

Red flag

Evidence to request

Accuracy

What field accuracy applies, beyond laboratory accuracy?

The quote lists only meter resolution

Stated field tolerance and test report

Data access

Can interval data be exported in an open format?

Data is available only in a vendor portal

Sample interval export for one unit

Communications

How will the network reach basements and garages?

No coverage check is included

Site coverage survey before installation

Billing support

How are estimates and corrections documented?

No record of changes or audit trail

Sample invoice and correction log

Service levels

What response times apply to faults and battery replacement?

Repair times are not defined

Written service levels in the contract

Licensing and insurance

What licences and insurance cover the work?

The licence cannot be checked

Licence number and certificate of insurance

Contract terms

What are the capital cost, term and exit conditions?

Fees or buyout terms are unclear

Full fee schedule and buyout terms

Check a sample interval export for timestamps, units and a billing-period identifier. The export should be usable outside the vendor's portal; otherwise, owners may have difficulty reviewing billing history or transferring records when a contract ends.

Put communications coverage, service response times and billing corrections in the written scope. Missing readings need a documented treatment before invoices are issued, and a correction should leave a trace that residents and property staff can review. Ask the vendor to explain how an exception is identified, investigated and resolved.

A defensible scope should state who coordinates system design, supplies approved metering equipment where required, commissions the system, takes reads and supports billing. Axis Meter Solutions is licensed by the Ontario Energy Board as a unit sub-meter provider for electricity unit sub-metering services in Ontario under licence ES-2022-0268. During consultation, Axis recommends electricity metering, water metering or both for the building. Require any vendor's recommendation to match the building's needs, with its reasoning set out in writing.

Signing gate: Do not issue tenant invoices until the property manager and vendor have signed the acceptance sheet and attached the variance test.

Settle ownership of interval data at contract end, the full fee schedule and the buyout terms before signing. Contract protections count when they are written down, not when they are described in a sales call. For general questions to consider when choosing a service provider, see business IT partner advice from F1Group. Before the purchase order, check the equipment model against the Measurement Canada approved meters list.

How to Deploy and Commission the Metering System

Commissioning is where good hardware turns into defensible billing data, and it's the stage vendors compress hardest when an installation runs behind. Push back. A meter that's mounted but not verified is a liability with a serial number.

The sequence that survives an audit

1. Inventory every meter against the floor plan. List each utility meter, unit, common area and shared load, and reconcile the list to the building footprint. A missed meter becomes an unallocated cost that the owner absorbs for years. The usual slip is a spare meter or a shared-load meter nobody claimed.

2. Confirm the equipment against the design. Check model numbers, CT or PT ratios and the wiring diagram before anything is mounted, because a ratio error skews every reading that follows for the life of the installation. The slip is copying ratios from the last building because the panel looked similar.

3. Install at accessible heights and label everything. Every meter gets its number and service address on a durable label, readable without a ladder or a torch. A unit mislabelled with the wrong address is worse than no label, because the error flows straight into a resident's invoice.

4. Verify phase association and CT polarity. Reversed polarity is the most common field failure, and it produces plausible-looking data that overstates or understates consumption depending on load balance. Confirm orientation with a load test rather than trusting the arrow printed on the CT.

5. Synchronise clocks to a common time source. Then confirm interval counts, units and billing-window alignment against the specification. Devices on different time sources misalign billing windows, which shows up later as a demand peak that never happened.

6. Compare submeter totals with the parent meter. Record the comparison during a stable load and again at peak, and investigate any interval where the sum of submeters exceeds the parent. Comparing only at low load hides ratio and polarity errors that appear under real demand.

7. Set acceptance thresholds below the stated field tolerance. An escalation level set above the tolerance lets a failing meter pass acceptance, and you'll spend the next year explaining variances. Keep pre- and post-commissioning test records with the serial numbers attached.

8. Sign off before billing starts. The property manager and the vendor both countersign a sheet listing every meter, its assigned unit, its interval count and its variance result. That single page is the difference between a billing dispute you can answer in an hour and one you argue about for a quarter.

Practical rule: if a meter's variance sits inside tolerance but its label, address or assignment is wrong, the meter is still failing.

Two administrative habits save trouble later. Photograph every installed meter with its label and CT orientation, and file the images against the meter register. Then hand the property manager a one-page map of what was installed, because the person answering a resident's question in eighteen months won't be the person who stood in the electrical room.

Connecting Meter Data to Billing and Operations

Trace the path before you trust it: meter, collector or concentrator, head-end system, data store, then billing and reporting tools. Each junction has a characteristic failure. A collector stops reporting and the gap fills with a repeat of the previous day. A head-end export drops a column and the upload imports zeroes. A billing tool applies the wrong rate period because the interval timestamps shifted an hour.

The monthly routine that catches all three is unglamorous. Check every meter for missing intervals, duplicated records and abnormal demand peaks. Sum the submeters and compare the total against the utility statement for the same period. Log every correction with its reason, date and approver, so the audit trail shows a decision rather than a mystery.

Monitoring data should not drive tenant allocation, savings claims or operating decisions until that month's completeness check has passed.

Completeness is an owner obligation, not a vendor promise. The California Energy Commission's building energy benchmarking program warns that benchmarking submissions may omit meters associated with the building, notes that utility data can be requested or uploaded into ENERGY STAR Portfolio Manager, and sets reporting for covered commercial and multifamily properties generally due by June 1 for the prior calendar year. State reporting aggregates whole-building use, and no automatic mechanism confirms every associated meter was included. If the completeness check runs only when a report is due, the omission surfaces after the deadline.

Billing runs should freeze on a rule, not on a date. Run the reconciliation first, then freeze the cycle, then hold any unit that fails until its exception clears. Holding one invoice for two days costs less than issuing a correction credit and rebuilding a resident's trust.

Mixed-use buildings need separate billing groups for residential, commercial and shared loads so one class never inherits another's errors. Connect the system to property accounting and to the maintenance ticketing queue as well, because a fault or leak alert that only appears on a dashboard nobody watches becomes a work order three weeks late.

KPIs That Show the System Is Working

Record consumption and the estimated-read rate for the 12 months before go-live. Without that baseline, every number afterwards is an opinion. Then track a short list, calculate each one from data you already hold, and give each a named owner.

KPI

How to calculate

Target range

Review cadence

Data completeness

Valid intervals divided by expected intervals

98% or higher

Monthly

Submeter-to-parent variance

(Sum of submeters minus parent meter) divided by parent meter

Within the stated field tolerance

Monthly

Estimated-read share

Estimated bills divided by total bills

Falling each quarter

Monthly

Billing dispute rate

Disputed bills divided by total bills

Falling each quarter

Monthly

Fault response time

Hours from alert to technician visit

As set in the service agreement

Quarterly

Consumption change after go-live

Post-installation use compared with baseline, adjusted for weather

Down against baseline in comparable weather

Quarterly

Cost recovery rate

Billed submetered cost divided by utility cost

100% of metered cost recovered

Monthly

Data completeness is the first number to watch because everything else inherits its failures. A meter at 89% completeness still bills, just with estimates filling the gaps, and the resident pays for a guess dressed as a reading. Submeter-to-parent variance tells you whether the equipment is still inside tolerance or has drifted since commissioning, which is a hardware question rather than a billing one. Estimated-read share and dispute rate are the two resident-facing measures, and they move together: a rising estimate share almost always drags disputes up a month or two later.

Cost recovery deserves a plain calculation. Compare billed submetered cost against the utility cost for the same period. If the programme recovers less than the utility charges, the shortfall lands on the owner's operating statement, and it usually traces to unallocated common loads rather than to rates.

Fault response time is the measure that exposes a service agreement in practice. Compare the hours from alert to technician visit against what the contract promised, and review it quarterly with the vendor rather than annually in a renewal meeting.

Consumption change needs patience. Compare post-installation use against the baseline under similar weather, because a single mild month will flatter any programme. Then set the review rhythm: monthly for reconciliation and billing, quarterly for service performance and consumption, annually for vendor performance against the contract.

Any KPI outside target for two consecutive months goes to a named owner with a fix date, not onto a slide.

Protecting Residents From Billing Errors and Arrears

An accurate meter can still lead to an unfair bill if an estimate is presented as a confirmed reading, a dispute has no clear route, or arrears notices omit repayment options. Protecting residents depends on the process around the data as much as the measurement itself.

Label estimated reads plainly on the invoice and explain why an estimate was used. When actual data becomes available, adjust the account and show the correction as a separate line. That lets residents distinguish an estimate from a measured consumption figure and follow how the balance changed.

Set up the dispute route before the first billing cycle. Define how residents submit complaints, how quickly the team responds, and how staff check interval data against the audit trail. Test the process with a sample case: an estimated bill is labelled, the resident submits a written dispute, staff review the data, and any error results in a corrected invoice. If a balance remains unpaid, apply the relevant notice and repayment process before considering any service limitation.

Ontario's Unit Sub-Metering Code amendments, effective August 18, 2025, require stronger disclosure of consumer-protection policies, including arrears-payment agreements, winter disconnection and reconnection policies, and reconnection charges, according to the Ontario Gazette government notices. Billing based on suite-meter consumption must also comply with the Energy Consumer Protection Act, Ontario Energy Board requirements, and applicable codes. Put these policies in resident-facing documents, where residents can find them, rather than leaving them only in a management contract.

The Ontario requirements apply in Ontario. Elsewhere, confirm local rules before drafting resident documents. Disconnection and repayment conditions vary by jurisdiction, so a template from another market can create compliance risk.

A monitoring system earns trust through a defensible exception and dispute process, not through dashboard refresh speed alone.

For practical guidance on invoice structure and tenant charges, see how to bill tenants for utilities. Align the dispute and adjustment workflow with the billing process before the first cycle.

Axis Meter Solutions provides electricity submetering as a full-service program, including design coordination, approved metering equipment where required, commissioning, tenant billing, and ongoing service. In Ontario, it is licensed as a unit sub-meter provider under licence ES-2022-0268. Typical projects move from agreement to live meters in 8 to 10 weeks, including equipment lead time, with no upfront capital cost to the owner. Review the building's metering needs with Axis Meter Solutions.