# Excess/shortfall quantity settlement between NB and MGV — NB view ## Process flow from the perspective of the NB \nSystem diagram: Mehr-/Mindermengenabrechnung zwischen NB und MGV — view of NB\n\n\nCustomer backend system\n\nMACO APP · NB\n\nMarket partner\n\n\n\n1. Aggregierte Mehr-/\nMindermengenmeldung\n\nMGV\n\nAS4\n70095, 70096\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Aggregierte Mehr-/\nMindermengenrechnung\n\n\nMGV\n\nAS4\n31007, 31008\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n3. Antwort\n\n\nMGV\n\nAS4\n33001, 33002\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n5. Zahlungsavis\n\n\nMGV\n\nAS4\n33001\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n6. Storno\n\n\nMGV\n\nAS4\n31004\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n7. Antwort\n\n\nMGV\n\nAS4\n33001, 33002\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Mehr-/Mindermengenabrechnung zwischen NB und MGV — view of NB\n\n\nBackend (customer)\n\n\nMACO APP · NB\n\n\nMGV\n\n\n1. Aggregierte Mehr-/ Mindermengenmeldung\nAS4 · PI 70095, 70096\n\nUpdate transaction\nUpdate process data\n\n2. Aggregierte Mehr-/ Mindermengenrechnung\nAS4 · PI 31007, 31008\n\nUpdate transaction\nUpdate process data\n\n3. Antwort\nAS4 · PI 33001, 33002 · E_0802\nE_0802 — aggregierte MMM-Rechnung prüfen\n\nUpdate transaction\nUpdate process data\n\n5. Zahlungsavis\nAS4 · PI 33001\n\nUpdate transaction\nUpdate process data\n\n6. Storno\nAS4 · PI 31004\n\nUpdate transaction\nUpdate process data\n\n7. Antwort\nAS4 · PI 33001, 33002 · E_0806\nE_0806 — Prüfen, ob Antwort auf Stornierung erforderlich\n\nUpdate transaction\nUpdate process data\n"} titel="NB" /> ## Process steps ### Aggregated excess/shortfall quantity notification
**Check identifiers** - `70095` — Surplus/shortfall quantity notification SLP · AS4 - `70096` — Surplus/shortfall quantity notification RLP · AS4
**Flow**
  1. Message to **MGV** · 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.
### Aggregated excess/shortfall quantity invoice
**Check identifiers** - [31007](/en/schnittstellen/202610/pruefi/INVOIC/PI_31007) — Aggreg. MMM invoice · AS4 - [31008](/en/schnittstellen/202610/pruefi/INVOIC/PI_31008) — Aggreg. MMM self-issued invoice · AS4
**Flow**
  1. Message to **MGV** · 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.
### Response
**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 **MGV** · AS4
    **Response per decision tree** - `33002` → [E_0802](/en/referenz/202610/ebd/E_0802) · Check aggregated MMM invoice
  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.
### Remittance advice
**Check identifiers** - [33001](/en/schnittstellen/202610/pruefi/REMADV/PI_33001) — Confirmation · AS4
**Flow**
  1. Message from **MGV** · 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.
### Cancellation
**Check identifiers** - [31004](/en/schnittstellen/202610/pruefi/INVOIC/PI_31004) — Cancellation invoice · AS4
**Flow**
  1. Message to **MGV** · 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.
### Response
**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 **MGV** · AS4
    **Response per decision tree** - `33002` → [E_0806](/en/referenz/202610/ebd/E_0806) · MGV · Check whether a response to the cancellation is required
  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.
Decision trees of this process | EBD | Name | |---|---| | [E_0802](/referenz/202610/ebd/E_0802) | Check aggregated MMM invoice | | [E_0806](/referenz/202610/ebd/E_0806) | Check whether a response to the cancellation is required |
## Process information
  1. ### First message The party involved on this page sends this itself: “Aggregated surplus/ shortfall quantity notification” to **MGV** (step 1).
*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: [1](#schritt-1), [2](#schritt-2) 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: [3](#schritt-3), [5](#schritt-5), [7](#schritt-7) 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), [6](#schritt-6)