DH-311 Notification of a new agreement
Event description
A supplier reports a new electricity sales agreement, which it has signed with a customer for the customer’s accounting point. New grid agreement information is created in Datahub if necessary, and the DSO receives information about the new agreement.
Parties
New supplier
Current supplier
Datahub
DSO
Third party
Balancing service provider
Interrupting events
A previously reported electricity sales agreement with the same agreement starting date for the same accounting point. Two new agreements cannot be reported to start on the same day, so the one reported later is rejected. A move-in (all customers change) is an exception that cancels all earlier change of agreement/supplier agreements reported to start on the same day on the same accounting point (if the earlier agreement is a move-in, then another move-in for the same date will be rejected).
If an agreement is made to start in the future, it is possible to make another sales agreement ”in-between” for the time before the earlier made agreement comes into force. In this case the ending date must be entered and it cannot be later than the starting date of the agreement reported earlier. See DH 310, example 3.
Time limits
Reason | Agreement’s start date | Exceptions |
|---|---|---|
Move-in | 0–90 days from the notification date |
|
Supplier switch | 14–90 days from the notification date | If the previous contract has already ended, the new contract can begin at the earliest from the end date of the previous one. |
Contract switch | 0–90 days from the notification date |
|
Retroactive move-in | Up to 3.5 years retroactively | A contract reported to start retroactively is handled as described on the page Retroactive error correction. |
Retroactive supplier switch | Up to 10 years retroactively | |
Retroactive contract switch | Up to 3.5 years retroactively |
Event processing in Datahub
Step | Description |
|---|---|
Creating a customer | If the customer for an agreement being reported is not found in Datahub, it is created in Datahub. |
Reason for agreement start | The system determines the reason for agreement start. |
Terminating a current agreement | Datahub terminates the valid agreement for the current supplier at the accounting point on the day preceding the starting date of the new agreement. The reason of current agreement ending is recorded based on the reason for starting the new agreement.
|
Agreement cancellation | If customers change at an accounting point, all the agreements made for the same date or to the future on the accounting point will be cancelled. See DH 310, example 4. Confirmed or unconfirmed grid agreements that correspond with the cancelled sales agreement will be cancelled too. |
Creating a grid agreement | If a new grid agreement is needed, Datahub creates the information for the new grid agreement (starting date same as for the sales agreement, grid agreement status ”unconfirmed”). In conjunction with creating a new grid agreement, Datahub terminates the valid grid agreement on the preceding day. Rules for conclusion:
|
Terminating authorizations | If there are authorizations on the accounting point that are valid at the start of the new agreement or will become valid during the new agreement, they are terminated for the start of occurrence or cancelled, unless the authorization customer is also a customer of the new agreement. An authorization that will take effect in the future is cancelled by setting the end date to the same as the start date. If a customer is reported as information restricted (“non-disclosure”) with the new agreement, all authorizations of that customer on any accounting point are terminated for the start of occurrence of the agreement, or cancelled, if the authorization is not yet valid at agreement start date. The authorization is cancelled by setting the end date to the same as the start date. |
Cancelling open connection/disconnection requests | If there are open (i.e., the actual connection or disconnection has not yet been reported) connection or disconnection requests for the accounting point with requested connection/disconnection date on or after the start date of the agreement, those requests are cancelled. |
Information storage
Origin of information | Information stored |
|---|---|
Information reported by party | New sales agreement information is created on the basis of the reported information and linked to the accounting point indicated in the notification. |
The customer information contained in the notification is updated in the customer information. | |
Datahub stores and forwards information on a post office located in Finland in upper case, even if the post office name is reported differently to Datahub. | |
Information processed by Datahub | The reason for agreement start. |
The end date of the current sales agreement and the reason for agreement termination. | |
The end date of the current grid agreement and the reason for termination if the customers change. | |
Information about the created grid agreement (status=‘unconfirmed’). | |
Agreement cancellations, if any. | |
Information about the created new customer. | |
Updated customer information, if any. | |
Updated authorization information, if any. |
Return of information
Party | Specification | Description | Message |
|---|---|---|---|
Supplier | Accepted event | Notification of successful or rejected notification. If the notification is successful, the reason for the new agreement registered in Datahub is returned (moving in, switching suppliers, change of agreement). | |
Rejected event | Agreement rejection includes information about the reason for rejection. The fixed-term end date of the current fixed-term agreement is returned if it is no further than 90 days in the future from the date of notification. If the current sales agreement has exceptional termination conditions, the first possible new agreement start date is returned. |
|
Forwarding of information
Party | Specification | Description | Message |
|---|---|---|---|
DSO | Accounting point’s DSO | Notification of a new sales agreement, including information on whether a new grid agreement is needed. | |
When a new customer is moving in, Datahub notifies the DSO of cancellation of grid agreement, if the upcoming grid agreement is cancelled due to the cancellation of the corresponding sales agreement. The notification should use reason code ”Agreement cancelled by customer”. | |||
Other DSOs | If the notification of a new agreement updates an already existing customer’s information in Datahub, the updated information is forwarded to all parties entitled to the information. | ||
Supplier | Accounting point’s current supplier | A possible current supplier for the accounting point is notified of the termination of the current sales agreement. | |
Related accounting point’s supplier | A possible current supplier for a related accounting point is notified of the customer moving out. The agreement for the related accounting point is not cancelled automatically. After receiving the notification of the moving out, the supplier for the related accounting point can terminate the agreement if they so wish. | ||
Accounting point’s future supplier | When a customer is moving in, Datahub sends a notification of sales agreement cancellation to the supplier who has an upcoming agreement with a customer that is not the customer who is moving in. The notification should use reason code ”Agreement cancelled by customer”. | ||
All of the customer’s suppliers | If the notification of a new agreement updates an already existing customer’s information in Datahub, the updated information is forwarded to all parties entitled to the information. | ||
If authorizations have been ended or cancelled due to the new agreement, a notification of authorization change is sent to related market parties. | |||
Third party |
| If the notification of a new agreement updates an already existing customer’s information in Datahub, the updated information is forwarded to all parties entitled to the information. | |
Notification of current sales agreement termination is forwarded to those third parties who have an authorization for the accounting point from at least one of the customers of the terminated agreement. | |||
If authorizations have been ended or cancelled due to the new agreement, a notification of authorization change is sent to related market parties. | |||
Balancing service provider |
| If the notification of an agreement cancellation changes a customer’s supplier information due to the cancelled (or a potentially restored) agreement and the customer has issued an ‘Accounting point’s balance responsibility information’ authorization for the accounting point, the new balance responsibility information is forwarded to the balancing service provider. The authorization must be valid on the reporting date of the event and the validity of the changed data must overlap with the validity of the authorization. If the change is retroactive, the information is forwarded only if its validity overlaps with the validity of the authorization during the last 60 days (counting from the reporting date). |
Composite processes
Party | Description | Composite process |
|---|---|---|
DSO | If a new grid agreement is required, a pending grid agreement is created for the DSO. |
Significant errors and consequences
Error | Consequence |
|---|---|
A sales agreement is reported for the wrong accounting point | A customer’s current agreement is terminated at the wrong accounting point without cause. |
Incorrect customer information is reported |
Maintaining the correctness of the information is the responsibility of the personal data registrar. Passing on incorrect personal data is a violation of data protection. |
Event cancellation
A notification of a new agreement can be cancelled using the event DH-341 before the agreement’s start date.
A valid agreement is cancelled using the processes described in DH-340.
Validation rules
Please see Datahub Validation Rules for a more thorough list.
Rule | Error code | Note |
|---|---|---|
A residential customer must be at least 18 years old. | EC.CUS.106 |
|
The date of entry into force of the notified agreement cannot overlap with an agreement beginning in the future. | EC.AGR.233 |
|
Only the supplier with a delivery obligation for the accounting point’s metering grid area may report an electricity delivery agreement. | EC.ARG.103 |
|
The accounting point is recorded in Datahub and is valid on the agreement start date. | EC.MPT.115 |
|
The accounting point is part of the notified metering grid area. | EC.MPT.116 |
|
The accounting point must not have the status ‘Removed from use’ or ‘Deleted’ on the agreement start date. | EC.MPT.120 | If the accounting point has already been removed from use, a new (retroactively beginning) agreement must end by the date of removal from use. |
The supplier’s balance responsible party has registered the required Supplier–BRP Relationship (RBR) with eSett prior to the agreement notification. The Supplier–BRP structure for the Supplier–metering grid area–consumption/production combination is in force on the start date of the sales agreement. | EC.BAR.100 |
|
If the termination of a sales agreement is already notified for the accounting point with the reason of ‘Meter removal’, a new (retroactively beginning) agreement must end by the date the meter is removed. | EC.AGR.249 |
|
If the termination of a grid agreement corresponding to a new sales agreement has already been notified for the accounting point, the new agreement must end by the termination date of the grid agreement. | EC.AGR.251 |
|
If a new sales agreement notification also specifies an agreement termination date, the termination date may only be a maximum of 90 days from the notification date. | EC.AGR.202 |
|
If the reason for beginning a new agreement is a customer’s moving into a new residence or changing their agreement, the earliest possible date that can be entered on the new sales agreement is the current date. | EC.AGR.202 |
|
If the supplier is being changed, the earliest possible start of the new sales agreement is after 14 days, unless the previous sales agreement has already terminated, in which case the new sales agreement may begin no earlier than upon termination of the previous agreement. | EC.AGR.202 |
|
The notification may be sent no earlier than 90 days before the start date of the reported sales agreement. | EC.AGR.202 |
|
A change of supplier is not permitted if a residential customer has a valid fixed-term agreement at their accounting point which has been in force for under 2 years. | EC.AGR.209 |
|
A change of supplier is not permitted if a business customer has a valid fixed-term agreement in force at the accounting point. | EC.ARG.207 |
|
A change of supplier or change of agreement is not permitted if the new agreement is contrary to a business customer’s valid special termination terms. | EC.AGD.204 |
|
Please observe that the list is not complete. | ||