ubl:ApplicationResponse

UBL version identifier
Requires UBL version 2.2

Fixed value: 2.2

Specification identification
Identifies the specification of content and rules that apply to the transaction.

Example value: urn:fdc:peppol.eu:prac:trns:t018:1.1

Business process type identifier
Identifies the BII profile or business process context in which the transaction appears.

Fixed value: urn:fdc:peppol.eu:prac:bis:p010:1.1

Response identifier
A transaction instance must contain an identifier. The identifier enables positive referencing the transaction instance for various purposes including referencing between transactions that are part of the same process. Must be expressed as a UUID.

Example value: 123e4567-e89b-12d3-a456-426614174000

Response issue date
The date on which the transaction instance was issued. Format "YYYY-MM-DD"

Example value: 2018-05-18

Response issue time
The time at which the transaction instance was issued. Format "hh:mm:ss

Example value: 14:44:33+01:00

Sender information
The party sending an electronic Tendering Message Response back to the sending party of the business document.

Receiver information
The party, an electronic Tendering Message Response was addressed to, and who is supposed to process the Tendering Message Response. This is the same party as the sender of the business document.

Document response
The tendering response is used to indicate the result of business document validation. The element 'cac:DocumentResponse/cac:Response/cbc:ResponseCode' MUST contain the overall result code.