When it comes to ERP systems or software in general, expectations related to accountability are of particular importance to municipal utilities. A private company is accountable to itself. A municipal utility is accountable to the public and operates under the expectation of transparency on a day-to-day basis.
If pulling a clean, defensible report means days of manual spreadsheet work, the transparency obligation becomes a burden on staff rather than a routine part of doing business. This article looks at compliance and what is required from a utility billing system.
Transparency Expectations for Municipal Utilities
To illustrate the point, electric cooperatives answer to a member-elected board within the cooperative’s own governance structure. By contrast, municipal utilities are governed by a publicly elected city council, an elected or appointed commission, or board. Utility records are generally treated as public records under state law.
That means a member of the public, a reporter, or a state auditor can request billing data, rate calculations, or service records, and the utility has a legal obligation to produce them within a set timeframe. Staff need to pull that information accurately and quickly, with minimum time involved.
Consider a common scenario: a reporter files an open records request asking for every rate adjustment applied to residential accounts over the past three years. Such a report should be a matter of a few clicks. Pulling data from more than one place, cross-checking dates by hand, and hoping nothing was missed should not be part of the exercise.
Open Records Requests
Open records requests don’t always fall within a convenient scope. A request might be for the number of late fees issued in each quarter over a given time, or a full history of rate changes over five years. Software built primarily for issuing bills, without much thought given to billing history and audit trails, can be a real headache for utility staff.
Billing systems should provide reports that go back further than the current period, so staff are not digging through archived files or old system exports to answer a question pertaining to the last five years. Such reports should be generated in a standard format without a developer or a third-party’s involvement.
Audit Trails: The Backbone of Defensible Reporting
Audits can come from a state agency, an outside accounting firm, or the city’s own internal auditor, and are typically extensive in nature.
An effective audit-trail requires utility practices to be accurate and consistent over time. With the right billing system, very adjustment, manual override or rate change should be logged, with a timestamp and a record of who made the change. Finance staff should not have to reconstruct history after the fact. A billing platform with audit trails built in makes for a much less stressful process.
Staffing also comes into play. Municipal utility offices are often lean, and the person fielding a records request is frequently the same person responsible for billing, customer service, or monthly reporting. Software that requires a specialist or a support ticket to pull a report is inconvenient and can cause a delayed or late response.
Board Reporting Without Manual Spreadsheets
Beyond audits and records requests, municipal utility governing bodies need regular reporting just to do their job. Monthly board packets, quarterly financial summaries, and annual reports to the city council all draw on the same underlying billing and usage data.
When reporting depends on staff manually exporting data into spreadsheets and rebuilding the same charts every month, it eats staff time and introduces room for error. The billing system should be able to generate standard reports directly from live billing data ensuring report data match the data in the system.
Another subtler problem is consistency. If one month’s board packet presents data in one way and the next month presents it differently, it begs questions and undermines confidence in the numbers even if they still add up. Standardized, system-generated reports remove that inconsistency because the definitions are in the software, not made by the staff member who happened to build the spreadsheet that month.
What to Look For
Municipal utilities evaluating billing and reporting software should look for a few specific things: report generation that does not require a developer, audit trails that log changes automatically rather than relying on staff notes, historical data retention well beyond the current billing cycle, and consistent report formats.
The CentralView CIS[1] was built with this kind of accountability in mind. Reporting and audit trail functions are native to the platform rather than an overlay, which means utility staff can respond to a records request or prepare for an audit without pulling data from multiple systems.
On a related topic see One Customer, One Bill: Why Your CIS Needs to Handle Multi-Service Billing From the Ground Up.
Public accountability is not going away, and compliance does not have to be burdensome. The utilities that handle records requests, audits, and board reporting with the least friction are the ones whose CIS was built to produce clean, defensible data from day one.
See How CentralView Supports Reporting
The information presented in this article is intended for general educational purposes. Utility software environments vary significantly. We recommend consulting with a qualified technology advisor to evaluate solutions appropriate to your organization’s specific operational requirements.
[1] CentralView CIS is part of an ERP product suite provided by Central Service Association (CSA). CentralView is a Trademark.