Most apartment owners do not have a utility billing problem. They have an operating model problem that happens to show up on a bill. Utility costs are typically the third-largest expense for multifamily owners.
That distinction matters. A lot.
When margins tighten, teams go hunting for a faster recoveries fix. They tweak a RUBS formula. They shop a new billing vendor. They talk about submeters as if meters alone create discipline. None of that solves the real issue if the property does not trust its own data, cannot explain its charge logic, and still treats utilities like a back office accounting task instead of a property level operating system.
This is exactly why utility billing deserves more attention right now. Multifamily operating costs have stayed elevated, and the industry is still dealing with the aftereffects of a sharp post pandemic expense run up. RealPage reported that average annualized operating expense per unit rose 24.4 percent between first quarter 2021 and first quarter 2024. NAA later reported 2024 total annual operating expenses at $8,657 per unit, even as some utility costs moderated from prior peaks. In other words, pressure did not disappear. Water and sewer costs increased 45% over time, outpacing inflation. It just got more selective, which means loose utility execution stands out faster in NOI than it did when revenue growth covered a lot of sins.
The operators who get this do not start with billing output. They start with a thirty day audit.
A real audit does not ask whether charges went out on time. It asks where the property is leaking value. Which vacant units were handled incorrectly. Which units have attributes that do not match the PMS. Which meters are mapped based on tribal memory instead of verified field logic. Which move ins, transfers, and occupancy changes are landing too late to be reflected cleanly. Which recurring credits exist only because nobody fixed the upstream cause. That is where the money is.
This is also where weaker portfolios fool themselves. They think under recovery is the problem. Sometimes it is. Just as often, the bigger issue is volatility. Volatility in charges. Volatility in resident complaints. Volatility in site team workarounds. A property that recovers ninety eight percent one month and then spends the next month unwinding disputes, write offs, and exceptions is not running a healthy billing system. It is borrowing peace from the future.
The audit has to expose the failure points of the current model, not just the errors inside it. That means being brutally honest about whether RUBS, submetering, or some improvised hybrid is actually failing because of the model itself or because of poor execution around it. Those are not the same thing. Plenty of owners blame RUBS when the real problem is stale unit attributes. Plenty of owners praise submetering without admitting they still do not have a clean reconciliation workflow. Technology does not rescue a disorganized operating process. It simply gives the disorder better branding.
Once the failure points are visible, the next move is to quantify lost NOI in plain financial language. Not in utility language. Not in billing jargon. In NOI.
Data Integrity Is the Real Cost Leak
If there is one place where sophisticated operators separate themselves from casual ones, it is data integrity.
Everybody says data matters. Very few run utility billing as if that were true.
Start with meter to unit mapping. This sounds mechanical, but it is one of the most dangerous blind spots in multifamily. A surprising number of properties are still relying on historical mapping that has never been fully reverified after renovations, reconfigurations, turnover events, vendor changes, or simple years of operational drift. When owners say residents do not trust their bills, this is often the quiet reason. A billing model cannot be more credible than the physical truth underneath it.
Then there is occupancy sync. This is where supposedly advanced operations often look amateur. If your utility process lags the PMS, you are not just creating occasional errors. You are institutionalizing them. Vacant units get charged when they should not. Occupied units inherit timing distortions from prior residents. Site teams start issuing manual fixes because the system is no longer trusted. And once a property starts depending on manual correction as a normal monthly behavior, scale is gone.
The same goes for unit attributes. Square footage. Bedroom count. Occupancy assumptions. These are treated like setup data, then forgotten. That is a mistake. In RUBS, attribute accuracy is not administrative housekeeping. It is the formula. Get those fields wrong and your allocation model becomes mathematically precise and economically wrong, which is the most dangerous kind of wrong because it looks professional.
The smarter move is to create a pre billing validation layer that runs every month, not every crisis. Utility data should be validated before charges go out, not after residents react. That means exception testing for vacancy status, unit attribute changes, missing reads, outlier consumption, unresolved move in and move out timing, and any invoice variance that breaks expected tolerance. Teams that do this consistently reduce complaint volume before communication even starts.
There is a broader reason to care about this now. EPA and ENERGY STAR continue to push benchmarking and measurement as the foundation of water and energy performance in multifamily. Existing multifamily properties with twenty or more units can generate an EPA one hundred point Water Score through Portfolio Manager, and EPA guidance continues to position benchmarking as the starting point for identifying waste and comparing performance across similar buildings. That is not just an ESG talking point. It is operational discipline. You cannot improve what you do not trust enough to measure.
Choosing the Right Billing Model Per Property
The next trap is portfolio level ideology.
Owners love clean portfolio rules because they make governance feel neat. Utilities do not care.
The right billing model is property specific. Always.
Submetering is worth it when three things line up. Properties where owners pay utilities see 26% higher energy usage. The retrofit is physically feasible. The hold period is long enough to realize the value. And the organization is prepared to operate the system after installation, not just celebrate the install. That last point gets ignored all the time. Submetering is not valuable because it creates more data. It is valuable because it can make consumption visible, defensible, and actionable. Without the operating muscle to reconcile reads, monitor outliers, and turn usage patterns into maintenance action, the meter becomes an expensive witness.
Still, the strategic upside is real. Transitioning to submetering can reduce utility consumption by 20%–40%. Current EPA guidance highlights leak detection and flow monitoring devices as increasingly practical tools for identifying irregular water use and reducing waste and damage in homes, multifamily, and commercial buildings. That matters because the best owners are no longer treating utility data as billing evidence only. They are treating it as an early warning system for leaks, fixture failures, and deferred maintenance that would otherwise show up later as higher expense and lower resident satisfaction.
RUBS, on the other hand, is still the smarter move in more situations than people like to admit. Especially in legacy assets where speed matters, capital is finite, and retrofit friction is real. The mistake is not choosing RUBS. The mistake is choosing lazy RUBS.
A lazy RUBS model uses a simplistic formula, handles vacant units poorly, and sends out bills nobody on site can explain without forwarding the resident to someone else. A disciplined RUBS model uses weighted logic that reflects the property’s actual demand drivers, tests fairness before rollout, adjusts for seasonal volatility, and makes every charge explainable in under two minutes. When operators say residents hate RUBS, what they usually mean is residents hate opaque RUBS.
This is where hybrids start to make sense.
High performing operators are not emotional about billing models. They are pragmatic. New developments may justify submetering by default because design, infrastructure, and hold period support it. Value add assets may justify phased submetering only where return thresholds are clear. Legacy assets may be better served by optimized RUBS with tighter controls and better resident communication. The winning strategy is not uniformity of infrastructure. It is uniformity of operating discipline.
RUBS and Submetering Are Not the Story. Judgment Is.
This is the real dividing line.
Average operators ask which model is best. Serious operators ask which model this property can execute well, defend clearly, and improve over time.
That is a much harder question. It is also the only useful one.
The reason utility billing gets mishandled in so many portfolios is that it sits in an awkward middle ground. Finance thinks it is operational. Operations thinks it is administrative. Site teams think it belongs to the vendor. Vendors think the owner will clean up the upstream data. And residents, of course, see none of that nuance. They just see a charge and decide whether they trust the property.
So the first part of the fix is not software. It is clarity.
Run the audit. Quantify the leakage in NOI terms. Clean up the data until the property trusts its own records. Then choose the billing model property by property, based on real constraints and real economics, not habit and not ideology.
Do that well and the rest of utility billing becomes a systems problem. Do it poorly and every month becomes a cleanup exercise disguised as operations.
That is the fork in the road.
The Utility Billing Execution Framework Is Where Good Strategy Either Compounds or Dies
Once a portfolio has cleaned up the data, chosen the right billing model for each property, and stopped pretending one policy can solve every asset, the real work begins.
This is the part most operators underestimate.
Utility billing looks simple from a distance because the output is simple. A resident sees a charge. Accounting sees a receivable. Ownership sees a recovery percentage. But inside the machine, the work is more sensitive than it looks. Small process flaws echo through the entire system. A late occupancy sync becomes a disputed bill. A missing read becomes a manual adjustment. A manual adjustment becomes a reconciliation mismatch. A reconciliation mismatch becomes a write off nobody notices until quarter end. Then leadership says the portfolio has a collections problem when it actually has a process design problem.
That is why the execution framework matters more than the billing model itself. At scale, utility billing is not a charge generation activity. It is a chain of controlled handoffs. Data collection. Allocation logic. invoice creation. Payment matching. exception management. dispute resolution. audit visibility. The chain only works when every link is designed to reduce variation, not accommodate it.
The industry is moving in that direction whether slower operators like it or not. RealPage’s 2025 operating expense work shows that while expense growth has moderated from the sharp post 2021 surge, margins are still under pressure and operators are leaning harder on precision in controllable cost areas. That is exactly where billing operations belong now. Not in the clerical bucket. In the margin protection bucket.
The strongest operators build the collection layer first. Not because it is glamorous. Because everything after it is downstream truth management. Meter data, occupancy status, unit attributes, move ins, move outs, transfers, concessions, and statement timing all need to speak to one another cleanly. If they do not, the organization starts inventing local workarounds. Once that happens, consistency disappears. Two properties in the same portfolio can appear to run the same billing system while actually producing very different risk profiles.
That is also why automation should be judged carefully. Automation is not the removal of human labor. It is the removal of human interpretation in places where interpretation creates drift. Companies spend around $60,000/year on manual tasks. Pulling invoice data electronically instead of keying it manually is useful. Automating statement generation is useful. Auto matching payments is useful. But automating bad source data simply lets errors travel faster. Systems only create leverage when upstream controls are mature enough to deserve it.
Billing Operations Need a Monthly Rhythm, Not Heroics
A surprising number of portfolios still rely on monthly heroics. Staff spend 132 hours per month on routine, automatable tasks.
You can always spot them. The billing cycle lives in someone’s head. Exceptions are handled by whoever remembers last month’s fix. Residents with questions get routed to different people depending on who is on site. Reconciliations close late. Credits pile up quietly. Leadership hears about utility billing only when complaint volume spikes or a regional manager gets embarrassed.
That is not operations. That is improv.
A real billing playbook creates a fixed monthly rhythm. Reads and invoice inputs come in on schedule. Exceptions are flagged before bills are generated. Vacancy handling is validated before allocation. Outliers are reviewed before charges hit ledgers. Statements go out in a format residents can understand quickly. Payments post into a reconciliation workflow that identifies mismatches immediately instead of burying them inside month end cleanup. Disputes have a service level expectation. Adjustments have approval logic. Write offs are categorized by root cause, not just dollar amount.
This is where software integration matters, but not in the sales brochure sense. It matters because fragmented workflows create operational lag. EPA and ENERGY STAR continue to push benchmarking and web services integration as a practical way to measure and track building energy and water consumption, and to connect utility data into larger management processes. That is useful not just for sustainability teams, but for billing operations because better data connectivity reduces the friction between what was consumed, what was billed, and what can be explained later.
The KPI layer has to mature too. Too many owners stop at recovery rate. Recovery rate matters, of course. But it is not enough. You also need dispute frequency, cycle time to resolution, volume of manual adjustments, late read frequency, billing completion time, reconciliation aging, and the concentration risk tied to specific employees. If one high performing accounting manager disappears and the process slows down by half, that is not a staffing issue. It is proof the operation was never truly systemized.
Resident Experience Is an Operating Choice, Not a Soft Skill
There is a lazy idea in multifamily that resident experience and revenue discipline are somehow in tension.
They are not.
Bad billing creates resident frustration because it is confusing, slow, and inconsistent. Not because residents object to all utility charges on principle. People can accept almost any charge that is timely, clear, and defensible. What they will not accept is opacity. They will not accept a bill that takes four emails to explain. They will not accept language that sounds improvised. And they definitely will not accept a property team that treats the bill like somebody else’s problem.
This is why the single bill strategy remains more important than many operators admit. When rent and utilities live in one coherent resident financial experience, payment behavior usually becomes simpler to manage. Not magically. Not perfectly. But simpler. Fragmented charges create fragmented accountability. One statement creates a cleaner collection path and a cleaner service path.
The bill itself should meet an explainability standard. Any trained team member should be able to explain the charge in under two minutes using the same logic every time. That standard sounds basic, but it is actually one of the best tests of operational maturity. If your own staff cannot explain the bill easily, the issue is not resident communication. The issue is system design.
This matters even more as fee transparency expectations tighten. In 2025, jurisdictions continued moving toward more explicit disclosure requirements around housing charges and billing practices, with public enforcement attention focused on transparency and completeness of information presented to residents. The District of Columbia’s attorney general, for example, issued specific guidance in May 2025 urging transparent and complete disclosures about utility billing practices. The broader signal is obvious. The era of vague pass through language is getting less defensible.
That does not mean revenue recovery needs to become timid. It means communication needs to become professional. Strong operators do not apologize for utility billing. They explain it clearly, disclose it fully, and resolve disputes fast enough that small issues do not harden into distrust.
Compliance and Risk Control Are Now Part of the Revenue Model
For years, many owners treated utility billing compliance as a lease drafting detail. That is no longer enough.
The rules are too fragmented and the scrutiny is too uneven for casual governance. State and local requirements increasingly shape what can be billed, how billing methods must be disclosed, whether certain markups or fees are limited, and how much underlying documentation must be available if a charge is challenged. Public debate around RUBS in particular has sharpened in several markets, and recent proposals and enforcement signals make one point clear. A billing model that works operationally can still create unnecessary exposure if the disclosure and audit trail are weak.
That means compliance cannot sit on the edge of the process. It has to live inside the workflow.
Lease language needs to match actual billing practice. Change notices need to be controlled and documented. Underlying invoices, formulas, reads, occupancy support, and adjustment history need to be retained in a way that makes reconstruction possible after the fact. Every charge should be defensible not because you expect every resident to ask, but because the portfolio should behave as if any charge could be reviewed.
This is where disciplined operators gain an edge. They stop treating audit trail requirements as legal overhead and start treating them as operating leverage. A property with a complete record can resolve disputes faster. It can defend charges more confidently. It can spot root causes more easily. It can transition billing methods with less friction. Documentation, in other words, is not just protection. It is speed.
Benchmarking Turns Billing From Recovery Into Strategy
This is where the conversation gets more interesting.
Most portfolios use utility billing to recover cost. Better portfolios use it to understand cost. The best portfolios use it to predict where cost is trying to go next.
Benchmarking is what makes that possible. ENERGY STAR’s Portfolio Manager and related data tools continue to expand the practical case for comparing energy and water performance across properties, and EPA now has data explorer resources drawing from more than 150,000 commercial and multifamily properties. That matters because benchmarking turns isolated bills into portfolio intelligence. It lets owners compare buildings against peers, identify structural outliers, and separate normal seasonal movement from property specific inefficiency.
Once you have that visibility, the role of billing changes. A spike in water recovery issues may not be a billing problem at all. It may be a leak problem. A chronic variance in one building may point to fixture age, irrigation behavior, common area waste, or poor maintenance follow through. A cluster of unusual usage in similar unit types may expose equipment decisions that looked harmless during renovation but are now dragging expense and resident experience in the wrong direction.
That is why EPA’s ongoing work around utility data access matters beyond compliance and sustainability. ENERGY STAR continues to emphasize streamlined utility data access and whole building benchmarking as a way for owners to understand performance and identify savings opportunities. The more directly portfolios can move utility data into analysis, the less they have to rely on anecdote and postmortem explanation.
Are you actually recovering ninety five to one hundred percent of utility cost, or just reporting a number that ignores adjustments and timing leakage. Can your team explain any bill instantly, or only after escalation. Are disputes trending down because the system is getting clearer, or down because residents have given up asking. Does the process still depend on one or two people everyone secretly hopes never leave. Do you have portfolio wide visibility, or just a stack of property level stories.
If those answers are uncomfortable, the ninety day plan almost writes itself. The first thirty days are for audit, cleanup, and model confirmation. The next thirty are for system build, workflow design, automation controls, and dispute playbooks. The final thirty are for rollout, resident communication, training, and quality assurance. After that, the real cadence begins. Monthly validation. Quarterly optimization. Then a quiet kind of discipline that does not attract attention because it is working the way it should.
That is usually the best sign the system is finally doing its job.
