Master data quality as the bottleneck of market communication: clearing cases, the MaLo ID and the clean-up before the MaBiS hub

Why master data became the bottleneck

Slack in the schedule is gone. That is the whole difference. Registration and switch date used to sit days apart, and in those days somebody could still straighten out a mismatched assignment. Germany's 24-hour supplier switch removed them.

Trade journal ZfK looked at what that meant in practice four weeks after the 6 June 2025 launch. In week one of the new market location identification process, only around 10 percent of roughly 250 grid operators under test could receive and process the messages cleanly. By 13 June it was about 80 percent. Message volumes multiplied overnight, and Stadtwerke Muenchen reported bilateral clearing cases up almost tenfold.

None of this is launch noise that fades. It is a number nobody used to measure.

One key sits at the centre of it: the market location ID, or MaLo ID. Eleven digits, purely numeric, and unlike a meter number it survives a meter replacement unchanged. In the new process nobody copies it off a document any more. A web service resolves it, and two hours are allowed for the answer. Miss that window and you hold up the switch.

How one wrong field spreads

A master data error almost never stays local. Consultancy HORIZONTE Group put it this way in May 2026: faulty master data hits roles, market locations, metering locations, balancing groups, message status and deadlines at once, because the same keys sit in all of them. One mismatched assignment therefore produces knock-on errors in settlement, in billing and in regulatory reporting.

Root causes rarely sit in market communication itself. They sit in the systems behind it. Geographic information systems, energy data management and SAP IS-U or S/4HANA Utilities each hold the same fact, grown over years, and not always identically. Which system is right has never been decided in many utilities.

There is a defined repair path, the bilateral master data reconciliation. Inventory lists go to the grid operator, who compares them against his own records, marks the deviations and sends them back. Going forward, each responsible party distributes its master data to the authorised parties, who check it and return a quality response.

What the MaBiS hub changes

Germany's MaBiS hub moves aggregation of quarter-hourly values and balancing group settlement for electricity onto a central platform. Distribution system operators will mainly supply billing-relevant master data after that. Responsibility for balancing group management stays with them.

Marcel Linnemann of IT service provider items summed up the core in one sentence: responsibility remains, control is reduced. Anyone who spots an implausible aggregation today spots it because they know the topology and the metering infrastructure of their own grid. That knowledge does not transfer to a platform.

Many utilities are therefore planning a shadow settlement. They keep calculating in parallel so they can check the hub's output. That builds duplicate structures with costs of their own, and it sits awkwardly next to the efficiency centralisation is meant to deliver.

Whether the effort is justified gets hard to argue against once you look at June 2025. A transmission system operator, otherwise known for a high quality standard, could not close balancing group settlement for that month on time. Problems during a software changeover for the 24-hour switch caused it. At central level, an outage like that hits everyone at once.

One more point tends to slip past. Complaints will no longer travel directly between two market partners but through additional bodies. The short path to a known contact at the neighbouring utility disappears.

The timeline to 2029

Dates are firm enough to plan a clean-up around. Regulatory proceeding BK6-24-210 at the Bundesnetzagentur was in its second consultation round in early 2026, with implementation due to finish by the end of 2028.

A counterpoint: not every deadline is a big IT project

A distinction gets lost in this debate, and it is worth making. For the 24-hour switch in gas, the BDEW expected no additional IT adjustments based on what was known at the time. German lawmakers adopted the EU requirement without adding anything, and that step demands no restructuring of master data exchange.

Effort in the gas market sits elsewhere, namely in GeLi Gas 2.0 and the new format. Treat the two as one thing and you tie up capacity in the wrong place.

Scepticism about the original schedule was there anyway. Dr Constanze Adolf of items called the 1 January 2026 gas date barely achievable back in August 2025 and put a stable productive launch at mid to late 2026 at the earliest. Both readings conflict less than they appear to: meeting the deadline is manageable, the process and format change behind it is not.

Where it breaks

Clean-up competes with day-to-day work, and both run through the same handful of people. That is the practical obstacle, not the technology.

There is one more factor, and it resists measurement. People who have phoned the same market partners for years settle some things in five minutes. That knowledge lives in no system, and it walks out with every change in the team.

What utilities should do now

Start by measuring, not by cleaning. Begin without numbers and you will tidy up wherever it happens to be easiest.

Five steps, in this order

1. Classify clearing cases by root cause

   Not by handler, not by market partner, but by the field that deviates. Three months give you a reliable picture. Cases usually concentrate on a few causes, and that is the good news.

2. Name a leading source per master data object

   An uncomfortable decision, because it shifts ownership. Without it, every clean-up stays provisional.

3. Schedule bilateral master data reconciliation as a routine run

   Not as a reaction to complaints. A fixed cycle, a named owner, a fixed reporting format.

4. Introduce a first-time-right rate per process and report it monthly

   Share of cases that complete without manual intervention. This single number makes progress visible and protects the topic when the next project competes for capacity.

5. Pace the clean-up against the hub timeline

   Whatever enters migration in 2028 has to be clean in 2027. Count backwards, not forwards.

A note on sequencing across the systems. Utilities planning the move off SAP IS-U should pull the clean-up forward. A migration carries wrong data across reliably, just faster. Same goes for the shift to API-based communication that the German market communication roadmap sets out.

Further reading

Frequently asked questions