Utility Bill Processing: Map Every Account to the Right Unit

High-volume utility bill processing is account-level work. Each utility account belongs to one unit, property or meter, and that link decides the GL account, class and location for every bill that account produces.

The reliable fix is to keep the account-to-unit map inside the AP system, not a spreadsheet, and let it drive coding, invoice numbers and how multi-account statements get split. MakersHub is set up around how your business already works, and our team configures it with you.

Our co-founder and President, Charley Howe, connected Pete Rose to a new customer that does this work at real scale:

Under the baseball is a hard AP problem, and it is common well beyond sports housing. The rest of this article covers the AP side.

Why does utility AP run on account numbers?

A utility bills per service account. Electric, gas, water and internet providers each assign an account number to every meter or connection, and that number is usually the only thing on the bill that says where the service is. The vendor doesn't know your property codes, your leasing programs or which entity owns the lease.

Everything your books need hangs off that account number. In QuickBooks terms, a bill needs a GL account (the expense line in your chart of accounts), often a class (a tag for tracking a business line or program) and a location (a tag for the property or market). When you hold thousands of accounts, the question for every bill is the same: which unit is this account, and what does that unit code to?

Here is what one row of that map looks like. Each line is one account, and every field to the right comes from the unit it belongs to, not from the bill:

The example values are illustrative. The structure is the point: one row per account, maintained in one place, and every bill coded from it.

When that map lives in a spreadsheet, someone has to look up every bill by hand. At a few hundred bills a month it is tedious. At two thousand, as in Charley's post, it becomes the job.

Why do summary statements break many AP tools?

Utilities and telecom providers often bundle many accounts into one document. Tampa Electric, for example, offers free summary billing to commercial customers with ten or more accounts under one name. It consolidates their bills into one, with each account's charges itemized inside.

That is convenient for paying and hard for accounting. One document arrives, but it holds dozens or hundreds of separate charges, each belonging to a different unit, each needing its own coding. Charley's cable vendor shows this problem at full size: one forty-page invoice covering two to four hundred accounts.

Many AP tools treat one document as one bill. Capture the vendor, the total and the due date, code it, done. A summary statement processed that way becomes one large bill coded to one place, and someone splits it by hand afterward, account by account. The right approach runs the other way: split the document into one bill per account first, then code each bill from the map.

Why do multi-column statements produce wrong numbers?

Layout. A two-column master statement is easy for a person to read: down the first column, then down the second. Software that reads a page straight across, left to right, can stitch the two columns together into rows that don't exist on the page.

This is a known PDF problem, not a quirk of one tool. The W3C's accessibility guidance on reading order in PDF documents uses exactly this example: a multi-column document that is clear to a sighted reader but that a screen reader may read straight across both columns, as if they were one. The order a machine reads a page in is not always the order a person sees.

Nested subtotals make it worse. A statement may show a charge for each account, a subtotal for each building, and a total for the statement. Every one of those numbers is printed on the page and every one is real. Pick up a building subtotal as if it were one account's charge and the amount is correct for the wrong thing. Nothing about it looks like an error.

Some utilities and telecom providers also offer billing data as a spreadsheet download or as electronic data interchange (EDI) files, a structured format for sending invoices between systems. When a vendor offers that alongside the PDF, it is worth asking for, because a data file has no columns to read out of order. Many vendors still send only the PDF, so reading the document correctly still matters.

The defense is arithmetic, not trust. The account charges should add up to each subtotal, and the subtotals should add up to the statement total. If they don't, a row was missed, doubled or misread. Charley described this check in his earlier post on where AI belongs in finance: when line items don't sum to the bill total, MakersHub flags the variance and goes back for the row it missed instead of posting a guess.

How do you build an account-to-unit map that holds up?

If you bill utility costs back to someone else, as Charley's customer does with each club, the map needs one more field: who pays in the end. Put the client or program on the unit, and the bill-back report comes straight out of the same coding instead of a second spreadsheet. At month-end, you no longer ask which bills belong to this client. You filter on a field you already have. It also makes disputes easier, because every charged-back amount traces to a specific account, unit and statement.

The map is also where most of the value sits. Get the vendor-plus-account match right and every bill after it follows. Get it wrong and every bill is wrong the same way, which at least means one fix corrects them all.

