Peppol BIS Billing 3.0 - Examples of selected parts of the transaction

French translation of chapter 11 of the official documentation Source: https://docs.peppol.eu/poacc/billing/3.0/bis/

11. Examples of selected parts of the transaction

In the sub-chapters below, you will find examples of selected parts of the transaction. Please also consult the chapter "UBL schemas and namespaces" for details on all elements and attributes, as well as their rules and the use of code lists.

11.1. Parties

The following roles can be specified. The same actor can play more than one role depending on the processing procedure.

Further details on roles/actors can be found in the chapter Parties and roles.

11.1.1. Seller (AccountingSupplierParty)

The seller is mandatory information and is provided in the cac:AccountingSupplierParty element

UBL example of seller information:

<cac:AccountingSupplierParty>
    <cac:Party>
        <cbc:EndpointID schemeID="0088">7300010000001</cbc:EndpointID>
        <!-- (1) -->
        <cac:PartyIdentification>
            <cbc:ID schemeID="0088">7300010000001</cbc:ID>
            <!-- (2) -->
        </cac:PartyIdentification>
        <cac:PartyName>
            <cbc:Name>SupplierTradingName Ltd.</cbc:Name>
        </cac:PartyName>
        <cac:PostalAddress>
            <cbc:StreetName>Main street 1</cbc:StreetName>
            <cbc:AdditionalStreetName>Postbox 123</cbc:AdditionalStreetName>
            <cbc:CityName>London</cbc:CityName>
            <cbc:PostalZone>GB 123 EW</cbc:PostalZone>
            <cbc:CountrySubentity>West London district</cbc:CountrySubentity>
            <cac:AddressLine>
                <cbc:Line>Third address line</cbc:Line>
            </cac:AddressLine>
            <cac:Country>
                <cbc:IdentificationCode>GB</cbc:IdentificationCode>
            </cac:Country>
        </cac:PostalAddress>
        <cac:PartyTaxScheme>
            <cbc:CompanyID>GB76576657</cbc:CompanyID>
            <!-- (3) -->
            <cac:TaxScheme>
                <cbc:ID>VAT</cbc:ID>
            </cac:TaxScheme>
        </cac:PartyTaxScheme>
        <cac:PartyTaxScheme>
            <cbc:CompanyID>TaxRegistrationID</cbc:CompanyID>
            <cac:TaxScheme>
                <cbc:ID>TAX</cbc:ID>
            </cac:TaxScheme>
        </cac:PartyTaxScheme>
        <cac:PartyLegalEntity>
            <cbc:RegistrationName>SupplierOfficialName Ltd</cbc:RegistrationName>
            <cbc:CompanyID>GB983294</cbc:CompanyID>
            <cbc:CompanyLegalForm>Private Limited Company</cbc:CompanyLegalForm>
        </cac:PartyLegalEntity>
        <cac:Contact>
            <cbc:Name>John Doe</cbc:Name>
            <cbc:Telephone>9384203984</cbc:Telephone>
            <cbc:ElectronicMail>john.doe@foo.bar</cbc:ElectronicMail>
        </cac:Contact>
    </cac:Party>
</cac:AccountingSupplierParty>
Ref Description
(1) The schemeID attribute is mandatory for electronic addresses, i.e. EndpointID
(2) The schemeID attribute is recommended for all party identifiers
(3) VAT identifiers must be prefixed with the country code

11.1.2. Buyer (AccountingCustomerParty)

The buyer is mandatory information and is provided in the cac:AccountingCustomerParty element

UBL example of buyer information:

