CEN/TS 17901:2023

SLOVENSKI STANDARD
01-februar-2024
Digitalna izmenjava informacij v zavarovalniški dejavnosti - Elektronski premijski
račun - Prikaz v elektronskem računu po standardu EN 16931-1:2017
Digital Information Interchange in the Insurance Industry - Electronic Premium Invoice -
Mapping to Electronic Invoice EN 16931-1:2017
Digitaler Informationsaustausch in der Versicherungswirtschaft - Elektronische Prämien-
Rechnung - Abbildung auf die elektronische Rechnung EN 16931-1:2017
Échange d'informations numériques dans le secteur de l'assurance - Facture
électronique - Cartographie avec la facture électronique dans la norme EN 16931-1:2017
Ta slovenski standard je istoveten z: CEN/TS 17901:2023
ICS:
03.060 Finance. Bančništvo. Finances. Banking. Monetary
Monetarni sistemi. systems. Insurance
Zavarovanje
35.240.20 Uporabniške rešitve IT pri IT applications in office work
pisarniškem delu
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 17901
TECHNICAL SPECIFICATION
SPÉCIFICATION TECHNIQUE
December 2023
TECHNISCHE SPEZIFIKATION
ICS 03.060; 35.240.20; 35.240.63
English Version
Digital Information Interchange in the Insurance Industry -
Electronic Premium Invoice - Mapping to Electronic
Invoice EN 16931-1:2017
Échange d'informations numériques dans le secteur de Digitaler Informationsaustausch in der
l'assurance - Facture électronique - Cartographie avec Versicherungswirtschaft - Elektronische Prämien-
la facture électronique dans la norme EN 16931- Rechnung - Abbildung auf die elektronische Rechnung
1:2017 EN 16931-1:2017
This Technical Specification (CEN/TS) was approved by CEN on 27 November 2023 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, Türkiye 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
© 2023 CEN All rights of exploitation in any form and by any means reserved Ref. No. CEN/TS 17901:2023 E
worldwide for CEN national Members.

Contents Page
European foreword . 3
Introduction . 4
1 Scope . 5
2 Normative references . 5
3 Terms and definitions . 6
4 Business processes and functionalities supported by the electronic premium invoice . 6
4.1 The business parties . 6
4.2 Requirements for the data of an electronic premium invoice on document level . 7
4.3 Requirements for the data describing the issuer of the premium invoice . 9
4.4 Requirements for the data describing the premium payer of the premium invoice. 10
4.5 Requirements for the data describing the payment instructions of the premium
invoice . 10
4.6 Requirements for the data describing allowances applicable to the premium invoice . 11
4.7 Requirements for the data describing fees charged with the premium invoice . 11
4.8 Requirements for the data describing taxes other than VAT charged with the
premium invoice . 12
4.9 Requirements for the data describing the details of the premium invoice on line
level . 12
4.10 Requirements for the data describing allowances applicable to the invoice line . 13
4.11 Requirements for the data describing taxes other than VAT charged with the invoice
line . 13
5 Mapping of the data elements of an electronic premium invoice to the core elements
of the electronic invoice described in EN 16931-1 . 13
5.1 Introduction . 13
5.2 Mapping . 15
5.3 Business rules . 24
Annex A (informative) Examples of premium invoices . 25
A.1 Example 1 (Insurance tax applied on total level) . 25
A.2 Example 2 (Insurance tax applied on line level) . 26
A.3 Example 3 (Different insurance tax rates) . 27
A.4 Example 4 (Different insurance tax rates and insurance tax applied on total level) . 29
A.5 Example 5 (Several charges on one invoice line) . 30
A.6 Example 6 (Premium amount with and without insurance tax) . 32
A.7 Example 7 (Premium invoice for motor insurance including vehicle tax) . 33