What does a missed utility bill actually cost?

More than a late fee. Utilities can disconnect service for nonpayment after giving notice, and the notice can be short. In Arkansas, for example, the Public Service Commission's rules require at least five days of written notice before disconnection, plus three days when the notice is mailed. Rules vary by state and by type of customer, so check the ones that apply to your accounts.

When you house tenants, a missed bill isn't a bookkeeping error. It is someone coming home, as Charley wrote, to no power. That is why a missing account on the map matters more than a slow approval.

How does MakersHub handle utility bills at volume?

It starts with the map. MakersHub imports your property and unit list, maps each vendor and account number to the unit it belongs to, and uses that match to set the GL account in your chart of accounts, the class, the location, and an invoice number built to your own convention. You set your coding rules once, and MakersHub applies them everywhere.

Multi-account statements are split into one bill per account, so a forty-page cable invoice becomes the hundreds of bills it actually represents, each coded from the map. WiseVision, the AI MakersHub uses to read documents, reads every line rather than only the total, and the statement's own arithmetic is checked before anything posts. Line-level automated coding then handles the rest without anyone retyping account numbers.

Approval and payment follow the same structure. Approvers use MakersHub without training. They approve from email in one click, and see only the bills that are theirs. MakersHub is transparent about where every bill sits and who is holding it, which matters when the question is whether a specific unit's power bill has been paid. Our real estate AP automation page covers the property-by-property setup, and the accounting system integration hub lists the systems MakersHub syncs with.

When is a spreadsheet map still enough?

If you manage a handful of buildings with a few dozen utility accounts, a well-kept spreadsheet and a careful person can handle it. The same goes for vendors that already send one electronic bill per account with the property name printed on it. The account-level approach earns its keep when three things show up together: hundreds or thousands of accounts, vendors that bundle them into summary statements, and coding that depends on more than the vendor name.

Hospitality and multi-location retail teams face the same problem with site-level bills. Our guide to multi-location hospitality AP covers it.

Frequently asked questions

What is utility bill processing in accounts payable?

Utility bill processing is the work of capturing, coding, approving and paying recurring bills for electric, gas, water and internet service, usually across many service accounts. At volume, most of the effort goes into matching each account to the property or unit it serves. MakersHub keeps that account-to-unit map inside the AP system and codes every bill from it.

How do you code a utility bill to the right property when only the account number identifies it?

You keep a map of vendor plus account number to unit, with each unit's GL account, class and location attached, and code every bill from that map. Using vendor and account number together avoids collisions between utilities. MakersHub imports your unit list, builds that mapping, and applies it to every bill automatically.

What is a utility summary bill?

A summary bill consolidates many service accounts from one utility into a single statement, with charges for each account listed inside. It simplifies payment but needs to be split into one bill per account for accurate coding. MakersHub splits multi-account statements into individual bills and codes each one from the account map.

Why do AP tools misread multi-column utility statements?

Software that reads a page left to right can merge two columns into rows that don't exist, and nested subtotals can be mistaken for account charges. The fix is to check that account charges add up to subtotals and subtotals to the statement total. MakersHub checks that arithmetic and flags a variance instead of posting a guess.

What invoice number should a utility bill get?

Many utility statements have an account number and a statement date but no unique invoice number, so teams build one from their own convention, often account number plus service period. That keeps every bill unique and searchable and helps catch duplicates. MakersHub assembles the invoice number to your convention when it creates each bill.

What happens if a utility bill is missed?

Late fees are the small part. Utilities can disconnect service for nonpayment after notice, and some states require only a few days of it. For anyone housing residents, that means a unit without power or water. MakersHub tracks each bill's status and owner, so a missing or stuck bill is visible before the due date.

Nobody notices utility AP when it works, and everybody notices when it doesn't. We built MakersHub so the account map does the remembering and the team does the checking. If your utility accounts still live in a spreadsheet someone is afraid to touch, we'd like to help move them. Get started with MakersHub.

Sources: Tampa Electric, Summary Billing; W3C Web Accessibility Initiative, Technique PDF3: Ensuring correct tab and reading order in PDF documents; Arkansas Public Service Commission, Suspension of Service. Account map example values are illustrative.