ERP for Municipal Utilities — software for Stadtwerke and regional energy providers
A German Stadtwerk is a multi-commodity utility: electricity, gas, water, district heating, sometimes telecoms and public transport, occasionally swimming pools and parking garages. The ERP requirement set is therefore not a single utility-ERP requirement but the intersection of several regulated commodity markets, each with its own data formats, settlement processes and customer-onboarding workflows. An ERP for Stadtwerke has to handle BDEW data formats (UTILMD, INVOIC, REMADV, MSCONS), grid-operator settlement processes (MaBiS, GPKE, GeLi Gas), the ongoing smart-meter rollout under BSI-TR03109, customer-tariff complexity including the GreenTariff certification and the unbundling rules that separate network operations from energy sales. The German utility market is one of the most regulated in Europe; the ERP decision is fundamentally a regulatory-compliance decision before it is a feature decision.
Requirements
The first requirement is BDEW data-format compliance. The German energy market communicates in EDIFACT-derived formats: UTILMD for master-data changes (customer move, supplier change, tariff change), MSCONS for metering values, INVOIC for invoicing between market participants, REMADV for payment-advice messages and CONTRL for technical acknowledgements. The ERP has to send and receive these formats, validate them against the current BDEW format-version (which changes typically twice per year), and produce the audit trail demanded by Bundesnetzagentur.
The second requirement is the grid-settlement processes: MaBiS for balancing-group accounting, GPKE for supplier-change in electricity, GeLi Gas for supplier-change in gas, WiM for metering-point management. Each has its own state machine with regulated maximum response times. The third is multi-commodity customer billing: a single customer can buy electricity, gas, water and district heating from the Stadtwerk, plus a fibre internet contract from the telecoms arm, and expects a consolidated bill with separate VAT treatment per commodity (full VAT for energy, reduced for water in some Länder).
Mandatory functions
Mandatory functions for a Stadtwerke ERP: full BDEW format coverage (UTILMD, MSCONS, INVOIC, REMADV, CONTRL, ORDERS, IFTSTA, APERAK) with automated version updates as BDEW publishes new format versions; grid-settlement process support (MaBiS, GPKE, GeLi Gas, WiM) with regulated-deadline tracking; smart-meter integration per BSI-TR03109 with the iMSys (intelligentes Messsystem) gateway communication and the SMGW (Smart Meter Gateway) administration role.
On the customer-billing side: multi-commodity invoicing with consolidated and per-commodity options, tariff modelling with peak/off-peak/heat-pump tariffs, prepaid-meter handling for socially-supported customers, GreenTariff certification handling (TUV, Grüner Strom Label, ok-Power), and Abschlagsplan (instalment-plan) management with annual reconciliation. On the regulatory side: full Bundesnetzagentur reporting (BNetzA reports), Marktstammdatenregister maintenance, unbundling-compliant separation of network and sales accounting, and increasingly Redispatch 2.0 process handling for grid operators.
Vendor landscape
The German Stadtwerke ERP market is heavily concentrated in vertical specialists. SAP IS-U (now part of SAP S/4HANA Utilities) is the dominant platform at larger Stadtwerke and the four big national utilities (E.ON, RWE, EnBW, Vattenfall), with the deepest BDEW coverage and the broadest functional footprint. Schleupen CS.SW is the second-largest player and the typical choice for mid-sized Stadtwerke (50,000–500,000 customers); KISTERS BelVis covers grid-operator use cases especially well.
Wilken NEUTRASOFT is a long-standing Stadtwerke specialist with a strong installed base in the south-west, and ENGINEERING IngenieurDV serves smaller Stadtwerke and regional utilities. Newer entrants like powercloud target the digital-native end of the market with a cloud-first architecture, gaining traction at challenger suppliers and Stadtwerke wanting to modernise without a multi-year SAP IS-U migration. The market is fundamentally a make-or-buy decision against SAP IS-U: above ~300,000 customers, SAP IS-U typically wins; below, the German specialists deliver comparable BDEW compliance at lower implementation cost.
Trends and outlook
Three trends are reshaping Stadtwerke ERP requirements. First, the smart-meter rollout under BSI-TR03109 has accelerated in 2025–2026, which means high-frequency metering values (15-minute intervals for many customer classes) flowing into the ERP at volumes previous billing systems were never designed for — pushing customers towards modern, cloud-capable platforms with proper time-series handling.
Second, the energy transition has multiplied the tariff portfolio: PV self-consumption tariffs, heat-pump tariffs, wallbox tariffs, dynamic-pricing tariffs based on EPEX spot prices. Third, regulatory complexity is increasing rather than decreasing: Redispatch 2.0, the new BNetzA price-cap regime, and the upcoming bundling of metering with grid services all force ERP changes that vertical specialists absorb faster than the bigger SAP IS-U installations can.
Related Topics
Frequently Asked Questions
Can a Stadtwerk run on a generic ERP plus a separate billing system?
No, not realistically. The intersection of BDEW formats, grid-settlement processes and multi-commodity billing is too tightly coupled to be split across a generic ERP and a separate billing engine without significant integration risk. Every Stadtwerk above ~10,000 customers runs on a utility-specialised platform (SAP IS-U, Schleupen, KISTERS, Wilken or ENGINEERING IngenieurDV), and the smaller Stadtwerke typically outsource billing to a shared-service provider running one of these platforms.
How does the smart-meter rollout affect ERP selection?
Substantially. The 15-minute metering-value stream from smart meters drives data volumes 100× higher than legacy meter-reading. ERPs that handle metering values in a proper time-series store (rather than the classical billing table) and that ship the BSI-TR03109 SMGW administration role natively reduce implementation risk significantly. Vendors without that capability typically bolt on a separate MDM (Meter Data Management) layer, which works but adds integration complexity.
What does unbundling mean for the ERP architecture?
The Energiewirtschaftsgesetz requires legal, operational and informational unbundling between network operations (grid) and energy sales above 100,000 connected customers. The ERP has to enforce this with strict access controls, separated chart-of-accounts and audit-trail evidence that grid-side staff cannot see sales-side customer-acquisition data and vice versa. Vendors with explicit unbundling-mode configuration (SAP IS-U, Schleupen) handle this cleanly; weaker implementations rely on user-permission discipline that does not survive a BNetzA audit.