DH-730 Invoice row information notification
Market parties can send invoice row information via Datahub. Invoice row information can be sent, for example, when a party has agreed with a customer that the customer receives only one invoice, containing both electricity supply and transmission. In this case, the other market party can report all its accounting point related billing information to the invoicing party using invoice rows. The market party that sends the invoice row information to Datahub needs to ensure that the information is forwarded to the right party. When using combined invoicing, the invoicing party also reports the receiving party’s identification and the agreement identification of the receiving party in the invoice row message. Parties receive these identifications through agreement processes. If, for example, a DSO reports invoice row information to the supplier, the DSO must be able to generate the grid agreement’s invoice rows for the correct recipient, taking into account a possible supplier change.
In the example above supplier B’s agreement starts on 1.5.2019. The grid agreement does not change in the supplier change situation. If the DSO has agreed on combined invoicing with both suppliers, it needs to ensure that it does not send invoice rows to supplier A for the period after 1.5.2019.
Invoice row information can also be used for forwarding billing information to a service provider offering invoicing services. In such cases, there is no agreement identification for the receiving party to report. Before forwarding invoice row information, the involved parties must agree on the terms of information exchange and report a party authorization in the user interface. The authorizing party selects the authorized party and sets the validity period for the authorization. The issued authorization applies to all invoice rows delivered to the authorized party. If needed, the receiving of invoice rows can be delegated to a service provider. If the DSO authorizes supplier A to its invoice rows, supplier A can delegate the reception of those rows to a third party, such as service provider C. A private customer cannot authorize a third party to access invoice row information.
A party reports invoice row information to Datahub after first having compiled it in its own system according to party-specific invoicing processes. Invoice row information is reported separately for each product component. For example, for an electricity product the basic fee component and energy component are reported as separate rows. The invoicing period for the whole invoice and the invoicing period for a separate invoice row are both reported in the message. The invoicing period may include invoice rows with data that has been corrected retroactively, and therefore the information may not always match. Invoice rows can also be used to communicate service fee invoicing between parties as separate invoice rows. The amount to be invoiced for a power-based product component can also be communicated using invoice row data. In this way, a party receiving invoice rows and handling customer billing does not necessarily have to maintain the calculation rules affecting the invoicing.
A notification of invoice rows to Datahub is never cancelled or modified. If the sending party corrects its own billing, it is obligated to send the correction data as separate invoice row entries via Datahub to the receiving party, first as credit rows and then as new debit rows.
Invoice row information is reported according to the structure below.