# Request for invoice handling of metering point operation via the LF by the LF — LF view The LF has the option of changing the default setting for the invoicing of the metering point operation by order placement, for example following a device replacement to the mME or iMS, following the assignment of a LF, or during ongoing operation. In doing so, the LF implicitly confirms that it is entitled under the supply contract with the AN to demand the billing of the metering charge in its relationship with the MSB of the market location. ## Process flow from the perspective of the LF \nSystem diagram: Anfrage zur Rechnungsabwicklung des Messstellenbetriebes über den LF durch den LF — view of LF\n\n\nCustomer backend system\n\nMACO APP · LF\n\nMarket partner\n\n\n\n1. Anfrage\nRechnungs-abwicklung des\nMessstellenbetriebes über…\n\nMSB (entspricht MSB a…\n\nAS4\n35002\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Angebot /Ablehnung\nAnfrage\n\n\nMSB (entspricht MSB a…\n\nAS4\n15002, 21033\n\nLoad data for the incoming\ncheck\n\n\nMarktlokation lesen\n\nAPI\n\nAPERAK check: Z33, Z10,\nZ17, Z18\n\n\nCreate transaction\n\n\nCreate process data\n\nAPI\n\nLoad data for the check\n\n\n3 read APIs called\n\nAPI\nlisted at the step\n\nEBD check: E_0205\nAngebot prüfen\n\n\nTrigger follow-up process:\n17005, 21032\n\n\nTriggered by incoming\nmessage: 15002\n\n\n3. Antwort Angebot\n\n\nMSB (entspricht MSB a…\n\nAS4\n17005, 21032\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Anfrage zur Rechnungsabwicklung des Messstellenbetriebes über den LF durch den LF — view of LF\n\n\nBackend (customer)\n\n\nMACO APP · LF\n\n\nMSB (entspricht MSB am Ob…\n\n\n1. Anfrage Rechnungs-abwicklung des Messstellenb…\nAS4 · PI 35002\n\nUpdate transaction\nUpdate process data\n\n2. Angebot /Ablehnung Anfrage\nAS4 · PI 15002, 21033 · E_0207\nE_0207 — Anfrage prüfen\n\nCreate transaction\nCreate process data\n\n3. Antwort Angebot\nAS4 · PI 17005, 21032 · E_0208\nE_0208 — Angebot bzw. Ablehnung der Anfrage verarbeiten\n\nUpdate transaction\nUpdate process data\n"} titel="LF" /> ## Process steps ### Request for invoice processing of metering point operation via the LF
**Check identifiers** - [35002](/en/schnittstellen/202610/pruefi/REQOTE/PI_35002) — Request for invoice processing MSB via LF · AS4
**Flow**
  1. Message to **MSB (corresponds to MSB at the market location object)** · AS4
  2. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/backend-schreiben-lf/updateprocessdata#prozessdaten-aktualiseren) `POST /updateProcessData` Try it out Updates the existing transaction in the backend once the message has been created.
### Quotation /rejection of request
**Check identifiers** - [15002](/en/schnittstellen/202610/pruefi/QUOTES/PI_15002) — Quotation billing metering point operation MSB · AS4 - [21033](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21033) — Rejection of the request · AS4
**Flow**
  1. Message from **MSB (corresponds to MSB at the market location object)** · AS4
    **Response per decision tree** - `21033` → [E_0207](/en/referenz/202610/ebd/E_0207) · MSB · Check request
  2. **Load data for the incoming check** - [Read market location](/en/api/202610/backend-lesen/getmarketlocationbasic#marktlokation-lesen) `GET /getMarketLocationBasic` Try it
  3. **APERAK checks** - `15002`, `21033` → `Z33` — APERAK check: Is referenced message known ? - `15002` → `Z10` — APERAK check: Is location known ? - `15002` → `Z17` - `15002` → `Z18`
  4. **Write endpoint** - Transaction created — [Create process data](/en/api/202610/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.
  5. **Load data for the check** - [Read energy supply contract](/en/api/202610/backend-lesen/getenergysupplycontractbasic#energieliefervertrag-lesen) `GET /getEnergySupplyContractBasic` Try it - [Read metering point operation contract](/en/api/202610/backend-lesen/getmeasuringpointoperationcontractbasic#messstellenbetriebsvertrag-lesen) `GET /getMeasuringPointOperationContractBasic` Try it - [Read price sheet](/en/api/202610/backend-lesen/getpricesheetbasic#preisblatt-lesen) `GET /getPriceSheetBasic` Try it
  6. **Decision tree** - `15002` → [E_0205](/en/referenz/202610/ebd/E_0205) — Check quotation
  7. **Trigger follow-up process** - [17005](/en/schnittstellen/202610/pruefi/ORDERS/PI_17005) — Order placement invoice processing MSB via LF - [21032](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21032) — Response to the quotation After processing, the MACO APP starts the follow-up process itself; which of them runs depends on the result of the processing.
### Response quotation
**Check identifiers** - [17005](/en/schnittstellen/202610/pruefi/ORDERS/PI_17005) — Order placement invoice processing MSB via LF · AS4 - [21032](/en/schnittstellen/202610/pruefi/IFTSTA/PI_21032) — Response to the quotation · AS4
**Flow**
  1. **Triggered by incoming message** - [15002](/en/schnittstellen/202610/pruefi/QUOTES/PI_15002) — Quotation billing metering point operation MSB The MACO APP sends this message itself, as a follow-up process after this incoming message.
  2. Message to **MSB (corresponds to MSB at the market location object)** · AS4
    **Response per decision tree** - `21032` → [E_0208](/en/referenz/202610/ebd/E_0208) · LF · Process quotation or rejection of the request
  3. **Write endpoint** - Transaction updated — [Update process data](/en/api/202610/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_0207](/referenz/202610/ebd/E_0207) | Check request | | [E_0208](/referenz/202610/ebd/E_0208) | Process quotation or rejection of the request |
## Process information Wording of the consolidated version, profile ch. 3.6.3.6.1, p. 74.
  1. ### Preconditions - For a market location with one assigned metering location, that metering location must be equipped with a mME or iMS. - For a market location with at least two assigned metering locations, at least one metering location must be equipped with a mME/a iMS. - The LF is assigned to the market location of the metering location(s). - LF is not the payer for the metering point operation.
  2. ### Results Order placement: The LF is assigned at the MSB of the market location as the payer for metering point operation.
  3. ### Error case #### Result in the error case The LF is not assigned as payer of the metering point operation at the MSB of the market location, or, in the case of iMS, the MSB of the market location has already set up the billing of the metering point operation via another LF of a market location affected by the POG determination and the requesting LF is not the payer. The invoicing applies from the confirmation of the quotation, with effect from the requested billing start, for an unlimited period. Any invoicing already confirmed earlier with the same LF that would begin after the billing start thus becomes void. #### Error cases The metering location could not be identified, or the LF has no authorization.
  4. ### First message The party involved on this page sends this itself: “Request for invoice processing of metering point operation via the LF” to **MSB (corresponds to MSB at the market location object)** (step 1).
  5. ### Objective The LF is the payer of the metering point operation.
## 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 MSB-MALO](/en/prozessdoku/202610/MSB/WiM-Teil1-anfrage-zur-rechnungsabwicklung-des-messstellenbetriebes-ueber-den-lf-durch-den-lf) — MSB at the market location object · 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 source does not yet name the event that triggers these steps. Applies to: [1](#schritt-1) 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: [2](#schritt-2)