European foreword
This document (CEN/TS 17901:2023) has been prepared by Work Group 1 “Electronic Premium
Invoice” of Technical Committee CEN/TC 445 “Digital Information Interchange in the Insurance
Industry”, the secretariat of which is held by DIN.
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.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
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, Türkiye and the
United Kingdom.
Introduction
Electronic invoicing is an important requirement for the digitalization in all commercial domains and in
the consumer sector. The European Commission mandated CEN to establish a European standard for
this prerequisite. CEN developed in several parts the semantic and syntactical standards for the
implementation of electronic invoicing. In the European standard EN 16931-1, the semantic data model
of the core elements of an electronic invoice is defined. This standard is designed to be implemented
cross-domain in all industries.
Since the first publication of EN 16931-1 in 2017, software applications based on EN 16931-1 are
increasingly in use. Therefore, clients using such software systems demand the delivery of electronic
invoices from their supplier. Also, in the consumer sector software applications support the digital
import of electronic invoices, e.g. in home-banking software.
The insurance industry is a significant supplier for all commercial domains and the consumer sector.
Consequently, commercial and consumer insurance clients demand an electronic invoicing from the
insurance sector.
Because the insurance industry is a cross-domain supplier, the insurance sector should use the core
semantic data model described in EN 16931-1 without insurance-specific extensions that would require
a special import software at the insurance client.
Therefore, this document defines the standardized mapping of the specific requirements of an
insurance premium invoice to the generic core semantic data model described in EN 16931-1.
The aim of this document is to establish European-wide implementation guidance for the insurance
industry containing the semantic mapping. The mapping to a concrete syntax is not part of this
document. A concrete implementation of this document complies with a “Core Invoice Usage
Specification” (CIUS) as specified in EN 16931-1. Therefore insurance industry trading partners can rely
on the syntax bindings provided for EN 16931-1.
Benefits for invoice issuers (insurance companies or insurance intermediaries) are:
• reduced costs for paper, printing, and physical transportation;
• reduced time for invoice delivery;
• reduced time for payment receipt;
• reduced time for service on incorrect or incomplete payments.
Benefits for commercial insurance clients are:
• import of digital premium invoices to their enterprise software;
• reduced manual processing;
• avoidance of payment errors.
Benefits for consumer insurance clients are:
• import of digital premium invoices to their banking software;
• easier payment process;
• avoidance of payment errors;
• use for digital tax declaration.
1 Scope
This document defines the standardized mapping of the specific requirements of an insurance premium
invoice to the generic electronic invoice described in EN 16931-1. This mapping meets the
requirements of an electronic premium invoice to ensure legal (including fiscal) compliance as well as
business and technical demands of the insurance industry.
Premium invoices can be issued by different organizations of the insurance industry to commercial
clients or consumers. This document includes premium invoices issued by insurance companies as well
as insurance intermediaries.
This document does not deal with data protection matters in premium invoices.
NOTE General Data Protection Regulation, EU Regulation 2016/679 can include requirements on personal
data.
Premium invoices are regularly not subject to VAT but to special taxes. In particular, the requirements
resulting from insurance tax regulations are considered. Requirements for other taxes are also
incorporated.
The rules defined in EN 16931-1 do not support invoices with amounts not subject to VAT together
with additional amounts which are subject to VAT. Therefore, this document also does not support
premium invoices which invoice other goods and services which are subject to VAT invoiced together
with premium amounts.
Out of the scope of this document are accounting transactions between insurance companies and
insurance intermediaries which may contain premium invoice data, but regularly consist of other data
(e.g. commissions) which are not part of a regular invoice.
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:2017+A1:2019, Electronic invoicing - Part 1: Semantic data model of the core elements of
an electronic invoice
ISO 4217, Codes for the representation of currencies
ISO/IEC 6523-1, Information technology - Structure for the identification of organizations and
organization parts - Part 1: Identification of organisation identification schemes
UNTDID 1153, Reference code qualifier
UNTDID 4461, Payment means code
UNTDID 5305, Duty or tax or fee category code
UN ECE Recommendation No. 20, Codes for Units of Measure Used in International Trade

