# Contract termination of metering point operation — MSBN view On behalf of the AN or ANN, the MSBN terminates the metering point operation contract existing for the named metering location. Any termination date in the future (also within a month) can be specified in the contract termination. The termination date can - to a fixed point in time of 00:00 or - to the next possible point in time of 00:00. The termination date is the point in time at which the service to be terminated is to end. The MSBA checks the contract termination and informs the MSBN of the result. The following rules apply: - If MSBN has terminated to a fixed point in time and this is not confirmed by MSBA, MSBA states the next possible point in time at which a contract termination can take effect and the notice period in the rejection. - If MSBN has terminated to the next possible point in time, MSBA confirms the contract termination stating this point in time. - If MSBA has already received an effective contract termination (from a MSBN or the AN or ANN), the corresponding constellations are described in Chapter 2.2.3 “Response MSBA in the case of the contract termination of a contract that has already been effectively terminated”. ## Process flow from the perspective of the MSB (MSBN) \nSystem diagram: Kündigung Messstellenbetrieb — view of MSB\n\n\nCustomer backend system\n\nMACO APP · MSB (entsprich…\n\nMarket partner\n\n\n\nProcess trigger received\n\nSTART_KUENDIGUNG_MSB\n\nAPI\n\nLoad data for processing\n\n\n5 read APIs called\n\nAPI\nlisted at the step\n\n1. Kündigung\n\n\nMSB (entspricht MSBA…\n\nAS4\n55039\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Antwort der Kündigung\n\n\nMSB (entspricht MSBA…\n\nAS4\n55040, 55041\n\nAPERAK check: Z33\n\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\nLoad data for processing\n\n\n5 read APIs called\n\nAPI\nlisted at the step\n"} gesamt={"\nSequence diagram: Kündigung Messstellenbetrieb — view of MSB\n\n\nBackend (customer)\n\n\nMACO APP · MSB (entsprich…\n\n\nMSB (entspricht MSBA am O…\n\n\nSTART_KUENDIGUNG_MSB\nTrigger event\n\n1. Kündigung\nAS4 · PI 55039\n\nUpdate transaction\nUpdate process data\n\n2. Antwort der Kündigung\nAS4 · PI 55040, 55041 · E_0200\nE_0200 — Kündigung Messstellenbetrieb prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="MSBN" /> ## Process steps ### Contract termination
**Check identifiers** - [55039](/en/schnittstellen/202610/pruefi/UTILMD/PI_55039) — Contract termination MSB · AS4
**Flow**
  1. **Prozessauslöser** [`START_KUENDIGUNG_MSB`](/en/api/202610/ausloeser-msb/start-kuendigung-msb) \"\n ]\n }\n ]\n },\n \"transaktionsdaten\": {\n \"pruefidentifikator\": \"\"\n },\n \"zusatzdaten\": {\n \"eventname\": \"START_KUENDIGUNG_MSB\",\n \"prozessId\": \"\"\n }\n}"} security={[{"bearer": []}]}>Ausprobieren The backend triggers this step with this event.
  2. **Load data for processing** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it - [Read metering location](/en/api/202610/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it - [Read metering point operation contract](/en/api/202610/backend-lesen/getmeasuringpointoperationcontractbasic#messstellenbetriebsvertrag-lesen) `GET /getMeasuringPointOperationContractBasic` Try it - [Read grid usage contract](/en/api/202610/backend-lesen/getgridusagecontractbasic#netznutzungsvertrag-lesen) `GET /getGridUsageContractBasic` Try it - [Read meter](/en/api/202610/backend-lesen/getcounterbasic#zahler-lesen) `GET /getCounterBasic` Try it
  3. Message to **MSB (corresponds to MSBA at the metering location object)** · AS4
  4. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Response to the contract termination
**Check identifiers** - [55040](/en/schnittstellen/202610/pruefi/UTILMD/PI_55040) — Confirmation contract termination MSB · AS4 - [55041](/en/schnittstellen/202610/pruefi/UTILMD/PI_55041) — Rejection contract termination MSB · AS4
**Flow**
  1. Message from **MSB (corresponds to MSBA at the metering location object)** · AS4
    **Response per decision tree** - `55040`, `55041` → [E_0200](/en/referenz/202610/ebd/E_0200) · Check contract termination of metering point operation
  2. **APERAK checks** - `55040`, `55041` → `Z33`
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-msb/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend with the data of the incoming message.
  4. **Load data for processing** - [Read metering location](/en/api/202610/backend-lesen/getmeterlocationbasic#messlokation-lesen) `GET /getMeterLocationBasic` Try it - [Read metering point operation contract](/en/api/202610/backend-lesen/getmeasuringpointoperationcontractbasic#messstellenbetriebsvertrag-lesen) `GET /getMeasuringPointOperationContractBasic` Try it - [Read grid usage contract](/en/api/202610/backend-lesen/getgridusagecontractbasic#netznutzungsvertrag-lesen) `GET /getGridUsageContractBasic` Try it - [Read meter](/en/api/202610/backend-lesen/getcounterbasic#zahler-lesen) `GET /getCounterBasic` Try it - [Read energy supply contract](/en/api/202610/backend-lesen/getenergysupplycontractbasic#energieliefervertrag-lesen) `GET /getEnergySupplyContractBasic` Try it
Decision trees of this process | EBD | Name | |---|---| | [E_0200](/referenz/202610/ebd/E_0200) | Check contract termination of metering point operation |
## Process information Wording of the consolidated version, profile ch. 2.2.1, pp. 18–19.
  1. ### Preconditions The MSBN holds the power of attorney of the AN or ANN to carry out the contract termination on its behalf.
  2. ### Results - Confirmation of the contract termination: - Immediately upon confirmation of the contract termination towards the MSBN, the MSBA is obliged to also trigger the use case „[End of metering point operation](/en/prozessdoku/202610/MSB--GMSB/WiM-Teil1-ende-messstellenbetrieb)“ towards the NB. - If the transmission of values to ESA is carried out, MSBA ends the transmission of values to ESA. - Rejection of the contract termination: MSBA does not regard the metering point operation contract as validly terminated.
  3. ### Further requirements - Notwithstanding the option available to the AN or ANN at any time to terminate its metering point operation contract in writing, MSBA may not reject a contract termination notified in accordance with this use case solely by invoking non-compliance with a contractually agreed form. In this case it must also accept and process a contract termination in electronic form using this use case. Note: - The use case does not cover the case in which the AN or ANN itself terminates the metering point operation contract with the MSBA. - If the AN or ANN terminates the contract itself in advance, MSBA must trigger the use case “[End of metering point operation](/en/prozessdoku/202610/MSB--GMSB/WiM-Teil1-ende-messstellenbetrieb)” towards NB immediately upon drafting the termination confirmation to the AN or ANN.
  4. ### First message The party involved on this page is itself the sender of: „Contract termination“ to **MSB (corresponds to MSBA on the metering location object)** (step 1).
  5. ### Objective The metering point operation contract concluded between AN or ANN and MSBA for the named metering location has been terminated.
## 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 MSBA](/en/prozessdoku/202610/MSB--MSBA/WiM-Teil1-kuendigung-messstellenbetrieb) — the transferring MSB · market role MSB *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 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: [2](#schritt-2)