DH-312-1 Grid agreement confirmation

DH-312-1 Grid agreement confirmation

image-20251017-051801.png
Details of grid agreement confirmation

Message DH-312-1 is of message type F04.

Message payload includes the following information:

Information field

Level

Necessity

Field content

Note

Information field

Level

Necessity

Field content

Note

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

Message DH-312-1 must contain the message identification for message DH-311-2.

Field usage

Original message sender

2

1..1

Message DH-312-1 must contain the message sender for message DH-311-2.

Field usage

Description

2

0..1

Reason for rejection of agreement

Description is mandatory if the grid agreement is rejected.

Grid agreement acceptance

2

1..1

Yes/No

If the DSO does not accept the grid agreement, a rejection message is returned. In that case agreement information is not included in the message.

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

0..1

 

Agreement information must be reported if the grid agreement is accepted.

Contact method

3

1..1

  • Electronic

  • Other

If the contact method of the agreement is electronic, then at least one of the customers must have an email address registered in Datahub.

Agreement identification

3

1..1

 

 

Agreement type

3

1..1

Grid agreement

 

Delivery agreement

3

1..1

Yes/No

The value of the ”delivery agreement” attribute on the grid agreement must match the ”delivery agreement” attribute of the sales agreement in DH-311.

Invoicing method

3

1..1

  • Separate invoicing

  • Grid invoices both

  • Supplier invoices both

If invoicing method is anything else than separate invoicing, the accounting point DSO must allow combined invoicing.

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

1..1

  • 0

  • 1

  • 2

 

Product data

3

1..n

 

 

Product code

4

1..1

Grid agreement product ID

 

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.

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:

  • 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.