Card Name Description
1..1 ubl:ApplicationResponse  
1..1 •   cbc:UBLVersionID

UBL VersionID
Identifies the UBL version on which the transaction instance is based.

Fixed value: 2.1

0..1 •   cbc:CustomizationID

Customization identifier
Identifies the specification of content and rules that apply to the transaction.

Example value: urn:www.cenbii.eu:transaction:biitrns058:ver2.0:extended:urn:www.difi.no:ehf:katalogbekreftelse:ver1.0

0..1 •   cbc:ProfileID

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

Example value: urn:www.cenbii.eu:profile:bii01:ver2.0

1..1 •   cbc:ID

Response identifier
An transaction instance must contain an identifier. The identifier enables positive referencing the document instance for various purposes including referencing between transactions that are part of the same process.

Example value: 1

1..1 •   cbc:IssueDate

Response issue date
The date on which the transaction instance was issued.

Example value: 2013-05-10

0..1 •   cbc:IssueTime

Response issue data
The time at which the transaction instance was issued.

0..n •   cbc:Note

Response textual notes
Used to make any comments or instructions relevant to the response, including the date that the reported decision becomes effective.

O •   •   @languageID
1..1 •   cac:SenderParty

Sender party
Information about message sender

0..1 •   •   cbc:EndpointID

Electronic address
A response may contain the party electronic address. The address can be of any format and the format should be identified in the message.

M •   •   •   @schemeID
0..1 •   •   cac:PartyIdentification

Party identification
Information about Party ID

1..1 •   •   •   cbc:ID

Party identifier
It should be possible to specify the identifier or identifiers for the party.

Example value: 923654321

O •   •   •   •   @schemeID
0..1 •   •   cac:PartyName

Party name
Information about party name.

1..1 •   •   •   cbc:Name

Party name
The name of the party sending the response.

Example value: Buyer

1..1 •   cac:ReceiverParty

Receiver party
Information about message receiver.

0..1 •   •   cbc:EndpointID

Electronic address
A response may contain the party electronic address. The address can be of any format and the format should be identified in the message.

M •   •   •   @schemeID
0..1 •   •   cac:PartyIdentification

Party identification
Information about Party ID

1..1 •   •   •   cbc:ID

Party identifier
It should be possible to specify the identifier or identifiers for the party.

Example value: 123456789

O •   •   •   •   @schemeID
0..1 •   •   cac:PartyName

Party name
Information about party name.

1..1 •   •   •   cbc:Name

Party name
The name of the party sending the response.

Example value: Supplier

0..1 •   cac:DocumentResponse

Document response
Information about the reason code

1..1 •   •   cac:Response

Response
Response information

0..1 •   •   •   cbc:ResponseCode

Coded decision
A code for the description of the response to the transaction document. AP= Accepted, RE = Rejected, UN/Cefact 4343 Response type code

Example value: AP

O •   •   •   •   @listID

Example value: UNCL4343

1..1 •   •   cac:DocumentReference

Document reference
Document reference information.

1..1 •   •   •   cbc:ID

Document identifier
Identifies the document being referred to

Example value: Catalogue-01

0..1 •   •   •   cbc:VersionID

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

Example value: 1