Utility bill management software: what to look for in 2026

Most organizations that manage more than a few dozen utility accounts are still moving bill data by hand. PDFs arrive by email, someone downloads statements from a utility portal, and a coordinator re-keys the totals into a spreadsheet or an accounting system. Numbers get transposed, periods overlap, a gas bill in cubic metres lands in a kWh column, and nobody notices until a report looks wrong. Utility bill management software exists to remove that step, but products differ a great deal in what they capture and how much they check.

This guide is for the people who have to choose one: facilities and sustainability teams, school boards, municipalities, consultants, and software teams. It covers the capabilities that matter (data capture from bills and from utility connections, validation, Ontario-specific fields such as Global Adjustment and rate class, multi-commodity support, delivery into the systems you already use, and an audit trail), then gives you an evaluation checklist, questions to put to vendors, and the failure modes we see most often.

Data capture: from bills and from utility connections

PDF and scanned bills

The software should read the bill's structure, not just its total. On an Ontario electricity bill the Ontario Energy Board describes the main components as Electricity, Delivery, Regulatory Charges and the Ontario Electricity Rebate, with Delivery broken into a Customer Service Charge, a Distribution Charge, a Transmission Charge and a Line Loss Adjustment, and Regulatory Charges including the Wholesale Market Service Charge and the IESO Administration Fee. Natural gas bills follow a different layout. The OEB lists a Customer Charge, Delivery (which covers transportation, storage and distribution), and a Gas Supply Charge, and notes that the federal carbon charge was eliminated effective April 1, 2025. Software that only extracts the amount due throws away those fields.

Bill scanning software also has to handle multi-account summary bills, several service addresses on one bill, credit notes, estimated reads, and skewed low-contrast scans. BillScan is EZGB's digitization service for this: it extracts consumption, demand, billing period, rate class and line items from PDF and scanned bills and validates them before delivery. The Green Button vs PDF bill digitization guide explains when a bill is the right source and when a utility feed is better.

Utility connections and Green Button

Bills give monthly totals; utility connections give the interval data behind them. The Green Button Alliance describes Green Button as a common XML format plus a protocol for automatic transfer of data from a utility to a third party based on customer authorization, in 5-minute, hourly, daily or monthly intervals depending on the provider. Ontario states that most regulated electricity and natural gas utilities had to provide Green Button access by November 1, 2023, including hourly electricity usage. Good utility tracking software treats the bill and the interval feed as two views of one account and reconciles them. Where a utility publishes Green Button usage summaries with billing categories such as tariff name, demand charges and third-party charges, the software should keep them rather than flattening the feed to kWh.

Validation: the part most tools skip

Extraction without validation is where utility bill processing projects fail. Every bill should pass these checks before anyone sees it in a report:

Line items sum to the subtotal, and subtotal plus tax equals the amount due, within rounding
The billing period is contiguous with the previous bill for the same account (no gaps, no overlaps)
Consumption is in the expected unit (kWh, m3, GJ, litres) and within a plausible range for that account's history
The account, meter and service address match a known record; duplicate and corrected bills are detected and flagged
Where interval data exists, the sum of intervals is compared to the billed consumption

Ask any vendor what happens when a check fails. If the record is silently accepted, keep looking. The how to validate utility bill data extracted from PDFs guide goes deeper on each of these checks.

Ontario-specific fields: Global Adjustment and rate class

In Ontario the largest single item on a commercial electricity bill is often not the energy charge but the Global Adjustment, and how it appears depends on the customer. The IESO states that for residential and small business Class B customers the GA is included in time-of-use or tiered rates, while for medium-sized Class B businesses it appears as a separate line item, and Class A customers (medium and large businesses in the Industrial Conservation Initiative) are charged according to their share of demand during Ontario's top five peak hours. The OEB adds that customers on a retailer contract pay their share of the Global Adjustment on top of the contract price and see it as a separate line.

The IESO's eligibility page sets the ICI thresholds: customers with an average monthly maximum hourly demand greater than 5 MW qualify automatically, those between 1 MW and 5 MW may opt in, and Class A customers pay GA on a peak demand factor tied to the top five peak hours over a May 1 to April 30 base period.

