# Grid usage settlement — LF view The process describes the communication between NB and LF on the billing of grid usage and, where applicable, the automated complaint case. An invoice correction always comprises a cancellation invoice and a new invoice. In the cases listed below in particular, an annual invoice can be corrected or supplemented without this being done by cancellation: - Change of the concession levy by submitting an attestation: check of the limit price comparison according to KAV - Correction of the electricity grid fees on the basis of an individual agreement for atypical and energy-intensive grid usage in accordance with StromNEV - Correction of the electricity grid fees on the basis of an individual agreement for singular grid usage in accordance with StromNEV - KWKG levy - Offshore grid levy. In these cases a separate, correspondingly marked invoice can be issued in which the fees paid in excess or short for the billing year are corrected and charged in accordance with the audit certificate, the individual agreement or the evidence. This invoice must refer unambiguously to the annual invoice whose item or items it corrects. ## Process flow from the perspective of the LF \nSystem diagram: Netznutzungsabrechnung — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n1. Netznutzungsrechnung\n\nNB\n\nAS4\n31001, 31002\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nAPERAK check: Z10, Z25,\nZ26\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_VERSAND_ANTWORT\n_NNA\n\nAPI\n\n2. Antwort\n\n\nNB\n\nAS4\n33001, 33003, 33004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Mitteilung, dass die\nursprüngliche\nNetznutzungsrechnung kor…\n\n\nNB\n\nAS4\n29001\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_VERSAND_ANTWORT\n_NNA\n\nAPI\n\n4. Antwort\n\n\nNB\n\nAS4\n33001, 33003, 33004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Storno der ursprünglichen\nRechnung\n\n\nNB\n\nAS4\n31004\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nProcess trigger received\n\n\nSTART_VERSAND_ANTWORT\n_NNA\n\nAPI\n\n6. Antwort\n\n\nNB\n\nAS4\n33001, 33002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Netznutzungsabrechnung — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nNB\n\n\n1. Netznutzungsrechnung\nAS4 · PI 31001, 31002\n\nCreate transaction\nCreate process data\n\nSTART_VERSAND_ANTWORT_NNA\nTrigger event\n\n2. Antwort\nAS4 · PI 33001, 33003, 33004 · E_0406\nE_0406 — Netznutzungsrechnung prüfen\n\nUpdate transaction\nUpdate process data\n\n3. Mitteilung, dass die ursprüngliche Netznutzun…\nAS4 · PI 29001 · E_0452\nE_0452 — Nicht-Zahlungsavise prüfen\n\nUpdate transaction\nUpdate process data\n\nSTART_VERSAND_ANTWORT_NNA\nTrigger event\n\n4. Antwort\nAS4 · PI 33001, 33003, 33004 · E_0407\nE_0407 — erneut Netznutzungsabrechnung prüfen\n\nUpdate transaction\nUpdate process data\n\n5. Storno der ursprünglichen Rechnung\nAS4 · PI 31004\n\nUpdate transaction\nUpdate process data\n\nSTART_VERSAND_ANTWORT_NNA\nTrigger event\n\n6. Antwort\nAS4 · PI 33001, 33002 · E_0459\nE_0459 — Prüfen, ob Antwort auf Stornierung erforderlich\n\nUpdate transaction\nUpdate process data\n"} titel="LF" /> ## Process steps ### Grid usage invoice
**Check identifiers** - [31001](/en/schnittstellen/202604/pruefi/INVOIC/PI_31001) — Instalment invoice · AS4 - [31002](/en/schnittstellen/202604/pruefi/INVOIC/PI_31002) — NN invoice · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **Load data for the incoming check** - [Read market location](/en/api/202604/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **APERAK checks** - `31001`, `31002` → `Z10` — APERAK check: Is location known ? - `31001`, `31002` → `Z25` - `31001`, `31002` → `Z26`
  4. **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
**Check identifiers** - [33001](/en/schnittstellen/202604/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33003](/en/schnittstellen/202604/pruefi/REMADV/PI_33003) — Electricity refusal header and total · AS4 - [33004](/en/schnittstellen/202604/pruefi/REMADV/PI_33004) — Electricity refusal line item · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_ANTWORT_NNA`](/en/api/202604/ausloeser-lf/start-versand-antwort-nna) \",\n \"avisTyp\": \"\",\n \"positionen\": [\n \"\"\n ],\n \"zuZahlen\": {\n \"waehrung\": \"\",\n \"wert\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"nachrichtendatum\": \"\",\n \"pruefidentifikator\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_ANTWORT_NNA\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · AS4
    **Response per decision tree** - `33003` → [E_0406](/en/referenz/202604/ebd/E_0406) · LF · Check grid usage invoice
  3. **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.
### Notification that the original grid usage invoice was correct
**Check identifiers** - [29001](/en/schnittstellen/202604/pruefi/COMDIS/PI_29001) — Rejection of REMADV · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `29001` → [E_0452](/en/referenz/202604/ebd/E_0452) · Check non-payment advices
  2. **APERAK checks** - `29001` → `Z33` — APERAK check: Is referenced message known ?
  3. **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 with the data of the incoming message.
### Response
**Check identifiers** - [33001](/en/schnittstellen/202604/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33003](/en/schnittstellen/202604/pruefi/REMADV/PI_33003) — Electricity refusal header and total · AS4 - [33004](/en/schnittstellen/202604/pruefi/REMADV/PI_33004) — Electricity refusal line item · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_ANTWORT_NNA`](/en/api/202604/ausloeser-lf/start-versand-antwort-nna) \",\n \"avisTyp\": \"\",\n \"positionen\": [\n \"\"\n ],\n \"zuZahlen\": {\n \"waehrung\": \"\",\n \"wert\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"nachrichtendatum\": \"\",\n \"pruefidentifikator\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_ANTWORT_NNA\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · AS4
    **Response per decision tree** - `33003` → [E_0407](/en/referenz/202604/ebd/E_0407) · LF · Check grid usage settlement again
  3. **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.