<cac:AccountingCustomerParty>
    <cac:Party>
        <cbc:EndpointID schemeID="0002">FR23342</cbc:EndpointID>
        <!-- (1) -->
        <cac:PartyIdentification>
            <cbc:ID schemeID="0002">FR23342</cbc:ID>
            <!-- (2) -->
        </cac:PartyIdentification>
        <cac:PartyName>
            <cbc:Name>BuyerTradingName AS</cbc:Name>
        </cac:PartyName>
        <cac:PostalAddress>
            <cbc:StreetName>Huvudgatan 32</cbc:StreetName>
            <cbc:AdditionalStreetName>Po box 878</cbc:AdditionalStreetName>
            <cbc:CityName>Stockholm</cbc:CityName>
            <cbc:PostalZone>45634</cbc:PostalZone>
            <cac:AddressLine>
                <cbc:Line>Third line</cbc:Line>
            </cac:AddressLine>
            <cac:Country>
                <cbc:IdentificationCode>SE</cbc:IdentificationCode>
            </cac:Country>
        </cac:PostalAddress>
        <cac:PartyTaxScheme>
            <cbc:CompanyID>SE459837593701</cbc:CompanyID>
            <!-- (3) -->
            <cac:TaxScheme>
                <cbc:ID>VAT</cbc:ID>
            </cac:TaxScheme>
        </cac:PartyTaxScheme>
        <cac:PartyLegalEntity>
            <cbc:RegistrationName>Buyer Official Name</cbc:RegistrationName>
            <cbc:CompanyID schemeID="0183">39937423947</cbc:CompanyID>
            <!-- (4) -->
        </cac:PartyLegalEntity>
        <cac:Contact>
            <cbc:Name>Lisa Johnson</cbc:Name>
            <cbc:Telephone>23434234</cbc:Telephone>
            <cbc:ElectronicMail>lj@buyer.se</cbc:ElectronicMail>
        </cac:Contact>
    </cac:Party>
</cac:AccountingCustomerParty>
Ref Description
(1) The schemeID attribute is mandatory for electronic addresses, i.e. EndpointID
(2) The schemeID attribute is recommended for all party identifiers
(3) VAT identifiers must be prefixed with the country code
(4) The schemeID attribute is recommended for party legal entity identifiers

11.1.3. Payee (PayeeParty)

The payee is optional information. If this information is not provided, the seller is the payee. When the payee information is sent, it indicates that a factoring situation is documented.

To reflect the assignment of an invoice to a factor, it is necessary to:

  1. have a non-liability clause (notice) on the invoice indicating that the invoice has been assigned to a factor. The clause must be given using the invoice note (BT-22) at document level.
  2. identify the factor as the payee
  3. have the bank account changed in favor of a factor.

UBL example of payee information:

<cac:PayeeParty>
    <cac:PartyIdentification>
        <cbc:ID schemeID="0192">987654325</cbc:ID>
        <!-- (1) -->
    </cac:PartyIdentification>
    <cac:PartyName>
        <cbc:Name>Payee party</cbc:Name>
    </cac:PartyName>
    <cac:PartyLegalEntity>
        <cbc:CompanyID schemeID="0192">987654325</cbc:CompanyID>
        <!-- (2) -->
    </cac:PartyLegalEntity>
</cac:PayeeParty>
Ref Description
(1) The schemeID attribute is recommended for all party identifiers
(2) The schemeID attribute is recommended for party legal entity identifiers

11.1.4. Seller's tax representative (TaxRepresentativeParty)

The seller's tax representative is relevant for sellers delivering goods and services in a country without a permanent establishment in that country. In such cases, the tax representative information must be included in the invoice.

UBL example of tax representative information:

<cac:TaxRepresentativeParty>
    <cac:PartyName>
        <cbc:Name>TaxRepresentative Name</cbc:Name>
    </cac:PartyName>
    <cac:PostalAddress>
        <cbc:StreetName>Regent street 32</cbc:StreetName>
        <cbc:AdditionalStreetName>Building 23</cbc:AdditionalStreetName>
        <cbc:CityName>London</cbc:CityName>
        <cbc:PostalZone>23W 45H</cbc:PostalZone>
        <cbc:CountrySubentity>Subentity</cbc:CountrySubentity>
        <cac:AddressLine>
            <cbc:Line>Back door</cbc:Line>
        </cac:AddressLine>
        <cac:Country>
            <cbc:IdentificationCode>GB</cbc:IdentificationCode>
        </cac:Country>
    </cac:PostalAddress>
    <cac:PartyTaxScheme>
        <cbc:CompanyID>GB122324324535</cbc:CompanyID>
        <!-- (1) -->
        <cac:TaxScheme>
            <cbc:ID>VAT</cbc:ID>
        </cac:TaxScheme>
    </cac:PartyTaxScheme>
