# Exchange of the delta time series carry-over list from ÜNB to NB — NB view The NB receives the DZÜ list from the ÜNB. ## Process flow from the perspective of the NB \nSystem diagram: Austausch der Deltazeitreihenübertrag-Liste von ÜNB an NB — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Übermittlung der\nDZÜ-Liste\n\nÜNB\n\nAS4\n55223\n\nAPERAK check: Z10, Z16,\nZ17, Z18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Austausch der Deltazeitreihenübertrag-Liste von ÜNB an NB — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nÜNB\n\n\n1. Übermittlung der DZÜ-Liste\nAS4 · PI 55223\n\nCreate transaction\nCreate process data\n"} titel="NB" /> ## Process steps ### Transmission of the DZÜ list
**Check identifiers** - [55223](/en/schnittstellen/202604/pruefi/UTILMD/PI_55223) — DZÜ list · AS4
**Flow**
  1. Message from **ÜNB** · AS4
  2. **APERAK checks** - `55223` → `Z10` - `55223` → `Z16` - `55223` → `Z17` - `55223` → `Z18`
  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.
## Process information Wording of the consolidated version, profile ch. 12.4.1, p. 170.
  1. ### Preconditions - The ÜNB has determined a DZÜ. - The NB knows the MaBiS-ZP of the DZÜ.
  2. ### Results - The NB can check the plausibility of the DZÜ list on the basis of its data.
  3. ### First message **ÜNB** sends “Transmission of the DZÜ list” (step 1). From here on, it is the turn of the party involved on this page.
  4. ### Objective The NB has the DZÜ list from the ÜNB.
## 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 ÜNB](/en/prozessdoku/202604/UENB/MaBiS-austausch-der-deltazeitreihenuebertrag-liste-von-uenb-an-nb) — ÜNB · market role UENB *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)