For software this means three things. Global Adjustment must be a distinct field, not folded into the energy charge. Rate class (Class A or Class B, and the utility's own rate category) must be captured and tracked over time, because a change in class changes the whole cost model. And whether the account is on utility supply or a retailer contract must be recorded. Energy tracking software built for other markets often has no place to put any of this.

Multi-commodity support and delivery

The same portfolio has natural gas, water, and often propane, fuel oil or district energy, each with its own units, billing cycles and layouts. The software should hold all of them in one schema with commodity and unit explicit on every record. The natural gas, water and propane data alongside electricity guide covers what changes per commodity.

For delivery, look for a REST API with JSON for applications, SFTP or scheduled file drops for accounting and BI systems, and CSV that follows a documented convention: RFC 4180 defines the common format for comma-separated values files, including CRLF line breaks, an optional header line, and double-quoted fields for values containing commas, quotes or line breaks. A vendor whose CSV column order changes between releases will cost you more than one whose API is slower. The how to receive utility data: API, SFTP or CSV guide compares the options.

If you benchmark, check how the software reaches ENERGY STAR Portfolio Manager. The EPA describes three ways in: manual entry, spreadsheet templates, or third-party providers using web services, and Portfolio Manager runs more than 70 data quality checks, so upstream validation determines how many alerts you deal with downstream.

Evaluation checklist

Capability	What to look for	Why it matters
Bill capture	PDF and scanned bills, multi-account summary bills, credit notes, estimated reads	Coverage of the accounts that have no digital feed
Utility connections	Green Button Connect My Data and authorized utility portal retrieval, refreshed on a schedule	Interval data and no manual downloads
Validation	Total vs line items, period continuity, unit checks, duplicate detection, interval vs billed comparison	Trust in the numbers
Ontario fields	Global Adjustment as its own field, rate class, Class A/B, utility vs retailer supply	Cost analysis that matches the bill
Delivery	REST API (JSON), SFTP, CSV, Portfolio Manager, BI connectors	Fits the systems you already run
Audit trail	Every value linked to its source document or feed, with timestamps and who changed what	Verification and dispute resolution

Questions to ask vendors

Which Ontario utilities do you retrieve from today by authorized connection, and which require bill upload?
When a bill fails validation, what does the user see, and can the original document be opened from the record?
Show me a Class A electricity bill and a retailer-contract bill in your data model. Where is the Global Adjustment?
What is the refresh schedule for connected accounts, and how are broken authorizations surfaced?
How is data delivered to Portfolio Manager, and who is responsible when the Data Quality Checker raises an alert?

Common failure modes

OCR without validation. The system reads the bill but nobody checks that the fields agree, so a misread digit becomes a 10x spike in a report. Manual re-keying that survives the purchase. Staff still copy totals into the accounting system because there is no delivery integration. Missing interval data. The tool is bill-only, so demand charge analysis is impossible. Flattened schemas. Everything is reduced to date, kWh and cost, and the Global Adjustment, rate class and demand fields are gone. No audit trail. When a number is questioned, nobody can find the bill it came from. Each of these is easy to test in a demo if you bring your own bills, including one you already know is unusual.

Frequently asked questions

What is the difference between utility bill management software and accounts-payable automation?

AP automation captures invoice totals, dates and vendor details so bills can be approved and paid. Utility bill management software captures consumption, demand, billing period, rate class and individual charges, validates them, and delivers them to energy and reporting systems. Many organizations run both, with the utility tool feeding the AP system.

Do I still need bill scanning if my utilities offer Green Button?

Usually yes, for part of the portfolio. Ontario's Green Button requirement covers most regulated electricity and natural gas utilities, but water, propane and fuel deliveries, sites outside Ontario, and accounts without a completed authorization still arrive as bills. One platform that does both keeps every account in the same dataset.

How should utility bill software handle Ontario's Global Adjustment?

As a separate, named field on every electricity record, with the customer's class (A or B) and supply arrangement stored alongside it. The IESO explains that the GA is embedded in rates for some Class B customers and a separate line for others, and Class A customers are charged on their share of the top five peak hours, so the software has to represent all three cases without forcing them into one column.

How EZGB fits

EZGB collects billing and interval data from 55+ Ontario electricity and natural gas utilities through authorized utility connections and Green Button, and digitizes PDF and scanned bills with BillScan for accounts without a digital feed. Retrieval runs on a schedule, typically daily. Every record is validated (totals against line items, period continuity, units, duplicates) and carries the Ontario fields described above, including Global Adjustment and rate class. Delivery is by REST API, SFTP, JSON and CSV into Portfolio Manager, Power BI, accounting and energy management systems. The automated bill and meter data retrieval page and how EZGB works describe the pipeline, and EZGB pricing lists the Freedom, Standard, Gold and Enterprise plans. The utility data for ESCOs and performance contracts guide shows the same data used for measurement and verification.

If you are evaluating utility bill management software, bring a sample of your own bills, including a Class A electricity bill and a gas bill, and we will run them through BillScan and show you the validated output and the delivered file formats. Request a demo on the pricing page.

Sources

Source: oeb.ca