# Exchange of the supplier clearing list between ÜNB and LF (incl. subscription) — LF view The LF requests or, where required, subscribes to the LF-CL from the ÜNB. The ÜNB sends the requested LF-CL to the LF. The LF has the option of plausibility-checking the LF-SZR (category B) against the data of the LF-CL. The LF can give a response message to the LF-CL received from the ÜNB. This response message is made electronically in standardised form by means of a correction list for the LF-CL. Further steps for clarification take place via other communication channels. A LF can request the LF-CL immediately after receiving the LF-SZR (category B). Alternatively, the LF can apply for the list to be sent regularly (subscription). An LF-CL can be requested for every version of an LF-SZR (category B) that has been sent. An LF-CL is created for every ZRT and can also be requested separately. ## Process flow from the perspective of the LF \nSystem diagram: Austausch der Lieferantenclearingliste zwischen ÜNB und LF (inkl. Abonnierung) — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n1. Anforderung der LF-CL\n\nÜNB\n\nAS4\n17202\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Übermittlung der LF-CL\n\n\nÜNB\n\nAS4\n55065\n\nAPERAK check: Z33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\n3. Rückmeldung zur LF-CL\n\n\nÜNB\n\nAS4\n55066\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Austausch der Lieferantenclearingliste zwischen ÜNB und LF (inkl. Abonnierung) — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nÜNB\n\n\n1. Anforderung der LF-CL\nAS4 · PI 17202\n\nUpdate transaction\nUpdate process data\n\n2. Übermittlung der LF-CL\nAS4 · PI 55065\n\nCreate transaction\nCreate process data\n\n3. Rückmeldung zur LF-CL\nAS4 · PI 55066 · E_0004, E_0014\nE_0004 — Marktlokationen mit LF-CL abgleichen\nE_0014 — Marktlokationen mit LF-CL abgleichen\n\nUpdate transaction\nUpdate process data\n"} titel="LF" /> ## Process steps ### Request for the LF-CL
**Check identifiers** - [17202](/en/schnittstellen/202604/pruefi/ORDERS/PI_17202) — Req. supplier clearing list · AS4
**Flow**
  1. Message to **ÜNB** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Transmission of the LF-CL
**Check identifiers** - [55065](/en/schnittstellen/202604/pruefi/UTILMD/PI_55065) — Supplier clearing list · AS4
**Flow**
  1. Message from **ÜNB** · AS4
  2. **APERAK checks** - `55065` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - Transaction created — [Create process data](/en/api/202604/backend-schreiben-lf/createprocessdata#prozessdaten-erstellen) `POST /createProcessData` Try it out Creates a new transaction in the backend with the data of the incoming message.
### Response message on the LF-CL
**Check identifiers** - [55066](/en/schnittstellen/202604/pruefi/UTILMD/PI_55066) — Correction list for supplier clearing list · AS4
**Flow**
  1. Message to **ÜNB** · AS4
    **Response per decision tree** - `55066` → [E_0004](/en/referenz/202604/ebd/E_0004) · LF · Reconcile market locations with LF-CL - `55066` → [E_0014](/en/referenz/202604/ebd/E_0014) · LF · Reconcile market locations with LF-CL
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202604/backend-schreiben-lf/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_0004](/referenz/202604/ebd/E_0004) | Reconcile market locations with LF-CL | | [E_0014](/referenz/202604/ebd/E_0014) | Reconcile market locations with LF-CL |
## Process information Wording of the consolidated version, profile ch. 8.5.1, pp. 96–97.
  1. ### Preconditions For a single request: - The LF has the LF-SZR (category B) from the ÜNB. - The LF knows the MaBiS-ZP of the LF-SZR (category B). In the case of a subscription: - The LF knows the MaBiS-ZP of the LF-SZR (category B).
  2. ### Further requirements If a subscription is requested again while a subscription already exists, from the point in time of receipt the recipient of the subscription refers to the new subscription in all LF-CL resulting from it.
  3. ### First message The party involved on this page sends this itself: “Request for the LF-CL” to **ÜNB** (step 1).
  4. ### Objective The LF has the requested LF-CL. If the LF-CL has been subscribed to by the LF, the LF is registered with the ÜNB as a subscriber of the LF-CL. Where applicable, the ÜNB has the response message of the LF on the LF-CL that was sent.
## 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-lieferantenclearingliste-zwischen-uenb-und-lf-inkl-abonnierung) — Ü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 source does not yet name the event that triggers these steps. 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), [3](#schritt-3)