Agreement information
Sales and grid agreement information stored in Datahub includes information on agreement dates, invoicing address information and contact details for contact persons. When parties report agreements to Datahub, the customer information submitted in the notification is stored in Datahub’s Customer entity (or in several, if the agreement has more than one customer), and the agreement is linked to a customer (or customers) and the specified accounting point in Datahub’s internal data structure. If the reported customer is not yet present in Datahub, a new customer is created in Datahub. If the customer already exists in Datahub, the customer’s information is updated when the new agreement is reported. If the customer information contains updates, the updated customer information is forwarded to all parties that are entitled to it. An agreement is identified in Datahub using the combination of agreement identifier, accounting point identifier and the relevant market party’s party identifier.
Agreements entered into Datahub are valid for whole days. The agreement start date is the first day when the agreement is in effect. The agreement end date is the first day when the agreement is no longer in effect. For clarity: the agreement begins at 00.00 on the start of occurrence of the notification of a new sales agreement. The agreement ends on the agreement end date at 00.00. In other words, the day before the agreement end date is the last day when the agreement is in effect.
The agreement information contains invoicing channel information, and the appropriate invoicing address details (including invoicing (postal) address, email invoicing address or e-invoicing address) must be linked to the agreement information. The invoicing address a customer provides when making a new agreement with a supplier is sent from the supplier to the DSO via Datahub. This data does not, however, bind the DSO to the use of the invoicing channel in question if the DSO is unable to provide said channel. The DSO reports the invoicing channel it uses in the agreement to Datahub as part of the grid agreement information.
A customer may also ask the DSO to send invoices to a different address to the one stated on the sales invoice. In such cases, the customer should contact the DSO to change the invoicing address. The DSO will report changes to invoicing addresses to Datahub. Datahub’s data model allows for separate invoicing addresses to be used in sales and grid agreements at the same accounting point; that is, invoicing address data is stored on an agreement-specific basis. It is worth noting that current rules prohibit residential customer e-invoicing data from being sent from one party to another. Nevertheless, it is possible to add a note in the invoicing channel field explaining that the customer wishes to use this particular invoicing channel. Even in cases when the invoicing channel is different from postal invoicing, a postal invoicing address needs to be reported to the agreements to Datahub for debiting purposes.
The agreement information also includes an invoicing method, which specifies whether both the supplier and DSO invoice the customer separately, or whether combined invoicing is carried out by either the supplier or the DSO. Corresponding sales and grid agreement must have the same invoicing method. If a new grid agreement is not created along with a new sales agreement, the DSO updates the grid agreement invoicing method to match the invoicing method of the sales agreement, if needed, or contacts the supplier to ask the supplier to update their sales agreement invoicing method.
It is possible to add contact persons to agreements in addition to the actual customer. The customer is the agreement partner legally responsible for the agreement. Contact persons are persons linked to the agreement and whose contact details are required by the parties for customer service purposes. For example, the recipient of an invoice may be reported as the contact person for an agreement if the recipient differs from the actual customer.
Similarly, contact persons for agreements may vary between sales and grid agreements. The contact person information provided to a supplier by a customer when making a new agreement with the supplier is stored in the sales agreement information and sent to the DSO. The DSO may use this information as the contact person for its own agreement. It is worth noting that parties may have many different kinds of contact persons in their own customer and agreement information, but the contact persons whose information must be exchanged between parties (from the supplier to the DSO or from the DSO to the supplier) are reported to Datahub. At least one contact person must always be reported for business customers. Separate contact persons are only reported for residential customers when necessary, such as if the customer’s contact details are insufficient.
If the new agreement concerns the customer moving in or another situation where a connection is required, a telephone number must be provided to ensure a safe connection. If the safe connection confirmation message is to be sent to a different telephone number than the number specified in the customer information, the supplier must provide a separate contact person for the agreement, using type ‘Responsible for connections’ and providing their telephone number.
The contact method agreed with the customer must be reported for the agreement. The ‘electronic’ contact method means that as a rule no letters will be posted to the customer. The contact method is agreement-specific, and the contact method the customer has agreed on with the supplier is forwarded as information to the DSO. However, the DSO must always expressly agree on the contact method with the customer, even if the supplier has reported that it is using the electronic contact method. If the contact method in the agreement is electronic, then at least one of the customers reported in this agreement needs to have provided an email address that has been reported to Datahub.
The sales and grid agreement information stored in Datahub is set out below in separate diagrams. An accounting point can have several consecutive agreements over time, but only one sales and one grid agreement can be valid at any one time. Agreement information sent in different processes is set out in more detail under each process.
Sales agreement information
Grid agreement information