Before billing starts, the system must correctly model “who is being billed for what.”

Core entities the system tracks:

• Customer accounts (person/business, contact info, communication preferences)
• Service locations (physical address, premise/service point, parcel references)
• Meters / endpoints (meter number, size, install date, route/zone)
• Services (water, sewer, electric, gas, stormwater, trash, fees)
• Billing cycle assignment (monthly, bi-monthly, quarterly; zones/routes)

Why this matters: If the account-to-service-location relationships are wrong, the rest of the process—usage, rates, bills, collections—falls apart.

A core job of utility billing software is to receive consumption data.

Common reading methods:

• AMI (Advanced Metering Infrastructure): frequent/near real-time reads via networked endpoints
• AMR (Automated Meter Reading): drive-by/handheld collection at intervals
• Manual readings: in-field entry or office entry from read cards
• Imports: batch files from meter reading vendors or an MDM system
• Submeters: especially for multifamily and property management billing

Key requirement: The system needs consistent meter metadata (multiplier, decimals, units) and must match readings to the correct meter and billing period.

Raw reads aren’t always bill-ready. This is where Validation, Estimation & Editing (VEE) comes in.

Typical VEE rules include:

• Detecting outliers (spikes, drops, negative consumption)
• Handling missed reads (estimate based on history or seasonal patterns)
• Flagging exceptions for review (leaks, stuck meters, rollovers)
• Approving corrected reads with audit trails

Expert note: The most revenue-impacting errors often come from unreviewed exceptions—especially when reading changes coincide with rate changes, meter exchanges, or occupancy turnover.

After usage is confirmed, the system applies the utility’s rate structures—which can be simple or extremely complex.

Common charge types:

• Fixed charges: base service fees by meter size/service type
• Volumetric charges: usage-based charges per unit (gallons, kWh, therms)
• Tiered / block rates: increasing (or decreasing) rates as usage rises
• Time-based rates: seasonal rates or time-of-use (common in electric)
• Demand charges: peak usage thresholds
• Sewer calculations: based on winter averages, water usage, caps
• Stormwater fees: based on impervious area or equivalent residential units (ERUs)
• Trash: flat fee, cart size, frequency, or add-ons
• Adjustments/credits: leak adjustments, back-billing, proration, refunds

What “rate flexibility” really means: A modern system should support rate changes without custom coding, maintain history, and recalculate accurately for proration, move-ins/move-outs, and billing corrections.

Once charges are calculated, the system generates bills—either as statements, invoices, or consolidated utility bills.

Most utilities support multiple delivery methods:

• Print and mail
• Email and eBill notifications
• Customer portal presentment
• Third-party print vendors (“bill print service”)

Bills typically include:

• Current charges + prior balance
• Payment due date
• Usage history (especially for AMI-driven customer transparency)
• Itemized service lines (water/sewer/trash/etc.)
• Messages/notices (rate changes, conservation, delinquency warnings)

Operational goal: consistent bill runs by billing cycle with minimal exceptions, plus strong auditability (who ran it, when, what changed).

This is where billing meets cash flow. Payment workflows commonly include:

Payment channels:

• Online payments (card/ACH)
• AutoPay
• Walk-in/counter payments
• Lockbox/check scanning
• IVR/pay-by-phone
• Third-party payment networks

Payment processing requirements:

• Accurate posting to the correct account and service location
• Handling partial payments and allocation rules (current charges vs past due)
• Receipting, reversals, refunds, and NSF handling
• PCI compliance for card data and secure tokenization

Metric to watch: Days Sales Outstanding (DSO). Faster, cleaner posting typically reduces customer disputes and improves collections.

Utilities need a consistent approach to past-due accounts—without creating unnecessary customer friction.

Delinquency tools commonly include:

• Late notices and reminders
• Late fees/penalties and interest
• Payment plans
• Service restrictions / disconnect workflows
• Field orders for disconnect/reconnect
• Customer contact history and dispute tracking

Best practice: Delinquency actions should be rules-based and role-aware (who can waive fees, create payment plans, approve adjustments), with clear audit trails.

A modern CIS/utility billing system should provide visibility into:

• Billing run health (exceptions, rebills, read failures)
• Revenue by service and rate component
• Collections performance and aging (A/R aging buckets)
• Usage patterns and anomalies (especially with AMI)
• Operational workload (work orders, service requests, contact volume)

This is where business intelligence and “utility usage analytics” matter—because billing accuracy isn’t just finance; it’s customer trust.