CEN/TS 16931-3-3:2017

SLOVENSKI STANDARD
01-februar-2018
Elektronsko izdajanje računov - 3-3. del: Sintaksa povezav za medsektorske
račune D16B v skladu z UN/CEFACT XML
Electronic invoicing - Part 3-3: Syntax binding for UN/CEFACT XML Industry Invoice
D16B
Elektronische Rechnungsstellung - Teil 3-3: Umsetzung in die Syntax UN/CEFACT XML
Cross Industry Invoice D16B
Facturation électronique - Partie 3-3 : Correspondance syntaxique pour les factures
intersectorielles - Schéma XML D16B UN/CEFACT
Ta slovenski standard je istoveten z: CEN/TS 16931-3-3:2017
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-3
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
October 2017
TECHNISCHE SPEZIFIKATION
ICS 35.240.20; 35.240.63
English Version
Electronic invoicing - Part 3-3: Syntax binding for
UN/CEFACT XML Industry Invoice D16B
Facturation électronique - Partie 3-3 : Correspondance Elektronische Rechnungsstellung - Teil 3-3: Umsetzung
syntaxique pour les factures intersectorielles - Schéma in die Syntax UN/CEFACT XML Cross Industry Invoice
XML D16B UN/CEFACT D16B
This Technical Specification (CEN/TS) was approved by CEN on 30 July 2017 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, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, 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: Avenue Marnix 17, B-1000 Brussels
© 2017 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 16931-3-3:2017 E
worldwide for CEN national Members.

Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 5
4 Syntax binding to the UN/CEFACT Cross Industry Invoice . 6
4.1 Introduction . 6
4.2 Data types . 7
4.3 Codes and identifiers . 8
4.4 Mapping the Invoice model . 8
4.5 Validation artefacts . 74
5 Mismatches . 74
5.1 Semantic level . 74
5.2 Structural level . 74
5.3 Cardinality level . 74
(informative) Examples . 75
A.1 Introduction . 75
A.2 Invoice with multiple line items . 75
A.3 IT equipment . 95
A.4 Subscription . 110
A.5 Domestic payment . 114
A.6 Maximum content . 121
A.7 Minimum content . 135
A.8 Taxes . 139
A.9 Electricity . 145
A.10 Licenses. 160
Bibliography . 166

European foreword
This document (CEN/TS 16931-3-3:2017) 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 has been prepared under a mandate given to CEN by the European Commission and the
European Free Trade Association, and supports essential requirements of EU Directive 2014/55/EU.
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:2017, Electronic invoicing - Part 3 - 2: Syntax binding for ISO/IEC 19845 (UBL
2.1) invoice and credit note
 CEN/TS 16931-3-3:2017, Electronic invoicing - Part 3 - 3: Syntax binding for UN/CEFACT XML Cross
Industry Invoice D16B
 CEN/TS 16931-3-4:2017, 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, methodology to be applied in the real environment
 CEN/TR 16931-6:2017, Electronic invoicing - Part 6: Result of the test of EN 16931-1 with respect to
