Embed Size (px)
Citation preview
Public
EU Norm and e-invoicing
in EuropeLIKTA workshop on eInvoicing
in the framework of annual conference
Riga, 07.12.2017
Tapani Turunen
Tieto, Value Networks
Public
Internet of Business
projectParticipants: ITL, Omniva AS, Telema
AS, Tiesto Estonia AS, Tieto Finland
Oy, LIKTAImplement EU Norm support for local practices
X-Road connectivity
PEPPOL access points
Public
AgendaIntroduction
EU Norm contents, impact and scope
Concepts: Semantic model – syntax –
syntax binding
Business processes, rules, code sets
Infrastructure
Some reflections
PEPPOL Basics
© Tieto Corporation
Public
Mindset and objectives makes the
difference
Standardization can be enablerfor new opportunities and efficiency improvements but it don’t guarantee them
Make right questions what youwant to achieve
4
© Tieto Corporation
Public
EU Norm for e-invoicing
5
European
Parliament
EU Directive
2014/55/EU
EU Commission
Order for
Standard
from CEN
CEN
Founded
TC-434
Call for
First Plenary
EU Norm
Published
In Official
Journal
EU Norm
In use for
central
government
EU Norm
In use for
local
government
17.10.2017 17.4.2019 17.4.20208.4.2015 23.5.201416.4.2014
Directive
defined date
27.11.2018
© Tieto Corporation
Public
Eurooppa NORM:n contents
6
Mandatory syntaxes are: ISO/IEC 19845 (UBL 2.1) and UN/CEFACT XML Cross
Industry Invoice D16B Notice! Both have to be supported
© Tieto Corporation
Public
Impact and scope
• Ensure that companiescan invoice their Public sector customersaccording the EU Norm
• Ensure that Public sectororganization capable to receive EU Norm invoices
7
EU Norm is targeted for B2G/B2B e-invoicing
Consumer invoicing has not been in the scope
What is the ambition level in the country?
Competitiveness
Regulated
© Tieto Corporation
Public
EU standard – strong gearing impact
• When public sector buyers shall be capable to process e-invoices they start to require e-invoices
• Public sector share of B2B e-invoices is around 18-20% that means e-invoicing usage rapid increase
• Corporates have to apply EU standard format towards public sector buyers and they start to use same format also between corporates
• SME adaption of e-invoicing shall also increase
8
Regulation Standard Usage
© Tieto Corporation
Public
What does EU Norm define
• Main part of the Norm is Semantic model
• Semantic model defines business processes, rules, terms, concepts, code sets, cardinalities, occurencies
• It also defines “must support” syntaxes
• Semantic model is not a message specification
• Syntax binding is the concrete implementation of the semantic model in a specific syntax
• Semantic model can be presented for example in UBL 2.1 as a one profile
• In this case
• UBL 2.1 is the syntax
• EU Norm in UBL 2.1 as a profile is syntax binding
9
EU Norm is the Reference Model
© Tieto Corporation
Public
Supported business processes
• Invoicing of deliveries of goods and services against purchase orders, based on a contract;
• Invoicing deliveries of goods and services based on a contract;
• Invoicing the delivery of an incidental purchase order;
• Pre-payment;
• Spot payment;
• Payment in advance of delivery;
• Invoices with references to a despatch advice;
• Invoices with references to a despatch advice and a receiving advice;
• Credit notes or invoices with negative amounts, issued for a variety of reasons including the return of empty packaging;
• Corrective invoicing (cancellation/correction of an invoice);
• Partial and final invoicing;
• Self billing.
10
EU Norm basis: Support for basic Purchase-to-pay process
© Tieto Corporation
Public
Rules
• Integrity related• An Invoice shall have an
Invoice number …
• Conditions• Each Invoice line shall be
categorized with an Invoiced item VAT category code …
• VAT related• In a document level
allowance where the Invoice item VAT category code is “Standard rated” the Invoiced item VAT rate shall be greater than zero…
11
Semantic model consists large number of specific rules
To answer the question ”Is your invoice EU Norm compliant?”
It is not enough to have required elements in place
© Tieto Corporation
Public
Code sets
• Code sets define thepossible values for numberof elements
• Currency representation
• Party identification
• Unit of measures
• Country identification
• Etc.
12
Code set specifications have deep impact on ERP implementation
For example currently Latvia has only one code set listed in ISO-6523 for
trading party identification – Latvian VAT Number (ISO 6523 code: 9939)
© Tieto Corporation
Public
Infrastructure
• EU Norm does not mandate anyspecific infrastructure to be used
• Part 4 consists of guidelines for interoperability and integrity in transmission level
• Main stream in Europe is in service provider networks and their interoperability
• PEPPOL usage and reach shallincrease
• There will be differentinfrastructures in use in• Countries
• Industries
• Commercial
• However, one can expectthat interoperabilitybetween differentinfrastructures will increase
13
© Tieto Corporation
Public
Acquiring relevant information
• EU Norm documentsavailable from localStandardizationorganization: https://www.lvs.lv/
• EU/INEA/CEF
Connecting Europe Facility
https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/CEF+Digital+Home
• CEN standards have a price
• EU does support E-invoicing deployment byfunding
• Lot of information and tools
14
Public
Some reflections
15
© Tieto Corporation
Public
Some figures in Europe
• European E-invoicing Service Providers Association reported for 2016:• Over 1.6 billion invoices
transferred
• 34% Growth in B2B/B2G invoices
• 20% Growth in B2C invoices
https://eespa.eu/eespa-aggregated-2016-volume-survey/
• PEPPOL infrastructure is growing:• Access Points from 18
countries
• 16 in European countries
• USA and Canda
• Access Points 151
• Authorities in 8 countries
• Monthly volumes in Norway over 5 milliontransactions
16
© Tieto Corporation
Public
17
Multiple
orders
Multiple
deliveries Consumer
invoicing
Current
practices
Other
regulation
GDPR
Data
privacy
VAT
Existing
investments
E-receipts
© Tieto Corporation
Public
OpenPEPPOL governance
• Secretary General is Andre Hoddevik (DIFI-Norway)
• Post Award CoordinatingCommunity is managing E-invoice matters
19
© Tieto Corporation
Public
Agreement structure• Service providers can act in Access
Point and SMP roles
• OpenPEPPOL can have Authorities(like DIFI in Norway, DIGST in Denmark etc.) that manage in theirdomain agreements with AP and SMP
• OpenPEPPOL association can havedirectly agreement with AP and SMP provider when local authority don’texist
• Multi-lateral agreement; when signingAccess Point agreement then AP is committed to communicate with allother Access Points
20
Open
PEPPOL
Domain
Authority
SMP Access
Point
© Tieto Corporation
Public
PEPPOL Infrastructure
• PEPPOL infrastructure = eDelivery Network
• Main components• Access Point – connects
trading parties into network
• SMP – directory of servicesand capabilities
• SML – address directory
21
© Tieto Corporation
Public
Service provider role
• Access Point provider• Transport interface to end
customers
• Message support for endcustomers
• Interface to address directory
• Interface to service/capabilitydirectory
• Peppol authorities mayhave own domain specificrequirements for Access points
• SMP provider• End user access point
information
• Description of messagesupport
• Send and Receive capability
• End customer can bedescribed only in one SMP
• Peppol authorities mayhave own domain specificrequirements for SMP providers
22
© Tieto Corporation
Public
Example: Tieto architecture for
PEPPOL implementation• Trading parties SMP are registered in SML (Service Locator). The SML is an
centralized service provided in the PEPPOL network.
• Each trading party data is available only one SMP
• Request to SML provides as response SMP in which tradingparty data is published
• SMP provides service and used AP for trading party
• AP (access point) implements the AS/2connectivity and message transport between APs.
SMP
SML
Tieto Hub
AP
1
2
3
SMPSMP
messages APAP
AP
1 Directory of trading parties and connection into SMP
2 Directory of trading party AP and supported services
3 AP transport trading partry messages to/from other AP
© Tieto Corporation
Public
Different options for implementation
• Develop from scratch own AP and SMP usingOpenPEPPOL specifications
• Use opensource packages• For Access Point
• For SMP
• Act ”virtual” Access Point/SMP• Use As a Service options
© Tieto Corporation
Public
Some useful data sources
• Service Metadata Publisher:
• CIPA SMP https://joinup.ec.europa.eu/software/cipaedelivery/home
• DIFI SMP, https://vefa.difi.no/peppol/tools/elma-production/
• Galaxy Gateway SMP, www.galaxygw.com
• phoss-SMP, https://github.com/phax/peppol-smp-server
• Access Points (AS2)
• CIPA AP, https://joinup.ec.europa.eu/software/cipaedelivery/home
• Oxalis, https://github.com/difi/oxalis
• Galaxy Gateway AP, www.galaxygw.com
• PH-AP, https://github.com/phax/as2-peppol-server, https://github.com/phax/as2-peppol-client
• PEPPOL Directory: http://directory.peppol.eu/public
25
Current Drummond Group AS2 certified implementations:
Company Name Product Name Optional Profiles Tested
Axway
Axway B2Bi 2.1 / Axway
Interchange 5.12 / Axway
Activator 5.12
MA, FN, FN-MA, CEM, Chunked Transfer Encoding (CTE),
Reliability, Restart, SHA-2
Axway Axway Gateway 6.15 FN
AxwayAxway SecureTransport
5.3
Axway
TradeSync Integration
Manager (TSIM) Version
3.9
MA, FN, FN-MA,FN-MDN
Cleo
Cleo Harmony™ v5.2 /
Cleo VLTrader® v5.2 /
Cleo LexiCom® v5.2
MA, FN, FN-MA, CEM, FN-MDN, Chunked Transfer Encoding
(CTE), Reliability, Restart, SHA-2
Dell Boomi AtomSphere April 2015
E2openE2 Cloud Connectivity
v6.1
MA, FN, FN‐MA, FN‐MDN, Chunked Transfer Encoding (CTE),
Reliability, Restart, SHA‐ 2
EXTOL International, Inc.EXTOL Secure Exchange
(ESX) v5.5.3FN, FN-MDN
Hewlett-Packard
Company
ELIT AS2 Connector
v4.19 with AS2API v1.7
Engine
FN, Chunked Transfer Encoding (CTE), SHA-2
IBMIBM DataPower Gateway
V7.1MA, FN, FN-MA, Chunked Transfer Encoding (CTE), SHA-2
IBMIBM® Sterling Information
Broker® 5.4
JSCAPE LLC JSCAPE MFT Server 9.1
MuleSoft, Inc.MuleSoft Anypoint B2B –
AS2 Connector 2.0
RSSBus Connect v4.0
© Tieto Corporation
Public
PEPPOL BIS v3• PEPPOL have executed gap analysis between current
PEPPOL Bis v2 and EN semantic model
• Gap analysis document
• PEPPOL will develop new version for PEPPOL Bis; notavailable yet
• Need to follow also how UN/CEFACT syntax will besupported
26
