ApplicationResponse

Specification identification
BEAst: Used by BEAst as the Order Receipt Response message. Peppol: Identifies the specification of content and rules that apply to the transaction.

Example value: urn:fdc:peppol.eu:logistics:trns:despatch_advice_response:1

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

Example value: urn:fdc:peppol.eu:logistics:bis:despatch_advice_w_response:1

Response identifier
BEAst: T6406, Order receipt response ID. Peppol: 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.

Example value: DN12345

Issue date
BEAst: T6325, Document date time. Peppol: Document date time.

Example value: 2021-08-15

Issue time
BEAst: T6325, Document date time. Peppol: Document date time.

Example value: 12:00:00

Sender information
Peppol: The party sending an electronic message level response message back to the sending party of the business document.

Receiver information
Peppol: The party, an electronic message level response was addressed to, and who is supposed to process the message level response. This is the same party as the sender of the business document.

Document response
Peppol: The document 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.