its practical application for an end user
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, Former Yugoslav Republic of Macedonia,
France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta,
Netherlands, Norway, Poland, Portugal, 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 [3] 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 [3], 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-3 defines the binding of the core elements of the
invoice to the Cross Industry Invoice of UN/CEFACT XML. 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 ISO/IEC 19845 (UBL 2.1) (CEN/TS 16931-3-2) and ISO/IEC 9735 (UN/EDIFACT)
(CEN/TS 16931-3-4).
By ensuring interoperability of electronic invoices, the European standard and its ancillary European
standardisation 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 CEN Technical Specification (TS) specifies the mapping between the semantic model of an
electronic invoice, included in EN 16931-1 and the Cross Industry Invoice in the UN/CEFACT XML
syntax. 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, in whole or in part, are normatively referenced in this document and are
indispensable for its application. 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 - Semantic data model of the core elements of an electronic invoice
ISO 4217, Codes for the representation of currencies
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
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 [i.1]]
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 the UN/CEFACT XML Cross Industry Invoice D16B
4.1 Introduction
One part of the basis for the European Core Data Model are the CEN MUG CWAs which are a subset of
Cross Industry Invoice (CII). UN XML standards are developed within UN/CEFACT. This guarantees an
international focus, openness in the process and free usage, as this is the mission of UN/CEFACT and the
policy of UNECE as a global standardisation body . For all published specifications and standards the
Inetelctual Property Rights (IPRs) are owned by the UN and as such are open for free use by everyone.
UN/CEFACT XML and all underlying standards (i.e. Core Component Methodology, Library, Message
Assembly, XML Naming & Design Rules) are maintained on a regular basis by UN/CEFACT, within the
United Nations framework of the Economic and Social Council, the United Nations Economic
Commission for Europe (UNECE). The maintenance process is documented, applied and governed. All
relevant procedural documents are available. Open participation for all interested stakeholders is
ensured through the national delegations, which are usually connected to the national standards bodies.
Also recognised organisations are able to participate in the development and maintenance process.
UN/CEFACT standards are actively used worldwide in various sectors like Agriculture, Transport &
Logistics, B2G EProcurement and cross-sector applicationsin different regions (APAC, US, Europe,
LatAm).
Apart from Invoice (CII) implementations, UN/CEFACT standards are implemented within the US
Department of Defense. Within the global GS1 Community UN/CEFACT XML is used (apart from
EANCOM & GS1 XML) in several countries worldwide. In other industries and domains CII and
UN/CEFACT syntax has been adopted as well, e.g. Japan, Taiwan (Single Window for reference WCO
DATA MODEL and UN/CEFACT XML & UNTDED) or Korea (cross industry tax e-invoice is obligation of
law).
CII, as part of cross-sector supply chain processes is implemented in various European countries, e.g.
 French Public eInvocing Platform (CHORUS)
 German B2B and B2C core invoice standard (ZUGFeRD)

See www.cen.eu, www.unece.org/cefact.html
UN/CEFACT provides the relevant standards and guidelines on their website.
Support to the implementers and users is provided through other standardisation bodies (e.g. CEN,
GS1), user communities, experts who are members of a national delegation at UN/CEFACT, etc. which
building their recommendations/guidelines upon published UN/CEFACT standards.
UN/CEFACT offers the CCBDA CCL message assembly methodology as guideline on how to modify the
underlying data model to enable subsetting. Applying the respective naming and design rules the syntax
becomes restricted or extended.
CCBDA supports message assembly and message contextual customisation based on the Reference ABIE
Library of the CCL. It is important to explain that extension is supported within the bounds of those
reference ABIEs and, of course, submissions to extend any ABIE can be submitted to Library
Maintenance for future inclusion. The aim is a controlled mechanism on extensions in order to facilitate
interoperability.
Using this standardised approach the EN requirement to take into account the UN/CEFACT XML Cross
3 4
Industry Invoice v. 2.0 and v.3.0 is reached .
In order to take the most current version of the Cross Industry Invoice into account to be prepared best
possible to support an easy, sustainable and effective implementation of the EN using the Cross
Industry Invoice the Syntax mapping is done to Cross Industry Invoice version 100 (release D16B
SCRDM). This version contains two sets of schemas. One with coupled code list modules that allow a
one-step validation for the UN/CEFACT Standard; the second with decoupled code list modules. It is
advised to implement the interface using the second set of schemas (decoupled) to get a fully
backwards compatible and stable implementation that enables a system to take future code list updates
into account.
4.2 Data types
Data Types and relevant Codelists for the Cross Industry Invoice can be found in the Requirement
Specification Mapping (RSM) document at the UNECE website . The following additional rules are
applied:
 For the udt:DateTimeType only the DateTimeString choice shall be used. For the corresponding
