# Capacity billing at exit points to final consumers — NB view ## Process flow from the perspective of the NB \nSystem diagram: Kapazitätsabrechnung an Ausspeisepunkten zu Letztverbrauchern — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1a. Kapazitätsrechnung\n\nKN\n\nAS4\n31010\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3a. Zahlungsavise\n\n\nKN\n\nAS4\n33001\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3b. Zahlungsablehnung\n\n\nKN\n\nAS4\n33002\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n7b. Kapazitätsabrechnung\nwar fehlerhaft. Bei\nAblehnung der Kapa…\n\n\nTK (KN)\n\nAS4\n31004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n9. Zahlungsavise\n\n\nKN\n\nAS4\n33001, 33002\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Kapazitätsabrechnung an Ausspeisepunkten zu Letztverbrauchern — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nKN\n\n\nTK (KN)\n\n\n1a. Kapazitätsrechnung\nAS4 · PI 31010\n\nUpdate transaction\nUpdate process data\n\n3a. Zahlungsavise\nAS4 · PI 33001\n\nUpdate transaction\nUpdate process data\n\n3b. Zahlungsablehnung\nAS4 · PI 33002\n\nUpdate transaction\nUpdate process data\n\n7b. Kapazitätsabrechnung war fehlerhaft. Bei Able…\nAS4 · PI 31004\n\nUpdate transaction\nUpdate process data\n\n9. Zahlungsavise\nAS4 · PI 33001, 33002\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Capacity invoice
**Check identifiers** - [31010](/en/schnittstellen/202610/pruefi/INVOIC/PI_31010) — Capacity invoice · AS4
**Flow**
  1. Message to **KN** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Remittance advices
**Check identifiers** - [33001](/en/schnittstellen/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4
**Flow**
  1. Message from **KN** · AS4
  2. **APERAK checks** - `33001` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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.
### Payment rejection
**Check identifiers** - [33002](/en/schnittstellen/202610/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. Message from **KN** · AS4
  2. **APERAK checks** - `33002` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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.
### Capacity billing was incorrect. Where the capacity billing is rejected by TK (KN) (process step No. 3 on payment rejection) and the check result of the NB (process step No. 4) shows that the original capacity billing was not correct and/or b) where relevant changes occur subsequently (process steps No. 5 to 8): the NB sends a cancellation invoice to TK (KN) and sends a new capacity billing.
**Check identifiers** - [31004](/en/schnittstellen/202610/pruefi/INVOIC/PI_31004) — Cancellation invoice · AS4
**Flow**
  1. Message to **TK (KN)** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-nb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Remittance advices
**Check identifiers** - [33001](/en/schnittstellen/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4 - [33002](/en/schnittstellen/202610/pruefi/REMADV/PI_33002) — Refusal · AS4
**Flow**
  1. Message from **KN** · AS4
  2. **APERAK checks** - `33001`, `33002` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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.
## Process information
  1. ### First message The party involved on this page is itself the sender of: „Capacity invoice“ to **KN** (step 1a).
*The source provides no use case profile for this process — objective, precondition and result are not recorded there.* *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 numbers are those of the source; where one is missing, it is missing there.* :::caution{title="Step sequence reconstructed"} For this process, the BNetzA consolidated version carries no sequence diagram. The steps are reconstructed from the BDEW check identifier table: grouped by the designation, ordered by the process step. The method agrees with the consolidated version in 200 of 200 cases that can be cross-checked — the individual line is nevertheless not editorially reviewed. Check it against the rulebook before adopting it into an implementation specification. ::: The source does not yet name the event that triggers these steps. Applies to: [1a](#schritt-1a) The connector table lists no write call for these steps. Derived from the process flow: the own role was already involved in this process, so the transaction already exists. Applies to: [3a](#schritt-3a), [3b](#schritt-3b), [9](#schritt-9) 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: [1a](#schritt-1a), [7b](#schritt-7b)