Interconnection of Service Providers - Ahti Allikas & Jari Salo

ELECTRONIC INVOICES & COMPLIANCE

TG5 – Framework for emerging network infrastructure of invoice operators throughout Europe

CEN/ISSS WORKSHOP eInvoicing Phase 2

18.06.2009, Brussels

©2005 CEN – all rights reserved

© 2008 CEN – all rights reserved 22/06/2009

2

Group Members

Ahti Allikas (Chair)

Jari Salo (Tech. ed.)

Francis Berthomieu

Maria Jesús Garcia Martin

Guido Colonnelli

Sören Lennartson

Oliver van der Linden

Peter Potgieser

Franco Ruggieri

Heli Salmi

Giso Schoder

Christian Tanner

Vito Umberto Vavalli

Lothar Winkelbauer

eInvoicing & Compliance



3

Agenda

Introduction of working group 5

Why interconnectivity is important?

Topics in scope and topics out of scope

Topics covered

To Be Done




6

Why Interconnectivity is important?

0

200

400

600

800

1000

1200

1400

2005 2006 2007 2008 2009(estim.)

B2B e-invoices (millions)Participants (thousands)

Source: E-Invoicing / E-Billing in Europe (Bruno Koch, Billentis, February 2009)




7

Topics in scope

B2B eInvoicing and operator functions

Exchange of eInvoices between the operators

eInvoice addressing

Promote standards, recommendations and good practices

General legal issues, taxation, signatures and archiving




8

Topics out of scope

Commercial models between operators

VAT issues

Legal issues for eInvoice content

Core components and other technical specifications

Recommendations on technical solutions




9

Pre-assumptions

one or many interoperable infrastructures (independent from

individual customers)

at least two members in each infrastructure

3 … n corner models are possible

suppliers and buyers can join the infrastructure as one-stop

shopping

no need for additional agreement between supplier and buyer




10

Topics covered, CWA content #1

Interoperability framework

Interconnection scenarios

Operator criteria

Interoperability agreement between operators

Data interchange

Routing (address)

Message confirmation

Conversion challengesConversion scenarios

Common format for eInvoice

Minimum information content




11

Message in envelope

Original (e)Invoice

Signature/Authentification

Archiving

Converging the TG5 approach with EEI group Standards and

Networking stream


Topics covered, CWA content #2



12

eInvoicing Address Registry

Addressing schemes

Minimum data content for address registry

basic security measures

Certification Centres

Other third party services

Archiving of eInvoices

Workflow management


Thrid Party Services, CWA content #3



13eInvoicing & Compliance

Supplier Customer

Operator Operator

OriginalInvoice

OriginalInvoice

FormatA inhouse Dataformat C

Datafromat D

Signed Format B

Dataformat D+ Format B

IS

Signed Format BSigned Format B

-Format B can be a data file (usually there is no need for format C, D etc), pre-assumption is that Supplier and Buyer can both recognize Format B, operator acts as a transmitter

-Format B can be an image file (usually Format D is used for processing), operator acts as a transmitter and converter

Use case for pan-European e-invoicing



14

Creation of conformance criteria for interoperability across

eBusiness networks and services

Uniform and simple rules for original invoice (authenticity & integrity)

… and to have that all in practise!


To Be Done



15

For more information, please contact:

TG5 chairAhti Allikas

[email protected] +372 6519 000GSM +372 5276 676

TG5 expertJari Salo

[email protected]

Phone +358 9 4763 0303GSM +358 43 820 0936

Jari Salo, TIEKE, 2008

Interconnection of Service Providers - Ahti Allikas & Jari Salo

Business

Transcript of Interconnection of Service Providers - Ahti Allikas & Jari Salo