attribute @format the codelist UN/CEFACT 2379 is applied.
 The the mapping of the SDM only code “102” (YYYYMMDD) shall be used. In a scenario with applied
extensions the two additional formats 610 (YYYYMM) and 616 (YYYYWW) can be used as well.

See C(2014) 7912 final, ANNEX 1, p.5
See CCTS 2.01 & CCBDA 1.0 & NDR 2.1 Artefacts at http://www.unece.org/tradewelcome/un-centre-for-trade-
facilitation-and-e-business-uncefact/outputs/technical-specifications/
https://www.unece.org/cefact/rsm/rsm_index.html
4.3 Codes and identifiers
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 listscan be used without any
additional mapping. For the following codes lists special rules are applied:
 ISO 4217 (Currencies): The alpha-3-representation shall be used. The currency shall only be given
on document level in /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/
ram:ApplicableSupplyChainHeaderTradeSettlement/ram:InvoiceCurrencyCode. Only if a different
TaxCurrencyCode is to be used the currency code shall be given at the appropriate element.
 BT-8 (Value added tax point date code). While the model defines a restriction of UNTDID 2005, CII
supports in the mapped to element a restriction of UNTDID 2475 as follows:
Table 1 — Codes
Semantic model Code in UNTDID 2005 Code for CII in UNTDID 2475
Invoice document issue date 3 5
Delivery date, actual 35 29
Paid to date 432 72
4.4 Mapping the Invoice model
In the following table the semantic data model of the EN 16931-1 is mapped to the corresponding
XPaths of the Cross Industry Invoice 100 (D16B) message structure. The cardinality column for the
syntax represents the cardinality as it is defined by UN/CEFACT to illustrate differences between the
semantic data model and the respective syntax. The cardinality of the data model is taken into account
by the corresponding validation artefacts.

