How to set up utility bills in AP with GL coding and accruals
Utility invoices are recurring, variable and spread across hundreds of accounts, which makes them awkward in an AP system built for purchase orders. Done well, each bill is matched to an account and a site, coded to a GL line and cost center by service type, approved on exceptions, and accrued when the invoice is not yet in hand. This guide sets out the design decisions in the order you will meet them, with the controls that keep the monthly close clean.
For ap managers, controllers and shared services teams · 8 min read
- 1
Set the vendor master structure
Decide whether each utility is one vendor with many remit-to or account records, or one vendor per account. A single vendor with an account table is easier to maintain and report on. Record the account number as a key field.
- 2
Map accounts to sites and cost centers
Use the account inventory so each account has a site ID, entity, cost center and service type. This mapping drives coding automatically.
- 3
Define the GL structure
Use separate GL lines for electricity, natural gas, water and sewer, and waste where possible. Add a line or dimension for taxes and fees only if you need to track them separately.
- 4
Choose the intake method
Prefer electronic delivery: utility EDI 810 invoices where offered, an aggregator feed, or portal downloads, over scanned paper. Electronic data brings meter and usage fields with it, which are needed for audit and reporting.
- 5
Automate coding and matching
Match each incoming invoice to its account record, apply the standing coding and route it. Invoices that do not match an account should go to an exception queue, not to default coding.
- 6
Set approval rules by exception
Auto-approve bills within a tolerance of the expected amount for the account and send exceptions to a reviewer: large variances, new accounts, estimated reads, duplicate invoice numbers, and closed sites.
- 7
Build the accrual process
Utility invoices usually arrive after the period they cover. At month end, estimate unbilled usage for each account from the last bill, the days since the last read and recent usage, and book it to the right period. Reverse it when the invoice posts.
- 8
Reconcile accruals to actuals
Each month compare prior accruals to posted invoices by account. Persistent gaps mean the estimation method needs adjusting or that bills are missing.
- 9
Report by site and service
Produce monthly cost by site and service type and a trailing 12-month view. This supports budgeting and gives the audit process a baseline.
Duplicates, late fees and closed sites
Three exception types cause most avoidable cost in utility AP. Duplicate invoices arrive when a utility re-sends a bill or a portal export repeats it. Late fees arise from approval delay on a recurring payable. Closed or vacant sites generate a minimum bill that continues until someone cancels service.
Build checks for each: invoice number and amount matching for duplicates, aging reports by due date for late fees, and a monthly match against the closed-site list for service that should have stopped.
Estimating accruals sensibly
A day-weighted method works for most accounts: take the average daily cost from the last invoice, adjust for known seasonality, and multiply by the days from the last service date to month end. Accounts with strong seasonal swings do better with the same period last year, scaled by the change in recent usage.
Document the method and apply it consistently, so that reviewers and auditors can follow it and so that reversals behave predictably.
Find out what your utilities owe you.
Connect bills for up to 50 meters. Get the findings report in about three weeks. Pay nothing unless money comes back.
- from bill access to first findings report
- 21 daysfrom bill access to first findings report
- of filed claims accepted by the utility in full or in part
- 94%of filed claims accepted by the utility in full or in part