Energy

Market Communication Exception Agent

One wrong street name and the registration bounces. The clock keeps running, and nothing can be backdated.

Pre-checks supplier-switch exceptions: cause, rule, resolution path.

Pre-checks supplier-switch exceptions: cause, rule, resolution path.

Open agent

Enlarge demo

Public administration

Four processes that take up the most time today

Developed in Germany · Hosted in the EU

Developed in Germany · Hosted in the EU or on-premises

Delivered together with

Sovereign hosting in Germany, single-tenant from the first user.

Sovereign hosting in Germany, single-tenant from the first user.

Legal, tax and compliance expertise for legally sound deployment.

Legal, tax and compliance expertise for legally sound deployment.

Advisory and implementation for the public sector, starting with the AI readiness assessment.

Advisory and implementation for the public sector, starting with the AI readiness assessment.

A rejected UTILMD takes longer to sort out than the switch itself.

The registration goes to the grid operator as a UTILMD and comes back as an APERAK with an error code. The specialist opens the exception, looks up the market location in the billing system and checks the meter number and address against the counterparty's records. Then she checks the process description for the deadline that now applies. Only then can she write the new message.

24 hours

switching deadline

A supplier switch must be processed within one day.

6

error codes

Six different APERAK responses come in during a single morning.

17 minutes

per exception

Compare master data, look up the rule, build the response message.

3

system switches

Market partner data, billing system and process description are not in one place.

The 55% reduction in manually handled exceptions comes from cases where cause, rule and draft response are already attached before anyone opens them.

This agent's headline figure is 55% fewer manual exceptions. The switching deadline comes from the regulated procedure; the error codes and minutes per exception describe a typical morning in market communication and are illustrative, not measured.

Three steps through the process.

The agent attaches the suspected cause, the applicable process rule and a resolution path to the exception; the market communication specialist decides whether the corrected message goes out to the market.

1.

1.

Check the error code against master data

The agent reads the error code from the APERAK and compares the master data sent with the grid operator's records. It flags each mismatched field separately.

The agent reads the error code from the APERAK and compares the master data sent with the grid operator's records. It flags each mismatched field separately.

Exception MK-7742, meter number differs by 2 digits

2.

2.

Apply the process rule and its deadline

The agent finds the rule that applies to this error code and this type of switch and attaches it to the case with its source reference. It also states the resulting deadline.

The agent finds the rule that applies to this error code and this type of switch and attaches it to the case with its source reference. It also states the resulting deadline.

Start of supply, to be processed by 14 March, 07:12

3.

3.

Provide the response message as a draft

The agent drafts the corrected UTILMD with the cleaned-up fields. The market communication specialist approves it as it stands or amends it first.

The agent drafts the corrected UTILMD with the cleaned-up fields. The market communication specialist approves it as it stands or amends it first.

utilmd_MK-7742.xml, 2 digits of the meter number corrected

What the agent does not do.

It does not send market messages.

It does not send market messages.

It saves the corrected UTILMD to the exception as a draft. The market communication specialist sends it from the market communication system.

It does not change master data itself.

It does not change master data itself.

For exception MK-7742 it names the field, the value sent and the counterparty's value. Billing enters the corrected meter number in the system of record.

The cause remains an assumption until the market partner replies.

The cause remains an assumption until the market partner replies.

It derives the assumption from the error code and the data comparison, and says what it is based on. If the grid operator gives a different reason, the grid operator's account takes precedence.

Connected systems

EDIFACT market communication

billing system

exception management

Operations

Deployment model

EU cloud or private cloud

EU cloud or private cloud

Data processing

GDPR-compliant, no model training on your data

GDPR-compliant, no model training on your data

Responsible teams

Market communication, switching processes

Market communication, switching processes

The questions that come up before the first meeting.

How quickly is the Market Communication Exception Agent ready to use?

Where is the data processed?

Where does the figure “55% fewer manual exceptions” come from?

Related agents.

All agents

Platform

Industries

Services

Resources

Company

Pricing

From AI strategy to a running platform: we show you the way.

Talk to us

Log in

DE

EN

English

Platform

Industries

Services

Resources

Company

Pricing

From AI strategy to a running platform: we show you the way.

Talk to us

Log in

DE

EN

English
neuland.ai

The AI management and orchestration platform from Cologne.

Developed in Cologne. Operated in the EU or in your data center.

Certifications and compliance: ISO 27001, ISO 9001, GDPR, EU AI Act, DORA, StBerG, and BRAO
WirtschaftsWoche Best of Technology 2026 seal, 2nd place in the Process Management category for neuland.ai

© 2026 neuland AI AG