As impacted by EN 16931-1:2017+A1:2019/AC:2020.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
premium invoice
invoice that contains premium amounts due for an insurance policy
3.2
insurance client
party that requests insurance coverage and pays the premium to an insurance company in exchange for
the coverage provided by an insurance policy
3.3
premium payer
party that pays the premium to an insurance company for an insurance policy
Note 1 to entry: The premium payer is normally identical to the insurance client, but in certain circumstances the
premium payer is different from the insurance client, for example when an employer, the premium payer, pays the
premium for an insurance policy of which an employee is the insurance client.
3.4
insurance intermediary
party that offers advice and arranges policies for clients
Note 1 to entry: Definition in accordance with IDD: Directive (EU) 2016/97 of the European Parliament and of the
Council of 20 January 2016 on insurance distribution (recast) (OJ L 26, 2.2.2016).
3.5
insurance company
organization that covers an insurance client against a financial loss on receipt of a premium
Note 1 to entry: Definition in accordance with Solvency II: Directive 2009/138/EC of the European Parliament and
of the Council of 25 November 2009 on the taking-up and pursuit of the business of Insurance and Reinsurance
(Solvency II) (recast) (OJ L 335, 17.12.2009).
4 Business processes and functionalities supported by the electronic premium
invoice
4.1 The business parties
Several business parties are involved in the process of an electronic premium invoice (see Figure 1).
The following parties are the main stakeholders of the business process “premium invoicing”:
— Insurance company;
— Insurance intermediary;
— Premium payer.
In EN 16931-1, describing the core elements of the electronic invoice, the issuer of an invoice is called
the “Seller” and the receiver of an invoice is called the “Buyer”.
Figure 1 — Parties involved in invoicing
4.2 Requirements for the data of an electronic premium invoice on document level
An electronic invoice described in EN 16931-1 is structured in the document level, which consists of the
data of the invoice as a whole (e.g. invoice number and total amounts), and the line level, which contains
the details of the invoiced items.
Each requirement is given a requirement ID in the form of R+number. In Table 1 the requirements are
allocated to the data elements reflecting the requirement ID.
The following requirements for the data of an electronic premium invoice on document level are
identified:
— R1 An invoice number shall be provided to identify uniquely the premium invoice.
— R2 The date shall be provided when the premium invoice was issued.
— R3 The type of the premium invoice shall specify whether it is a regular invoice to be paid by the
premium payer or a credit note with a credit to the premium payer.
— R4 The currency shall be specified in which all amounts of the premium invoice are given.
— R5 A payment due date may be provided for the premium invoice. The payment due date is not
mandatory if the premium payer knows the due date of the invoice from other sources, for example
the insurance policy document.
— R6 The payment due date is mandatory if the invoice amount is debited from the account of the
premium payer by means of a SEPA direct debit mandate. In this case the payment due date is the
date when the invoice amount is debited from the account of the premium payer.
— R7 Optionally a reference of the premium payer for internal routing purposes may be provided (e.g.
contact identifier, department or office identifier).
— R8 The identification, the policy number, shall be specified to identify the insurance policy to which
the invoice relates.
— R9 In case of an open cover insurance policy the insurance client declares each individual risk
which is insured under the open cover contract. In this case a premium invoice is normally related
to a specific individual risk declaration. Therefore an identifier of the individual risk declaration
should be provided in the premium invoice.
— R10 If the premium invoice relates to a specific class of business or insurance product of the
insurance policy, the name or an identifier of this class of business or insurance product shall be
provided.
— R11 Optionally a reference identifier issued by the premium payer for the insurance policy may be
provided.
— R12 Optionally a textual description of the payment terms that apply to the amount due for
payment may be provided. It may include a description of possible penalties. This text may contain
multiple terms.
— R13 Optionally several notes may give unstructured textual information that is relevant to the
premium invoice as a whole. This text may explain the reason for the premium invoice.
— R14 Optionally the type of the premium invoice may be specified, such as first invoice, subsequent
invoice, renewal invoice.
— R15 An identification of the electronic specification and its version that the issuer of the electronic
premium invoice has implemented shall be provided.
— R16 A preceding invoice reference may be specified in a premium invoice, e.g. for a regulation
invoice.
— R17 Information about the issuer of the premium invoice shall be provided. The detailed
requirements are given in 4.3.
— R18 Information about the premium payer of the premium invoice shall be provided. The detailed
requirements are given in 4.4.
— R19 If the premium payer is different from the insurance client the name of the insurance client
shall be provided.
— R20 Optionally the invoicing period may be specified with the start date and the end date of the
period.
— R21 Information about the payment instructions for the premium invoice may be provided. The
detailed requirements are given in 4.5.
— R22 Information about allowances (deductions) applicable to the premium invoice as a whole may
be provided in detail and with the total sum of all allowances. The detailed requirements are given
in 4.6.
— R23 Information about fees charged with the premium invoice may be provided. The detailed
requirements are given in 4.7.
— R24 Information about taxes other than VAT, such as insurance tax, charged with the premium
invoice on document level may be provided. The detailed requirements are given in 4.8.
— R25 The total sum of net premiums (not including fees and taxes) shall be provided.
— R26 If fees or taxes (other than VAT) are charged with the premium invoice the total sum of fees
and taxes shall be provided.
— R27 The total amount of the premium invoice shall be provided.
— R28 Optionally the sum of amounts which have been paid in advance for this premium invoice may
be provided.
— R29 The amount due for payment shall be provided which is the total amount of the premium
invoice minus the paid amount.
— R30 Additional supporting documents may be used for referencing a document which is an external
document (referenced by a URL) or as an embedded document. The option to link to an external
document will be needed, for example in the case of large attachments and/or when sensitive
information, e.g. person-related information, has to be separated from the invoice itself.
— R31 Each supporting document shall be referenced by an identifier.
— R32 Optionally a description of the supporting document may be provided.
— R33 For external documents the URL (Uniform Resource Locator) shall be specified.
— R34 Embedded documents shall be transmitted as part of the electronic premium invoice.
— R35 Information about the details of the premium invoice on line level shall be provided which
includes information about the invoiced premium per insured person or insured object and/or per
type of coverage. The detailed requirements are given in 4.9.
4.3 Requirements for the data describing the issuer of the premium invoice
The issuer of a premium invoice is either an insurance company if the premium is collected by the
insurance company or an insurance intermediary if the premium is collected by the insurance
intermediary.
In EN 16931-1, describing the core elements of the electronic invoice, the issuer of an invoice is called
the “seller”. This document follows the naming of EN 16931-1 to support a clear mapping of the
insurance requirements to the core elements of the electronic invoice.
Therefore in the premium invoice the “seller” is either an insurance company or an insurance
intermediary.
The following requirements for the data of the seller in a premium invoice are identified:
— R36 The name of the seller shall be provided.
— R37 Optionally the seller may be identified by one or multiple identifiers each uniquely identifying
the seller in a specified identification scheme.
— R38 Optionally the seller may be identified by a legal registration identifier.
— R39 Optionally a tax registration identifier regarding insurance tax may be provided. If the seller is
an insurance company, this is the insurance tax registration identifier of the insurance company. If
the seller is an insurance intermediary, the insurance tax registration identifier of the insurance
intermediary is only required when the intermediary transfers the insurance tax directly to the tax
authorities.
— R40 If the seller is an insurance intermediary, the name and insurance tax registration identifier of
the insurance company shall be mentioned on the invoice in certain legislations. In this case, if the
insurance contract is shared between several insurance companies (i.e. in coinsurance), the names
and insurance tax registration identifiers of all insurance companies shall be mentioned on the
invoice.
— R41 Optionally the electronic address of the seller may be provided to which the application level
response to the invoice may be delivered.
— R42 The postal address of the seller shall be provided.
— R43 Optionally a contact point at the seller may be provided, such as a person name, a contact
identification, a department or office identification.
— R44 Optionally the telephone number of the contact point at the seller may be provided.
— R45 Optionally the email address of the contact point at the seller may be provided.
4.4 Requirements for the data describing the premium payer of the premium invoice
The receiver of a premium invoice is the premium payer who is normally, but not in all cases, the
insurance client.
In EN 16931-1, the receiver of an invoice is called the “buyer”. This document follows the naming of
EN 16931-1 to support a clear mapping of the insurance requirements to the core elements of the
electronic invoice.
Therefore in the premium invoice the “buyer” is the premium payer.
The following requirements for the data of the buyer in a premium invoice are identified:
— R46 The name of the buyer shall be provided.
— R47 Optionally the buyer may be identified by an identifier which uniquely identifies the buyer in
the system of the seller.
— R48 Optionally the buyer may be identified by a legal registration identifier.
— R49 Optionally the electronic address of the buyer may be provided to which the invoice is
delivered.
— R50 The postal address of the buyer shall be provided.
— R51 Optionally a contact point at the buyer may be provided, such as a person name, a contact
identification, a department or office identification.
— R52 Optionally the telephone number of the contact point at the buyer may be provided.
— R53 Optionally the email address of the contact point at the buyer may be provided.
4.5 Requirements for the data describing the payment instructions of the premium
invoice
Information about the payment instructions for the premium invoice may be provided. If the payment
instructions are included in a concrete premium invoice the following detailed requirements are
identified:
— R54 A payment means type code shall be specified for how a payment is expected to be or has been
settled, such as cash, payment transfer, direct debit, credit or debit card, or other payment
instruments.
— R55 Additional textual information for the payment means may be provided.
— R56 Remittance information may be provided which is a textual value issued by the seller that the
buyer should use in the payment order to establish a link between the payment and the invoice.
Commonly this information is the invoice number perhaps in combination with other references,
e.g. the policy number.
— R57 In case of a payment transfer the payment account identifier at a payment service provider
shall be specified to which payment should be made, such as IBAN or bank account identifier.
— R58 In case of a payment transfer the name of the payment account at a payment service provider
may be provided.
— R59 In case of a payment transfer the identifier of the payment service provider, where a payment
account is located, may be specified, such as a BIC or a national clearing code.
— R60 In case of a payment by credit or debit card the card account number shall be specified.
— R61 In case of a payment by credit or debit card the name of the card holder may be provided.
— R62 In case of a payment by direct debit the unique identifier assigned by the seller for referencing
the direct debit mandate may be provided.
— R63 In case of a payment by direct debit the unique creditor identifier assigned to the seller may be
provided.
— R64 In case of a payment by direct debit the account identifier to be debited may be provided.
4.6 Requirements for the data describing allowances applicable to the premium invoice
For allowances (e.g. deductions) applicable to the premium invoice as a whole the following
requirements are identified:
— R65 The amount of an allowance shall be specified without insurance tax on the allowance amount.
— R66 The base amount that may be used, in conjunction with the allowance percentage, to calculate
the allowance amount, may be provided.
— R67 The percentage that may be used, in conjunction with the allowance base amount, to calculate
the allowance amount, may be provided.
— R68 The reason for the allowance, expressed as text, may be provided.
4.7 Requirements for the data describing fees charged with the premium invoice
If fees, such as a fee for issuing the insurance policy document, are charged with the premium invoice
the following requirements are identified:
— R69 The fee amount shall be specified without insurance tax on the fee amount.
— R70 The base amount that may be used, in conjunction with the fee percentage, to calculate the fee
amount, may be provided.
— R71 The percentage that may be used, in conjunction with the fee base amount, to calculate the fee
amount, may be provided.
— R72 The type of the fee, expressed as a text, shall be specified.
4.8 Requirements for the data describing taxes other than VAT charged with the
premium invoice
If taxes, other than VAT, such as insurance tax, are charged with the premium invoice the following
requirements are identified:
— R73 The tax amount shall be specified.
— R74 The base amount that may be used, in conjunction with the tax percentage, to calculate the tax
amount, may be provided.
— R75 The percentage that may be used, in conjunction with the tax base amount, to calculate the tax
amount, may be provided.
— R76 The type of the tax, expressed as a text, shall be specified.
4.9 Requirements for the data describing the details of the premium invoice on line level
A premium invoice contains one or more invoice lines with information about the invoiced premium
per insured person or insured object and/or per type of coverage.
The following requirements for the data of an electronic premium invoice on line level are identified:
— R77 A unique identifier for the individual line within the invoice shall be specified.
— R78 Information to identify the insured person or object may be provided, such as the name of an
insured person, the address of an insured object or the registration id of an insured vehicle.
— R79 Optionally a reference identifier issued by the seller for the insured person or object may be
provided, such as a person number or object number.
— R80 The quantity of insured persons or objects that is charged in the invoice line shall be specified.
— R81 The total amount for the invoice line shall be provided.
— R82 Optionally the net premium amount (not including taxes) for each single insured object or
person may be provided in relation to the quantity of R80.
— R83 Optionally a reference identifier issued by the buyer for the insured person or object may be
provided, such as a person number, object number or line number in the insurance declaration.
— R84 Optionally a reference identifier issued by the buyer for the invoice line may be provided, such
as an accounting reference.
— R85 Optionally an invoicing period for the invoice line may be specified with the start date and the
end date of the period.
— R86 Information about allowances (deductions) applicable to the invoice line may be provided. The
detailed requirements are given in 4.10.
— R87 Information about taxes other than VAT, such as insurance tax, charged on the invoice line may
be provided. The detailed requirements are given in 4.11.
— R88 The coverage protecting the insured person or object shall be specified for the invoice line.
— R89 Optionally rating information for the given coverage may be provided, such as tariff class,
regional class, no-claims-bonus class.
— R90 Optionally a product or formula name of the seller for the given coverage may be provided.
— R91 Optionally additional information about the insured person or object and/or the coverage may
be provided.
4.10 Requirements for the data describing allowances applicable to the invoice line
For allowances (e.g. deductions) applicable to the invoice line the following requirements are identified:
— R92 The amount of an allowance shall be specified without insurance tax on the allowance amount.
— R93 The base amount that may be used, in conjunction with the allowance percentage, to calculate
the allowance amount, may be provided.
— R94 The percentage that may be used, in conjunction with the allowance base amount, to calculate
the allowance amount, may be provided.
— R95 The reason for the allowance, expressed as text, may be provided.
4.11 Requirements for the data describing taxes other than VAT charged with the
invoice line
If taxes, other than VAT, such as insurance tax, are charged with the invoice line the following
requirements are identified:
— R96 The tax amount shall be specified.
— R97 The base amount that may be used, in conjunction with the tax percentage, to calculate the tax
amount, may be provided.
— R98 The percentage that may be used, in conjunction with the tax base amount, to calculate the tax
amount, may be provided.
— R99 The type of the tax, expressed as a text, shall be specified.
5 Mapping of the data elements of an electronic premium invoice to the core
elements of the electronic invoice described in EN 16931-1
5.1 Introduction
The mapping of the data elements of an electronic premium invoice to the core elements of the
electronic invoice are specified in 5.2 in Table 1. This table is a subset of Table 2 in EN 16931-1:2017
+A1:2019 . The columns “ID”, “Level”, “Cardinality”, and “Business Term” are direct copies of Table 2 in
EN 16931-1:2017 +A1:2019 .
The two columns “Req” and “Insurance Requirement” in Table 1 of this document are additions to
Table 2 in EN 16931-1:2017+A1:2019 . These columns specify the mapping of the requirements of an
insurance premium invoice to the electronic invoice standardized in EN 16931-1.
The column “Req” refers to the identifiers “Rnn” of the premium invoice requirements specified in
Clause 4.
The column “Insurance Requirement” contains descriptions for the mapping of an insurance premium
invoice.
Table 1 of this document does not include all rows, i.e. invoice data elements, of Table 2 in EN 16931-
1:2017+A1:2019 because invoice data elements not applicable for premium invoices are not shown in
Table 1.
5.2 Mapping
Table 1 — Mapping of the insurance requirements to the semantic data model of the core
elements of an electronic invoice
ID Level Card. Business Term Req Insurance Requirement
BT-1 + 1.1 Invoice number R1 Invoice number
BT-2 + 1.1 Invoice issue date R2 Invoice issue date
Invoice type code according to the entries in
UNTDID 1001:
BT-3 + 1.1 Invoice type code R3
380 = Commercial invoice
381 = Credit note
Invoice currency code according to the entries
BT-5 + 1.1 Invoice currency code R4
in ISO 4217.
R5
BT-9 + 0.1 Payment due date Payment due date
R6
Reference of the Premium Payer for internal
BT-10 + 0.1 Buyer reference R7 routing purposes (e.g. contact ID, department,
office id).
Mandatory contract reference of the insurance
BT-12 + 0.1 Contract reference R8
policy.
Identifier of the individual risk declaration for
BT-13 + 0.1 Purchase order reference R9 an open cover contract for which this invoice is
issued.
This is the name / identifier of the class of
BT-18 + 0.1 Invoiced object identifier R10 business of the insurance contract or of the
insurance product.
If it may be not clear for the receiver what
scheme is used for the identifier, a conditional
0.1 Scheme identifier  scheme identifier should be used that if used
shall be chosen from the UNTDID 1153 code
list entries.
Buyer accounting Reference identifier of the Premium Payer for
BT-19 + 0.1 R11
reference the insurance policy.
A textual description of the payment terms
that apply to the amount due for payment
BT-20 + 0.1 Payment terms R12 (Including description of possible penalties).
This text may contain multiple lines and
multiple terms.
A group of business terms providing textual
BG-1 + 0.n INVOICE NOTE
notes that are relevant for the invoice.
BT-21 ++ 0.1 Invoice note subject code R13 The subject of the textual note in BT-22.
A textual note that gives unstructured
BT-22 ++ 1.1 Invoice note R13 information that is relevant to the invoice as a
whole.
A group of business terms providing
BG-2 + 1.1 PROCESS CONTROL  information on the business process and rules
applicable to the invoice document.
ID Level Card. Business Term Req Insurance Requirement
Type of the insurance premium invoice
specified by the Seller, e.g.:
•  First invoice
BT-23 ++ 0.1 Business process type R14 •  Subsequent invoice
•  Renewal invoice
•  Provisional invoice
•  Regulation invoice
Specification identifier as defined in EN 16931-
BT-24 ++ 1.1 Specification identifier R15
1.
A preceding invoice reference may be specified
PRECEDING INVOICE
BG-3 + 0.n  in a premium invoice, e.g. for a regulation
REFERENCE
invoice.
A preceding invoice reference may be specified
Preceding Invoice
BT-25 ++ 1.1 R16 in a premium invoice, e.g. for a regulation
reference
invoice.
A preceding invoice issue date may be
Preceding Invoice issue
BT-26 ++ 0.1 R16 specified in a premium invoice, e.g. for a
date
regulation invoice.
The Seller is either the Insurance Company if
the premium is collected by the Insurance
Company or the Insurance Intermediary if the
premium is collected by the Insurance
BG-4 + 1.1 SELLER R17
Intermediary.
All following attributes are the data of either
the Insurance Company or of the Insurance
Intermediary.
BT-27 ++ 1.1 Seller name R36 Seller name
BT-28 ++ 0.1 Seller trading name  Optionally used.
Identification of the Seller, i.e. the Insurance
BT-29 ++ 0.n Seller identifier R37
Company or the Insurance Intermediary.
If used, the identification scheme identifier
shall be chosen from the entries of the list
0.1 Scheme identifier
published by the ISO/IEC 6523-1 maintenance
agency.
Seller legal registration An identifier issued by an official registrar that
BT-30 ++ 0.1 R38
identifier identifies the Seller as a legal entity or person.
If used, the identification scheme shall be
0.1 Scheme identifier  chosen from the entries of the list published by
the ISO/IEC 6523-1 maintenance agency.
ID Level Card. Business Term Req Insurance Requirement
Tax registration identifier regarding insurance
tax.
If the Seller is an Insurance Company this is the
insurance tax identifier of the Insurance
Seller tax registration Company.
BT-32 ++ 0.1 R39
identifier If the Seller is an Insurance Intermediary this
insurance tax identifier of the Insurance
Intermediary is only required when the
intermediary transfers the insurance tax
directly to the tax authorities.
Some legislations require that the name and
insurance tax identifier of the Insurance
Company is mentioned on the invoice if the
Seller is an Insurance Intermediary.
Seller additional legal
BT-33 ++ 0.1 R40 In this case if the insurance contract is shared
information
between several Insurance Companies (i.e.
coinsurance) the names and insurance tax
identifiers of all Insurance Companies must be
mentioned on the invoice.
BT-34 ++ 0.1 Seller electronic address R41 Seller electronic address.