</cac:TaxRepresentativeParty>
Ref Description
(1) VAT identifiers must be prefixed with the country code

11.2. Delivery details (Date and Place)

Delivery details can be given at document level.

The delivery place and date are recommended and must be sent unless this does not affect the ability to guarantee the accuracy of the invoice.

The delivery element contains information on the name, address and identifier of the delivery location (cac:Delivery/cac:DeliveryLocation/cbc:ID) which can be used if the delivery location is defined by an identifier. For example the GLN (Global Location Number) issued by GS1.

UBL example of delivery information:

<cac:Delivery>
    <cbc:ActualDeliveryDate>2017-11-01</cbc:ActualDeliveryDate>
    <cac:DeliveryLocation>
        <cbc:ID schemeID="0088">7300010000001</cbc:ID>
        <cac:Address>
            <cbc:StreetName>Delivery street 2</cbc:StreetName>
            <cbc:AdditionalStreetName>Building 56</cbc:AdditionalStreetName>
            <cbc:CityName>Stockholm</cbc:CityName>
            <cbc:PostalZone>21234</cbc:PostalZone>
            <cac:AddressLine>
                <cbc:Line>Gate 15</cbc:Line>
            </cac:AddressLine>
            <cac:Country>
                <cbc:IdentificationCode>SE</cbc:IdentificationCode>
            </cac:Country>
        </cac:Address>
    </cac:DeliveryLocation>
    <cac:DeliveryParty>
        <cac:PartyName>
            <cbc:Name>Delivery party Name</cbc:Name>
        </cac:PartyName>
    </cac:DeliveryParty>
</cac:Delivery>

11.3. References

Invoice verification support is a key function of an invoice. The invoice must provide enough information to look up the relevant existing documentation, electronic or paper.

Note: Any reference element must contain valid information; if you do not have a reference, the element must not be present in the instance document.

Invoice and credit note transactions support the following references to existing documentation:

11.3.1. Purchase order and sales order reference

The purchase order is conditional. If a purchase order reference exists, use it, otherwise use the buyer reference (see "Buyer reference").

The customer will issue an order with a unique order number. This unique purchase order number must be provided as the order reference on the invoice.

If the order reference is given at header level, the line-level order reference element can be used to indicate the order line numbers.

A sales order is issued by the seller, confirming the sale of specified products.

Note: In the invoice, a purchase order reference and a sales order reference can be given, but be aware that an invoice instance cannot have a sales order reference without the corresponding purchase order reference.

UBL example of order and sales order reference:

<cac:OrderReference>
    <cbc:ID>o-998877</cbc:ID>                    <!-- (1) -->
    <cbc:SalesOrderID>so-12343</cbc:SalesOrderID> <!-- (2) -->
</cac:OrderReference>
Ref Description
(1) Purchase order reference
(2) Sales order reference

11.3.2. Buyer reference

The buyer reference, known as "Your ref.", is conditional. An invoice must have either the buyer reference or the order reference (see "Purchase order and sales order reference").

The element is used for the reference of the person who ordered the products/services. For example the name of the person ordering, the employee number or a code identifying that person or that department/group. "Your ref." is often used for internal routing at the recipient, and it is therefore important to fill this element with the correct values according to the recipient's needs.

If neither the buyer reference nor a reference to an order is provided by the customer, the name of the person ordering or designated for the customer can be provided in the buyer reference if known by the supplier.

Note: When a reference is provided by the customer, the correct element must contain the provided reference.

UBL example of buyer reference:

<cbc:BuyerReference>0150abc</cbc:BuyerReference>

11.3.3. Invoiced object identifier

The invoiced object identifier is the identifier of an object on which the invoice is based, given by the seller. Examples can be a subscription number, a phone number, a meter point, a vehicle, a person, etc., as the case may be.

If it is not clear to the recipient which scheme is used for the identifier, a conditional scheme identifier must be used, which must be chosen from the "Invoiced object identifier scheme" list.

