Peppol BIS Billing 3.0 - Data types and VAT

French translation of chapters 7 and 8 of the official documentation Source: https://docs.peppol.eu/poacc/billing/3.0/bis/

7. Semantic data types

Semantic data types are used to link the semantic concepts expressed by the information elements defined in the EN 16931 semantic model and the technical implementation. Semantic data types define the allowed value domain for the content, as well as any additional information component (attributes) necessary to guarantee its precise interpretation.

Note: The technical implementation details can be found in the chapter "UBL schemas and namespaces".

7.1. Primitive types

The content of semantic data types can be one of the following primitive types. These primitive types come from ISO 15000-5:2014, Annex A.

Primitive type Definition
Binary A finite-length sequence of binary digits.
Date Time point representing a calendar day on a time scale consisting of an origin and a succession of calendar days (ISO 8601:2004).
Decimal A subset of real numbers, which can be represented by decimal digits.
String A finite sequence of characters.

7.2. Semantic data types

The different semantic data types are described in the tables below, where various characteristics such as attributes, format and decimals as well as the base type are defined for each semantic data type. They are based on ISO 15000-5:2014.

When used in an invoice instance, each data element will contain data. In the tables below, this is identified as the "content". Whenever a business term is used, this term must always have a content and therefore the content is always mandatory.

7.2.1. Amount

An amount indicates a numerical monetary value. The currency of the amount is defined as a separate business term.

Note: The amount is floating up to two digits after the decimal point.

Component Usage Primitive type Example
Content Mandatory Decimal 10000.25

7.2.2. Unit price amount

A unit price amount indicates a numerical monetary value for data elements containing item prices that can be multiplied by item quantities. The currency of the amount is defined as a separate business term.

Note: The unit price amount does not set a restriction on the number of decimals, unlike the Amount type.

Component Usage Primitive type Example
Content Mandatory Decimal 10000.1234

7.2.3. Percentage

Percentages are given in hundredths (per cent), for example the value 34.78% in percentage terms is given as 34.78.

Note: No restriction on the number of decimals for percentages.

Component Usage Primitive type Example
Content Mandatory Decimal 34.7812

7.2.4. Quantity

Quantities are used to indicate a number of units, for example for items. The unit of measure code is defined as a separate business term.

Note: No restriction on the number of decimals for quantities.

Component Usage Primitive type Example
Content Mandatory Decimal 10000.1234

7.2.5. Code

Codes are used to specify the allowed values in elements as well as for option lists. The code differs from the identifier in that the allowed values have standardized meanings that can be known to the recipient.

Note: Codes must be entered exactly as indicated in the selected code list of the applicable syntax.

Component Usage Primitive type Example
Content Mandatory String Abc123

7.2.6. Identifier

Identifiers (ID) are keys issued by the issuer or the recipient of a document or line, or by a third party.

Note: The use of attributes is specified for each information element.

Component Usage Primitive type Example
Content Mandatory String abc:123-DEF
Scheme identifier Conditional String GLN
Scheme version identifier Conditional String 1.0

7.2.7. Date

Dates must comply with the "Complete calendar date representation" as specified by ISO 8601:2004, format YYYY-MM-DD.

Note: Dates must not include time zone information.

Component Usage Primitive type Example
Content Mandatory Date 2017-12-01

7.2.8. Document reference

Document reference types are identifiers that have been assigned to a document or document line by the buyer, the seller or a third party.

Component Usage Primitive type Example
Content Mandatory String abc:123-DEF

7.2.9. Text

Text is the actual wording of anything that is written or printed. Line breaks in the text may be present, and any line break must be preserved and respected by the recipient's system.

Component Usage Primitive type Example
Content Mandatory String 5% discount if paid within 30 days

7.2.10. Binary objects

Binary objects can be used to describe files transmitted with the invoice. The attachment feature is not intended to include a copy of the invoice in an image format (such as PDF). Attaching a copy of the invoice is not compliant with this specification.

Attachments must be transmitted with the invoice. The binary object has two additional components: a MIME code, which specifies the MIME type of the attachment, and a file name provided by (or on behalf of) the issuer of the invoice or credit note.

Component Usage Primitive type Example
Content Mandatory Binary QmFzZTY0IGNvbnRlbnQgZXhhbXBsZQ==
MIME code Mandatory String image/jpeg
File name Mandatory String drawing5.jpg

An invoice or credit note recipient must accept and process attachments compliant with the "Document attachment media type" code list.

8. Value added tax (VAT)

The chapters below describe the different VAT information that can be provided in a Peppol invoice or credit note.

See also VAT exemption codes for details on the VAT category code list, and VAT calculation for a detailed explanation and an example on how to perform the calculations for the VAT breakdown.

8.1. Line VAT information

Each invoice line must have the VAT category code of the invoiced item (BT-151), and for all VAT categories except "Not subject to VAT" (O), the VAT rate must be provided.

8.2. Document-level allowance or charge

Each document-level charge or allowance must have the document-level allowance or charge VAT category code (BT-95 and BT-102), and for all VAT categories except "Not subject to VAT" (O), the VAT rate must be provided.

8.3. VAT breakdown

A VAT breakdown must be provided for each distinct combination of VAT category code and VAT rate found either in the line VAT information or in the document-level allowances or charges. For some VAT categories, the VAT rate must be zero, and therefore the rate is not needed to group the VAT breakdown for those.

Please note that for the VAT rate, only significant decimals must be taken into account, i.e. any difference in trailing zeros must not lead to different VAT breakdowns.

Example:

Invoice line 1 has category code = S and VAT rate = 25 Invoice line 2 has category code = S and VAT rate = 25.00

This must give a single VAT breakdown.

8.4. Invoice total VAT amount

The invoice total VAT amount (BT-110) is the sum of all VAT amounts by category (BT-117).