# Transmission of price sheet NB to LF — LF view The NB transmits its electronic price sheet to the LF if the LF does not have the electronic price sheet or if at least one price component of the price sheet has changed. ## Process flow from the perspective of the LF \nSystem diagram: Übermittlung Preisblatt NB an LF — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n1. Preisblatt\n\nNB\n\nAS4\n27003\n\nAPERAK check: Z33\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\nkategorie = A\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\nkategorie = B\n"} gesamt={"\nSequence diagram: Übermittlung Preisblatt NB an LF — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\n1. Preisblatt\nAS4 · PI 27003\n\nCreate transaction\nCreate process data · kategorie = A\n\nUpdate transaction\nUpdate process data · kategorie = B\n"} titel="LF" /> ## Process steps ### Price sheet
**Check identifiers** - [27003](/en/schnittstellen/202604/pruefi/PRICAT/PI_27003) — Price sheets for NB services · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **APERAK checks** - `27003` → `Z33` — APERAK check: Is referenced message known ?
  3. **Write endpoint** - `kategorie = A` → 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.
  4. **Write endpoint** - `kategorie = B` → 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 with the data of the incoming message.
## Process information Wording of the consolidated version, profile ch. 3.4.4.1, p. 97.
  1. ### Preconditions - The EDIFACT communication between NB and LF has been established. - The LF does not have the current or updated price sheet of the NB.
  2. ### Results - The billing of another service can be created, or - the grid usage invoice can be created.
  3. ### Error case #### Result in the error case In the error cases, the price sheet is transmitted again. #### Error cases - Price sheet contains an error - Price sheet was not transmitted in the current version - Price sheet was not transmitted in full - Price sheet does not begin at 00:00 of a calendar day
  4. ### Further requirements Notes: - If the provisional grid fees of a year (valid from 1 January of the following year) are not corrected, they are applied automatically from 1 January of the following year and no renewed dispatch to LF takes place. - If the provisional grid fees of a year (valid from 1 January of the following year) are corrected, NB sends a new version valid as of 1 January of the following year to LF. - Price sheets are also to be transmitted to the final customer in its role as LF if, within grid usage settlement (incl. any dunning costs incurred in this connection), the final customer is itself the grid user (= grid user without an all-inclusive contract) and assumes the role of LF within the meaning of this process description, insofar as these provisions are applicable to it accordingly.
  5. ### First message **NB** sends “Price sheet” (step 1). From here on, it is the turn of the party involved on this page.
  6. ### Objective The LF has the electronic price sheet of the NB. In the case of grid transitions, the LF may have the price sheets.
## 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/NB/GPKE-Teil2-uebermittlung-preisblatt-nb-an-lf) — 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.*