CEN/TS 16931-3-2:2020
(Main)Electronic invoicing - Part 3-2: Syntax binding for ISO/IEC 19845 (UBL 2.1) invoice and credit note
Electronic invoicing - Part 3-2: Syntax binding for ISO/IEC 19845 (UBL 2.1) invoice and credit note
This document specifies the mapping between the semantic model of an electronic invoice, included in EN 16931-1 and the UBL 2.1 syntax (ISO/IEC 19845). For each element in the semantic model (including sub-elements or supplementary components such as Identification scheme identifiers) it is defined which element in the syntax is to be used to contain its information contents. Any mismatches between semantics, format, cardinality or structure are indicated.
Elektronische Rechnungsstellung - Teil 3-2: Umsetzung in die Syntax ISO/IEC 19845 (UBL 2.1) Rechnung und Gutschrift
Dieses Dokument legt die Zuordnung (en: mapping) zwischen dem semantischen Modell einer elektronischen Rechnung, das in EN 16931 1 enthalten ist, und der Syntax UBL 2.1 (ISO/IEC 19845) fest. Für jedes Element im semantischen Modell (einschließlich Unterelemente oder Ergänzungskomponenten wie Identifikationsschema-Kennungen [en: Identification scheme identifiers]) wird definiert, welches Syntax-Element für seine Informationsinhalte verwendet werden muss. Nichtübereinstimmungen zwischen Semantik, Format, Kardinalität oder Struktur werden angezeigt.
Facturation électronique - Partie 3-2 : Liaison de syntaxe pour ISO/IEC 19845 (UBL 2.1) Factures et les notes de crédit
Elektronsko izdajanje računov - 3-2. del: Povezava sintakse za račun in dobropis ISO/IEC 19845 (UBL 2.1)
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
01-september-2020
Nadomešča:
SIST-TS CEN/TS 16931-3-2:2018
SIST-TS CEN/TS 16931-3-2:2018/AC:2018
Elektronsko izdajanje računov - 3-2. del: Povezava sintakse za račun in dobropis
ISO/IEC 19845 (UBL 2.1)
Electronic invoicing - Part 3-2: Syntax binding for ISO/IEC 19845 (UBL 2.1) invoice and
credit note
Elektronische Rechnungsstellung - Teil 3-2: Umsetzung in die Syntax ISO/IEC 19845
(UBL 2.1) Rechnung und Gutschriftsanzeige
Facturation électronique - Partie 3-2 : Correspondance syntaxique pour les factures et
les avoirs utilisant l'ISO/IEC 19845 (UBL 2.1)
Ta slovenski standard je istoveten z: CEN/TS 16931-3-2:2020
ICS:
03.100.20 Trgovina. Komercialna Trade. Commercial function.
dejavnost. Trženje Marketing
35.240.63 Uporabniške rešitve IT v IT applications in trade
trgovini
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
CEN/TS 16931-3-2
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
June 2020
TECHNISCHE SPEZIFIKATION
ICS 35.240.20; 35.240.63 Supersedes CEN/TS 16931-3-2:2017
English Version
Electronic invoicing - Part 3-2: Syntax binding for ISO/IEC
19845 (UBL 2.1) invoice and credit note
Facturation électronique - Partie 3-2 : Liaison de Elektronische Rechnungsstellung - Teil 3-2: Umsetzung
syntaxe pour ISO/IEC 19845 (UBL 2.1) Factures et les in die Syntax ISO/IEC 19845 (UBL 2.1) Rechnung und
notes de crédit Gutschrift
This Technical Specification (CEN/TS) was approved by CEN on 11 November 2019 for provisional application.
The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to
submit their comments, particularly on the question whether the CEN/TS can be converted into a European Standard.
CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS
available promptly at national level in an appropriate form. It is permissible to keep conflicting national standards in force (in
parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2020 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 16931-3-2:2020 E
worldwide for CEN national Members.
Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 6
3 Terms and definitions . 6
4 Syntax binding to UBL 2.1 . 7
4.1 Introduction . 7
4.2 Data types . 7
4.3 Mapping the Invoice model .10
4.4 Mapping the Credit Note model .74
4.5 Validation artefacts . 136
5 Mismatches . 136
5.1 Semantic level . 136
5.2 Structural level . 136
5.3 Cardinality level . 136
5.4 Syntactical level . 137
Annex A (normative) Code lists . 138
A.1 Introduction . 138
A.2 Code lists . 138
A.2.1 ISO 3166-1 — Country Codes . 138
A.2.2 ISO 4217 — Currency codes . 138
A.2.3 ISO/IEC 6523 — Identifier scheme code . 139
A.2.4 UNTDID 1001 — Document type . 140
A.2.5 UNTDID 1153 — Reference code qualifier . 141
A.2.6 VAT Identifier . 142
A.2.7 VAT Category code . 142
A.2.8 UNTDID 2005/ UNTDID 2475 — Event time code . 143
A.2.9 UNTDID 4451 — Text subject qualifier . 143
A.2.10 UNTDID 4461 — Payment means . 144
A.2.11 UNTDID 5305 — Duty or tax or fee category . 144
A.2.12 UNTDID 5189 — Allowance codes . 145
A.2.13 UNTDID 7143 — Item type identification code . 146
A.2.14 UNTDID 7161 — Charge codes . 146
A.2.15 Mime type codes — Mime codes . 146
A.2.16 CEF EAS — Electronic address scheme identifier . 147
A.2.17 CEF VATEX — VAT exemption reason code . 147
A.2.18 UN/ECE Recommendation N°20 and UN/ECE Recommendation N°21 — Unit
codes . 147
A.3 International registration authority for ISO/IEC 6523 . 148
A.4 UN/Cefact: new code request / code change request . 156
Annex B (informative) Examples . 159
B.1 Introduction . 159
B.2 Invoice with multiple line items . 159
B.3 Subscription. 200
B.4 Domestic payment . 206
B.5 Maximum content . 213
B.6 Minimum content . 228
B.7 Taxes . 233
B.8 Electricity . 240
B.9 Licenses . 260
Bibliography . 265
European foreword
This document (CEN/TS 16931-3-2:2020) has been prepared by Technical Committee CEN/TC 434
“Electronic invoicing”, the secretariat of which is held by NEN.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes CEN/TS 16931-3-2:2017.
This document has been prepared under a mandate given to CEN by the European Commission and the
European Free Trade Association.
This document is part of a set of documents, consisting of:
— EN 16931-1:2017 Electronic invoicing - Part 1: Semantic data model of the core elements of an
electronic invoice
— CEN/TS 16931-2:2017, Electronic invoicing - Part 2: List of syntaxes that comply with EN 16931-1
— CEN/TS 16931-3-1:2017, Electronic invoicing - Part 3 - 1: Methodology for syntax bindings of the
core elements of an electronic invoice
— CEN/TS 16931-3-2:2020, Electronic invoicing - Part 3 - 2: Syntax binding for ISO/IEC 19845
(UBL 2.1) invoice and credit note
— CEN/TS 16931-3-3:2020, Electronic invoicing - Part 3 - 3: Syntax binding for UN/CEFACT XML Cross
Industry Invoice D16B
— CEN/TS 16931-3-4:2020, Electronic invoicing - Part 3 - 4: Syntax binding for UN/EDIFACT
INVOIC D16B
— CEN/TR 16931-4:2017, Electronic invoicing - Part 4: Guidelines on interoperability of electronic
invoices at the transmission level
— CEN/TR 16931-5:2017, Electronic invoicing - Part 5: Guidelines on the use of sector or country
extensions in conjunction with EN 16931-1, including a methodology to be applied in the real
environment
— CEN/TR 16931-6:2017, Electronic invoicing - Part 6: Result of the test of the European standard with
respect to its practical application for an end user - Testing methodology
According to the CEN/CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United
Kingdom.
Introduction
The European Commission estimates that “The mass adoption of e-invoicing within the EU would lead to
significant economic benefits and it is estimated that moving from paper to e-invoices will generate
savings of around EUR 240 billion over a six-year period” . Based on this recognition “The Commission
wants to see e-invoicing become the predominant method of invoicing by 2020 in Europe.”
As a means to achieve this goal, Directive 2014/55/EU [5] on electronic invoicing in public procurement
aims at facilitating the use of electronic invoices by economic operators when supplying goods, works
and services to the public administration (B2G), as well as the support for trading between economic
operators themselves (B2B). In particular, it sets out the legal framework for the establishment and
adoption of a European standard (EN) for the semantic data model of the core elements of an electronic
invoice (EN 16931-1).
In line with Directive 2014/55/EU [5], and after publication of the reference to EN 16931-1 in the Oficial
Journal of the European Union, all contracting public authorities and contracting entities in the EU will
be obliged to receive and process an e-invoice as long as:
— it is in conformance with the semantic content as described in EN 16931-1;
— it is represented in any of the syntaxes identified in CEN/TS 16931-2, in accordance with the request
referred to in paragraph 1 of article 3 of the Directive 2014/55/EU;
— it is in conformance with the appropriate mapping defined in the applicable subpart of
CEN/TS 16931-3.
The semantic data model of the core elements of an electronic invoice – the core invoice model – as
described in EN 16931-1 is based on the proposition that a limited, but sufficient set of information
elements can be defined that supports generally applicable invoice-related functionalities.
This CEN Technical Specification CEN/TS 16931-3-2 defines the binding of the core elements of the
invoice to ISO/IEC 19845 (UBL 2.1). Other subparts of this CEN Technical Specifications define the
binding method (CEN/TS 16931-3-1) and map the core invoice model to other syntaxes such as
UN/CEFACT XML (CEN/TS 16931-3-3) and ISO 9735 (UN/EDIFACT) (CEN/TS 16931-3-4).
By ensuring interoperability of electronic invoices, the European standard and its ancillary European
standardization deliverables will serve to remove market barriers and obstacles to trade deriving from
the existence of different national rules and standards – and thus contribute to the goals set by the
European Commission.
http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=COM:2010:0712:FIN:en:PDF.
1 Scope
This document specifies the mapping between the semantic model of an electronic invoice, included in
EN 16931-1 and the UBL 2.1 syntax (ISO/IEC 19845). For each element in the semantic model (including
sub-elements or supplementary components such as Identification scheme identifiers) it is defined which
element in the syntax is to be used to contain its information contents. Any mismatches between
semantics, format, cardinality or structure are indicated.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
EN 16931-1, Electronic invoicing - Part 1: Semantic data model of the core elements of an electronic invoice
ISO/IEC 19845, Information technology — Universal business language version 2.1 (UBL v2.1)
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1
electronic invoice
invoice that has been issued, transmitted and received in a structured electronic format which allows for
its automatic and electronic processing
[SOURCE: Directive 2014/55/EU [5]]
3.2
semantic data model
structured set of logically interrelated information elements
3.3
information element
semantic concept that can be defined independent of any particular representation in a syntax
3.4
syntax
machine-readable language or dialect used to represent the information elements contained in an
electronic document (e.g. an electronic invoice)
3.5
business term
label assigned to a given information element which is used as a primary reference
3.6
core invoice model
semantic data model of the Core elements of an electronic invoice
3.7
core elements of an electronic invoice
set of essential information elements that an electronic invoice may contain in order to enable cross-
border interoperability, including the necessary information to ensure legal compliance
3.8
identifier
character string used to establish the identity of, and distinguish uniquely, one instance of an object
within an identification scheme from all other objects within the same scheme
Note 1 to entry: An identifier may be a word, number, letter, symbol, or any combination of those.
3.9
identification scheme
collection of identifiers applicable for a given type of object governed under a common set of rules
4 Syntax binding to UBL 2.1
4.1 Introduction
The Universal Business Language (UBL) is developed by the OASIS open standards consortium. OASIS is
a non-profit, international consortium that drives the development, convergence and adoption of open
standards for the global information society.
UBL is designed to provide a universally understood and recognized syntax for legally binding business
documents and to operate within a standard business framework such as ISO 15000 (ebXML) to provide
a complete, standards-based infrastructure that can extend the benefits of existing EDI systems to
businesses of all sizes. UBL is freely available to everyone without legal encumbrance or licensing fees.
UBL is widely used around the world for procurement (e.g. ordering and electronic invoicing), sourcing
(e.g. tendering and catalogues), replenishment (e.g. managed inventory) and transportation and logistics
(e.g. waybills, forwarding instructions, and intermodal freight management). UBL provides the standards
for the PEPPOL (Pan European eProcurement Online) network and public procurement initiatives in
Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy,
Netherlands, Norway, Spain, Sweden, and UK (NHS).
Version 2.1 of UBL has been approved for release as an ISO and IEC International Standard, and given the
designation ‘ISO/IEC 19845:2015’.
UBL schemas are modular, reusable, and extensible in XML-aware ways. As the first standard
implementation of ebXML Core Components Technical Specification 2.01, the UBL Library is based on a
conceptual model of information components known as Business Information Entities (BIEs). These
components are assembled into specific document models such as invoice and order. These document
models are then transformed in accordance with UBL Naming and Design Rules into W3C XSD schema
syntax. This approach facilitates the creation of UBL-based document types beyond those specified in this
release.
4.2 Data types
As stated, UBL messages are constructed using reusable Business Information Entities. The (data) typing
mechanism in UBL also relies heavily on reuse of generic components, both within UBL, but also on the
Core Component Technical Specification. Typically this has the following structure:
— The message specification (the invoice XSD) imports schema that specifies all the reusable Business
Information Entities (expressed as XML elements);
— The message is constructed by using these BIE’s;
— Each BIE (e.g. DocumentCurrencyCode) is based on a type with a similar name (e.g.
DocumentCurrencyCodeType);
— Each type is based on one of the UBL “Unqualified Data Types” (e.g. CodeType);
— Each Unqualified Data Type is based on one of the Core Component Types (ccts:CodeType).
In the EN, each element is based on one of the seven specified ‘semantic data types’: Amount, Unit price
amount, Quantity, Percentage, Identifier, Code, Date, Text, and Binary object. Some of these datatypes
have attributes. In UBL, the “Unqualified Data Types” also have attributes, comparable with the datatypes
in the EN.
When making a mapping from the EN to UBL, datatypes and their attributes (if applicable) have to be
taken into consideration. For each element in the EN, it should be clear where to map the contents of the
element, but also how to map the attributes. In most cases, an element from the EN with a specific
datatype (e.g. a Code) is mapped to an element in UBL that has a comparable datatype (e.g. CodeType).
There are however some exceptions. The table below shows what datatype mappings occur in the UBL
mapping, and how often they occur
Table 1 — UBL data types
From (EN) To (UBL) #
Amount (A) AmountType (A) 46
Code (C) CodeType (C) 17
Code (C) IdentifierType (I) 4
Code (C) TextType (T) 1
Date (D) DateType (D) 8
Identifier (I) IdentifierType (I) 27
Identifier (I) CodeType (C) 1
Percent (P) PercentType (P) 4
Percent (P) NumericType (Nb) 4
Quantity (Q) QuantityType (Q) 2
Text (T) TextType (T) 32
Text (T) NameType (N) 25
Text (T) IdentifierType (I) 4
Unit Price Amount
AmountType (A) 3
(U)
BinaryObjectType
Binary Object (B) 1
(B)
Document
Reference IdentifierType (I) 10
Identitifier (O)
Attribute (S) Identifier (I) 14
Attribute (S) Code (C) 1
Attribute (S) Text (T) 1
Only two datatypes in the EN have attributes. For these datatypes the mapping is straight-forward: simply
put the value in the XML element in UBL. For the datatypes that do have attributes (italic in the table
above), a mapping is made to the relevant datatype (attributes) in UBL. The attributes marked in bold are
mandatory.
These mappings are presented below.
Table 2 — UBL attributes
EN UBL
Amount AmountType
currencyID
Unit Price Amount AmountType
currencyID
Quantity QuantityType
Percentage PercentageType
Code CodeType
Identifier IdentifierType
Scheme identifier schemeID
Scheme version identifier schemeVersionID
Binary Object BinaryObjectType
Mime Code mimeCode
Filename filename
The amount data type in UBL has a mandatory attribute called currencyID. This attribute is used to define
the currency of the amount. In the EN, the currency of the amount is defined as a single business term,
the BT-5 and defines that only one currency shall be used in the Invoice except for the Total VAT amount
in accounting currency (BT-111) in accordance with Article 230 of Directive 2006/112/EC on VAT. In
consequence, every currencyID attribute in the UBL AmountType elements shall map to the BT-5 Invoice
currency code except for the currencyID in /Invoice/cac:TaxTotal/cbc:TaxAmount that can mapped to
BT-5 or to BT-6 if exists.
The EN 16931-1 semantic data model uses semantic data types that consist of more than one information
entity. For instance with the Identifier data type it is possible to accompany the content with a
corresponding Scheme identifier. The EN 16931-1 does not apply unique identifiers to those additional
entities. In order to clearly identify those components in the following syntax mapping, those additional
entities are numbered by adding a dash and an additional number to the original ID. For example the
Scheme identifier that corresponds to the Buyer identifier (BT-46) gets the unique ID BT-46-1. As
UN/CEFACT XML fully supports the codelists referenced by the Semantic Data Model (SDM) the
corresponding codes to the semantic requirements of the latest published lists can be used without any
additional mapping.
4.3 Mapping the Invoice model
Table 3 — Semantic model to UBL invoice syntax elements mapping (normative)
ID BT Desc. Path Match Rules
BT-1 1 1.1 Invoice A unique I /Invoice/cbc:ID I 1.1
number identification of the
Invoice.
BT-2 1 1.1 Invoice issue The date when the D /Invoice/cbc:IssueDate D 1.1
date Invoice was issued.
BT-3 1 1.1 Invoice type A code specifying the C /Invoice/cbc:InvoiceTypeCode C 0.1 CAR-2
code functional type of the
Invoice.
BT-5 1 1.1 Invoice The currency in which C /Invoice/cbc:DocumentCurrencyCode C 0.1 CAR-2
currency all Invoice amounts
code are given, except for
the Total VAT amount
in accounting
currency.
BT-6 1 0.1 VAT The currency used for C /Invoice/cbc:TaxCurrencyCode C 0.1 SEM-2
accounting VAT accounting and
currency reporting purposes as
code accepted or required
in the country of the
Seller.
BT-7 1 0.1 Value added The date when the D /Invoice/cbc:TaxPointDate D 0.1 SEM-2
tax point date VAT becomes
accountable for the
Seller and for the
Buyer in so far as that
date can be
determined and
differs from the date
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
of issue of the invoice,
according to the VAT
directive.
BT-8 1 0.1 Value added The code of the date C /Invoice/cac:InvoicePeriod/cbc:Description C 0.1 SEM-2
tax point date when the VAT Code
code becomes accountable
for the Seller and for
the Buyer.
BT-9 1 0.1 Payment due The date when the D /Invoice/cbc:DueDate D 0.1
date payment is due.
BT-10 1 0.1 Buyer An identifier assigned T /Invoice/cbc:BuyerReference T 0.1
reference by the Buyer used for
internal routing
purposes.
BT-11 1 0.1 Project The identification of O /Invoice/cac:ProjectReference/cbc:ID I 0.n CAR-3
reference the project the invoice
refers to.
BT-12 1 0.1 Contract The identification of a O /Invoice/cac:ContractDocumentReference/c I 0.n CAR-3
reference contract. bc:ID
BT-13 1 0.1 Purchase An identifier of a O /Invoice/cac:OrderReference/cbc:ID I 0.1
order referenced purchase
reference order, issued by the
Buyer.
BT-14 1 0.1 Sales order An identifier of a O /Invoice/cac:OrderReference/cbc:SalesOrde I 0.1
reference referenced sales rID
order, issued by the
Seller.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-15 1 0.1 Receiving An identifier of a O /Invoice/cac:ReceiptDocumentReference/cb I 0.n CAR-3
advice referenced receiving c:ID
reference advice.
BT-16 1 0.1 Despatch An identifier of a O /Invoice/cac:DespatchDocumentReference/ I 0.n CAR-3
advice referenced despatch cbc:ID
reference advice.
BT-17 1 0.1 Tender or lot The identification of O /Invoice/cac:OriginatorDocumentReference I 0.n CAR-3
reference the call for tender or /cbc:ID
lot the invoice relates
to.
BT-18 1 0.1 Invoiced The identification of I /Invoice/cac:AdditionalDocumentReference I 0.n CAR-3 with
object the call for tender or /cbc:ID cbc:DocumentTy
identifier lot the invoice relates peCode = 130
to.
BT- 2 0.1 Scheme The identification S /Invoice/cac:AdditionalDocumentReference I 0.1 Code list
18–1 identifier scheme identifier of /cbc:ID/@schemeID UNTDID 1153
the Invoiced object
identifier.
BT-19 1 0.1 Buyer A textual value that T /Invoice/cbc:AccountingCost T 0.1
accounting specifies where to
reference book the relevant data
into the Buyer's
financial accounts.
BT-20 1 0.1 Payment A textual description T /Invoice/cac:PaymentTerms/cbc:Note T 0.n CAR-3
terms of the payment terms
that apply to the
amount due for
payment (Including
description of
possible penalties).
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BG-1 1 0.n INVOICE A group of business
NOTE terms providing
textual notes that are
relevant for the
invoice, together with
an indication of the
note subject.
BT-21 2 0.1 Invoice note The subject of the C /Invoice/cbc:Note T 0.n SYN-2, Use #subject
subject code following textual note. SEM-2 code#
Code list
UNTDID 4451
BT-22 2 1.1 Invoice note A textual note that T /Invoice/cbc:Note T 0.n
gives unstructured
information that is
relevant to the Invoice
as a whole.
BG-2 1 1.1 PROCESS A group of business
CONTROL terms providing
information on the
business process and
rules applicable to the
BT-23 0.1 Business Identifies the T /Invoice/cbc:ProfileID I 0.1
process type business process
context in which the
transaction appears,
to enable the Buyer to
process the Invoice in
an appropriate way.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-24 2 1.1 Specification An identification of I /Invoice/cbc:CustomizationID I 0.1 CAR-2
identifier the specification
containing the total
set of rules regarding
semantic content,
cardinalities and
business rules to
which the data
contained in the
instance document
conforms.
BG-3 1 0.n PRECEDING A group of business /Invoice/cac:BillingReference/cac:InvoiceD 0.n CAR-3
INVOICE terms providing ocumentReference
REFERENCE information on one or
more preceding
Invoices.
BT-25 2 1.1 Preceding The identification of O /Invoice/cac:BillingReference/cac:InvoiceD I 1.1
Invoice an Invoice that was ocumentReference/cbc:ID
number previously sent by the
Seller.
BT-26 2 0.1 Preceding The date when the D /Invoice/cac:BillingReference/cac:InvoiceD D 0.1
Invoice issue Preceding Invoice was ocumentReference/cbc:IssueDate
date issued.
BG-5 1 1.1 SELLER A group of business /Invoice/cac:AccountingSupplierParty 1.1
terms providing
information about the
Seller.
BT-27 2 1.1 Seller name The full formal name T /Invoice/cac:AccountingSupplierParty/cac: N 0.n CAR-2,
by which the Seller is Party/cac:PartyLegalEntity/cbc:Registration CAR-3
registered in the Name
national registry of
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
legal entities or as a
Taxable person or
otherwise trades as a
person or persons.
BT-28 2 0.1 Seller trading A name by which the T /Invoice/cac:AccountingSupplierParty/cac: N 0.n CAR-3
name Seller is known, other Party/cac:PartyName/cbc:Name
than Seller name (also
known as Business
name).
BT-29 2 0.n Seller An identification of I /Invoice/cac:AccountingSupplierParty/cac: I 0.n CAR-3
identifier the Seller. Party/cac:PartyIdentification/cbc:ID
BT- 3 0.1 Seller The identification S /Invoice/cac:AccountingSupplierParty/cac: I 0.1
29–1 identifier scheme identifier of Party/cac:PartyIdentification/cbc:ID/@sche
identification the Seller identifier. meID
scheme
identifier
BT-30 2 0.1 Seller legal An identifier issued by I /Invoice/cac:AccountingSupplierParty/cac: I 0.n CAR-3
registration an official registrar Party/cac:PartyLegalEntity/cbc:CompanyID
identifier that identifies the
Seller as a legal entity
or person.
BT- 3 0.1 Seller legal The identification S /Invoice/cac:AccountingSupplierParty/cac: I 0.1
30–1 registration scheme identifier of Party/cac:PartyLegalEntity/cbc:CompanyID
identifier the Seller legal /@schemeID
identification registration identifier.
scheme
identifier
BT-31 2 0.1 Seller VAT The Seller's VAT I /Invoice/cac:AccountingSupplierParty/cac: I 0.n CAR-3 with
identifier identifier (also known Party/cac:PartyTaxScheme/cbc:CompanyID cac:TaxScheme/c
as Seller VAT bc:ID = “VAT”
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
identification
number).
BT-32 2 0.1 Seller tax The local I /Invoice/cac:AccountingSupplierParty/cac: I 0.n CAR-3 with
registration identification Party/cac:PartyTaxScheme/cbc:CompanyID cac:TaxScheme/c
identifier (defined by the bc:ID ! = “VAT”
Seller’s address) of
the Seller for tax
purposes or a
reference that enables
the Seller to state his
registered tax status.
BT-33 2 0.1 Seller Additional legal T /Invoice/cac:AccountingSupplierParty/cac: T 0.n CAR-3
additional information relevant Party/cac:PartyLegalEntity/cbc:CompanyLe
legal for the Seller. galForm
information
BT-34 2 0.1 Seller Identifies the Seller's I /Invoice/cac:AccountingSupplierParty/cac: I 0.1
electronic electronic address to Party/cbc:End pointID
address which a business
document may be
delivered.
BT- 3 1.1 Seller The identification S /Invoice/cac:AccountingSupplierParty/cac: I 0.1 CAR-2
34–1 electronic scheme identifier of Party/cbc:End pointID/@schemeID
address the Seller electronic
identification address
scheme
identifier
BG-5 2 1.1 SELLER A group of business /Invoice/cac:AccountingSupplierParty/cac: 0.1 CAR-2
POSTAL terms providing Party/cac:PostalAddress
ADDRESS information about the
address of the Seller.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-35 3 0.1 Seller The main address line T /Invoice/cac:AccountingSupplierParty/cac: N 0.1 STR-5
address line in an address. Party/cac:PostalAddress/cbc:StreetName
BT-36 3 0.1 Seller An additional address T /Invoice/cac:AccountingSupplierParty/cac: N 0.1 STR-5
address line line in an address that Party/cac:PostalAddress/cbc:AdditionalStre
2 can be used to give etName
further details
supplementing the
main line.
BT- 0.1 Seller An additional address T /Invoice/cac:AccountingSupplierParty/cac: T 0.n CAR-3
162 address line line in an address that Party/cac:PostalAddress/cac:AddressLine/c
3 can be used to give bc:Line
further details
supplementing the
main line.
BT-37 3 0.1 Seller city The common name of T /Invoice/cac:AccountingSupplierParty/cac: N 0.1
the city, town or Party/cac:PostalAddress/cbc:CityName
village, where the
Seller address is
located.
BT-38 3 0.1 Seller post The identifier for an T /Invoice/cac:AccountingSupplierParty/cac: T 0.1
code addressable group of Party/cac:PostalAddress/cbc:PostalZone
properties according
to the relevant postal
service.
BT-39 3 0.1 Seller The subdivision of a T /Invoice/cac:AccountingSupplierParty/cac: T 0.1
country country. Party/cac:PostalAddress/cbc:CountrySuben
subdivision tity
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-40 3 1.1 Seller A code that identifies C /Invoice/cac:AccountingSupplierParty/cac: C 0.1 CAR-2
country code the country. Party/cac:PostalAddress/cac:Country/cbc:I
dentificationCode
BG-6 2 0.1 SELLER A group of business /Invoice/cac:AccountingSupplierParty/cac: 0.1
CONTACT terms providing Party/cac:Contact
contact information
about the Seller.s
BT-41 3 0.1 Seller contact A contact point for a T /Invoice/cac:AccountingSupplierParty/cac: N 0.1
point legal entity or person. Party/cac:Contact/cbc:Name
BT-42 3 0.1 Seller contact A phone number for T /Invoice/cac:AccountingSupplierParty/cac: T 0.1
telephone the contact point. Party/cac:Contact/cbc:Telephone
number
BT-43 3 0.1 Seller contact An e-mail address for T /Invoice/cac:AccountingSupplierParty/cac: T 0.1
email the contact point. Party/cac:Contact/cbc:ElectronicMail
address
BG-7 1 1.1 BUYER A group of business /Invoice/cac:AccountingCustomerParty 1.1
terms providing
information about the
Buyer.
BT-44 2 1.1 Buyer name The full name of the T /Invoice/cac:AccountingCustomerParty/cac N 0.n CAR-2,
Buyer. :Party/cac:PartyLegalEntity/cbc:Registratio CAR-3
nName
BT-45 2 0.1 Buyer A name by which the T /Invoice/cac:AccountingCustomerParty/cac N 0.n CAR-3
trading name Buyer is known, other :Party/cac:PartyName/cbc:Name
than Buyer name
(also known as
Business name).
BT-46 2 0.n Buyer An identifier of the I /Invoice/cac:AccountingCustomerParty/cac I 0.n CAR-3
identifier Buyer. :Party/cac:PartyIdentification/cbc:ID
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT- 3 0.1 Buyer The identification S /Invoice/cac:AccountingCustomerParty/cac I 0.1
46–1 identifier scheme identifier of :Party/cac:PartyIdentification/cbc:ID/@sch
identification the Buyer identifier. emeID
scheme
identifier
BT-47 2 0.1 Buyer legal An identifier issued by I /Invoice/cac:AccountingCustomerParty/cac I 0.n CAR-3
registration an official registrar :Party/cac:PartyLegalEntity/cbc:CompanyID
identifier that identifies the
Buyer as a legal entity
or person.
BT- 3 0.1 Buyer legal The identification S /Invoice/cac:AccountingCustomerParty/cac I 0.1
47–1 registration scheme identifier of :Party/cac:PartyLegalEntity/cbc:CompanyID
identifier the Buyer legal /@schemeID
identification registration identifier.
scheme
identifier
BT-48 2 0.1 Buyer VAT The Buyer's VAT I /Invoice/cac:AccountingCustomerParty/cac I 0.n CAR-3,
identifier identifier (also known :Party/cac:PartyTaxScheme/cbc:CompanyID SEM-2
as Buyer VAT
identification
number).
BT-49 2 0.1 Buyer Identifies the Buyer's I /Invoice/cac:AccountingCustomerParty/cac I 0.1
electronic electronic address to :Party/cbc:End pointID
address which a business
document should be
delivered.
BT- 3 1.1 Buyer The identification S /Invoice/cac:AccountingCustomerParty/cac I 0.1 CAR-2
49–1 electronic scheme identifier of :Party/cbc:End pointID/@schemeID
address the Buyer electronic
identification address.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
scheme
identifier
BG-8 2 1.1 BUYER A group of business /Invoice/cac:AccountingCustomerParty/cac 0.1 CAR-2
POSTAL terms providing :Party/cac:PostalAddress
ADDRESS information about the
postal address for the
Buyer.
BT-50 3 0.1 Buyer The main address line T /Invoice/cac:AccountingCustomerParty/cac N 0.1 STR-5
address line in an address. :Party/cac:PostalAddress/cbc:StreetName
BT-51 3 0.1 Buyer An additional address T /Invoice/cac:AccountingCustomerParty/cac N 0.1 STR-5
address line line in an address that :Party/cac:PostalAddress/cbc:AdditionalStr
2 can be used to give eetName
further details
supplementing the
main line.
BT- 0.1 Buyer An additional address T /Invoice/cac:AccountingCustomerParty/cac T 0.n CAR-3
163 address line line in an address that :Party/cac:PostalAddress/cac:AddressLine/
3 can be used to give cbc:Line
further details
supplementing the
main line.
BT-52 3 0.1 Buyer city The common name of T /Invoice/cac:AccountingCustomerParty/cac N 0.1
the city, town or :Party/cac:PostalAddress/cbc:CityName
village, where the
Buyer's address is
located.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-53 3 0.1 Buyer post The identifier for an T /Invoice/cac:AccountingCustomerParty/cac T 0.1
code addressable group of :Party/cac:PostalAddress/cbc:PostalZone
properties according
to the relevant postal
service.
BT-54 3 0.1 Buyer The subdivision of a T /Invoice/cac:AccountingCustomerParty/cac T 0.1
country country. :Party/cac:PostalAddress/cbc:CountrySuben
subdivision tity
BT-55 3 1.1 Buyer A code that identifies C /Invoice/cac:AccountingCustomerParty/cac C 0.1 CAR-2
country code the country. :Party/cac:PostalAddress/cac:Country/cbc:I
dentificationCode
BG-9 2 0.1 BUYER A group of business /Invoice/cac:AccountingCustomerParty/cac 0.1
CONTACT terms providing :Party/cac:Contact
contact information
relevant for the Buyer.
BT-56 3 0.1 Buyer A contact point for a T /Invoice/cac:AccountingCustomerParty/cac N 0.1
contact point legal entity or person. :Party/cac:Contact/cbc:Name
BT-57 3 0.1 Buyer A phone number for T /Invoice/cac:AccountingCustomerParty/cac T 0.1
contact the contact point. :Party/cac:Contact/cbc:Telephone
telephone
number
BT-58 3 0.1 Buyer An e-mail address for T /Invoice/cac:AccountingCustomerParty/cac T 0.1
contact email the contact point. :Party/cac:Contact/cbc:ElectronicMail
address
BG-10 1 0.1 PAYEE A group of business /Invoice/cac:PayeeParty 0.1
terms providing
information about the
Payee, i.e. the role that
receives the payment.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-59 2 1.1 Payee name The name of the T /Invoice/cac:PayeeParty/cac:PartyName/cb N 0.n CAR-2,
Payee. c:Name CAR-3
BT-60 2 0.1 Payee An identifier for the I /Invoice/cac:PayeeParty/cac:PartyIdentifica I 0.n CAR-3
identifier Payee. tion/cbc:ID
BT- 3 0.1 Payee The identification S /Invoice/cac:PayeeParty/cac:PartyIdentifica I 0.1
60–1 identifier scheme identifier of tion/cbc:ID/@schemeID
identification the Payee identifier.
scheme
identifier
BT-61 2 0.1 Payee legal An identifier issued by I /Invoice/cac:PayeeParty/cac:PartyLegalEnti I 0.n CAR-3
registration an official registrar ty/cbc:CompanyID
identifier that identifies the
Payee as a legal entity
or person.
BT- 3 0.1 Payee legal The identification S /Invoice/cac:PayeeParty/cac:PartyLegalEnti I 0.1
61–1 registration scheme identifier of ty/cbc:CompanyID/@schemeID
identifier the Payee legal
identification registration identifier.
scheme
identifier
BG-11 1 0.1 SELLER TAX A group of business /Invoice/cac:TaxRepresentativeParty 0.1
REPRESENTterms providing
ATIVE information about the
PARTY Seller's tax
representative.
BT-62 2 1.1 Seller tax The full name of the T /Invoice/cac:TaxRepresentativeParty/cac:P N 0.n CAR-2,
representativSeller's tax artyName/cbc:Name CAR-3
e name representative party.
Level
Card.
DT
Type
Card.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...