The invoiced object reference is provided using the cac:AdditionalDocumentReference element with document type code = 130

UBL example of invoiced object identifier:

<cac:AdditionalDocumentReference>
    <cbc:ID schemeID="ABT">DR35141</cbc:ID>       <!-- (1) -->
    <cbc:DocumentTypeCode>130</cbc:DocumentTypeCode> <!-- (2) -->
</cac:AdditionalDocumentReference>
Ref Description
(1) Scheme identifier from the UN/CEFACT 1153 code list
(2) The document type code must be '130' to indicate the invoiced object

11.3.4. Contract reference

To reference or match an invoice to a purchase contract, the contract number can be specified as follows:

UBL example of contract reference:

<cac:ContractDocumentReference>
    <cbc:ID>framework no 1</cbc:ID>
</cac:ContractDocumentReference>

11.3.5. Despatch advice and receipt advice references

To reference or match an invoice to a despatch advice or a receipt advice, use the following elements:

UBL example of despatch advice and receipt advice:

<cac:DespatchDocumentReference>
    <cbc:ID>despadv-3</cbc:ID>     <!-- (1) -->
</cac:DespatchDocumentReference>
<cac:ReceiptDocumentReference>
    <cbc:ID>resadv-1</cbc:ID>      <!-- (2) -->
</cac:ReceiptDocumentReference>
Ref Description
(1) Despatch advice
(2) Receipt advice

11.3.6. Tender reference

To identify the tender or the lot to which the invoice relates, use 'OriginatorDocumentReference'. The identifier is, in most cases, the procurement procedure identifier.

UBL example of tender reference:

<cac:OriginatorDocumentReference>
    <cbc:ID>ppid-123</cbc:ID>
</cac:OriginatorDocumentReference>

11.3.7. Project reference

The project reference is optional and is sent in an invoice in the cac:ProjectReference/cbc:ID element. In a credit note, this element does not exist, and the project reference is sent using the cac:AdditionalDocumentReference[cbc:DocumentTypeCode='50']/cbc:ID element.

Note: When sending the project reference, only cbc:ID and cbc:DocumentTypeCode are allowed in the cac:AdditionalDocumentReference element.

UBL example of project reference in an invoice:

<cac:ProjectReference>
    <cbc:ID>project333</cbc:ID>
</cac:ProjectReference>

UBL example of project reference in a credit note:

<cac:AdditionalDocumentReference>
    <cbc:ID>p-2347234</cbc:ID>              <!-- (2) -->
    <cbc:DocumentTypeCode>50</cbc:DocumentTypeCode> <!-- (1) -->
</cac:AdditionalDocumentReference>
Ref Description
(1) Code 50 indicating that it is a project reference
(2) The project reference identifier

11.4. Previous invoice references

A credit note or a negative invoice can refer to one or more original invoices. This is done in the business group BG-3 Previous invoice reference, by providing the invoice number and the issue date. The issue date must be provided if the previous invoice reference is not unique.

In the case where the correction applies to a large number of invoices, the invoicing period (BG-14), possibly combined with a clarifying invoice note (BT-22), can be given instead at document level.

UBL example of previous invoice information:

<cac:BillingReference>
    <cac:InvoiceDocumentReference>
        <cbc:ID>123</cbc:ID>                      <!-- (1) -->
        <cbc:IssueDate>2017-10-20</cbc:IssueDate> <!-- (2) -->
    </cac:InvoiceDocumentReference>
</cac:BillingReference>
<cac:BillingReference>                            <!-- (3) -->
    <cac:InvoiceDocumentReference>
        <cbc:ID>124</cbc:ID>
    </cac:InvoiceDocumentReference>
</cac:BillingReference>
Ref Description
(1) The identifier is mandatory if cac:BillingReference is provided
(2) The issue date must be filled in if the invoice reference is not unique
(3) Repeat cac:BillingReference to add several previous invoice references

11.5. Allowances and charges

Invoice and credit note transactions have elements for allowances/charges at 3 levels.

