What utilities ERP and billing software must do
Utilities ERP is not generic invoicing with a meter attached. It must maintain the service location and device relationships, validate consumption, apply regulated rates, create bills at high volume, post receivables, allocate payments, run collections, and preserve an audit trail through every correction.
The core sequence is meter-to-cash:
- Collect and validate interval or register reads.
- Bind consumption to the correct installation, service agreement, and customer account.
- Apply the effective tariff, rider, tax, discount, and proration rules.
- Create and deliver the bill.
- Post receivables, allocate payments, and manage returns, dunning, and collections.
- Reconcile the billing platform with finance and the general ledger.
A product that cannot explain how it handles estimated reads, meter exchanges, backdated rate changes, move-in and move-out, multi-service accounts, and rebilling is not ready for a utility procurement.
How meter data reaches the bill
Advanced metering infrastructure (AMI) collects reads. Meter data management (MDM) validates measurements and prepares bill determinants, such as consumption for a billing period. The customer information system (CIS) connects that usage to the account and applies the tariff. Contract accounting records receivables and payments; finance receives reconciled postings for the general ledger.
| Boundary | Information passed | Check to include in integration acceptance |
|---|---|---|
| Metering to MDM | Reads, timestamps, device identity and quality indicators | Detect missing reads, duplicates and meter exchanges |
| MDM to CIS billing | Validated usage or bill determinants for the correct service period | Match the service point and account; distinguish estimates from actual reads |
| CIS to contract accounting | Invoice charges, adjustments and account references | Reconcile the billed total and the receivable before collecting payment |
| Contract accounting to finance | Reconciled posting totals and accounting references | Prove the subledger and general ledger agree for the same period |
This is a reference flow for evaluating interfaces, not a requirement to buy a separate product for every box. Oracle’s MDM integration overview distinguishes meter-related records from CC&B account and tariff records. SAP’s Utilities documentation explains its utilities data model and FI-CA subledger. Sources checked on 16 October 2026.
For an acceptance test, send an estimated reading through billing, then replace it with a corrected actual reading. Check the recalculated consumption, any invoice adjustment and the corresponding accounting entry. Include retries and rejected records so a successful file transfer cannot conceal a missing bill.
Use the Oracle product and migration guide or the SAP meter-to-cash example for the platform-specific decision. The CIS selection scorecard turns these checks into comparable vendor evidence.
SAP IS-U vs Oracle CC&B vs Cayenta CIS
| Platform | Best-fit context | Billing and CIS posture | Main implementation trade-off |
|---|---|---|---|
| SAP IS-U and S/4HANA Utilities | Large utility or established SAP estate | Deep meter-to-cash, FI-CA receivables, device management, and finance integration | Broad capability with a configuration-heavy program and demanding data conversion |
| Oracle Utilities CC&B | Large utility or established Oracle Utilities estate | Customer care and billing tied to Oracle MDM, network, and customer products | Strong utilities depth with a substantial implementation and integration footprint |
| Cayenta CIS | Municipal and mid-market utility seeking an integrated suite | CIS and billing alongside Harris utility products such as MDM, OMS, and customer channels | Smaller suite footprint, with less depth for the largest or most complex operating models |
The vendor product descriptions are useful starting points, not selection evidence. SAP documents its current utilities scope in the SAP for Utilities portal; Oracle publishes the CC&B documentation; and the Cayenta product catalog shows the modules in its suite. A selection still needs scripted demonstrations using the utility’s own rates, exceptions, and operating scenarios.
Seven questions that decide platform fit
How complex are the rates? Count active rate variants, riders, taxes, proration rules, and exceptions. The count matters less than the combinations the billing engine must evaluate and test.
How many commodities and service models share the account? Electric, gas, water, wastewater, district energy, and non-metered charges create different device and billing relationships.
Which surrounding systems are already strategic? MDM, OMS, CRM, payment, finance, data platform, and field service integration can decide the platform before a feature score does.
What must remain available during conversion? A billing cutover requires parallel validation, operational fallback, and clear ownership for exceptions. The migration design should state how the utility proves a bill is correct, not simply how records are loaded.
How much configuration can the operating team sustain? Enterprise breadth is useful only when the utility can test, release, and support the resulting rules after the implementation team leaves.
What deployment and security controls are mandatory? Data residency, identity, audit, integration boundaries, recovery, and release governance belong in the shortlist criteria.
Where does AI sit? AI can explain bills, triage exceptions, and assist agents, but the tariff calculation, posting, and control decisions must stay deterministic and auditable. The architecture view is in AI across service-to-cash.
Build the shortlist from operating evidence
Turn the seven questions into demonstration scripts. Give each vendor the same account history, meter event, rate change, payment exception, and rebill scenario. Score whether the product completes the workflow, which configuration or customization it needs, what lands in the audit log, and how the result reconciles to finance.
Then test the data model. The most expensive failures come from ambiguous ownership of customer, account, premise, service point, contract, and device records. The Oracle CC&B data model guide shows the Oracle relationships; the SAP CIS guide maps the comparable SAP concepts.
For the enterprise choice, continue with Oracle vs SAP for utilities. For a municipal or mid-market alternative, use the Cayenta CIS review.