# Determination and reconciliation of the billing-relevant curtailed energy – planned value model — NB view
## Process flow from the perspective of the NB
\nSystem diagram: Ermittlung und Abstimmung der abrechnungsrelevanten Ausfallarbeit – Planwertmodell — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Ausfallarbeit und\nFahrplananteil je TR\n\nBTR\n\nRD\n13022\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n2. NB bestätigt Ausfallarbeit\nund Fahrplananteile des BTR\n\n\nBTR\n\nRD\n21037\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. NB lehnt mit Begründung\nab und übermittelt\nGegenvorschlag\n\n\nBTR\n\nRD\n21037, 13022\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Übernahme\nGegenvorschlag\n\n\nBTR\n\nRD\n21038\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Ablehnung\nGegenvorschlag\n\n\nBTR\n\nRD\n21038\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n6. Ablehnung inkl.\nKorrekturanforderung\n\n\nBTR\n\nRD\n21037\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={""} titel="NB" />
## Process steps
### Curtailed energy and schedule share per TR
**Check identifiers**
- [13022](/en/schnittstellen/202604/pruefi/MSCONS/PI_13022) — Redispatch 2.0 individual time series curtailed energy · RD
**Flow**
Message from **BTR** · RD
**Write endpoint**
- Transaction created — [Create process data](/en/api/202604/backend-schreiben-nb/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out
Creates a new transaction in the backend with the data of the incoming message.
### NB confirms curtailed energy and schedule shares of the BTR
**Check identifiers**
- [21037](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21037) — View NB · RD
**Flow**
Message to **BTR** · RD
**Response per decision tree**
- `21037` → [E_0902](/en/referenz/202604/ebd/E_0902) · NB · Check plausibility of curtailed energy including the schedule share
**Write endpoint**
- Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out
Updates the existing transaction in the backend once the message has been created.
### NB rejects with reason and transmits a counterproposal
**Check identifiers**
- [21037](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21037) — View NB · RD
- [13022](/en/schnittstellen/202604/pruefi/MSCONS/PI_13022) — Redispatch 2.0 individual time series curtailed energy · RD
**Flow**
Message to **BTR** · RD
**Response per decision tree**
- `21037` → [E_0902](/en/referenz/202604/ebd/E_0902) · NB · Check plausibility of curtailed energy including the schedule share
**Write endpoint**
- Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out
Updates the existing transaction in the backend once the message has been created.
**Write endpoint**
- Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out
Updates the existing transaction in the backend with the data of the incoming message.
**Write endpoint**
- Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out
Updates the existing transaction in the backend with the data of the incoming message.
### Rejection incl. correction request
**Check identifiers**
- [21037](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21037) — View NB · RD
**Flow**
Message to **BTR** · RD
**Write endpoint**
- Transaction updated — [Update process data](/en/api/202604/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out
Updates the existing transaction in the backend once the message has been created.
Decision trees of this process
| EBD | Name |
|---|---|
| [E_0902](/referenz/202604/ebd/E_0902) | Check plausibility of curtailed energy including the schedule share |
## Process information
### First message
**BTR** sends “Curtailed energy and
schedule share per TR” (step 1). From here on, it is the turn of the party involved on this page.
*The source provides no use case profile for this process — objective, precondition and result are not recorded there.*
*The steps are the **possible** messages of this process, not a sequence — the source lists neither conditions nor alternatives. The small box on the step names the own view on the left: with **←** it receives, with **→** it sends. Collapsed steps run between other market partners.*
:::caution{title="Step sequence reconstructed"}
For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification.
:::
The connector table lists no write call for these steps. Derived from the process flow: the process begins for the own role with their message, so the transaction is created.
Applies to: [1](#schritt-1)
The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists.
Applies to: [4](#schritt-4), [5](#schritt-5)
For the check identifiers of these steps there is no test case in the test data set; the »Try it out« button of the write interface therefore offers no body.
Applies to: [1](#schritt-1), [2](#schritt-2), [3](#schritt-3), [4](#schritt-4), [5](#schritt-5), [6](#schritt-6)