Table 2 — Semantic model to UN/CEFACT syntax elements mapping (normative)
ID BT Desc. Path Match Rules
BT-1 1 1.1 Invoice A unique identification of I /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:ID E 1.1
number the Invoice.
BT-2 1 1.1 Invoice issue The date when the D /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IssueDateTi E 1.1  @format="10
date Invoice was issued. me/udt:DateTimeString 2"
/rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IssueDateTi A  Only value
me/udt:DateTimeString/@format "102"
BT-3 1 1.1 Invoice type A code specifying the C /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:TypeCode E 0.1 CAR-2
code functional type of the
Invoice.
BT-5 1 1.1 Invoice The currency in which all C /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 CAR-2
currency code Invoice amounts are pplicableHeaderTradeSettlement/ram:InvoiceCurrencyCode
given, except for the
Total VAT amount in
accounting currency.
BT-6 1 0.1 VAT The currency used for C /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 CAR-2
accounting VAT accounting and pplicableHeaderTradeSettlement/ram:TaxCurrencyCode
currency code reporting purposes as
accepted or required in
the country of the Seller.
BT-7 1 0.1 Value added The date when the VAT D /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 1.1 STR-2 @format="10
tax point date becomes accountable for pplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:TaxPo 2"
the Seller and for the intDate/udt:DateString
Buyer in so far as that
date can be determined
and differs
from the date of issue of
the invoice, according to
the VAT directive.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A A  Only value
pplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:TaxPo "102"
intDate/udt:DateString/@format
BT-8 1 0.1 Value added The code of the date C /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 STR-2
tax point date when the VAT becomes pplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:DueDa
code accountable for the Seller teTypeCode
and for the Buyer.
BT-9 1 0.1 Payment due The date when the D /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 1.1  @format="10
date payment is due. pplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/r 2"
am:DueDateDateTime/udt:DateTimeString
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A A  Only value
pplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/r "102"
am:DueDateDateTime/udt:DateTimeString/@format
BT-10 1 0.1 Buyer An identifier assigned by T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
reference the Buyer used for pplicableHeaderTradeAgreement/ram:BuyerReference
internal routing
purposes.
BT-11 1 0.1 Project The identification of the O /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 1.1  Use "Project
reference project the invoice refers pplicableHeaderTradeAgreement/ram:SpecifiedProcuringProject/ram: reference" as
to. ID default value
for Name.
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 1.1  Use "Project
pplicableHeaderTradeAgreement/ram:SpecifiedProcuringProject/ram: reference" as
Name default value
for Name.
BT-12 1 0.1 Contract The identification of a O /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
reference contract. pplicableHeaderTradeAgreement/ram:ContractReferencedDocument/r
am:IssuerAssignedID
BT-13 1 0.1 Purchase An identifier of a O /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
order referenced purchase pplicableHeaderTradeAgreement/ram:BuyerOrderReferencedDocume
reference order, issued by the nt/ram:IssuerAssignedID
Buyer.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-14 1 0.1 Sales order An identifier of a O /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
reference referenced sales order, pplicableHeaderTradeAgreement/ram:SellerOrderReferencedDocumen
issued by the Seller. t/ram:IssuerAssignedID
BT-15 1 0.1 Receiving An identifier of a O /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
advice referenced receiving pplicableHeaderTradeDelivery/ram:ReceivingAdviceReferencedDocum
reference advice. ent/ram:IssuerAssignedID
BT-16 1 0.1 Despatch An identifier of a O /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
advice referenced despatch pplicableHeaderTradeDelivery/ram:DespatchAdviceReferencedDocum
reference advice. ent/ram:IssuerAssignedID
BT-17 1 0.1 Tender or lot The identification of the O /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1  Use for
reference call for tender or lot the pplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument "Tender or lot
invoice relates to. /ram:IssuerAssignedID reference"
with
TypeCode
"50"
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1  Use for
pplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument "Tender or lot
/ram:TypeCode reference"
with
TypeCode
"50"
BT-18 1 0.1 Invoiced The identification of the I /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 CAR-2 Use for
object call for tender or lot the pplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument "Invoiced
identifier invoice relates to. /ram:IssuerAssignedID object
identifier"
with
TypeCode
"130" and
ReferenceTyp
eCode
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 CAR-2 Use for
pplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument "Invoiced
/ram:TypeCode object
identifier"
with
TypeCode
"130" and
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
ReferenceTyp
eCode
BT-18-1 2 0.1 Scheme The identification S /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
identifier scheme identifier of the pplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument
Invoiced object /ram:ReferenceTypeCode
identifier.
BT-19 1 0.1 Buyer A textual value that T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 1.1 CAR-2
accounting specifies where to book pplicableHeaderTradeSettlement/ram:ReceivableSpecifiedTradeAccou
reference the relevant data into the ntingAccount/ram:ID
Buyer's financial
accounts.
BT-20 1 0.1 Payment A textual description of T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.n CAR-3
terms the payment terms that pplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/r
apply to the amount due am:Description
for payment (Including
description of possible
penalties).
BG-1 1 0.n INVOICE NOTE A group of business /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IncludedNo E 0.n
terms providing textual te
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 /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IncludedNo E 0.1
subject code following textual note. te/ram:SubjectCode
BT-22 2 1.1 Invoice note A textual note that gives T /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IncludedNo E 0.n CAR-3
unstructured te/ram:Content
information that is
relevant to the Invoice as
a whole.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BG-2 1 1.1 PROCESS A group of business /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext E 1.1
CONTROL terms providing
information on the
business process and
rules applicable to the
BT-23 2 0.1 Business Identifies the business T /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext/ram: E 0.1
process type process context in which BusinessProcessSpecifiedDocumentContextParameter/ram:ID
the transaction appears,
to enable the Buyer to
process the Invoice in an
appropriate way.
BT-24 2 1.1 Specification An identification of the I /rsm:CrossIndustryInvoice/rsm:ExchangedDocumentContext/ram:Gui E 0.1 CAR-2,
identifier specification containing delineSpecifiedDocumentContextParameter/ram:ID CAR-3
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 /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
INVOICE terms providing pplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument
REFERENCE information on one or
more preceding Invoices.
BT-25 2 1.1 Preceding The identification of an O /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 CAR-2
Invoice Invoice that was pplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument/ra
number previously sent by the m:IssuerAssignedID
Seller.
BT-26 2 0.1 Preceding The date when the D /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 1.1
Invoice issue Preceding Invoice was pplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument/ra
date issued. m:FormattedIssueDateTime/qdt:DateTimeString
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A A  Fixed value
pplicableHeaderTradeSettlement/ram:InvoiceReferencedDocument/ra "102"
m:FormattedIssueDateTime/qdt:DateTimeString/@format
BG-5 1 1.1 SELLER A group of business /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
terms providing pplicableHeaderTradeAgreement/ram:SellerTradeParty
information about the
Seller.
BT-27 2 1.1 Seller name The full formal name by T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 CAR-2
which the Seller is pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:Name
registered in the national
registry of 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 /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
name Seller is known, other pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:Specified
than Seller name (also LegalOrganization/ram:TradingBusinessName
known as Business
name).
BT-29 2 0.n Seller An identification of the I /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.n SYN-1, GloablID, if
identifier Seller. pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:ID CAR-3 global
identifier
exists and can
be stated in
@schemeID,
ID else
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.n SYN-1, GloablID, if
pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:GlobalID CAR-3 global
identifier
exists and can
be stated in
@schemeID,
ID else
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-29-1 3 0.1 Seller The identification S /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A A
identifier scheme identifier of the pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:GlobalID
identification Seller identifier. /@schemeID
scheme
identifier
BT-30 2 0.1 Seller legal An identifier issued by an I /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
registration official registrar that pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:Specified
identifier identifies the Seller as a LegalOrganization/ram:ID
legal entity or person.
BT-30-1 3 0.1 Seller legal The identification S /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A A
registration scheme identifier of the pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:Specified
identifier Seller legal registration LegalOrganization/ram:ID/@schemeID
identification identifier.
scheme
identifier
BT-31 2 0.1 Seller VAT The Seller's VAT I /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1  @schemeID="
identifier identifier (also known as pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:Specified VA"
Seller VAT identification TaxRegistration/ram:ID
number).
BT-32 2 0.1 Seller tax The local identification I /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1  @schemeID="
registration (defined by the Seller’s pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:Specified FC"
identifier address) of the Seller for TaxRegistration/ram:ID
tax purposes or a
reference that enables
the Seller to
state his registered tax
status.
BT-33 2 0.1 Seller Additional legal T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.n CAR-3
additional information relevant for pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:Descripti
legal the Seller. on
information
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-34 2 0.1 Seller Identifies the Seller's I /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 CAR-3
electronic electronic address to pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUnive
address which a business rsalCommunication/ram:URIID
document may be
delivered.
BT-34-1 3 1.1 Seller The identification S /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A A
electronic scheme identifier of the pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:URIUnive
address Seller electronic address rsalCommunication/ram:URIID/@schemeID
identification
scheme
identifier
BG-5 2 1.1 SELLER A group of business /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
POSTAL terms providing pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTra
ADDRESS information about the deAddress
address of the Seller.
BT-35 3 0.1 Seller address The main address line in T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
line 1 an address. pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTra
deAddress/ram:LineOne
BT-36 3 0.1 Seller address An additional address T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
line 2 line in an address that pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTra
can be used to give deAddress/ram:LineTwo
further details
supplementing the main
line.
BT-162 0.1 Seller address An additional address T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
line 3 line in an address that pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTra
can be used to give deAddress/ram:LineThree
further details
supplementing the main
line.
BT-37 3 0.1 Seller city The common name of the T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
city, town or village, pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTra
where the Seller address deAddress/ram:CityName
is located.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-38 3 0.1 Seller post The identifier for an T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
code addressable group of pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTra
properties according to deAddress/ram:PostcodeCode
the relevant postal
service.
BT-39 3 0.1 Seller country The subdivision of a T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.n CAR-3
subdivision country. pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTra
deAddress/ram:CountrySubDivisionName
BT-40 3 1.1 Seller country A code that identifies the C /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
code country. pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:PostalTra
deAddress/ram:CountryID
BG-6 2 0.1 SELLER A group of business /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.n CAR-3
CONTACT terms providing contact pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:DefinedT
information about the radeContact
Seller.s
BT-41 3 0.1 Seller contact A contact point for a legal T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 STR-5
point entity or person. pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:DefinedT
radeContact/ram:PersonName
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 STR-5
pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:DefinedT
radeContact/ram:DepartmentName
BT-42 3 0.1 Seller contact A phone number for the T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
telephone contact point. pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:DefinedT
number radeContact/ram:TelephoneUniversalCommunication/ram:CompleteN
umber
BT-43 3 0.1 Seller contact An e-mail address for the T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
email address contact point. pplicableHeaderTradeAgreement/ram:SellerTradeParty/ram:DefinedT
radeContact/ram:EmailURIUniversalCommunication/ram:URIID
BG-7 1 1.1 BUYER A group of business /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
terms providing pplicableHeaderTradeAgreement/ram:BuyerTradeParty
information about the
Buyer.
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-44 2 1.1 Buyer name The full name of the T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 CAR-2
Buyer. pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:Name
BT-45 2 0.1 Buyer trading A name by which the T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
name Buyer is known, other pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:Specified
than Buyer name (also LegalOrganization/ram:TradingBusinessName
known as Business
name).
BT-46 2 0.n Buyer An identifier of the I /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 SYN-1, GloablID, if
identifier Buyer. pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:ID CAR-3 global
identifier
exists and can
be stated in
@schemeID,
ID else
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 SYN-1, GloablID, if
pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:GlobalID CAR-3 global
identifier
exists and can
be stated in
@schemeID,
ID else
BT-46-1 3 0.1 Buyer The identification S /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A A
identifier scheme identifier of the pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:GlobalID
identification Buyer identifier. /@schemeID
scheme
identifier
BT-47 2 0.1 Buyer legal An identifier issued by an I /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
registration official registrar that pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:Specified
identifier identifies the Buyer as a LegalOrganization/ram:ID
legal entity or person.
BT-47-1 3 0.1 Buyer legal The identification S /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A A
registration scheme identifier of the pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:Specified
identifier Buyer legal registration LegalOrganization/ram:ID/@schemeID
identification identifier.
scheme
identifier
Level
Card.
DT
Type
Card.
ID BT Desc. Path Match Rules
BT-48 2 0.1 Buyer VAT The Buyer's VAT I /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1  @schemeID="
identifier identifier (also known as pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:Specified VA"
Buyer VAT identification TaxRegistration/ram:ID
number).
BT-49 2 0.1 Buyer Identifies the Buyer's I /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1 CAR-3
electronic electronic address to pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:URIUniv
address which a business ersalCommunication/ram:URIID
document should be
delivered.
BT-49-1 3 1.1 Buyer The identification S /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A A
electronic scheme identifier of the pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:URIUniv
address Buyer electronic address. ersalCommunication/ram:URIID/@schemeID
identification
scheme
identifier
BG-8 2 1.1 BUYER A group of business /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
POSTAL terms providing pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:PostalTr
ADDRESS information about the adeAddress
postal address for the
Buyer.
BT-50 3 0.1 Buyer address The main address line in T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
line 1 an address. pplicableHeaderTradeAgreement/ram:BuyerTradeParty/ram:PostalTr
adeAddress/ram:LineOne
BT-51 3 0.1 Buyer address An additional address T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:A E 0.1
line 2 line in an address that pplicableHeaderTradeAgreement/ram:BuyerTr
...