Peppol BIS version 3 - November 2023 Release

Card	Name	Description
1..1	ubl:ApplicationResponse
1..1	• cbc:CustomizationID	Specification identification Identifies the specification of content and rules that apply to the transaction. Example value: `urn:fdc:peppol.eu:poacc:trns:invoice_response:3`
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:poacc:bis:invoice_response:3`
1..1	• cbc:ID	Response identifier An 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: `imr-123`
1..1	• cbc:IssueDate	Response issue date The date on which the transaction instance was issued. Example value: `2018-08-02`
0..1	• cbc:IssueTime	Response issue time The time at which the transaction instance was issued. Example value: `13:34:32`
0..1	• cbc:Note	Invoice response note General comments or instructions that are relevant to the response as a whole. Example value: `Please refer to previous email exchange regarding this invoice.`
1..1	• cac:SenderParty	Sender party
1..1	• • cbc:EndpointID	Sender party electronic address Identifies the sender party's electronic address Example value: `7300010000001`
M	• • • @schemeID	Scheme identifier Scheme identifier for the electronic address Example value: `0088`
0..1	• • cac:PartyIdentification	Party identification
1..1	• • • cbc:ID	Party identifier It should be possible to specify the identifier or identifiers for the party. Example value: `DK88777654`
o	• • • • @schemeID	Scheme identifier Scheme identifier for party identification Example value: `0184`
1..1	• • cac:PartyLegalEntity	Party name
1..1	• • • cbc:RegistrationName	Sender party name The name of the party sending the response. Example value: `Test company AS`
0..1	• • cac:Contact	Contact information
0..1	• • • cbc:Name	Party contact point name Then name of the sending party contact point for communication regarding this message. Example value: `Jens Jensen`
0..1	• • • cbc:Telephone	Party contact point telephone Then telephone for the sending party´s contact point for communication regarding this message. Example value: `23 23 23 23`
0..1	• • • cbc:ElectronicMail	Party contact point email Then email for the sending party´s contact point for communication regarding this message. Example value: `jj@test-company.dk`
1..1	• cac:ReceiverParty	Receiver party
1..1	• • cbc:EndpointID	Reciever party electronic address Identifies the receiver party's electronic address Example value: `7300010000001`
M	• • • @schemeID	Scheme identifier Scheme identifier for the electronic address Example value: `0088`
0..1	• • cac:PartyIdentification	Party identification
1..1	• • • cbc:ID	Reciever party identifier It should be possible to specify the identifier or identifiers for the party. Example value: `987654321`
o	• • • • @schemeID	Scheme identifier Scheme identifier for party identification Example value: `0192`
1..1	• • cac:PartyLegalEntity	Party name
1..1	• • • cbc:RegistrationName	Receiver party name The name of the party receiving the response. Example value: `AS MerTest`
1..1	• cac:DocumentResponse	Document response
1..1	• • cac:Response	Response
1..1	• • • cbc:ResponseCode	Invoice status A code stating the status of the invoice in the process. Example value: `RE`
0..1	• • • cbc:EffectiveDate	Status date The date when the status became effective. Example value: `2018-08-02`
0..unbounded	• • • cac:Status	Clarification information Clarification is mandatory when the status is UQ-Under query, RE - Rejected and CA - Conditionally accepted. Clarification may be given as a code, a description or both. If both are used, they must indicate the same clarification.
0..1	• • • • cbc:StatusReasonCode	Clarification code A code defining a clarification given for the invoice status.
M	• • • • • @listID	List identifier List identifier for clarification Example value: `OPStatusAction`
0..1	• • • • cbc:StatusReason	Clarification description The description of the clarification given for the invoice status. Example value: `TAX Reference not found`
0..unbounded	• • • • cac:Condition	Condition
1..1	• • • • • cbc:AttributeID	Detail type code A code defining the type of the detail Example value: `BT-48`
0..1	• • • • • cbc:Description	Detail value The value of the detail. Example value: `EU123456789`
1..1	• • cac:DocumentReference	Document reference
1..1	• • • cbc:ID	Invoice identifier An identifier for the invoice that the status applies to. The invoice identifier must be of the main invoice number that appears in the invoice itself. Example value: `inv-99876`
0..1	• • • cbc:IssueDate	Invoice issue date The date on which the referenced invoice was issued. Example value: `2018-08-01`
1..1	• • • cbc:DocumentTypeCode	Identifier Type code Example value: `380`
0..1	• • cac:IssuerParty	Seller party information
0..1	• • • cac:PartyIdentification	Party identification
1..1	• • • • cbc:ID	Seller party identifier It should be possible to specify the identifier or identifiers for the party. Example value: `987654321`
o	• • • • • @schemeID	Scheme identifier Scheme identifier for party identification Example value: `0192`
1..1	• • • cac:PartyName	Party name information
1..1	• • • • cbc:Name	Seller party name The party that issued the reference invoice. Example value: `AS MerTest`
0..1	• • cac:RecipientParty	Buyer party information
0..1	• • • cac:PartyIdentification	Party identification
1..1	• • • • cbc:ID	Buyer party identifier It should be possible to specify the identifier or identifiers for the party. Example value: `999888777`
o	• • • • • @schemeID	Scheme identifier Scheme identifier for party identification Example value: `0192`
1..1	• • • cac:PartyName	Party name
1..1	• • • • cbc:Name	Buyer party name The party to who the referenced invoice is issued. Example value: `Test company AS`

Peppol Invoice Response transaction 3.1 (T111)