DH-311-1 Notification of a new agreement
Message DH-311-1 is of message type F04.
Message payload includes the following information:
Information field | Level | Necessity | Field content | Note |
|---|---|---|---|---|
Payload | 1 | 1..1 |
|
|
Start of occurrence | 2 | 1..1 | Agreement start date | Agreement start time must be midnight. |
End of occurrence | 2 | 0..1 | Agreement end date | The possible agreement end date must be after the start date. The possible agreement end time must be midnight. |
Accounting point data | 2 | 1..1 |
|
|
Accounting point identification | 3 | 1..1 |
|
|
Area information | 2 | 1..1 |
|
|
Metering grid area identification | 3 | 1..1 |
|
|
Agreement information | 2 | 1..1 |
|
|
Customer note | 3 | 0..1 |
|
|
Contact method | 3 | 1..1 |
| If the contact method for the agreement is electronic, then at least one of the customers must have an email address reported in the event. |
Agreement identification | 3 | 1..1 |
|
|
Agreement type | 3 | 1..1 | Sales agreement |
|
Delivery agreement | 3 | 1..1 | Yes/No |
|
Fixed-term agreement | 3 | 1..1 | Yes/No |
|
Fixed-term start date | 3 | 0..1 | Mandatory for fixed-term sales agreement | This information cannot be reported for an agreement that is not fixed term. ”Fixed-term start date” must be the same as ”Agreement start date” for the agreement. Start time for a fixed-term agreement must be midnight. |
Fixed-term end date | 3 | 0..1 | Mandatory for fixed-term sales agreement | This information cannot be reported for an agreement that is not fixed term. ”Fixed-term end date” must be the same as or earlier than ”Agreement end date” for the agreement. ”Fixed-term end date” must be later than ”Fixed-term start date”. End time for a fixed-term agreement must be midnight. |
Invoicing method | 3 | 1..1 |
| In case of an electricity delivery agreement, the invoicing method should be ”Supplier invoices both”. If invoicing method is anything else than separate invoicing, the accounting point DSO must allow combined invoicing. |
Special termination clause | 3 | 1..1 | Yes/No | Special termination clause can only be reported for a company customer’s sales agreement. |
Special termination period | 3 | 0..1 | Special termination period in days | If an agreement has a special termination clause, either the notice period in days or the entire notice period must be specified in the agreement. Information cannot be reported if the agreement does not have special termination clause. |
Notice period | 3 | 0..1 |
| If an agreement has a special termination clause, either the notice period in days or the entire notice period must be specified in the agreement. Information cannot be reported if the agreement does not have special termination clause. The notice period specifies the time period during which the agreement may be terminated. If a notice period is used, the supplier must ensure that it is updated in the agreement. |
Termination period start date | 4 | 0..1 |
| A special termination period’s start time must be midnight. |
Termination period end date | 4 | 0..1 |
| A special termination period’s end time must be after the termination period’s start date and at midnight. |
Interruption critical | 3 | 1..1 | Yes/No |
|
Invoicing channel | 3 | 1..1 |
| The consumer’s e-invoicing address is not reported to Datahub. E-invoice or direct debit may still be marked as the invoicing channel. If so, the postal invoicing address is mandatory. |
Tax category | 3 | 0..1 |
|
|
Product data | 3 | 0..n |
| If a product is reported for an agreement, the product must be in Datahub, be valid at the start date of the agreement and belong to the party reporting the agreement. |
Product code | 4 | 1..1 | Sales agreement product identification |
|
Contact person | 3 | 0..n |
| If the customer of the agreement is of type company, at least one contact person must be reported. Contact persons are persons that the parties need in customer service situations, and they may differ between sales and grid agreements. There cannot be multiple contact persons with the same contact person type. For each contact person at least one of the name attributes must be reported. The parties may have their own contact persons, but only those that the party deems necessary to pass on to the other party (from the supplier to the DSO or from the DSO to the supplier) are reported to Datahub. |
Contact person type | 4 | 1..1 |
|
|
Given name | 4 | 0..1 |
|
|
Family name | 4 | 0..1 |
|
|
Other name | 4 | 0..1 |
|
|
Contact information | 4 | 1..2 |
|
|
Contact information type | 5 | 1..1 |
|
|
Telephone number/Email address | 5 | 1..1 |
| A phone number must start with a plus ’+’. A phone number may not contain spaces. The country code ‘+358’ may not be followed by the number zero. |
Postal invoicing address | 3 | 1..1 |
| Address information must contain the postal code and either street name and building number or PO Box. Address information may not contain both PO Box and street address information (street name, building number, stairwell identification or apartment). If apartment information is reported, stairwell identification is mandatory. |
Address specifier | 4 | 0..1 | c/o |
|
Street name | 4 | 0..1 |
|
|
Building number | 4 | 0..1 |
| When the address is in Finland, the building number field:
|
Stairwell identification | 4 | 0..1 |
| Rules for the stairwell identification field:
|
Apartment | 4 | 0..1 |
| When the address is in Finland, the apartment field:
|
Postal code | 4 | 1..1 |
| The postal code and post office must match. This check is only performed for addresses located in Finland. |
PO Box | 4 | 0..1 |
|
|
Post office | 4 | 1..1 |
| The postal code and post office must match. This check is only performed for addresses located in Finland. |
Country | 4 | 1..1 | ISO 31661 code used in accordance with alpha-2 |
|
Electronic invoicing address | 3 | 0..1 |
| Mandatory if invoicing channel is electronic invoice. |
Buyer reference | 4 | 0..1 |
|
|
Electronic invoicing address | 4 | 1..1 |
|
|
Operator identification | 4 | 1..1 |
|
|
Other invoicing address | 3 | 0..1 |
| Mandatory if invoicing channel is mobile invoice (telephone number must be reported) or email (email address must be reported). |
Type | 4 | 1..1 |
|
|
Electronic address | 4 | 1..1 |
| A phone number must start with a plus ’+’. A phone number may not contain spaces. The country code ‘+358’ may not be followed by the number zero. |