The cac:AllowanceCharge element with the cbc:ChargeIndicator sub-element indicates whether the instance is a charge (true) or an allowance (false).

The header level: Applies to the whole invoice and is included in the calculation of the invoice total amount.

  • Several allowances and charges can be provided
  • The VAT specification for allowances and charges, cac:TaxCategory with sub-elements, must be provided
  • The sum of all allowances and charges at header level must be specified respectively in cbc:AllowanceTotalAmount and cbc:ChargeTotalAmount. See Calculation formulas in UBL syntax

The line level: Applies at line level and is included in the line amount calculation.

  • Several allowances and charges can be provided
  • The VAT specification for allowances and charges must not be specified, because the VAT category indicated for the invoice line itself also applies to the allowances or charges of that line.
  • The sum of all allowances and charges at line level must be taken into account, subtracted or added, when calculating the line extension amount. These line-level allowances and charges must not be calculated in the header-level elements.

The Price element at line level: A way to inform the buyer how the price is set. Also relevant if the seller or the buyer wants to record the discount in their accounting systems. The price itself must always be the net price, i.e. the base amount reduced by an allowance.

  • Only one allowance occurrence is allowed.
  • The VAT specification for the allowance must not be specified
  • The price-related allowance must not be part of any other calculation.
  • The price-related allowance can specify the amount and the base amount.

Further details on the allowance/charge amount calculation can be found in Allowance/charge amount calculation.

UBL example of allowances and charges at document level:

<cac:AllowanceCharge>
    <cbc:ChargeIndicator>true</cbc:ChargeIndicator>                <!-- (1) -->
    <cbc:AllowanceChargeReasonCode>FC</cbc:AllowanceChargeReasonCode>
    <cbc:AllowanceChargeReason>Service de fret</cbc:AllowanceChargeReason>
    <cbc:MultiplierFactorNumeric>2</cbc:MultiplierFactorNumeric>   <!-- (4) -->
    <cbc:Amount currencyID="EUR">20</cbc:Amount>                   <!-- (5) -->
    <cbc:BaseAmount currencyID="EUR">1000</cbc:BaseAmount>         <!-- (3) -->
    <cac:TaxCategory>
        <cbc:ID>S</cbc:ID>
        <cbc:Percent>25</cbc:Percent>
        <cac:TaxScheme>
            <cbc:ID>VAT</cbc:ID>
        </cac:TaxScheme>
    </cac:TaxCategory>
</cac:AllowanceCharge>
<cac:AllowanceCharge>
    <cbc:ChargeIndicator>false</cbc:ChargeIndicator>               <!-- (2) -->
    <cbc:AllowanceChargeReasonCode>65</cbc:AllowanceChargeReasonCode>
    <cbc:AllowanceChargeReason>Remise erreur de production</cbc:AllowanceChargeReason>
    <cbc:Amount currencyID="EUR">10</cbc:Amount>
    <cac:TaxCategory>
        <cbc:ID>S</cbc:ID>
        <cbc:Percent>25</cbc:Percent>
        <cac:TaxScheme>
            <cbc:ID>VAT</cbc:ID>
        </cac:TaxScheme>
    </cac:TaxCategory>
</cac:AllowanceCharge>
Ref Description
(1) ChargeIndicator = true to indicate a charge
(2) ChargeIndicator = false to indicate an allowance
(3) Base amount, to be used with the percentage to calculate the amount
(4) Charge percentage
(5) Amount = Base amount x (Percentage / 100)

UBL example of allowances and charges on an invoice line:

<cac:AllowanceCharge>
    <cbc:ChargeIndicator>true</cbc:ChargeIndicator>
    <cbc:AllowanceChargeReasonCode>CG</cbc:AllowanceChargeReasonCode>
    <cbc:AllowanceChargeReason>Nettoyage</cbc:AllowanceChargeReason>
    <cbc:MultiplierFactorNumeric>10</cbc:MultiplierFactorNumeric>
    <cbc:Amount currencyID="EUR">1</cbc:Amount>
    <cbc:BaseAmount currencyID="EUR">10</cbc:BaseAmount>
