Utility invoices are a third of your invoice count and none of your approval value

Count invoices by vendor at any property and utilities dominate. Electric, gas, water and sewer, trash, and sometimes separate stormwater and recycling accounts, each arriving monthly, each on its own cycle.

A 40-property portfolio can be processing well over a thousand utility invoices a year, and the approval step on essentially all of them is a regional signing off on a bill nobody can dispute or decline.

Four things make utility invoices structurally different

Volume with low variance. The amount changes seasonally and the vendor, the account, and the coding do not. That combination is the definition of work a person should not be doing.

Hard due dates with real penalties. Unlike a vendor who waits, a utility charges a late fee, commonly around 1.5% monthly, and in some jurisdictions moves toward shutoff. A late utility payment has a mechanical cost that a late landscaping payment does not.

Billing cycles that do not match your accounting periods. A gas bill covering March 12 to April 11 spans two months. Every utility invoice at every property has this problem, which makes utilities the largest source of accrual estimation at close.

Multiple meters per property. A property with house meters for common areas, irrigation, pool, and laundry has four or five accounts with one utility, all needing different coding. An invoice consolidating them needs line-level allocation rather than a single code.

Trusted vendor bypass is the right answer and it needs boundaries

The approval chain exists to catch spend somebody should question. A $340 electric bill for a property under management is not that.

Routing routine utility invoices around the approval chain removes the stage consuming the days, for the population where approval was adding no information. That is what recovers the late fees and it is also most of the cycle time improvement available on this vendor category.

Three boundaries worth setting:

A dollar threshold. Bypass under an amount that represents normal for that account, so a bill three times normal still gets a human. That is the case where approval genuinely adds value, because an abnormal utility bill usually means a leak.

Account-level rather than vendor-level. The same utility company may bill you for both routine service and for a new meter installation. The routine account bypasses; the other does not.

No bypass on purchase orders. A PO-backed invoice needs its match checked regardless of who sent it.

Allocation is where utility processing gets genuinely hard

Two distinct allocation problems, and they need different handling.

Common area versus resident-billed. Where residents are billed for utilities through a ratio utility billing system or through submeters, the property's utility invoice covers both the common area portion you expense and the resident portion you recover. Those code differently and the split depends on your billing methodology.

Multi-property invoices. Some utilities bill several properties on one account, which arrives as one invoice covering four properties and needs splitting before it can be coded. This is the case that most reliably breaks automated coding, because the correct answer is four postings rather than one.

Being clear about our own boundary: BillRoute codes to the property chart of accounts at line-item level, so a multi-line invoice can be coded across lines. It does not calculate RUBS allocations or run resident utility billing. That is a utility billing system or a module in your PMS, and any AP platform claiming to handle resident utility recovery should be asked to show the allocation math.

The cycle time payoff is concentrated here

Utilities are where an AP cycle time improvement is worth the most, for a simple reason: they are the invoice population with a penalty for being late.

On most other vendors, a slow approval costs you a discount you probably were not capturing anyway. On utilities it costs you a fee that posts to the GL.

So if you are sequencing an AP automation rollout, utilities are the first vendor category to move. Highest volume, clearest bypass case, and a measurable dollar outcome in late fees that appears within one billing cycle.

Watch three numbers

Utility invoices as a share of total invoice count. Establishes the size of the opportunity, and it is usually larger than people guess.

Late fees on utility accounts, from the GL, trailing twelve months. The direct measure.

Utility invoices exceeding a variance threshold against their own trailing average, per account. This is the leak detector, and it is worth running whether or not you automate anything else.

That third one produces the most operational value of the three and almost nobody runs it, because it requires per-account history rather than per-vendor totals.

What we handle

Intake from vendor email and uploads, extraction with vendor-specific templates for utility formats, duplicate detection, validation against the supplier master and property chart of accounts, line-level GL coding, trusted vendor bypass with configurable rules, and posting into the accounting stack. Our overall automation rate is 98%, and utilities are among the cleanest categories in that number because the formats are consistent month to month.

What we do not do: RUBS or submeter allocation, resident utility billing, direct connections to utility providers to pull bills rather than receive them, and shutoff risk monitoring. On the last one, the practical substitute is watching late fees and treating any appearance of a reconnection charge as an escalation.

Pull one account's twelve months

Pick one water account at one property. Pull twelve months of billed amounts.

Look for any month more than 50% above the trailing average. If you find one, check whether a work order was opened that month.

If there was a spike and no work order, you paid for water that left the building through something nobody found.

Did you find one?