Pre-checks supplier-switch exceptions: cause, rule, resolution path.
Developed in Germany · Hosted in the EU or on-premises
Delivered together with
Sovereign hosting in Germany, single-tenant from the first user.
Legal, tax and compliance expertise for legally sound deployment.
Advisory and implementation for the public sector, starting with the AI readiness assessment.
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.
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.
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 digitsThe 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:12The 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 correctedIt saves the corrected UTILMD to the exception as a draft. The market communication specialist sends it from the market communication system.
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.
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
Operations
A pilot typically runs on your own data within 6 to 8 weeks. The agent connects to your existing systems rather than running as a separate, parallel environment.
EU cloud or private cloud. Processing is GDPR-compliant and models are never trained on your data. Details in the Trust Center.
It is based on experience from comparable projects and process benchmarks, not a commitment. We establish the realistic effect for your organisation in the assessment before the pilot.