</cac:AllowanceCharge>
<cac:AllowanceCharge>
    <cbc:ChargeIndicator>false</cbc:ChargeIndicator>
    <cbc:AllowanceChargeReasonCode>95</cbc:AllowanceChargeReasonCode>
    <cbc:AllowanceChargeReason>Remise</cbc:AllowanceChargeReason>
    <cbc:Amount currencyID="EUR">101</cbc:Amount>
</cac:AllowanceCharge>

11.6. VAT accounting currency

Article 230 of Directive 2006/112/EC states:

The amounts shown on the invoice may be expressed in any currency, provided that the VAT amount payable is expressed in the national currency of the Member State in which the supply of goods or services takes place, using the conversion mechanism provided for in Article 91.

If the billing currency is different from the national currency, this is expressed in the invoice by indicating the national currency in the VAT accounting currency element (BT-6), and the VAT amount payable in the national currency is indicated in the Invoice total VAT amount in the accounting currency element (BT-111). The exchange rate to be used for the calculation is described in Article 91 of Directive 2006/112/EC. The exchange rate is not specified in the invoice instance, and therefore this calculation is not validated.

UBL example of VAT currency:

<cbc:DocumentCurrencyCode>EUR</cbc:DocumentCurrencyCode>
<!-- (1) -->
<cbc:TaxCurrencyCode>SEK</cbc:TaxCurrencyCode>
<!-- (2) -->

<cac:TaxTotal>
    <cbc:TaxAmount currencyID="EUR">1000.00</cbc:TaxAmount>
    <!-- (3) -->
    <cac:TaxSubtotal>
        <cbc:TaxableAmount currencyID="EUR">4000.0</cbc:TaxableAmount>
        <cbc:TaxAmount currencyID="EUR">1000</cbc:TaxAmount>
        <cac:TaxCategory>
            <cbc:ID>S</cbc:ID>
            <cbc:Percent>25</cbc:Percent>
            <cac:TaxScheme>
                <cbc:ID>VAT</cbc:ID>
            </cac:TaxScheme>
        </cac:TaxCategory>
    </cac:TaxSubtotal>
</cac:TaxTotal>
<cac:TaxTotal>
    <cbc:TaxAmount currencyID="SEK">100017.50</cbc:TaxAmount>
    <!-- (4) -->
</cac:TaxTotal>
Ref Description
(1) Billing currency
(2) National currency
(3) VAT amount in the billing currency
(4) VAT amount in the national currency

11.7. Payment means information

11.7.1. Credit transfer

If payment is made by credit transfer, the payment account identifier (BT-84) is mandatory.

See "Payment means type code" for all allowed codes. Example codes for payment by credit transfer:

  • 30 - Credit transfer
  • 58 - SEPA credit transfer

UBL example of payment means information for a credit transfer:

<cac:PaymentMeans>
    <cbc:PaymentMeansCode name="Credit transfer">30</cbc:PaymentMeansCode> <!-- (1) -->
    <cbc:PaymentID>93274234</cbc:PaymentID>                                <!-- (2) -->
    <cac:PayeeFinancialAccount>
        <cbc:ID>32423940</cbc:ID>                                          <!-- (3) -->
        <cbc:Name>AccountName</cbc:Name>
        <cac:FinancialInstitutionBranch>
            <cbc:ID>BIC32409</cbc:ID>                                      <!-- (4) -->
        </cac:FinancialInstitutionBranch>
    </cac:PayeeFinancialAccount>
</cac:PaymentMeans>
Ref Description
(1) Mandatory, payment means code for credit transfer
(2) Remittance information
(3) Mandatory, IBAN (in the case of a SEPA payment) or a national account number (BBAN)
(4) BIC or a national clearing code

11.7.2. Payment by card

If the buyer has chosen to pay using a payment card such as a credit or debit card, the primary account number (PAN) information must be present in the invoice.

See "Payment means type code" for all allowed codes. Example codes for payment by card:

  • 48 - Payment card
  • 54 - Credit card
  • 55 - Debit card

UBL example of payment means information for a card payment:

