Tg 4 Adrian Mueller Cen 18 06 2009

eInvoicing Workshop Meeting
Brussels, 18 June 2009

CEN WORKSHOP eInvoicing
Phase 2 Taskgroup 4
Final Report
Anders Grangard, GS1 International
Adrian Mueller, Expert Task Group 4

Task Group 4:

Emerging technologies and
business processes

eInvoicing Workshop Public Meeting
Brussels, 18 June 2009 ©2005 CEN – all rights reserved 2
© 2008 CEN – all rights reserved 22/06/2009

Members:
Anders Grangard (GS 1 International),
Andrea Caccia (Innovery),
Francis Berthomieu (Orange FT Group),
Otto Mueller (Dr. Otto Mueller Consulting),
Klaus Foerderer (GS1 Germany),
Wolfgang Eckert (Deutsche Post),
Peter Potgieser (ABN Amro),
Erwann Revolt (Orange FT Group),
Dirk Weidenbach (xft)
Expert:
Adrian Mueller (Dr. Otto Mueller Consulting)


Task Group 4: The main objectives
Main objectives are based on the CEN/ISSS Phase II
business plan:
Implementation of compliant electronic invoice systems
in using emerging technologies and business processes;
this will include issues such as:
- assessment of business processes, i.e. b-2-b trading
platforms.
Identification of new and emerging technologies with
potential impact on electronic invoices and related
business processes

“Yesterday’s papers”

Different perceptions of what a “new” technology /
process is
Might be well established for a big market player – but
new to an SME
Usage of a technology/process in new context
Promising new technologies and processes arise
frequently
Comply with legal regulations, market environment
Describe specific technologies/processes: Danger of
lagging behind, republishing “yesterday’s papers”

CWA is about:

Methodology
Categorising and assessing new technologies and
processes
By scheming and explaining a four-layered
framework for this categorisation and assessment:
Semantics
Interaction Models
Processes
Technology


CWA is about (cont.):

Give guidance upon applying the framework for the
assessment of emerging technologies and
processes
Demonstrating this with examples
Existing work is referenced and quoted
(CWA 15582, e-Invoicing Compliance Guidelines, …)
– not reinventing the wheel


Framework

Semantics Semantics:
Common basis for communication,
terms and definitions
Interaction Models Interaction Models:
Parties involved (Bilateral, 3- or 4-
Corner Model)
Processes Processes:
Process (steps) and components

Technology Technologies:
Specific implementations


Framework: Semantics

Common basis for understanding
Between experts in different areas: legal, financial,
technical, …
Proper / common usage of terms
Sample list of terms and their definitions provided as
annex in the document


Framework: Interaction Models

High level business view on how sellers and buyers
organise the transfer of invoices and the exchange
of related documents
Number of involved parties
Models:
Bilateral model (with different flavours)
3-corner model
4-corner model (also multi-corner model)


Framework: Processes

Process as such is eInvoicing, i.e. traditional billing
or self-billing with electronic means
Composed of different process steps:
operational components of the process
Functional modules
“Atomic” building blocks Business Process

Same functional module can
be contained in different Process Steps

process steps
Functional Modules


Framework: Technology

Specific technologies
Nuts and bolts
Serve to implement the functional modules and the
process steps of the processes layer


Guidance for assessment

Pragmatic
Low learning curve
Six main steps for technologies / processes
Compare with the four layers of framework
Plus
Decision
Implementation / Adaptation


Guidance for assessment (cont.)

Bottom-up approach: Step into lower layers first
Discussing examples:
Technology: Communication specification AS2
Processes: Adaptation of Registered E-Mail as business
process to eInvoicing

Tool for getting a quick overview how a new
technology/process can be utilised or
adapted to eInvoicing


Example assessment

Example chosen is AS2 Semantics

(Applicability Statement 2)
AS2 is a specification for
Interaction Models
reliable transportation of
data over HTTP
“New” or “old” technology Processes

depends of context
Technology


Example assessment (cont.)

1. Technology: AS2 specified in IETF RFC 4130
2. Processes:
2.1 Functional modules:
Communication, Authentication, Integrity
2.2 Process steps:
First mile
Send
Receipt and technical verification
Last mile
include functional modules identified in 2.1
benefit from AS2


Example assessment (cont.)

3. Interaction models:
AS2 can be applied within all models (2,3,4-corner)
4. Semantics:
Terms and definitions of AS2-RFC in line with list of
definitions (sample in Annex A)
5. Possible decision:
Service provider implements AS2 for first / last mile
6. Implementation:
Consider e-Invoicing Compliance Guidelines for
process steps first / last mile

Questions?


Tg 4 Adrian Mueller Cen 18 06 2009

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Ähnlich wie Tg 4 Adrian Mueller Cen 18 06 2009

Ähnlich wie Tg 4 Adrian Mueller Cen 18 06 2009 (20)

Mehr von Friso de Jong

Mehr von Friso de Jong (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Tg 4 Adrian Mueller Cen 18 06 2009