March 16, 2026
What Data Can You Extract from a Utility Bill?
A comprehensive inventory of every data field available on electric, gas, water, and telecom utility bills—and why structured extraction matters for analytics and reporting.
More than just the total amount
Most organizations that process utility bills focus on one number: the total amount due. It gets entered into the accounting system, coded to the correct GL account, and paid. The bill is filed away and forgotten.
But utility bills contain far more data than the total amount. A typical commercial electricity bill carries 20 to 40 distinct data points that, when extracted and structured, enable cost analysis, usage trending, anomaly detection, rate optimization, sustainability reporting, and operational benchmarking.
The challenge is that this data is trapped in a document format designed for human readability, not data analysis. Extracting it requires either meticulous manual effort or purpose-built technology. Understanding what data is available is the first step toward unlocking its value.
Electric utility bill data fields
Electric bills are the most data-rich utility documents, particularly for commercial and industrial accounts. Here is a comprehensive inventory of extractable fields:
Account and service identification
- Account number - The primary identifier for the utility account. Essential for matching bills to accounts in your database.
- Customer name - The legal entity name on the account.
- Service address - The physical location receiving electric service. This may differ from the mailing address and is critical for emissions factor mapping.
- Meter number - The unique identifier for the specific meter being read. Large facilities may have multiple meters on a single account.
- Rate schedule or tariff code - The pricing structure applied to the account, such as General Service, Large Power, or Time-of-Use Commercial. This determines how charges are calculated.
Billing period and dates
- Service period start date - The first day of the billing period.
- Service period end date - The last day of the billing period.
- Invoice date - When the bill was generated by the utility provider.
- Due date - The payment deadline.
- Number of billing days - The total days in the billing period, used for normalizing usage comparisons across periods of different lengths.
Meter read data
- Previous meter read - The meter reading at the start of the billing period.
- Current meter read - The meter reading at the end of the billing period.
- Read type - Whether the read is actual, estimated, or customer-provided. This is critical for data quality assessment.
- Meter multiplier - A factor applied to the meter read difference to calculate actual consumption. Common on commercial meters where the meter registers a fraction of actual usage.
- Calculated usage - The consumption derived from the difference between current and previous reads, multiplied by the meter multiplier.
Usage and demand
- Total kWh consumption - The total electricity consumed during the billing period.
- On-peak kWh - Consumption during designated peak hours for time-of-use rate schedules.
- Off-peak kWh - Consumption during off-peak hours.
- Shoulder kWh - Consumption during intermediate or shoulder periods, if applicable.
- Peak demand (kW) - The maximum rate of electricity draw during the billing period, measured in kilowatts. This is a major cost driver on commercial bills.
- On-peak demand - Peak demand during designated peak hours.
- Off-peak demand - Peak demand during off-peak hours.
- Billing demand - The demand value used for charge calculation, which may differ from actual demand due to ratchet provisions.
- Power factor - The ratio of real power to apparent power, expressed as a percentage. Low power factor can trigger additional charges and indicates power quality issues.
- Reactive demand (kVAR) - Reactive power demand, related to power factor.
Charges and line items
- Supply or generation charges - The commodity cost of the electricity consumed.
- Delivery or distribution charges - Costs for transporting electricity from the generator to the facility.
- Transmission charges - Costs for high-voltage transmission system use.
- Demand charges - Charges based on peak power draw, often the largest single line item on commercial bills.
- Customer or service charges - Fixed monthly charges for maintaining the account and connection.
- Riders and surcharges - Regulatory fees, renewable energy surcharges, storm recovery charges, fuel adjustment clauses, and similar variable charges.
- Taxes - State, county, municipal, and franchise taxes applied to electric service.
- Total current charges - The sum of all charges for the current billing period.
- Previous balance - Any outstanding amount from prior periods.
- Payments received - Payments applied since the previous bill.
- Total amount due - The final payment amount.
Natural gas utility bill data fields
Gas bills share some common fields with electric bills but include fuel-specific data:
Gas-specific usage data
- Total consumption - Measured in therms, CCF (hundred cubic feet), MCF (thousand cubic feet), or cubic meters depending on the provider and region.
- Heating degree days (HDD) - Some gas bills include HDD data for the billing period, which is valuable for weather-normalizing consumption.
- BTU factor or heat content - The energy content of the gas delivered, which varies by source and season. This factor converts volume measurements to energy units.
Gas-specific charges
- Commodity or supply charges - The cost of the gas itself, often from a separate supplier in deregulated markets.
- Distribution charges - The cost of delivering gas through the local distribution network.
- Balancing charges - Charges related to imbalances between nominated and actual gas deliveries for large commercial accounts.
- Storage charges - Charges for gas storage services, applicable to some large accounts.
The critical difference with gas bills is the unit diversity. Converting between therms, CCF, MCF, and cubic meters requires specific conversion factors. A CCF of natural gas equals approximately 1.037 therms. An MCF equals approximately 10.37 therms. Getting these conversions wrong by confusing CCF with MCF, for example, introduces errors of an order of magnitude.
Water and sewer utility bill data fields
Water bills are generally simpler than electric bills but include their own specific data:
Water-specific fields
- Total water consumption - Measured in gallons, CCF (hundred cubic feet where 1 CCF equals 748 gallons), or cubic meters.
- Tiered rate breakdowns - Many water utilities use increasing block rates where the per-unit cost rises as consumption increases. Bills may show consumption and charges at each tier.
- Irrigation vs domestic usage - Some accounts separate indoor and outdoor water use.
- Sewer charges - Typically calculated as a percentage of water consumption, based on the assumption that most consumed water returns to the sewer system.
- Stormwater charges - Fixed or area-based charges for stormwater management, often assessed based on impervious surface area rather than water consumption.
- Fire service charges - Charges for maintaining fire suppression water supply infrastructure.
Telecom utility bill data fields
While less commonly classified as "utility" bills, telecom invoices share similar extraction challenges:
- Line-level charges - Individual charges for each phone line, data circuit, or service.
- Device and equipment charges - Monthly fees for leased or financed equipment.
- Plan and service charges - Recurring charges for voice, data, and feature packages.
- Usage-based charges - Variable charges for long-distance, international calls, or data overages.
- Regulatory fees and surcharges - Universal Service Fund contributions, E911 fees, and carrier-specific surcharges.
- Taxes - Federal, state, and local telecom taxes, which can be numerous and complex.
Universal fields across all utility types
Regardless of utility type, certain fields appear on virtually every bill and should always be extracted:
- Account number - The unique account identifier.
- Service address - The physical location receiving service.
- Billing period start and end dates - The time range covered by the bill.
- Due date - The payment deadline.
- Total amount due - The final payment amount.
- Previous balance and payments - Carryover and payment history.
Why structured extraction matters for analytics
Extracting only the total amount from utility bills is like reading only the bottom line of an income statement. You know what you owe, but you have no insight into why costs changed, where inefficiencies exist, or how to optimize.
Structured extraction of the full field inventory enables:
- Cost driver analysis - Understanding whether cost increases come from higher consumption, demand spikes, rate changes, or new surcharges.
- Usage trending - Tracking consumption patterns over time to identify efficiency opportunities and seasonal patterns.
- Demand management - Analyzing peak demand patterns to identify load-shifting opportunities that reduce demand charges.
- Rate optimization - Comparing actual usage patterns against available rate schedules to determine if a tariff change would reduce costs.
- Anomaly detection - Identifying billing errors, meter malfunctions, and unusual consumption patterns that warrant investigation.
- Sustainability reporting - Calculating emissions based on actual consumption data by utility type, facility, and meter.
- Benchmarking - Comparing energy use intensity, cost per square foot, and other metrics across facilities in your portfolio.
The depth of analytics you can perform is directly limited by the depth of data you extract. Organizations that extract only totals are limited to total cost tracking. Organizations that extract the full field inventory can perform sophisticated cost analysis, operational optimization, and environmental reporting from the same dataset.
Extract every field from your utility bills
Parsepoint captures 30+ fields per utility bill with AI-powered extraction—delivering the complete, structured data your analytics and reporting require.