1.1 Scheme identifier
SELLER POSTAL
BG-5 ++ 1.1 R42 Seller postal address
ADDRESS
Seller address line 1. Usually the street name
BT-35 +++ 0.1 Seller address line 1 R42
and number or post office box.
BT-36 +++ 0.1 Seller address line 2 R42 Seller address line 2
BT-162 +++ 0.1 Seller address line 3 R42 Seller address line 3
BT-37 +++ 0.1 Seller city R42 Seller city
BT-38 +++ 0.1 Seller post code R42 Seller post code
Seller country
BT-39 +++ 0.1  Optionally used.
subdivision
BT-40 +++ 1.1 Seller country code R42 Seller country code
BG-6 ++ 0.1 SELLER CONTACT  Seller contact
Seller contact point, such as person name,
BT-41 +++ 0.1 Seller contact point R43 contact identification, department or office
identification.
Seller contact telephone
BT-42 +++ 0.1 R44 Seller contact telephone number
number
Seller contact email
BT-43 +++ 0.1 R45 Seller contact email address
address
ID Level Card. Business Term Req Insurance Requirement
The Buyer is the Premium Payer who is
normally, but not in all cases, the Insurance
BG-7 + 1.1 BUYER R18 client.
All following attributes are the data of the
Premium Payer.
BT-44 ++ 1.1 Buyer name R46 Buyer name
BT-45 ++ 0.1 Buyer trading name  Optionally used.
BT-46 ++ 0.1 Buyer identifier R47 Buyer identifier in the system of the Seller.

