Peppol Message Level Response 3.0 (T71)

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

Example value: urn:fdc:peppol.eu:poacc:trns:mlr:3

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

Fixed value: urn:fdc:peppol.eu:poacc:bis:mlr:3

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.

Example value: 23

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: 12:01:34

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

Sender party electronic address
Identifies the sender party's electronic address

Example value: 7300010000001

Scheme identifier
Scheme identifier for the electronic address

Example value: 0088

Receiver information
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.

Reciever party electronic address
Identifies the receiver party's electronic address

Example value: 7300010000001

Scheme identifier
Scheme identifier for the electronic address

Example value: 0088

Document response
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.

Response information

Message response code
An indicator stating whether the referenced message was cleared through validation and advanced to the next step in the process. A negative response states that the document was not processed because of identified issues.

Example value: RE

Response textual notes
Used to make any comments or instructions relevant to the response. The use of this element requires manual assessment by the receiver.

Example value: Rejected due to validation errors

Document reference
The document reference is used to provide a reference to the envelope of the business document on which the message level response is based. The message level response message may only cover exactly one business document. The element 'cac:DocumentResponse/cac:DocumentReference/cbc:ID' MUST contain the instance identifier of the envelope of the original business document.

Document identifier
Identifies the document on which the message level response is based.

Example value: EnvelopeID-12345

Document type code
The type of the document being referred to, expressed as a code.

Example value: 9

Document version identifier
The version of the document that has been identified with the document identifier.

Example value: 2

Line response information
A response to a particular line in the document. If the document response is negative (code='RE'), the line response element is used to specify the errors in the business document.

Line reference
Identifies the line in the business document to which the reported issue applies

Section identifier
Identifies the section of the document to which the reported issue applies. The LineID element must be used to indicate where in the business document the error occurred by using XPath to reference the element causing the error. To cater for scenarios where it is not possible to provide XPath, a dummy value must be applied. The dummy value must consist of the characters NA. This is due to that the LineID element is mandatory in the ApplicationResponse message in UBL 2.1 on which the MLR message is based.

Example value: /Catalogue/cac:CatalogueLine[3]/cac:Item[1]/cac:ClassifiedTaxCategory[1]/cbc:ID[1]

Line response information

Line response code
A code stating whether the referenced line was accepted or rejected.

Example value: RE

Issue description
The description of the issue identified in the transaction document.

Example value: Validation gives error [CL-T77-R002]- Tax categories MUST be coded using UN/ECE 5305 code list

Status information

Issue type coded
A codified verison of the issue description that describes the nature of the issue e.g. Syntax violation, Business rule violation, etc.

Example value: BV