<cac:PaymentMeans>
    <cbc:PaymentMeansCode name="Credit card">54</cbc:PaymentMeansCode>     <!-- (1) -->
    <cbc:PaymentID>9387439</cbc:PaymentID>
    <cac:CardAccount>
        <cbc:PrimaryAccountNumberID>123236</cbc:PrimaryAccountNumberID>   <!-- (2) -->
        <cbc:NetworkID>VISA</cbc:NetworkID>                               <!-- (3) -->
        <cbc:HolderName>Card holders name</cbc:HolderName>                <!-- (4) -->
    </cac:CardAccount>
</cac:PaymentMeans>
Ref Description
(1) Payment means code for credit card
(2) Mandatory, must be the last 4 to 6 digits of the payment card number
(3) Mandatory, used to identify the financial services network provider of the card. Examples: VISA, MasterCard, American Express.
(4) Cardholder name

11.7.3. Direct debit

See "Payment means type code" for all allowed codes. Example codes for payment by direct debit:

  • 49 - Direct debit
  • 59 - SEPA direct debit

UBL example of payment means information for a SEPA direct debit:

<cac:AccountingSupplierParty>
    <cac:Party>
        <cbc:EndpointID schemeID="0088">7300010000001</cbc:EndpointID>
        <cac:PartyIdentification>
            <cbc:ID>99887766</cbc:ID>
        </cac:PartyIdentification>
        <cac:PartyIdentification>
            <cbc:ID schemeID="SEPA">23123687</cbc:ID>                     <!-- (1) -->
        </cac:PartyIdentification>
<!-- code omis pour clarté -->
<cac:PaymentMeans>
    <cbc:PaymentMeansCode name="SEPA direct debit">59</cbc:PaymentMeansCode> <!-- (2) -->
    <cbc:PaymentID>payref2</cbc:PaymentID>                                   <!-- (3) -->
    <cac:PaymentMandate>
        <cbc:ID>123456</cbc:ID>                                              <!-- (4) -->
        <cac:PayerFinancialAccount>
            <cbc:ID>DK12328462834823</cbc:ID>
        </cac:PayerFinancialAccount>
    </cac:PaymentMandate>
</cac:PaymentMeans>
Ref Description
(1) Unique bank reference identifier of the seller or the payee, schemeID must have the value "SEPA"
(2) Payment means code
(3) Remittance information
(4) Mandate reference identifier

11.7.4. Payment by postal or bank giro

See "Payment means type code" for all allowed codes. Example codes for payment by postal or bank giro:

  • 50 - Payment by postal giro
  • 56 - Bank giro

UBL example of payment means information for a postal giro:

<cac:PaymentMeans>
    <cbc:PaymentMeansCode name="Postgiro">50</cbc:PaymentMeansCode> <!-- (1) -->
    <cbc:PaymentID>PgPaymRef-345</cbc:PaymentID>                    <!-- (2) -->
    <cac:PayeeFinancialAccount>
        <cbc:ID>98765432</cbc:ID>                                   <!-- (3) -->
    </cac:PayeeFinancialAccount>
</cac:PaymentMeans>
Ref Description
(1) Payment means code
(2) Remittance information
(3) Local postal account number

11.8. Intrastat

When EU Member States purchase from other EU members, traders generally need certain statistical information in the invoice, normally a classification code such as the Combined Nomenclature.

It is recommended to use the item classification identifier (BT-158) for this purpose, with the code "HS" as the list identifier.

UBL example of Combined Nomenclature information:

<cac:CommodityClassification>
    <cbc:ItemClassificationCode listID="HS">080110</cbc:ItemClassificationCode>
</cac:CommodityClassification>

11.9. Item information

11.9.1. Item identifiers

In an invoice line, the seller's item identifier, the buyer's item identifier and the standard item identifier can be provided. For the seller's and buyer's item identifiers, no scheme attribute is used, while the schemeID is mandatory for the standard item identification, and must come from the ISO 6523 ICD list.

UBL example of item identifiers:

<cac:Item>

    <!-- Code omis pour clarté -->
    <cac:BuyersItemIdentification>
        <cbc:ID>b-13214</cbc:ID>
    </cac:BuyersItemIdentification>
    <cac:SellersItemIdentification>
        <cbc:ID>97iugug876</cbc:ID>
    </cac:SellersItemIdentification>
    <cac:StandardItemIdentification>
        <cbc:ID schemeID="0160">97iugug876</cbc:ID> <!-- (1) -->
    </cac:StandardItemIdentification>

    <!-- Code omis pour clarté -->
Ref Description
(1) 0160 is the ICD value for a GTIN identifier

11.9.2. Item classification

Several different item classification codes can be provided per invoice line, and the codes must come from one of the classification schemes of the UNCL7143 code list.

UBL example of CPV usage:

<cac:CommodityClassification>
    <cbc:ItemClassificationCode listID="STI">09348023</cbc:ItemClassificationCode> <!-- (1) -->
</cac:CommodityClassification>
Ref Description
(1) listID must come from the UNCL7143 code list, and the code STI indicates that it is a CPV classification.

UBL example of UNSPSC:

<cac:CommodityClassification>
    <cbc:ItemClassificationCode listID="TST" listVersionID="19.05.01">86776</cbc:ItemClassificationCode> <!-- (1) -->
</cac:CommodityClassification>
Ref Description
(1) listID must come from the UNCL7143 code list, and the code TST indicates that it is an UNSPSC classification, listVersionID is optional, but can be used to specify the UNSPSC version. NOTE: in previous versions, the code MP was used as a temporary solution to identify UNSPSC. In the autumn 2019 version, it is replaced by the new 7143 code TST which is specific to UNSPSC.

11.10. Price information

An invoice must contain information on the item net price and additional information such as the gross price, the item price base quantity and the price allowance can be added.

For details on the price calculation, see Item net price (BT-146).

UBL example of price with price allowance:

<cac:Price>
    <cbc:PriceAmount currencyID="EUR">410</cbc:PriceAmount>     <!-- (4) -->
    <cbc:BaseQuantity unitCode="XBX">1</cbc:BaseQuantity>       <!-- (3) -->
    <cac:AllowanceCharge>
        <cbc:ChargeIndicator>false</cbc:ChargeIndicator>
        <cbc:Amount currencyID="EUR">40</cbc:Amount>            <!-- (2) -->
        <cbc:BaseAmount currencyID="EUR">450</cbc:BaseAmount>   <!-- (1) -->
    </cac:AllowanceCharge>
</cac:Price>
Ref Description
(1) Item gross price
(2) Allowance on item price
(3) Item price base quantity
(4) Item net price, must be equal to the item gross price - price allowance (if these elements are used)

UBL example of price without price allowance:

<cac:Price>
    <cbc:PriceAmount currencyID="EUR">200</cbc:PriceAmount>
    <cbc:BaseQuantity unitCode="C62">2</cbc:BaseQuantity>
</cac:Price>

11.11. Unit of measure

The unit of measure in an invoice allows the use of codes from UNECE Recommendation n 20 (version 11e), as well as codes from UNECE Recommendation n 21 prefixed with an X. See also "Unit of measure" for more information on the code lists.

Table 8. Examples of units of measure from Recommendation n 20:

Code Name
H87 Piece
KGM Kilogram
MTR Metre
LTR Litre
MTK Square metre
MTQ Cubic metre
KTM Kilometre
TNE Tonne (metric ton)
KWH Kilowatt hour
DAY Day
HUR Hour
MIN Minute

Table 9. Examples of units of measure from Recommendation n 21, prefixed with an X:

Code Name
XBG Bag
XBX Box
XCT Carton
XCY Cylinder
XBA Barrel
XPK Package
XPX Pallet
XRL Roll
XSA Bag
XST Sheet

UBL example of unit of measure:

<cbc:InvoicedQuantity unitCode="H87">10</cbc:InvoicedQuantity> <!-- (1) -->
<cbc:InvoicedQuantity unitCode="XPX">10</cbc:InvoicedQuantity> <!-- (2) -->
Ref Description
(1) Code H87 from Recommendation n 20
(2) Code PX, prefixed with an X from Recommendation n 21