Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 6

Utilities in 2027: IS-U deadlines

10 min

Listen to this lesson

0:00 / 7:44

Utilities run some of the largest billing operations in the SAP world: hundreds of thousands or millions of customers, billed every month or quarter, with regulated rates and little tolerance for error. Most of them do it in SAP IS-U (Industry Solution Utilities) on SAP ECC 6.0, with contract accounting in FI-CA and a CRM-based front office. That stack is reaching the end of its maintenance, and the move to SAP S/4HANA Utilities is one of the most testing-heavy transitions in the SAP world, because a bill is a legal document that customers and regulators read.

The dates

  1. End of 2027ECC 6.0 EHP 6–8 mainstream maintenance endsIS-U runs on ECC, so it follows the ECC dates
  2. End of 2030Extended maintenance endsOptional, at extra cost
  3. 2031 onwardSAP ERP, private edition, transition optionAnnounced in 2025 for 2031–2033; on October 13, 2026 SAP extended it so subscriptions may run to the end of 2035, with prerequisites (SAP Note 3591251)
  4. OngoingSAP S/4HANA UtilitiesThe successor, part of SAP S/4HANA
The dates that drive IS-U programs. Check SAP Note 3591251 and your contract for the transition option prerequisites.
The Sign-Off Table · thesignofftable.com/academy/sap-ind-201

The transition option buys time but does not change the destination, and it has prerequisites, such as running on SAP ERP, private edition, on SAP HANA before the end of 2030. Most utilities are planning S/4HANA Utilities programs now, which is why public tenders for IS-U transformations appeared through 2026.

What moves where

ECC landscapeSAP S/4HANA landscapeNote
IS-U device management, meter reading, billing, invoicingSAP S/4HANA UtilitiesCore processes continue; check simplification items
FI-CA contract accountingFI-CA in SAP S/4HANAPostings in the Universal Journal via FI-CA summary records
SAP CRM for UtilitiesSAP S/4HANA Utilities for customer engagementFront office embedded in S/4HANA, harmonized data model
Classic invoicing and bill printClassic invoicing, or Convergent Invoicing as an added optionDecide per contract type before comparing bills
How the IS-U landscape maps to SAP S/4HANA. Product names and scope vary by release.
The Sign-Off Table · thesignofftable.com/academy/sap-ind-201
Northwind's target: IS-U and FI-CA converted, the CRM front office moved into S/4HANA, meter data interfaces retested.
The Sign-Off Table · thesignofftable.com/academy/sap-ind-201

Choosing the path

Utilities choose between a system conversion, which keeps history, configuration and custom billing logic, and a new implementation with migration, which allows redesign but needs every customer, device, installation and open item migrated (see sap-s4t-102). Many utilities with large, stable IS-U systems choose conversion; those with heavy customization or a planned rate redesign consider a new implementation. Either way, the test that decides go-live is the same: bills after the move must match bills before it, within agreed tolerances, for every rate and situation that matters.

The testing scope of an IS-U transition at a glance.
The Sign-Off Table · thesignofftable.com/academy/sap-ind-201

What would you do?

Northwind's CIO proposes to rely on the SAP ERP private edition transition option and postpone the S/4HANA Utilities program indefinitely. What should the program lead say?

What goes wrong in testing

  • Treating the move as technical because "billing logic does not change", and planning too little billing regression.
  • Ignoring the front office: move-in, move-out and customer service processes now run in a different product.
  • Not budgeting for regulator-facing evidence when a commission oversees bills and rates.

Who is involved

Role at Northwind (illustrative)OwnsSigns
Billing process ownerRates, billing and invoicing resultsBilling comparison per mock, billing go-live
FI-CA ownerContract accounting, payments, dunning, G/L transferFI-CA reconciliation per mock
Customer service ownerFront office processes in customer engagementMove-in, move-out and service test results
Meter data leadReads, interval data, the meter data system interfaceRead completeness and plausibility
Regulatory affairsTariff filings and regulator communicationEvidence pack for the commission, where required
Test leadTest strategy, comparison method, defect processThat every obligation has a test and evidence

The people whose signatures decide billing readiness.

Regulatory affairs is the role programs forget. Where a public utility commission approves tariffs, it may expect evidence that customers are billed according to the approved tariff after a system change, and complaints about wrong bills reach the regulator quickly. Ask regulatory affairs in the first month which evidence they will need, and design the comparison reports so that they produce it as a by-product rather than a separate effort.

Key points
  • IS-U follows ECC maintenance: mainstream to 2027, extended to 2030.
  • The SAP ERP private edition transition option has prerequisites and is a buffer, not a destination.
  • IS-U and FI-CA move to SAP S/4HANA Utilities; CRM for Utilities moves to customer engagement.
  • Go-live depends on proving bills match, within tolerances, for every rate and situation that matters.

Check your understanding · not graded

Lesson check

  1. 1. When does mainstream maintenance end for IS-U on ECC 6.0 EHP 6–8?

  2. 2. What replaces SAP CRM for Utilities in the S/4HANA landscape?

  3. 3. What decides go-live in an IS-U transition, whatever the path?

  4. 4. What is true of the SAP ERP private edition transition option?