Card Name Description
1..1 ubl:ApplicationResponse

Notice publication response, root element

1..1 •   cbc:UBLVersionID

UBL version identifier
Requires UBL version 2.2

Fixed value: 2.2

1..1 •   cbc:CustomizationID

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

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

1..1 •   cbc:ProfileID

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:p008:1.1

1..1 •   cbc:ID

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

1..1 •   cbc:IssueDate

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

Example value: 2018-05-18

0..1 •   cbc:IssueTime

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

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

1..1 •   cac:SenderParty

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

1..1 •   •   cbc:EndpointID

Contracting body electronic address identifier
Electronic address of the sending party.

Example value: DE122268496

M •   •   •   @schemeID

Scheme identifier
Scheme identifier for the electronic address

Example value: 9930

1..1 •   cac:ReceiverParty

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.

1..1 •   •   cbc:EndpointID

Economic operator electronic address identifier
Electronic address of the receiving party

Example value: 500820007

M •   •   •   @schemeID

Scheme identifier
Scheme identifier for the electronic address

Example value: 9946

1..1 •   cac:DocumentResponse

Document response
The notice 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. The element 'cac:DocumentResponse/cac:Response/cac:Status/cbc:ConditionCode' MUST contain a condition related to the publication of the notice.

1..1 •   •   cac:Response

Response information

1..1 •   •   •   cbc:ResponseCode

Message response code
An indicator stating whether the referenced message was cleared through validation and advanced to the next step in the process. A "rejection" states that the notice was not processed because of identified issues. "Conditionally accepted" indicates that the publication of the notice is done with warnings indicated in the message. "Accepted" indicates that the notice will be published at a certain time. "Published" indicates that the notice has been published at a certain time.

Example value: RE

0..1 •   •   •   cbc:Description

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

0..1 •   •   •   cbc:EffectiveDate

Publication date
The date upon which this notice is published.

Example value: 2021-07-20

0..1 •   •   •   cbc:EffectiveTime

Publication time
The time upon which this notice is published.

Example value: 09:00:00+01:00

1..1 •   •   •   cac:Status

Publication status information

1..1 •   •   •   •   cbc:ConditionCode

Publication condition code
Specifies the condition related to the publication of the notice. The value "test" is used to indicate that the notice will be only used for the purpose to check its validity and not its publication. The value "test" is also used for negative responses. The value "forcast" is used to indicate a planned publication date in the future. The value "effective" is used to indicate an actual publication date.

Example value: FCST

1..1 •   •   cac:DocumentReference

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

1..1 •   •   •   cbc:ID

Publish notice identifier
Specifies the unique identifier of the container that describes the request to publish a notice on which the Notice Publication Response is based.

Example value: 4e3517fd-724d-44fc-b90b-5743c33ff68e

1..1 •   •   •   cbc:UUID

Notice identifier
Specifies the notice identifier (BT-701) allowing to uniquely distinguishing the notice.

Example value: 53EB9F20-EE12-474F-9424-78FC604E8FAE

0..1 •   •   •   cbc:DocumentTypeCode

UBL document schema
An identification of the UBL document schema of the notice being referred to, expressed as a code.

Fixed value: CN

0..1 •   •   •   cbc:VersionID

Notice version identifier
An identification of the version of the underlying notice (BT-757).

Example value: 1

0..n •   •   cac:LineResponse

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.

1..1 •   •   •   cac:LineReference

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

1..1 •   •   •   •   cbc:LineID

Section identifier
Identifies the section of the notice to which the reported issue applies. The LineID element must be used to indicate where in the notice 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: /ContractNotice/cac:ContractingParty[1]/cac:Party[1]/cac:PostalAddress[1]/cbc:CountrySubentityCode[1]

1..1 •   •   •   •   cac:DocumentReference

Document identifier
Specifies the unique document identifier to which the line response is related. Line responses may be given for the container that describes the request to publish a notice or they can be related to the referenced notice within the container.

1..1 •   •   •   •   •   cbc:ID

Document reference
A reference to the document containing the referenced line.

Fixed value: 53EB9F20-EE12-474F-9424-78FC604E8FAE

1..1 •   •   •   cac:Response

Line response information

0..1 •   •   •   •   cbc:ResponseCode

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

Example value: RE

1..1 •   •   •   •   cbc:Description

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

Example value: Validation gives error [Rule ID] - Organisation country subdivision (BT-500) MUST be coded using http://publications.europa.eu/resource/authority/nuts code list

1..1 •   •   •   •   cac:Status

Status information

1..1 •   •   •   •   •   cbc:StatusReasonCode

Issue type code
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