Energy and utilities
Every request touches several systems.
For municipal utilities, grid operators and energy suppliers: a billing complaint, a rejected supplier switch, a registration under § 14a of the Energy Industry Act (EnWG) or a new ruling by the Federal Network Agency (Bundesnetzagentur). The agent reads billing, meter data, market communication and more, and presents a reply, a correction or a review note as a draft.
neuland.ai HUB · Customer service
- and more systems
Ms. Keller, contract account (CA) 3391208, is calling about a €480.80 back payment and wants a written explanation. Where does the amount come from?
Tools chosen automatically
- Billing system · Annual bill 2025/26read
- Billing system · Line items by price periodread
- Meter data · Reading Jan 12, 2026 and prior yearread
- Billing system · Installment plan 2025read
- Customer service software · Contact historyread
The back payment has two causes. €288.80 comes from higher consumption: the reading shows 3,940 kWh, compared with 3,180 kWh in the prior year [1] [2]. €192.00 is missing because the monthly installment was €16 too low [3]. The new unit price only applies from April 1 and is shown separately in the breakdown [1]. Ms. Keller has already called twice [4].
- [1]Annual bill 2025/26 · 4 line items, 2 price periods
- [2]Reading Jan 12, 2026 · 3,940 kWh, prior year 3,180 kWh
- [3]Installment plan 2025 · 12 months at €16 too low
- [4]Contact history · 2 calls since the bill was sent
Please prepare the reply to her. She is also asking about paying in installments.
- Billing system · Open items CA 3391208read
- Document output · Reply to Ms. KellerDraft
The reply explains the €480.80 in short sentences, with the breakdown below as a statement. The amount is due on February 28, 2026 [1]. Your energy billing team decides on an installment plan; the draft explains how to request one.
- [1]Open items · due Feb 28, 2026
Reply to the customer
Draft- To
- Ms. Keller, CA 3391208
- Subject
- Your annual bill 2025/26
- Breakdown
- €288.80 consumption, €192.00 installments
- Installment plan
- via energy billing
The registration for supply start on Nov 1, 2026 for market location (MaLo) 50713348921 came back with an error message. What is wrong, and by when do we have to respond?
- Market communication · Error message for exception case MK-7742
- Market communication · Registration sent on Oct 16
- Billing system · Market location master data
- SharePoint · Supply start process description
- Market communication · Corrected registration
The grid operator rejects it because the meter number differs from its records in two digits [1] [2]. Your master data shows the same number, so the discrepancy is on your side [3]. According to the process description, the correction must go out by Oct 20, 7:12 AM [4]. The corrected registration is in the exception case as a draft. The cause remains an assumption until the grid operator replies.
- Market communication · Grid operator error message · Exception case MK-7742
- Market communication · Registration of Oct 16 · Meter number
- Billing system · Master data market location 50713348921
- SharePoint · Supply start process description · Section 3
- Exception case management · MK-7742
- Cause: meter number differs in 2 digits
- Rule: supply start process description, section 3
- Deadline: Oct 20, 7:12 AM
- Draft: corrected registration
- Billing corrects the master data
- Your market communication specialist triggers the dispatch.
New request NA-2026-3308 from the portal: heat pump at Musterweg 12. Is it complete, and what is still missing?
- Grid connection portal · Request NA-2026-3308
- Grid connection portal · 9 mandatory fields
- Geographic information system · Musterweg 12, local grid South
- Grid information system · Service connection Musterweg 12
- SharePoint · Guide to controllable consumer devices
- Grid information system · Request with follow-up for missing items
8 of 9 mandatory fields are documented [1]. The device data sheet with the electrical rating is missing; the stated rating is 11 kW. That makes the heat pump a controllable consumer device under § 14a of the Energy Industry Act (EnWG) [2]. The service connection is recorded in local grid South [3]. The request has been created, with the follow-up for the missing item attached.
- Grid connection portal · Request NA-2026-3308 · 8 of 9 mandatory fields
- SharePoint · Guide to controllable consumer devices · Section 2
- Grid information system · Service connection Musterweg 12 · Local grid South
Can the feeder carry the 11 kW?
- SharePoint · Grid connection guide · Responsibilities
I do not calculate that. Whether the feeder can carry the heat pump is checked by your grid planning team in the grid calculation software [1]. Rating and address are attached to the request for that purpose; the connection approval is signed by your grid connection specialist.
- SharePoint · Grid connection guide · Grid planning responsibility
- Follow-up NA-2026-3308 · PDF
- 8 of 9 mandatory fields documented
- Controllable consumer device, 11 kW
- Service connection recorded in local grid South
- Device data sheet missing
- Grid planning: check the feeder
Which Bundesnetzagentur publications from this week affect our grid? Please include deadline and source.
- Bundesnetzagentur · Publications CW 40
- Document management · 8 ongoing proceedings
- Document management · Grid fees, metering, connection
- Deadline calendar · Statements
This week, 11 documents were published on 8 ongoing proceedings [1]. Two affect your grid: the proceeding on grid fees, para. 47 [2], and one on metering, para. 12 [3]. The deadline for comments on grid fees ends on Oct 23 [4]. The other six proceedings do not affect your grid.
- Bundesnetzagentur · Publications CW 40 · 11 documents
- Document management · Grid fees proceeding · Para. 47
- Document management · Metering proceeding · Para. 12
- Deadline calendar · Comments on grid fees · Oct 23
Please run this check every Monday from now on.
- Orchestration · Weekly briefing Mondays 7:00 AM
The orchestration is set up: from now on, every Monday at 7:00 AM it reads the new publications and files the weekly briefing in your SharePoint [1]. Your regulatory management team still writes the statement to the authority.
- SharePoint · Regulation · Weekly briefing
- Regulatory briefing CW 40 · Excel
- Proceeding · Finding
- Grid fees · Para. 47, deadline Oct 23
- Metering · Para. 12, deadline Nov 6
- 6 other proceedings · not affected
- Orchestration active · next run Mon 7:00 AM
Delivered together with and at
From grid operation to regulation
The energy transition brings new rulings every year, and the staff to handle them does not grow. Agents take over what comes before every decision: reading, matching, drafting.
Example · The weekly list for service and market communication
Mondays at six, an orchestration puts the open exception cases from customer service and market communication on one list. Each case shows the system where the cause lies and the draft that is ready.
3 of 5 resolvedA
| Case | Resolved | Cause | Located in |
|---|---|---|---|
| CA 2104 7781 · Back payment complaintMeter data | resolved | Meter reading Jan 1 estimated · Reply in draftB | Meter dataC |
| MaLo 50713348921 · Switch rejectedMarket communication | resolved | Meter number differs in master data · Correction in draft | Market communication |
| CA 2093 1142 · Installment too highBilling system | resolved | Meter replacement 06/2026 missing from billing · Correction in draft | Billing system |
| CA 2117 0385 · Duplicate billBilling system | Question | Two contract accounts for one address · Query to master data | Billing system |
| MaLo 50719902214 · Supply start openMarket communication | open | Supplier registration without response · Reminder in draft | Market communication |
- Resolved means: cause found, with evidence.
- Drafts go out only when the responsible team agrees.
- Reading happens with the permissions of the team that owns the case.
Ready in the Agent Library
From customer service to regulation: eight of dozens of energy agents.
Billing Explanation Agent
up to 65%
less processing time
Breaks down every bill and drafts the reply before the back payment escalates.
Energy
Customer service, billing
EEG Billing Agent
60%
fewer corrections
Reviews billing under the Renewable Energy Sources Act (EEG) in a structured way and detects deviations early.
Energy
EEG, billing
Market Communication Exception Agent
55%
fewer manual exception cases
Pre-checks exception cases in supplier switching: cause, regulation, solution.
Energy
Market communication, switching processes
Grid Connection Guide Agent
55%
faster processing
Takes connection requests for wallboxes, heat pumps and PV through to completion.
Energy
Grid services, customer service, grid connection
Smart Meter Rollout Agent
45%
less evidence effort
Tracks mandatory installation quotas against the statutory timeline and makes any backlog visible early.
Energy
Metering point operation, regulation
Network Reporting Agent
70%
less reporting effort
Aggregates grid, load and consumption data for management reports.
Energy
Grid management, controlling
Regulatory Radar Agent
60%
less research time
Tracks parallel Bundesnetzagentur rulings and reports weekly what needs review.
Energy
Regulatory management, legal, grid operation
NIS2 and KRITIS Evidence Agent
50%
less evidence effort
Answers auditor questions on the status of security obligations with evidence, not assertions.
Energy
Information security, management board, legal
Figures are based on comparable projects and are not a guarantee.
Unbundling by role and tenant
Grid and sales stay separate. Sales never sees the grid file.
Admins define which role reaches which system; on request, grid operation and sales work as separate tenants. Each agent only reaches the data its role allows, and consumption data, bills and customer letters are never used to train language models.
Log
06:02Billing agentgrid.read(
Certificates, DPA and TOMs for download:
Several systems, one agent
The neuland.ai HUB reads systems such as billing, meter data management or market communication with the permissions admins set per role and agent. In unbundled sales, it only sees the readings from market communication. We connect legacy systems via API or MCP.
Data from Billing system, Meter data management, Market communication system, SharePoint etc. flows through neuland.ai HUB to Customer service software, Outlook etc.
Before grid operation and IT security get started
NIS2, the EU directive on network and information security, also requires security in the supply chain, meaning from vendors like us. Here are the answers for grid operation, IT security and sales.
Bring an exception case.
We show which systems the agent reads for it.
Describe a case that gets stuck today between billing, meter data, market communication or other systems, ideally with your price sheets and process manual.
After your request
01
You name the case and the systems it touches
02
We show the case with matching agents from the library
03
You know which agent your organization starts with