DH-831-1 Authorization request to customer – supplier
Message DH-831-1 is of message type F30.
Message payload includes the following information:
Information field | Level | Necessity | Field content | Note |
|---|---|---|---|---|
Payload | 1 | 1..1 |
|
|
Authorization request | 2 | 1..1 |
|
|
Authorization request identification | 3 | 1..1 | A unique identifier (UUID) used in the authorization service to present a specific request to the customer for approval. | The same identification can be used in multiple authorization requests for the same customer (with different authorization types), if the customer is redirected from the party’s service to the authorization service and is expected to approve several requests at once. |
Authorization period | 3 | 0..1 |
| The authorization period must correspond to the time frame agreed upon with the customer. If a fixed-term service has been agreed, the authorization must also be requested as fixed-term. |
Start time | 4 | 0..1 |
| The start time of the authorization is not mandatory in the request. The authorization will begin either at the time the customer approves it or at another start time set by the customer in the authorization service. If the authorization is intended to begin on a specific date, this desired start time can be included in the request. |
End time | 4 | 0..1 |
| The end time of the authorization is not mandatory in the request. For authorizations requested with the reason ‘Invitation to tender’, a maximum validity period is set starting from the moment the customer approves the request, unless another time has been specified. If an authorization request with the reason ‘Accounting points’ is made without an end time, the customer is asked to issue an authorization valid until further notice. |
Authorization reason | 3 | 1..1 |
|
|
Description | 3 | 0..1 | Message to the customer, displayed in the authorization service and included in the email sent to the recipient of the request. |
|
Party identification | 3 | 1..1 | Identification of the notifying party |
|
Customer identification | 3 | 1..1 |
|
|
Accounting point data | 3 | 0..n |
| If the request is made without accounting point identifications, it applies to all of the customer’s accounting points where valid agreements exist at the time of approval. |
Accounting point identification | 4 | 1..1 |
|
|
Recipient | 3 | 0..1 |
|
|
Name | 4 | 1..1 |
|
|
Email address | 4 | 1..1 |
|
|
Request end date | 3 | 0..1 | Date until which the request is valid | Maximum of 30 days, after which the request expires even if no end date has been specified. |
Reminder time | 3 | 0..1 | Number of days after which a reminder is sent to the recipient, if the request has not been approved or rejected. | Sent only if recipient information has been included in the request. |