Insights
Not because a regulator says so. No rule in Great Britain, Northern Ireland or Ireland makes every supplier replace its billing platform by 2030. But SAP IS U loses support at the end of 2030, the Irish market’s own central system is moving, and a run of rule changes lands before then. Here is what applies to whom.
By Christopher Fagan, Managing Partner, PEF Consulting Partners
There is no 2030 rule that says suppliers must move to new software, and nothing that says they must move to SaaS. The date most people are reacting to is SAP’s. Suppliers running SAP IS U have to leave the ECC platform underneath it before SAP’s support runs out, which for most means a decision now and a migration well before 2030. Everyone else faces a series of smaller but firm changes: new settlement arrangements, new market interfaces, new prepayment systems and new invoicing rules. Those mean upgrading what you have, not necessarily replacing it.
SAP’s mainstream support for ECC, and therefore for IS U, ends at the end of 2027. Paid extended support runs to the end of 2030. After that SAP offers only customer specific maintenance, with no new patches or legal changes, plus a narrow transition option to 2033 that runs only in SAP’s own cloud and is aimed at the very largest estates. S/4HANA, the successor, is supported until at least 2040.
That leaves an IS U supplier with three real routes: move to S/4HANA Utilities, on premise, hosted or through RISE with SAP; move to a SaaS billing platform such as Kraken; or buy time with extended or third party support while it decides. The dates and the choices are set out in full in SAP IS U end of support, and our independent platform comparison covers how the platforms differ.
For how the Irish market fits together, see how the Irish electricity market works and smart meters in Ireland, and for how we support suppliers there, our Ireland page.
Northern Ireland is the one part of the UK still without a smart meter rollout, and that is changing. The Department for the Economy’s smart meter design plan decision, published in April 2026, puts NIE Networks in charge of procuring and installing smart meters and the IT systems behind them, with a detailed programme plan to follow. No dates are set yet, but suppliers will need the data, tariff and billing capability to use half hourly information once the meters arrive.
No, but every supplier needs a platform that can carry the next four years of change. Three questions settle it. Is your billing platform supported by its vendor beyond 2030? Can it handle half hourly data and pricing without workarounds? Can it absorb market changes like these without a rebuild each time? If the answer to any of them is no, a platform decision is coming whether or not a regulator forces it, and it is far better made on your timetable than on a vendor’s.
No. Nothing in Great Britain, Northern Ireland or Ireland forces a platform replacement by 2030. The hard date applies to suppliers on SAP IS U, whose paid extended support from SAP ends at the end of 2030.
No. Moving to S/4HANA Utilities meets the SAP deadline as fully as moving to a SaaS platform. SaaS is a choice about operating model and cost, not a regulatory requirement.
Because the market’s central retail system runs on IS U too. ESB Networks is moving it to S/4HANA Utilities by the end of 2027, so every supplier has interface and testing work ahead, whatever platform it runs.
MHHS, with every MPAN migrated by 7 May 2027 and four month settlement from 2 July 2027, and structured electronic invoicing for business and public sector customers from 1 April 2029.
Dynamic price contracts for suppliers with over 200,000 customers since 1 October 2025, new gas prepayment meters from 2027 to around 2030, ESB Networks’ S/4HANA move by the end of 2027 and electronic invoicing from November 2028 to July 2030.
Related reading: SAP IS U end of support, SAP ECC end of life options, SAP S/4HANA Utilities migration, half hourly meters explained.
If you are weighing a platform decision against these dates, we can show you which of them actually bind you, in what order, and what that means for your programme. We sit on the client side, independent of every vendor.