← Back to Blog
4 min read

How Do You Automate Utility Bill-Back for Multifamily Property Managers?

Stylized landscape with rolling dunes and a pale sun

Multifamily operators without individual meters still need to charge each resident their share of the property’s water, gas, and electric bill, and that starts with pulling the master bill data out of a utility portal every cycle. Deck automates that retrieval so the bill-back calculation runs on current numbers instead of whatever a coordinator managed to copy down by hand.

How Does Deck Automate Utility Bill-Back for a Multifamily Portfolio?

Deck automates utility bill-back by retrieving master bill data directly from utility provider portals, then returning it as structured data a ratio utility billing calculation can run against. Deck is a computer use agent platform that automates workflows by operating any web interface directly, so the target system never has to expose an API for it to work.

The workflow runs in four steps:

  1. Authenticate. Deck logs into each utility provider’s portal using stored credentials and completes MFA where required.
  2. Retrieve the master bill. Deck reads the current billing period’s charges, whether the provider presents them as an HTML table or a locked PDF statement.
  3. Structure the data. Charges are mapped into a consistent schema across every provider, since no two utility portals present a bill the same way.
  4. Feed the allocation. Structured bill data flows into the ratio utility billing calculation, whether that runs in a property management platform or a separate billing system.

This matters because almost no utility provider exposes a billing API a property manager can call directly, and Green Button data, where it exists, typically covers usage rather than the full billed amount a bill-back calculation needs.

It helps to separate two things that get conflated: knowing how much water or electricity a property used, and knowing how much the utility actually charged for it. Green Button, where a utility supports it, answers the first question. Bill-back needs the second, and that number, taxes, fees, and rate adjustments included, usually only exists on the statement itself.

Why Doesn’t RUBS Software Already Solve This?

RUBS software vendors handle the allocation math well but generally assume the master bill amount is already in the system. Getting it there each cycle, from however many utility providers a portfolio spans, is left as a manual step or a separate integration project.

Manual retrieval, checking each provider’s portal and re-keying the total, is the default most portfolios run on today. It scales linearly with the number of providers and properties, which means it gets slower and more error-prone exactly as a portfolio grows.

Custom scripts built to pull one or two utility portals tend to break the first time a provider updates their statement layout. Utility companies aren’t optimizing their websites for automation, and a script with no session or layout resilience needs constant babysitting to stay accurate.

Submetering sidesteps the retrieval problem for properties that install it, since usage is measured directly rather than allocated by formula. It’s the more accurate approach, but retrofitting submeters across an existing property is a capital project with a payback period measured in years, not a fix for this cycle’s bill-back run.

What Does This Look Like Across a Multi-Provider Utility Portfolio?

A property management company running RUBS across a portfolio spanning several regional utility providers needs the master bill amount from each provider, every cycle, before residents can be billed accurately. Manually checking a dozen provider portals every month is slow enough that bill-back often runs a cycle behind actual usage. Deck’s use cases in internal workflows cover exactly this shape of problem: recurring, authenticated retrieval across many source systems, normalized into one structure a downstream calculation can consume on schedule.

FAQs

Does Deck work with regional utility providers that don’t offer Green Button data?

Deck retrieves bill data directly from a utility provider’s customer portal, regardless of whether that provider participates in Green Button or exposes any usage API at all.

Is Deck a replacement for RUBS billing software?

Deck is not a replacement for RUBS allocation software. Deck handles the retrieval step that feeds it, pulling master bill data from utility portals so the allocation calculation runs on current numbers.

What is the difference between usage data and bill data for utility bill-back?

Usage data shows consumption, often available through Green Button where a utility supports it. Bill data shows the actual dollar amount charged, which is what a bill-back calculation needs and what Green Button frequently doesn’t cover.

How long does it take to automate utility bill retrieval across a portfolio with Deck?

Most portfolios see their first providers live within a couple of weeks, with additional providers added incrementally as Deck’s existing retrieval infrastructure extends to each new portal.

Ready to get started?

See how Deck can connect your product to any system — no APIs needed.

Build my Agent →

Related reading