# Order placement for a change of billing data for balancing group settlement from ÜNB to NB — ÜNB view The LF or ÜNB transmits the order placement for a change of billing data to the NB. The NB checks the order placement and informs the LF or ÜNB of the processing status. ## Process flow from the perspective of the ÜNB \nSystem diagram: Bestellung einer Änderung von Abrechnungsdaten zur Bilanzkreisabrechnung von ÜNB an NB — view of ÜNB\n\n\nCustomer backend system\n\nMACO APP · ÜNB\n\nMarket partner\n\n\n\n1. Bestellung einer Änderung\nvon Abrechnungsdaten zur\nBilanzkr…\n\nNB\n\nAS4\n55614, 55675\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n\n2. Bearbeitungsstand zur\nBestellung\n\n\nNB\n\nAS4\n21047\n\nUpdate transaction\n\n\nUpdate process data\n\nAPI\n"} gesamt={"\nSequence diagram: Bestellung einer Änderung von Abrechnungsdaten zur Bilanzkreisabrechnung von ÜNB an NB — view of ÜNB\n\n\nBackend (customer)\n\n\nMACO APP · ÜNB\n\n\nNB\n\n\n1. Bestellung einer Änderung von Abrechnungsdate…\nAS4 · PI 55614, 55675\n\nUpdate transaction\nUpdate process data\n\n2. Bearbeitungsstand zur Bestellung\nAS4 · PI 21047 · E_0613\nE_0613 — Bestellung prüfen\n\nUpdate transaction\nUpdate process data\n"} titel="ÜNB" /> ## Process steps ### Order placement for a change of billing data for the balancing group settlement
**Check identifiers** - [55614](/en/schnittstellen/202604/pruefi/UTILMD/PI_55614) — Response message/request bill. data BG settl. consum. MaLo · AS4 - [55675](/en/schnittstellen/202604/pruefi/UTILMD/PI_55675) — Response message/request bill. data BG settl. gen. Malo · AS4
**Flow**
  1. Message to **NB** · AS4
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend once the message has been created.
### Processing status of the order placement
**Check identifiers** - [21047](/en/schnittstellen/202604/pruefi/IFTSTA/PI_21047) — Processing status message · AS4
**Flow**
  1. Message from **NB** · AS4
    **Response per decision tree** - `21047` → [E_0613](/en/referenz/202604/ebd/E_0613) · NB · Check order placement (Based on EBD: E_0573_Check order placement for master data change)
  2. **Write endpoint** - Transaction updated — `AKTUALISIEREN_PROZESSDATEN` Updates the existing transaction in the backend with the data of the incoming message.
Decision trees of this process | EBD | Name | |---|---| | [E_0613](/referenz/202604/ebd/E_0613) | Check order placement (Based on EBD: E_0573_Check order placement for master data change) |
## Process information Wording of the consolidated version, profile ch. 3.1.3.1, pp. 77–79.
  1. ### Preconditions - The device technology available at the ordered point in time permits the change. - In the case of the order placement of a change of billing data for grid usage settlement: - If there is a need to apply a metering time period definition of NB with the metering time period usage purpose “grid usage”, a corresponding configuration must have been set up on time and successfully via the use cases in the chapter “Order placement of a configuration” (GPKE Part 3). - This is a consuming market location. - The LF has billing data on the basis of the use case “[Billing data grid usage settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung)”. - In the case of the order placement of a change of the concession levy: - In the case of the order placement of an off-peak concession levy: - An electricity supply contract exists which meets the requirements for billing the reduced concession levy at the market location. - In the case of an off-peak concession levy for which the contractual precondition for the off-peak concession levy between LF and the final customer will cease/has ceased to apply, LF must order a change of the concession levy to a concession levy other than the off-peak concession levy. - In the case of the order placement of a change of billing data for balancing group settlement: - The LF has billing data on the basis of the use case “[Billing data balancing group settlement](/en/prozessdoku/202604/UENB/GPKE-Teil2-abrechnungsdaten-bilanzkreisabrechnung)” or - the ÜNB has billing data available on the basis of the use case “[Billing data balancing group settlement](/en/prozessdoku/202604/UENB/GPKE-Teil2-abrechnungsdaten-bilanzkreisabrechnung)”.
  2. ### Results - In the case of the order placement of a change of billing data for grid usage settlement: NB carries out the use case “[Billing data for grid usage settlement](/en/prozessdoku/202604/LF/GPKE-Teil2-abrechnungsdaten-netznutzungsabrechnung)”. - In the case of the order placement of a change of billing data for balancing group settlement: NB carries out the use case “[Billing data for balancing group settlement](/en/prozessdoku/202604/UENB/GPKE-Teil2-abrechnungsdaten-bilanzkreisabrechnung)”.
  3. ### Error case #### Result in the error case The LF or ÜNB checks whether a new order placement is required. #### Error cases - The device technology available at the ordered point in time does not permit the change. - In the case of the order placement of a change of billing data for grid usage settlement: This concerns a generating market location or a tranche.
  4. ### Further requirements - Note: A change of the balancing method is not to be ordered via this use case, but via the use case “[Order placement of a configuration from LF to NB](/en/prozessdoku/202604/LF/GPKE-Teil3-bestellung-einer-konfiguration-vom-lf-an-nb)” (GPKE Part 3). - Notes on generating market locations or on tranches: - For a change of the marketing type with simultaneous assignment of the LF to the market location or tranche, the LF applies the use case “Start of supply“. - For a change of the tranche size, the LF applies the use case “Start of supply“ (see business transaction 3). - Note: If the device technology available at the ordered point in time does not permit the order placement, the change of the device technology is not to be ordered via this use case. A corresponding change of the device technology can be commissioned as part of a device replacement or via the use cases for the metering location change (WiM Part 1). - With regard to the regulatory determination on grid fees for controllable connections and consumption devices (NSAVER) under § 14a EnWG (BK8-22/010-A), the following applies: in the case of an order placement for a change of billing data for grid usage settlement, supplementary requirements (such as preconditions and deadlines) are published and maintained by the expert group EDI@Energy based at the BDEW, with the involvement of the Bundesnetzagentur.
  5. ### Trigger - The LF needs a change of billing data for the grid usage settlement (e.g. change of the grid usage billing model from energy price/basic price to energy price/demand price, or change of the payer of the grid usage from final customer to LF). - The LF needs a change of billing data for the balancing group settlement (e.g. change of the annual consumption forecast or change of the marketing type) - The ÜNB needs a change of billing data for the balancing group settlement. - The LF or ÜNB assumes a data discrepancy.
  6. ### First message The party involved on this page is itself the sender of: „Order placement for a change of billing data for balancing group settlement“ to **NB** (step 1).
  7. ### Objective The processing status of the change of billing data ordered by the LF or ÜNB is available to the LF or ÜNB from the NB.
## 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-bestellung-einer-aenderung-von-abrechnungsdaten-zur-bilanzkreisabrechnung-von-uenb-an-nb) — 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.* The source does not yet name the event that triggers these steps. Applies to: [1](#schritt-1) 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) For this market role there is no write catalog; the step therefore shows only the command of the write call, without address and without button. Applies to: [1](#schritt-1), [2](#schritt-2)