1. CEN ELECTRONIC INVOICES – OPEN MEETING
December 12th 2011
MUG - 'Core' Cross Industry Invoice European
Message Implementation Guideline – CWA 16356
Ulrike Linde
Agenda
 MUG project
 Deliverables of the MUG project
 Possible next steps
2005 CEN – all rights reserved
1

2. MUG project organisation
 Project Leader
 Bernard Longhi
 Steering Committee
 eInvoicing3 Anders Grangard, Ulrike Linde
 BII2 Jostein Frömyr, Bergthor Skulason
 eBES Bernard Longhi, Nicolas Botton
 Secretariat Tim Kniep, NEN
 CCMC Alain Dechamps
 Editors team
 Georg Birgisson
 Kevin Smith, Michel Entat
2005 CEN – all rights reserved
MUG project experts
 Antonio Conte  Ole Madson
(Commission observer)  Wolfgang Matt
 Isabelle Desmeytere  Tim Mcgrath
 Michael Dill  Tony Nisbett
 Edmund Gray  Peter Potgieser
 Markus Gudmundsson  Sue Probert
 Marc Hemmerling  Aurelie Virgilie
 Dirk Hill  Jörg Walther
2005 CEN – all rights reserved
2

3. Deliverables of the MUG project
 CWA 16356 "Guide for a European CORE
INVOICE data model with UN/CEFACT CII
Implementation Guideline“ September 2011
 Part 1: Introduction
 Part 2: European CORE INVOICE data model
 Part 3: European CORE INVOICE syntax mapping
 The MUG project was common to 3 CEN
Workshops: BII, eBES and eInvoicing 3
http://www.cen.eu/cen/sectors/sectors/ISSS/Activity/pages/mug.aspx
2005 CEN – all rights reserved
CWA 16356 Part 1:
Introduction - Scope
 The MUG core invoice
 provides for data and business rules that can
support business requirements of companies and
organizations within the European Union and EEA
(B2B and B2G)
 supports the subset of information that is used by
most or all industries
(CROSS INDUSTRY invoicing)
 does not support data that is specific to a
particular industry
 does not aim to provide support for data that may
be required in regions other than European Union
and EEA
 enables both VAT and non-VAT invoicing
2005 CEN – all rights reserved
3

4. CWA 16356 Part 2:
European CORE INVOICE data model
 The objective of part two is to specify the content
of a core invoice
 This is achieved through the following steps:
 The scope of the core invoice is specified.
 Common business process related to invoices are
identified and described
 Business process that fall within the scope are identified
 Data and business rules that are required to support the
relevant business processes are specified
 BII01 core invoice and Expert group report
annex 7 were used as key input along with other
documents from the participating workshops
2005 CEN – all rights reserved
Data model comparision
 UN/CEFACT Cross Industry Invoice (CII)
D09B XML Schema
 EEI Experts Group Report Annex 7
 BII01
 ISO 20022 financial invoice message
 Cross border porposal by Edmund Gray and
Sue Probert
2005 CEN – all rights reserved
4

5. CWA 16356 Part 3: European CORE
INVOICE syntax mapping
 Requirements Mapping (XPaths for Data Elements
identified in CWA 16356 Part 2)
 XML Example ‘Walkthrough’
 Complete Example Core Invoice XML Instance
 Identifier Schemes and Code Lists
 Annexes
 XPaths Table Spreadsheet
 XML Schema Pack including instance file, XSL style sheet and
CSS files
 HTML view of XML instance (which is created using the XSL
and CSS files. XSL and CSS files can be modified for
implementer’s own requirements)
 Code Lists Spreadsheet
 DRAFT CCTS 3.0/NDR 3.0 version of Core Invoice
(informative)
2005 CEN – all rights reserved
Possible next steps
 Documenting the mapping of the different
UN/CEFACT CII „dialects“ (auto-gration, GS1,
ISO 20022 financial invoice message) to the
MUG-Format
 Definition of extensions and decision taking,
which extensions are registered for which
application domain (i.e. national extensions
for e-Procurement)
 Establishment of a change management
process for accepting, editing and adopting
change requests to the MUG deliverables
 Publication of current versions of the MUG
deliverables including the apporiate XML
schemata
2005 CEN – all rights reserved
5