# Reconciliation of the grid time series — NBB view The responsible NB transmits the NZR at BG level to the NB of the neighbouring BG and reconciles it with the neighbouring NB. If the reconciliation of the NZR between the two NB shows that a correction is needed, the necessary correction is carried out and the process starts again with the sending of the NZR to the NB of the neighbouring BG. ## Process flow from the perspective of the NB (NBB) \nSystem diagram: Abstimmung der Netzzeitreihe — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB (benachbart…\n\nMarket partner\n\n\n\n1. Übermittlung NZR\n\nNB (verantwortlicher…\n\nAS4\n13003\n\nLoad data for the incoming\ncheck\n\n\n2 read APIs called\n\nAPI\nlisted at the step\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n2. Übermittlung\nPrüfmitteilung\n\n\nNB (verantwortlicher…\n\nAS4\n21001\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Abstimmung der Netzzeitreihe — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB (benachbart…\n\n\nNB (verantwortlicher NB)\n\n\n1. Übermittlung NZR\nAS4 · PI 13003\n\nCreate transaction\nCreate process data\n\n2. Übermittlung Prüfmitteilung\nAS4 · PI 21001 · E_0040\nE_0040 — NZR prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="NBB" /> ## Process steps ### Transmission of NZR
**Check identifiers** - [13003](/en/schnittstellen/202604/pruefi/MSCONS/PI_13003) — Aggregated time series · AS4
**Flow**
  1. Message from **NB (responsible NB)** · AS4
  2. **Load data for the incoming check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read meter](/en/api/202604/backend-lesen/getcounterbasic#zahler-lesen) `GET /getCounterBasic` Try it
  3. **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.
### Transmission of validation notification
**Check identifiers** - [21001](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21001) — Status message · AS4
**Flow**
  1. Message to **NB (responsible NB)** · AS4
    **Response per decision tree** - `21001` → [E_0040](/en/referenz/202604/ebd/E_0040) · NB · Check NZR
  2. **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_0040](/referenz/202604/ebd/E_0040) | Check NZR |
## Process information Wording of the consolidated version, profile ch. 5.4.1, p. 50.
  1. ### Preconditions - The MaBiS-ZP for the NZR is activated at the neighboring NB. - The responsible NB has transmitted the grid load time series to the NB of the neighbouring BG on every working day by 12:00 at the latest, for the previous day or the previous days.
  2. ### Results - The agreed NZR is a basis for the balancing settlement of the BG. - The responsible NB is able to transmit the NZR to the BIKO with the identical version as it is held by the neighbouring NB.
  3. ### First message **NB (responsible NB)** sends “Transmission NZR” (step 1). From here on, it is the turn of the party involved on this page.
  4. ### Objective The neighboring NB has the same NZR in content as the responsible NB as the basis for balancing out its BG.
## Other views of the process The same process through the eyes of the other parties involved: the same steps, each read from their point of view. - [View NBV](/en/prozessdoku/202604/NB--NBV/MaBiS-abstimmung-der-netzzeitreihe) — responsible grid operator · market role NB *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.* 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) 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)