# Transmission of the delivery note for grid usage settlement — NB view Before the grid usage invoice is sent, the NB transmits to the LF the underlying values of the grid usage invoice at the level of the market location. Depending on the trigger, this can be a periodic or an event-driven dispatch of a delivery note. If values relevant to the delivery note change for the time period covered by a delivery note, the delivery note already sent that contains the corresponding billing energy quantity/demand value must be cancelled by the NB. A new delivery note with a corrected billing energy quantity and, where applicable, corrected demand values must then be sent to the LF. The delivery note contains the energy quantity/quantities and the annual maximum demand that occurred, which are billed on the associated grid usage invoice. If only the billing energy quantity or the demand value has to be corrected, the new delivery note must contain the still correct, uncorrected value. ## Process flow from the perspective of the NB \nSystem diagram: Übermittlung des Lieferscheins zur Netznutzungsabrechnung — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\nProcess trigger received\n\n2 alternative events\n\nAPI\n\n1. Lieferschein\n\n\nLF\n\nAS4\n13016, 13019\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Rückmeldung auf\nLieferschein\n\n\nLF\n\nAS4\n21035\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\n2 alternative events\n\nAPI\n\n3. Widerspruch gegen\nAblehnung\n\n\nLF\n\nAS4\n29002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n4. Stornierung Lieferschein\n\n\nLF\n\nAS4\n13006\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Übermittlung des Lieferscheins zur Netznutzungsabrechnung — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nLF\n\n\n2 alternative events\nTrigger event\n\n1. Lieferschein\nAS4 · PI 13016, 13019\n\nUpdate transaction\nUpdate process data\n\n2. Rückmeldung auf Lieferschein\nAS4 · PI 21035 · E_0456\nE_0456 — Lieferschein prüfen\n\nUpdate transaction\nUpdate process data\n\n2 alternative events\nTrigger event\n\n3. Widerspruch gegen Ablehnung\nAS4 · PI 29002 · E_0458\nE_0458 — Weitere Bearbeitung prüfen\n\nUpdate transaction\nUpdate process data\n\n4. Stornierung Lieferschein\nAS4 · PI 13006\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Delivery note
**Check identifiers** - [13016](/en/schnittstellen/202604/pruefi/MSCONS/PI_13016) — Energy quantity and max. power (electricity) · AS4 - [13019](/en/schnittstellen/202604/pruefi/MSCONS/PI_13019) — Energy quantity (electricity) · AS4
**Flow**
  1. **Process trigger** - [`START_ERHEBUNG_MESSWERTE`](/en/api/202604/ausloeser-nb/start-erhebung-messwerte) \"\n ],\n \"lokationsId\": \"\"\n }\n ],\n \"ZAEHLER\": [\n {\n \"zaehlernummer\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"anfrageReferenz\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"lokationsTyp\": \"\",\n \"sparte\": \"\",\n \"typ\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_ERHEBUNG_MESSWERTE\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_VERSAND_LIEFERSCHEIN`](/en/api/202604/ausloeser-nb/start-versand-lieferschein) \"\n ],\n \"lokationsId\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"anfrageReferenz\": \"\",\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_LIEFERSCHEIN\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with one of these events.
  2. Message to **LF** · AS4
  3. **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.
### Response message on delivery note
**Check identifiers** - [21035](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21035) — Response re. supply point · AS4
**Flow**
  1. Message from **LF** · AS4
    **Response per decision tree** - `21035` → [E_0456](/en/referenz/202604/ebd/E_0456) · LF · Check delivery note
  2. **APERAK checks** - `21035` → `Z33`
  3. **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.
### Objection to rejection
**Check identifiers** - [29002](/en/schnittstellen/202604/pruefi/COMDIS/PI_29002) — Rejection of IFTSTA · AS4
**Flow**
  1. **Process trigger** - [`START_VERSAND_COMDIS`](/en/api/202604/ausloeser-nb/start-versand-comdis) \",\n \"hinweis\": \"\"\n },\n \"nummer\": \"\",\n \"typ\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_COMDIS\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren - [`START_WIEDERSPRUCH_ABLEHNUNG`](/en/api/202604/ausloeser-nb/start-wiederspruch-ablehnung) \",\n \"hinweis\": \"\"\n },\n \"nummer\": \"\",\n \"typ\": \"\"\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_WIEDERSPRUCH_ABLEHNUNG\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with one of these events.
  2. Message to **LF** · AS4
    **Response per decision tree** - `29002` → [E_0458](/en/referenz/202604/ebd/E_0458) · Check further processing
  3. **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.
### Cancellation of delivery note
**Check identifiers** - [13006](/en/schnittstellen/202604/pruefi/MSCONS/PI_13006) — Meter reading value cancellation · AS4
**Flow**
  1. Message to **LF** · AS4
  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_0456](/referenz/202604/ebd/E_0456) | Check delivery note | | [E_0458](/referenz/202604/ebd/E_0458) | Check further processing |
## Process information Wording of the consolidated version, profile ch. 3.2.3.1, pp. 84–86.
  1. ### Preconditions - This is a consuming market location. - The LF is the payer of the grid usage. - Values from MSB are available. - The energy and demand values measured so far, in the case of an intra-year allocation start and where the market location is billed with an energy and demand price, have been transmitted by NB to LF. - The billing of the grid usage is to be issued. - If there is a need to apply a metering time period definition of NB with the metering time period usage purpose “grid usage”, a corresponding configuration must have been set up on time and successfully via the use cases in the chapter “Order placement of a configuration” (GPKE Part 3). This applies only if the ordered setup of a configuration falls within the billing-relevant time period of the delivery note to be created. - The information required for the grid usage settlement has been transmitted via the use case „[Billing data grid usage settlement](/en/prozessdoku/202604/NB/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung)“.
  2. ### Results A grid usage invoice can be issued.
  3. ### Error case #### Result in the error case A delivery note has to be transmitted again.
  4. ### Further requirements It must be possible to assign and check a line item in the grid usage invoice unambiguously in time by means of one line item or by adding up several line items from the delivery note. The NB has to take this into account when building the delivery note.
  5. ### Trigger - The end of the billing period has been reached or - an end of supply process has been carried out or - there is a change of the payer of the grid usage or - a grid operator change has been carried out or - the switch between the base price/energy price model and the energy price/demand price model has been carried out.
  6. ### First message The party involved on this page is itself the sender of: „Delivery note“ to **LF** (step 1).
  7. ### Objective The LF has the delivery note of the billing energy quantities/demand values, which forms one of the bases for the grid usage settlement.
## 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 LF](/en/prozessdoku/202604/LF/GPKE-Teil2-uebermittlung-des-lieferscheins-zur-netznutzungsabrechnung) — LF *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.*