### Cancellation of the original invoice
**Check identifiers** - [31004](/en/schnittstellen/202604/pruefi/INVOIC/PI_31004) — Cancellation invoice · AS4
**Flow**
  1. Message from **NB** · AS4
  2. **APERAK checks** - `31004` → `Z33` — APERAK check: Is referenced message known ?
  3. **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 with the data of the incoming message.
### Response
**Check identifiers** - [33001](/en/schnittstellen/202604/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202604/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. **Prozessauslöser** [`START_VERSAND_ANTWORT_NNA`](/en/api/202604/ausloeser-lf/start-versand-antwort-nna) \",\n \"avisTyp\": \"\",\n \"positionen\": [\n \"\"\n ],\n \"zuZahlen\": {\n \"waehrung\": \"\",\n \"wert\": \"\"\n }\n }\n ]\n },\n \"transaktionsdaten\": {\n \"absender\": {\n \"rollencodenummer\": \"\"\n },\n \"empfaenger\": {\n \"marktrolle\": \"\",\n \"rollencodenummer\": \"\"\n },\n \"kategorie\": \"\",\n \"nachrichtendatum\": \"\",\n \"pruefidentifikator\": \"\",\n \"sparte\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_VERSAND_ANTWORT_NNA\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. Message to **NB** · AS4
    **Response per decision tree** - `33002` → [E_0459](/en/referenz/202604/ebd/E_0459) · LF · Check whether a response to the cancellation is required
  3. **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_0406](/referenz/202604/ebd/E_0406) | Check grid usage invoice | | [E_0407](/referenz/202604/ebd/E_0407) | Check grid usage settlement again | | [E_0452](/referenz/202604/ebd/E_0452) | Check non-payment advices | | [E_0459](/referenz/202604/ebd/E_0459) | Check whether a response to the cancellation is required |
## Process information Wording of the consolidated version, profile ch. 3.3.1, pp. 87–89.
  1. ### Preconditions - This is a consuming market location. - The current grid usage fees have been published by NB and were transmitted to LF in the price sheet grid usage within the use case „[Transmission of price sheet NB to LF](/en/prozessdoku/202604/LF/GPKE-Teil2-uebermittlung-preisblatt-nb-an-lf)“ - The LF is assigned to the market location. - The grid usage invoice contains only items that - are contained as an article ID in the grid usage price sheet or - were transmitted in advance as a surcharge/discount on an article ID of the grid usage price sheet of the NB within the use case “[Billing data grid usage settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung)”. - The information required for the grid usage settlement has been transmitted via the use case „[Billing data grid usage settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung)“. - The billing of the grid usage is due (cyclical invoice, partial payment invoice or final invoice, or event-driven). - The delivery note was transmitted beforehand (except for instalment invoices) and, in the case of a rejection with a specific reason by the LF, the complaint was refuted by the NB. - The LF is the payer of the grid usage.
  2. ### Results The LF will pay the grid usage invoice issued by the NB.
  3. ### Error case #### Error cases - The grid usage invoice contains items that are not - are contained as an article ID in the grid usage price sheet of the NB or - were transmitted in advance as a surcharge/discount on an article ID of the grid usage price sheet of the NB within the use case “[Billing data grid usage settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung)”. - The information required for the grid usage settlement has not been transmitted via the use case „[Billing data grid usage settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung)“. - The information required for the grid usage settlement has been transmitted via the use case „[Billing data grid usage settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung)“, but was not taken into account accordingly in the grid usage invoice. - The billing energy quantities/demand values of the grid usage invoice do not match those of the delivery note. - The price of an article ID stated in the grid usage invoice does not match the price of the corresponding article ID stated in the grid usage price sheet of the NB.
  4. ### Further requirements - The case of a grid usage invoice that has been complained about or turns out to be incorrect (the cancellation of the original invoice is carried out either without a prior complaint by the LF or on the basis of a prior complaint by the LF) forms part of the standard process and, apart from clarifications, must be handled fully automatically. In the event of a complaint, the so-called “all-or-nothing principle” applies, according to which an invoice is either accepted in full as correct or rejected in full. If a grid usage invoice turns out to be incorrect (the cancellation of the original invoice is carried out either without a prior complaint by the LF or on the basis of a prior complaint by the LF), the corresponding delivery note must also be cancelled in this context and a corrected delivery note must be transmitted to the LF before the new invoice is sent, provided a correction of the billing energy quantities/demand values is necessary. The processes to be handled in the event of a conflict as part of receivables management or the dunning procedure are not shown and are to be resolved bilaterally. - The grid usage invoice can be unambiguously assigned to the previously exchanged delivery note via a reference. - The final invoice/annual invoice shows all partial payment invoices of the billing period contained in it in a comprehensible manner, stating the invoice number. - An item in the grid usage invoice must be uniquely assignable in time and verifiable by means of one item or by adding up several items from the delivery note.
  5. ### First message **NB** sends “Grid usage invoice” (step 1). From here on, it is the turn of the party involved on this page.
  6. ### Objective The NB has been informed that the LF accepts the grid usage invoice.
## 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-netznutzungsabrechnung) — 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.* 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: [5](#schritt-5)