0.1 Scheme identifier
Buyer legal registration Optionally a Buyer legal registration identifier
BT-47 ++ 0.1 R48
identifier may be used.
0.1 Scheme identifier
BT-49 ++ 0.1 Buyer electronic address R49 Buyer electronic address.

1.1 Scheme identifier
BUYER POSTAL
BG-8 ++ 1.1 R50 Buyer postal address
ADDRESS
Buyer address line 1. Usually the street name
BT-50 +++ 0.1 Buyer address line 1 R50
and number or post office box.
BT-51 +++ 0.1 Buyer address line 2 R50 Buyer address line 2
BT-163 +++ 0.1 Buyer address line 3 R50 Buyer address line 3
BT-52 +++ 0.1 Buyer city R50 Buyer city
BT-53 +++ 0.1 Buyer post code R50 Buyer post code
Buyer country
BT-54 +++ 0.1  Optionally used.
subdivision
BT-55 +++ 1.1 Buyer country code R50 Buyer country code
BG-9 ++ 0.1 BUYER CONTACT  Buyer Contact
Buyer contact point, such as person name,
BT-56 +++ 0.1 Buyer contact point R51 contact identification, department or office
identification.
Buyer contact telephone
BT-57 +++ 0.1 R52 Buyer contact telephone number
number
Buyer contact email
BT-58 +++ 0.1 R53 Buyer contact email address
address
BG-10 + 0.1 PAYEE  Optionally used if factoring is used.
BT-59 ++ 1.1 Payee name  Optionally used if factoring is used.
BT-60 ++ 0.1 Payee identifier  Optionally used if factoring is used.
ID Level Card. Business Term Req Insurance Requirement
0.1 Scheme identifier  Optionally used if factoring is used.
Payee legal registration
BT-61 ++ 0.1  Optionally used if factoring is used.
identifier
0.1 Scheme identifier
If the Premium Payer is different from the
DELIVERY
BG-13 + 0.1 R19 Insurance Client this data group provides the
INFORMATION
name of the Insurance Client.
BT-70 ++ 0.1 Deliver to party name R19 Party name of the Insurance Client.
BG-14 ++ 0.1 INVOICING PERIOD R20 Invoicing period
Invoicing period start
BT-73 +++ 0.1 R20 Invoicing period start date.
date
BT-74 +++ 0.1 Invoicing period end date R20 Invoicin
...