SIST EN 16931-1:2017+A1:2020/oprA2:2022
(Amendment)Electronic invoicing - Part 1: Semantic data model of the core elements of an electronic invoice
Electronic invoicing - Part 1: Semantic data model of the core elements of an electronic invoice
This European Standard establishes a semantic data model of the core elements of an electronic invoice. The semantic model includes only the essential information elements that an electronic invoice needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross sector and for domestic trade. The semantic model may be used by organizations in the private and the public sector for public procurement invoicing. It may also be used for invoicing between private sector enterprises. It has not been specifically designed for invoicing consumers.
This European Standard complies at least with the following criteria:
- it is technologically neutral;
- it is compatible with relevant international standards on electronic invoicing;
- the application of this standard should comply with the requirements for the protection of personal data of Directive 95/46/EC, having due regard to the principles of privacy and data protection by-design, data minimization, purpose limitation, necessity and proportionality;
- it is consistent with the relevant provisions of Directive 2006/112/EC [2];
- it allows for the establishment of practical, user-friendly, flexible and cost-efficient electronic invoicing systems;
- it takes into account the special needs of small and medium-sized enterprises as well as of sub-central contracting authorities and contracting entities;
- it is suitable for use in commercial transactions between enterprises.
Elektronische Rechnungsstellung - Teil 1: Semantisches Datenmodell der Kernelemente einer elektronischen Rechnung
Facturation électronique - Partie 1 : modèle sémantique de données des éléments essentiels d'une facture électronique
Elektronsko izdajanje računov - 1. del: Semantični podatkovni model osrednjih elementov za elektronski račun - Dopolnilo A2
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 16931-1:2017+A1:2020/oprA2:2022
01-marec-2022
Elektronsko izdajanje računov - 1. del: Semantični podatkovni model osrednjih
elementov za elektronski račun - Dopolnilo A2
Electronic invoicing - Part 1: Semantic data model of the core elements of an electronic
invoice
Elektronische Rechnungsstellung - Teil 1: Semantisches Datenmodell der Kernelemente
einer elektronischen Rechnung
Facturation électronique - Partie 1 : modèle sémantique de données des éléments
essentiels d'une facture électronique
Ta slovenski standard je istoveten z: EN 16931-1:2017+A1:2019/prA2
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 EN 16931- en,fr,de
1:2017+A1:2020/oprA2:2022
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
---------------------- Page: 2 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
DRAFT
EUROPEAN STANDARD
EN 16931-
NORME EUROPÉENNE
1:2017+A1:2019
EUROPÄISCHE NORM
prA2
January 2022
ICS 35.240.20; 35.240.63
English Version
Electronic invoicing - Part 1: Semantic data model of the
core elements of an electronic invoice
Facturation électronique - Partie 1 : modèle Elektronische Rechnungsstellung - Teil 1:
sémantique de données des éléments essentiels d'une Semantisches Datenmodell der Kernelemente einer
facture électronique elektronischen Rechnung
This draft amendment is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee CEN/TC 434.
This draft amendment A2, if approved, will modify the European Standard EN 16931-1:2017+A1:2019. If this draft becomes an
amendment, CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for
inclusion of this amendment into the relevant national standard without any alteration.
This draft amendment was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.
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.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
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
© 2022 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 16931-1:2017+A1:2019/prA2:2022
worldwide for CEN national Members. E
---------------------- Page: 3 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
Contents Page
European foreword . 4
1 Modification to Clause 2. 5
2 Modification to 4.2 . 5
3 Modifications to 5.2.2 . 5
4 Modification to 5.2.4 . 5
5 Modification to 5.2.5 . 5
6 Modification to 5.2.6 . 5
7 Modifications to 5.2.8 . 5
8 Modification to 5.2.9 . 6
9 Modification to 5.2.10 . 6
10 Modification to 5.2.11 . 6
11 Modifications to 5.3.3 . 6
12 Modification to 5.3.4 . 7
13 Modification to 5.4 . 7
14 Modification to Figure 14 . 7
15 Modification to 6.1 . 7
16 Modification to 6.3 – Table 2 . 9
17 Modification to 6.4.1 – Table 3 .19
18 Modification to 6.4.2 – Table 4 .19
19 Modification to 6.4.3.2 – Table 5 .22
20 Modification to 6.4.3.2 – Table 6 .23
21 Modification to 6.4.3.4.2 – Table 7 .24
22 Modifications to 6.4.3.4.3 .25
23 Modifications to 6.4.3.4.4 .26
24 Modification to 6.4.3.4.5 .27
25 Modification to 6.4.3.4.6 .29
26 Modification to 6.4.3.4.7 .30
27 Modification to 6.4.3.4.8 .30
28 Addition of 6.4.3.4.9 – Specific national regulation .32
29 Modification to 6.5.3 .33
30 Modification to 6.5.4 .33
31 Modification to 6.5.5 .33
32 Addition of 6.5.10 .33
2
---------------------- Page: 4 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
33 Modification to 6.5.12 . 34
34 Modification to 6.5.13 – Decimals . 34
35 Modification to 6.5.14 – Rounding . 35
36 Modification to Table C.1 . 36
3
---------------------- Page: 5 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
European foreword
This document (EN 16931-1:2017+A1:2019/prA2:2022) has been prepared by Technical Committee
CEN/TC 434 “Electronic Invoicing”, the secretariat of which is held by NEN.
This document is currently submitted to Enquiry.
This document has been prepared under a Standardization Request given to CEN by the European
Commission and the European Free Trade Association, and supports essential requirements of EU
Directive(s) / Regulation(s).
For relationship with EU Directive(s) / Regulation(s), see informative Annex B which is an integral part
of EN 16931-1:2017+A1:2019.
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
INVOICE 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
1
— CEN/TR 16931-6 , Electronic invoicing – Part 6: Result of the test of EN 16931-1 with respect to its
practical application for an end user – Testing methodology
1
In preparation.
4
---------------------- Page: 6 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
1 Modification to Clause 2
Remove:
IEEE/ISO/IEC 60559-2020 – ISO/IEC/IEEE International Standard – Floating-point arithmetic
2 Modification to 4.2
Add in the last paragraph:
The methodology to create extensions is described in CEN/TR 16931-5.
3 Modifications to 5.2.2
Replace the last two sentences of the 1st paragraph by
This delivery or deliveries is/are then invoiced by the Seller to the Buyer. Finally, the Buyer pays the
Payee.
Replace the last two sentences of the 2nd paragraph by:
Deliveries result in an invoice. An invoice may refer to multiple deliveries and multiple purchase orders.
Replace the 1st sentence of the 3rd paragraph by:
A delivery may include the pick-up and return of returnable packaging from previous deliveries and, for
which a payment (deposit) had previously been made by the Buyer and had been received by the Seller.
4 Modification to 5.2.4
Replace the last two sentences of the last paragraph by:
A purchase order serves as a contract and triggers the deliveries. A purchase order may be confirmed by
the Seller (not shown in the diagram).
5 Modification to 5.2.5
Delete the last sentence:
Each delivery … one purchase order.
6 Modification to 5.2.6
Delete the last sentence:
An invoice … to one delivery.
7 Modifications to 5.2.8
Replace – paragraph with:
After receipt of the purchase order the Seller sends a despatch advice in advance of the deliveries. In the
invoice a reference is made to the relevant despatch advice(s). The invoice content should reflect the
content of despatch advices which it refers to. An invoice may refer to multiple purchase order and
multiple despatch advices.
5
---------------------- Page: 7 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
8 Modification to 5.2.9
Replace the paragraph with:
After delivery and before the invoice is issued, the Seller waits for a receiving advice from the Receiver,
in which the Receiver acknowledges that the goods and services have been received and if there are any
issues with the delivery. The Seller bases the invoice on information contained in the receiving advices.
The invoice may refer to multiple despatch advices, multiple receiving advices and may also refer to
multiple purchase orders.
9 Modification to 5.2.10
Replace the last sentence by:
The invoice or credit note may refer to multiple preceding invoices.
10 Modification to 5.2.11
Delete the last sentence
See Annex A … mechanisms.
11 Modifications to 5.3.3
In the “In scope for the core invoice model” replace R5, R7, R9 and R10 by:
R5 information to trace to related purchase orders from the document and line level (all processes,
except P2 and P5);
R7 information to trace to a single contract and the underlying call for tenders from the document
or line level (all processes, except P3 and P5);
R9 information to trace to multiple despatch advices from the document and line level (processes
P7 and P8);
R10 information to trace to multiple receiving advices from the document and line level (process P8);
Replace the list in “Out of scope for the core invoice model” by:
— reference to one or more related purchase order lines on header level;
— reference to multiple related purchase order lines on line level;
— reference to multiple contracts;
— reference to one or more price lists;
— reference to the exact time of delivery;
— reference to more than one receiving advice;
— reference to one or more receiving advice lines at invoice line level;
— reference to supporting documents at invoice line level;
— reference to one or more consumption reports or performance records;
— reference to one or more invoices for payment in advance;
6
---------------------- Page: 8 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
— reference to multiple sales orders (issued by the Seller);
— sub-lines of allowances and charges;
— delivered quantities of goods and services if different from invoiced quantities;
— ordered quantities of goods and services if different from invoiced quantities;
— back-ordered quantities of goods and services if different from invoiced quantities;
— coded attributes of goods and services;
— specific coded quality information of goods or services;
— structured metered values;
— lot numbers of goods and services (except in free text);
— serial numbers or other identification numbers (e.g. of the person rendering the services) (except
in free text);
12 Modification to 5.3.4
In “In scope for the core invoice model” replace R55 by:
R55 codes for exemption and out of scope reasons at document and invoice line level.
13 Modification to 5.4
Replace the 1st paragraph with:
An invoice, compliant with the core invoice model may reference multiple purchase orders and multiple
deliveries explicitly. For automatic processing of invoices, usually explicit, qualified references are
needed.
14 Modification to Figure 14
Add the title of the figure
Figure 14 — Invoice relations
15 Modification to 6.1
Replace Figure 15 by:
7
---------------------- Page: 9 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
8
---------------------- Page: 10 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
16 Modification to 6.3 – Table 2
Semanti
Cardinalit Business Req.
c data
ID Level Description Usage Note
y Term ID
2
type
The time of the day
BT- Invoice issue
+ 0.1 when the Invoice was R56 Time
188 time
issued.
Identifies the Seller's
electronic address to
Seller R13
BT- which the application Identifie
++ 0.1 electronic ,
34 level response to the r
address R57
invoice may be
delivered.
The identification The scheme identifier shall be
Scheme scheme identifier of the chosen from the EAS
1.1
identifier Seller electronic (Electronic Address Scheme)
address. list.
Identifies the Buyer's
Buyer R13
BT- electronic address to Identifie
++ 0.1 electronic ,
49 which the invoice is r
address R57
delivered.
The identification The scheme identifier shall be
Scheme scheme identifier of the chosen from the EAS
1.1
identifier Buyer electronic (Electronic Address Scheme)
address. list.
A group of business In the case of pick-up, the
terms providing deliver to address is the pick-
BG- DELIVER TO information about the up address. Sufficient
++ 0.1 R32
address to which goods components of the address
15 ADDRESS
and services invoiced are to be filled to comply with
were or are delivered. legal requirements.
A group of business
PAYMENT
BG- terms providing
+ 0.n INSTRUCTIO R58
16 information about the
NS
payment.
The amount to be paid In case of a split payment.
BT- Amount to
++ 0.1 according this payment May be the amount to be Amount
166 be paid
instruction withheld.
2
The suffix ".Type" has been deleted for readability.
9
---------------------- Page: 11 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
Semanti
Cardinalit Business Req.
c data
ID Level Description Usage Note
y Term ID
2
type
A group of business
BG- CREDIT
++ 0.1 terms to specify credit R58
17 TRANSFER
transfer payments.
Document
R15
BT- level The amount of an
++ 1.1 , Amount
92 allowance allowance, without VAT.
R19
amount
The base amount that
may be used, in
Document
conjunction with the R15
BT- level
++ 0.1 document level , Amount
93 allowance
allowance percentage, to R42
base amount
calculate the document
level allowance amount.
10
---------------------- Page: 12 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
Semanti
Cardinalit Business Req.
c data
ID Level Description Usage Note
y Term ID
2
type
The following entries of
UNTDID 5305 [6] are used
(further clarification between
brackets):
- Standard rate (Liable for
VAT in a standard way)
- Zero rated goods (Liable for
VAT with a percentage rate of
zero)
- Exempt from tax
(VAT/IGIC/IPSI)
- VAT Reverse Charge
(Reverse charge
VAT/IGIC/IPSI rules apply)
- VAT exempt for intra
R15
community supply of goods
Document
,
(VAT/IGIC/IPSI not levied
level A coded identification of
R16
due to Intra-community
BT- allowance what VAT category
++ 1.1 , Code
supply rules)
95 VAT applies to the document
R45
category level allowance.
- Free export item, tax not
,
code
charged (VAT/IGIC/IPSI not
R48
levied due to export outside
of the EU)
- Services outside scope of tax
(Sale is not subject to
VAT/IGIC/IPSI)
- Canary Islands General
Indirect Tax (Liable for IGIC
tax)
- Liable for IPSI
(Ceuta/Melilla tax)
- Transferred (VAT) for
Italian split payment
- Specific national regulation
(to be detailed in the
Exemption reason)
Document
A textual statement of R48
Level
the reason why the ,
BT- Allowance Articles 226 items 11 to 15
0.1
+++ amount is exempted R49 Text
167 VAT Directive 2006/112/EC [2].
from VAT or why no ,
exemption
VAT is being charged R51
reason text
11
---------------------- Page: 13 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
Semanti
Cardinalit Business Req.
c data
ID Level Description Usage Note
y Term ID
2
type
R48
Document
,
Level A coded statement of the
R49
BT- Allowance reason for why the VATEX (VAT Exemption
+++ 0.1 Code
,
168 VAT amount is exempted Reasons) code list.
R51
exemption from VAT.
reason code
R55
Document
Indicator that shows
level
BT- that the allowance
++ 0.1 allowance Yes or no R38 Text
169 amount is subject to tax
tax withheld
withholding process
indicator
R15
Document ,
BT- The amount of a charge,
++ 1.1 level charge R16 Amount
99 without VAT.
amount ,
R19
The base amount that
may be used, in R15
Document conjunction with the ,
BT-
++ 0.1 level charge document level charge R16 Amount
100
base amount percentage, to calculate ,
the document level R19
charge amount.
12
---------------------- Page: 14 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
Semanti
Cardinalit Business Req.
c data
ID Level Description Usage Note
y Term ID
2
type
The following entries of
UNTDID 5305 [6] are used
(further clarification between
brackets):
- Standard rate (Liable for
VAT in a standard way)
- Zero rated goods (Liable for
VAT with a percentage rate of
zero)
- Exempt from tax
(VAT/IGIC/IPSI)
- VAT Reverse Charge
(Reverse charge
VAT/IGIC/IPSI rules apply)
- VAT exempt for intra
community supply of goods
(VAT/IGIC/IPSI not levied
Document R15
A coded identification of
due to Intra-community
level charge ,
BT- what VAT category
supply rules)
1.1
++ VAT R45 Code
102 applies to the document
category - Free export item, tax not ,
level charge.
code charged (VAT/IGIC/IPSI not R48
levied due to export outside
of the EU)
- Services outside scope of tax
(Sale is not subject to
VAT/IGIC/IPSI)
- Canary Islands General
Indirect Tax (Liable for IGIC
tax)
- Liable for IPSI
(Ceuta/Melilla tax)
- Transferred (VAT) for
Italian split payment
- Specific national regulation
(to be detailed in the
Exemption reason)
Document A textual statement of R48
Level Charge the reason why the ,
BT- Articles 226 items 11 to 15
+++ 0.1 VAT amount is exempted R49 Text
170 Directive 2006/112/EC [2].
exemption from VAT or why no ,
reason text VAT is being charged R51
R48
Document
,
A coded statement of the
Level Charge
R49
BT- reason for why the VATEX (VAT Exemption
+++ 0.1 VAT Code
,
amount is exempted
171 Reasons) code list.
exemption
R51
from VAT.
reason code
R55
13
---------------------- Page: 15 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
Semanti
Cardinalit Business Req.
c data
ID Level Description Usage Note
y Term ID
2
type
Document Indicator that shows
BT- level charge that the charge amount
++ 0.1 Yes or no R38 Text
172 tax withheld is subject to tax
indicator withholding process
The Invoice total amount
without VAT is the Sum of
Invoice line net amount (BT-
Invoice total
BT- The total amount of the 109) minus Sum of
++ 1.1 amount R40 Amount
109 Invoice without VAT. allowances on document
without VAT
level (BT-92) plus Sum of
charges on document level
(BT-99).
The sum of amount
which have been paid in
This amount is subtracted
advance or shall not be R40
BT- from the invoice total amount
+++ 0.1 Paid amount calculated into the , Amount
113 with VAT to calculate the
amount due for payment R66
amount due for payment.
(e.g. split payment
amount).
Part of the tax or social
BG- securities amount that is
+ 0.n Tax withheld R38
33 not to be paid to the
Seller.
BT- Amount Amount that is not to be
++ 1.1 R38 Amount
172 withheld paid to the Seller.
Base of the amount that
BT- Withheld
++ 0.1 is not to be paid to the R38 Amount
173 base amount
Seller.
Percentage of the base
BT- Withheld Percent
0.1 amount that is not to be
++ R38
174 percentage age
paid to the Seller.
BT- Tax withheld Description/Reason of
++ 0.1 R38 Text
175 reason text tax withholding process
14
---------------------- Page: 16 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
Semanti
Cardinalit Business Req.
c data
ID Level Description Usage Note
y Term ID
2
type
The following entries of
UNTDID 5305 [6] are used
(further clarification between
brackets):
- Standard rate (Liable for
VAT in a standard way)
- Zero rated goods (Liable for
VAT with a percentage rate of
zero)
- Exempt from tax
(VAT/IGIC/IPSI)
- VAT Reverse Charge
(Reverse charge
VAT/IGIC/IPSI rules apply)
- VAT exempt for intra
community supply of goods
R38
(VAT/IGIC/IPSI not levied
VAT ,
due to Intra-community
BT- Coded identification of a
++ 1.1 category R45 Code
supply rules)
118 VAT category.
code ,
- Free export item, tax not
R49
charged (VAT/IGIC/IPSI not
levied due to export outside
of the EU)
- Services outside scope of tax
(Sale is not subject to
VAT/IGIC/IPSI)
- Canary Islands General
Indirect Tax (Liable for IGIC
tax)
- Liable for IPSI
(Ceuta/Melilla tax)
- Transferred (VAT) for
Italian split payment
- Specific national regulation
(to be detailed in the
Exemption reason)
R48
,
A coded statement of the
VAT
R49
BT- reason for why the VATEX (VAT Exemption
++ 0.1 exemption Code
,
121 amount is exempted Reasons) code list.
reason code
R51
from VAT.
R55
15
---------------------- Page: 17 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
Semanti
Cardinalit Business Req.
c data
ID Level Description Usage Note
y Term ID
2
type
Attached document is used
when documentation shall be
stored with the Invoice for
future reference or audit
purposes.
A Receiver of an Invoice,
compliant to the core invoice
An attached document
Binary
model may accept and
BT- Attached embedded as binary
object
++ 0.1 process the following types of R35
125 document object or sent together
attachments with a warning.
with the invoice.
A warning is given because
the processing of a structured
attachment requires the
knowledge of its semantics,
which have to be given via a
bilateral agreement,.
Allowed mime codes:
- application/pdf
- image/png
- image/jpeg
- text/csv
-
Attached
The mime code of the
application/vnd.openxmlfor
1.1 document
attached document.
mats-
Mime code
officedocument.spreadsheet
ml.sheet
-
application/vnd.oasis.opendo
cument. spreadsheet
— application/xml (.xml).
It may be a subscription
number, telephone number,
An identifier for an
Invoice line meter point etc., as
BT- object on which the Identifie
++ 0.n object applicable. It is possible to R33
128 invoice line is based, r
identifier reference multiple types of
given by the Seller.
reference (not multiple
references of the same type).
If it may be not clear for the
receiver what scheme is used
The identification for the identifier, a
Scheme scheme identifier of the conditional scheme identifier
0.1
identifier Invoice line object should be used that shall be
identifier. chosen from the
UNTDID 1153 code list [6]
entries.
16
---------------------- Page: 18 ----------------------
SIST EN 16931-1:2017+A1:2020/oprA2:2022
EN 16931-1:2017+A1:2019/prA2:2022 (E)
Semanti
Cardinalit Business Req.
c data
ID Level Description Usage Note
y Term ID
2
type
Indicator that shows
Invoice line
BT- that the Invoice line
++ 0.1 tax withheld Yes or no R37 Text
176 amount is subject to tax
indicator
withholding process
Invoice line An identifier for a
BT- purchase referenced purchase
++ 0.1 R5 Text
177 order order, issued by the
reference Buyer.
Invoice line An identifier for a
BT-
++ 0.1 project referenced project, R44 Text
185
reference issued by the Buyer.
Invoice line
BT- An identifier for a
++ 0.1 tender or lot R7 Text
186 referenced tender or lot
reference
Invoice line
BT- An identifier for a
++ 0.1 contract R7 Text
187 referenced contract
reference
Invoice line An identifier for a
BT-
++ 0.1 sales order referenced sales order, R5 Text
178
reference issued by the Seller.
Invoice line An identifier for a
BT- despatch referenced despatch
++ 0.1 R9 Text
179 advice advice, issued by the
reference Seller.
Invoice line An identifier for a
BT- receiving referenced receiving
++ 0.1 R10 Text
180 advice advice, issued by the
reference Buyer.
Invoice line An identifier for a Docume
The purchase order identifier
BT- purchase referenced line within a nt
++ 0.1 may be referenced on R6
132 order line purchase order, issued referenc
document level.
reference by the Buyer. e
Invoice line R15
BT- The amount of an
+++ 1.1 allowance , Amount
136 allowance, w
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.