DH-311-2 Forwarding information about new agreement to DSO

Payload

1

1..1

Start of occurrence

2

1..1

End of occurrence

2

0..1

Agreement end date

Original message identification

2

1..1

This field is used for the original DH-311-1 message identification.

Field usage

Original message sender

2

1..1

This field is used for the original DH-311-1 message sender.

Field usage

Requires new grid agreement

2

1..1

Yes/No

Reason for agreement start

2

1..1

• Agreement change

• Switching suppliers

• Moving in

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

Contact method

3

1..1

• Electronic

• Other

Agreement identification

3

1..1

Agreement type

3

1..1

Sales agreement

Delivery agreement

3

1..1

Yes/No

Invoicing method

3

1..1

• Separate invoicing

• Grid invoices both

• Supplier invoices both

Interruption critical

3

1..1

Yes/No

Invoicing channel

3

1..1

• Paper invoice

• Electronic invoicing

• E-Invoice

• E-mail

• OmaPosti

• Direct debit

• Mobile invoice

• Other invoicing channel

Tax category

3

0..1

• 0

• 1

• 2

Customer note

3

0..1

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

• Trustee

• Responsible for agreements

• Responsible for invoicing

• Responsible for connections

• Fault communication

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

• E-mail address

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.

c/o

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:

• may not contain spaces

• the only special characters allowed are dot (.), hyphen (-) and slash (/)

• special characters only are not allowed

Stairwell identification

4

0..1

Rules for the stairwell identification field:

• if the value is one of the following: "as", "as.", "bst" or "bst.", it must be in lowercase

• if only one letter used, it must be in uppercase, if the address is in Finland

• spaces are not allowed

Apartment

4

0..1

When the address is in Finland, the apartment field:

• may not contain spaces

• may not contain uppercase letters

• the only special characters allowed are dot (.), hyphen (-) and slash (/)

• special characters only are not allowed

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

• Telephone

• E-mail address

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.

Supplier information

3

1..1

Party identification

4

1..1

Basic customer information

3

1..n

Customer identification

4

1..1

• Business ID

• Personal identity code

• Party’s own customer identification

If a personal identity code is provided, it must comply with the format requirements for personal identity codes.

If a party’s own customer identification is used, it must be provided as <notifying supplier’s identification>_<customer number> (used as specifying data in a situation in which the personal identity code is not known or business ID does not exist). Datahub checks that the identification starts with the supplier’s identification of notifying supplier.

Customer identification type

4

1..1

• Business ID

• Personal identity code

• Party’s own customer identification

If the customer type is consumer, customer identification type must be either personal identity code or party’s own identification. If the customer type is company, customer identification type must be business ID or party’s own identification.

Customer type

4

1..1

• Company

• Consumer

The customer type for an already existing customer cannot be updated.

If the agreement includes both a company customer and a consumer customer, the rules for the consumer customer apply to the agreement.

Customer sub-type

4

1..1

• Normal

• Estate of a deceased person