SIST-TS CEN/TS 16931-3-3:2020
(Main)Electronic invoicing - Part 3-3: Syntax binding for UN/CEFACT XML Industry Invoice D16B
Electronic invoicing - Part 3-3: Syntax binding for UN/CEFACT XML Industry Invoice D16B
This CEN Technical Specification (TS) contains the mapping between the semantic data model of an electronic invoice (EN 16931-1)
and the following syntax: UN/CEFACT XML Industry Invoice D16B. For each element in the semantic model (including sub-elements
or supplementary components such as Code List 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.
Any rules to be followed when using the specific syntax are stated informally in this TS. Together with this TS a set of validation
artefacts is published, including formalisation of the rules.
In addition, the deliverable shall unambiguously define the code lists and, where applicable, the subset of codes to be used for each
coded element in the model of EN 16931-1 when using the UN/CEFACT XML Industry Invoice D16B syntax as defined in CEN/TS
16931-3-3. The deliverable must guide the user how and where to apply for additions to these code lists. It will be issued as an annex
to the existing text of CEN/TS 16931-3-3:2017
Elektronische Rechnungsstellung - Teil 3-3: Umsetzung in die Syntax UN/CEFACT XML Cross Industry Invoice D16B
Dieses Dokument legt die Zuordnung (en: mapping) zwischen dem semantischen Modell einer elektronischen Rechnung, das in EN 16931 1 enthalten ist, und der Cross Industry Invoice in der Syntax UN/CEFACT XML 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-3 : Correspondance syntaxique pour les factures intersectorielles - Schéma XML D16B UN/CEFACT
Elektronsko izdajanje računov - 3-3. del: Povezava sintakse za UN/CEFACT XML Cross Industry Invoice D16B
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
SIST-TS CEN/TS 16931-3-3:2020
01-oktober-2020
Nadomešča:
SIST-TS CEN/TS 16931-3-3:2018
Elektronsko izdajanje računov - 3-3. del: Povezava sintakse za UN/CEFACT XML
Cross Industry Invoice D16B
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: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
SIST-TS CEN/TS 16931-3-3:2020 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
---------------------- Page: 2 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
June 2020
TECHNISCHE SPEZIFIKATION
ICS 35.240.20; 35.240.63 Supersedes CEN/TS 16931-3-3:2017
English Version
Electronic invoicing - Part 3-3: Syntax binding for
UN/CEFACT XML Industry Invoice D16B
Facturation électronique - Partie 3-3 : Liaison de Elektronische Rechnungsstellung - Teil 3-3: Umsetzung
syntaxe pour UN/CEFACT XML Facture industrielle in die Syntax UN/CEFACT XML Cross Industry Invoice
D16B D16B
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-3:2020 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
Contents
European foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 6
3 Terms and definitions . 6
4 Syntax binding to the UN/CEFACT XML Cross Industry Invoice D16B . 7
4.1 Introduction . 7
4.2 Data types . 8
4.3 Codes and identifiers . 8
4.4 Mapping the Invoice model . 9
4.5 Validation artefacts . 94
5 Mismatches . 94
5.1 Semantic level . 94
5.2 Structural level . 94
5.3 Cardinality level . 94
Annex A (normative) Code lists . 95
A.1 Introduction . 95
A.2 Code lists . 95
A.2.1 ISO 3166-1 — Country Codes . 95
A.2.2 ISO 4217 — Currency codes . 95
A.2.3 ISO/IEC 6523 — Identifier scheme code . 96
A.2.4 UNTDID 1001 — Document type . 97
A.2.5 UNTDID 1153 — Reference code qualifier . 99
A.2.6 VAT Identifier . 99
A.2.7 VAT Category code . 99
A.2.8 UNTDID 2005/ UNTDID 2475 — Event time code . 100
A.2.9 UNTDID 4451 — Text subject qualifier . 100
A.2.10 UNTDID 4461 — Payment means . 101
A.2.11 UNTDID 5305 — Duty or tax or fee category . 101
A.2.12 UNTDID 5189 — Allowance codes . 102
A.2.13 UNTDID 7143 — Item type identification code . 103
A.2.14 UNTDID 7161 — Charge codes . 104
A.2.15 Mime type codes — Mime codes . 104
A.2.16 CEF EAS — Electronic address scheme identifier . 104
A.2.17 CEF VATEX — VAT exemption reason code . 105
2
---------------------- Page: 4 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
A.2.18 UN/ECE Recommendation N°20 and UN/ECE Recommendation N°21 — Unit codes . 105
A.3 International registration authority for ISO/IEC 6523 . 105
A.4 UN/Cefact: new code request / code change request . 112
Annex B (informative) Examples . 115
B.1 Introduction . 115
B.2 Invoice with multiple line items . 115
B.3 IT equipment . 137
B.4 Subscription. 146
B.5 Domestic payment . 158
B.6 Maximum content . 164
B.7 Minimum content . 175
B.8 Taxes . 186
B.9 Electricity . 191
B.10 Licenses . 203
Bibliography . 214
3
---------------------- Page: 5 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
European foreword
This document (CEN/TS 16931-3-3: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-3: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, 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.
4
---------------------- Page: 6 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
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
1
. Based on this recognition “The Commission
savings of around EUR 240 billion over a six-year period”
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 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
1
http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=COM:2010:0712:FIN:en:PDF.
5
---------------------- Page: 7 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
1 Scope
This document 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 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 4217, Codes for the representation of currencies
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 [3]]
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
6
---------------------- Page: 8 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
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
2
policy of UNECE as a global standardization 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 and 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 recognized organisations are able to participate in the development and maintenance process.
UN/CEFACT standards are actively used worldwide in various sectors like Agriculture, Transport and
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 Defence. Within the global GS1 Community UN/CEFACT XML is used (apart from
EANCOM and 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 and 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)
2
See www.cen.eu, www.unece.org/cefact.html
7
---------------------- Page: 9 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
— German B2B and B2C core invoice standard (ZUGFeRD)
UN/CEFACT provides the relevant standards and guidelines on their website.
Support to the implementers and users is provided through other standardization 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 standardized 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. For
syntax binding of EN 16931-1 electronic invoices, the second set of schemas (decoupled) shall be used
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
5
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 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.
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/
3
See C(2014) 7912 final, ANNEX 1, p.5
4
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/
5
https://www.unece.org/cefact/rsm/rsm_index.html
8
---------------------- Page: 10 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
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.
9
---------------------- Page: 11 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
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 I /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:ID E 1.1
number identification of the
Invoice.
BT-2 1 1.1 Invoice The date when the D /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IssueDate E 1.1 @format
issue date Invoice was issued. Time/udt:DateTimeString = ”102”
/rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:IssueDate A Only
Time/udt:DateTimeString/@format value
“102”
BT-3 1 1.1 Invoice A code specifying C /rsm:CrossIndustryInvoice/rsm:ExchangedDocument/ram:TypeCode E 0.1 CAR-2
type code the functional type
of the Invoice.
BT-5 1 1.1 Invoice The currency in C /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram: E 0.1 CAR-2
currency which all Invoice ApplicableHeaderTradeSettlement/ram:InvoiceCurrencyCode
code amounts are given,
except for the Total
VAT amount in
accounting
currency.
BT-6 1 0.1 VAT The currency used C /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram: E 0.1 CAR-2
accounting for VAT accounting ApplicableHeaderTradeSettlement/ram:TaxCurrencyCode
currency and reporting
code purposes as
accepted or
required in the
country of the
Seller.
10
Leve
Card
DT
Typ
Card
---------------------- Page: 12 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
ID BT Desc. Path Match Rules
BT-7 1 0.1 Value The date when the D /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram: E 1.1 STR-2 @format
added tax VAT becomes ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:Ta = ”102”
point date accountable for the xPointDate/udt:DateString
Seller and for the
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.
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram: A Only
ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:Ta value
xPointDate/udt:DateString/@format “102”
BT-8 1 0.1 Value The code of the date C /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram: E 0.1 STR-2
added tax when the VAT ApplicableHeaderTradeSettlement/ram:ApplicableTradeTax/ram:Du
point date becomes eDateTypeCode
code accountable for the
Seller and for the
Buyer.
BT-9 1 0.1 Payment The date when the D /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram: E 1.1 @format
due date payment is due. ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerm = ”102”
s/ram:DueDateDateTime/udt:DateTimeString
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram: A Only
ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerm value
s/ram:DueDateDateTime/udt:DateTimeString/@format “102”
BT-10 1 0.1 Buyer An identifier T /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram: E 0.1
reference assigned by the ApplicableHeaderTradeAgreement/ram:BuyerReference
Buyer used for
internal routing
purposes.
11
Leve
Card
DT
Typ
Card
---------------------- Page: 13 ----------------------
SIST-TS CEN/TS 16931-3-3:2020
CEN/TS 16931-3-3:2020 (E)
ID BT Desc. Path Match Rules
BT-11 1 0.1 Project The identification of O /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram: E 1.1 Use
reference the project the ApplicableHeaderTradeAgreement/ram:SpecifiedProcuringProject/r “Project
invoice refers to. am:ID reference
” as
default
value for
Name.
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram: E 1.1 Use
Applica
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.