Table of Contents
Summary
Contact point | Tadeusz Rudnicki - Tadeusz.Rudnicki@ilim.poznan.pl (Institute of Logistics and Warehousing (Standard/Solution development)) Sebastian Christow - Sebastian.Christow@mr.gov.pl |
Date | 27th Nov 2017 |
Venue | The workshop venue address: Pl. Trzech Krzyży 3/5 |
Room capacity | |
Target audience (and expected number of attendees) | 50 expected - 34 actual |
Content and topics to be covered
Please comment on the table below to let us know your preferable module session. Feel free to comment on specific topics you would like to see covered, so we can adapt the module session according to the target audience needs and expectations.
# | Modules | Your choice |
---|---|---|
1 | Introduction to eInvoicing | |
2 | The legal background | |
3 | The European norm and its content | X |
4 | Infrastructure based on the eDelivery DSI architecture | X |
5 | eInvoicing from a user perspective (including ordering and payments) | X |
6 | Examples of early adopters of large scale eInvoicing – lessons learned | |
7 | Basic XML using examples from the EN-syntaxes + mapping/conversion considerations | X |
8 | XML Validation mechanisms | X |
9 | Understanding OASIS UBL 2.1 | X |
10 | Understanding UN/CEFACT CII D16B | X |
11 | Funding and grants for e-Invoicing | |
12 | Introduction to the eInvoice DSI resources and tools | X |
13 | Introduction to CEF Digital and e-Invoice readiness checker |
Agenda
11:00 Welcome & Introduction to CEF eInvoicing and our services
A few words on the Directive on electronic invoicing in public procurement eInvoicing from a user’s perspective
The development of the European standard
12:30 Coffee break
Key concept of the standard UBL / CII & Conversion issues
Interoperability and validation
14:20 Lunch break
Usage specifications and compliance
Infrastructure (eDelivery) in coherence with CEF eInvoicing
Discussion
17:00 Close
Communication channels
Name | Channel (e.g. LinkedIn group, internal network, news platform, Twitter...) | Target audience | Content to be shared | Date |
---|---|---|---|---|
Questions
Question (Audience/Speaker) | Answer (Audience/Speaker) | Notes | Actions |
---|---|---|---|
How many from public sector | 60% | ||
Private sector | 40% | ||
Service provider | 30% | ||
Knowledge about eInvoicing | 80% | ||
Knowledge about CEF | 10% | ||
Knowledge about the EN | 0% | ||
Do you have a CEF Digital profile? | 1 participant | ||
Other topics that would be of interest (webinars) | - | ||
Straight through processing - how does it relate to public procurement - this could be an issue to have automatic approval processes in some administrations? | It depends on the country and its legal constraints - in Sweden there is a cap/limit on how much the invoice can be at for an automatic approval. Then there is the problem of electronic signatures - in some countries like Sweden we dont have that in place, it is enough with the electronic signing on the serverside. | ||
How many here have heard about PEPPOL and the four corner model? | 6-7 participants | ||
In Poland is work process for automated invoices support already in place? | A few participants thinks it has to be done before the directive goes into place | ||
Which format for eInvoicing are being used here in Poland today - EANCOM / EDIFACT we know. | Some XML formats are used but not widely | ||
The European Standard requires a lot of information and high quality - is the a problem? | Yes, some participants agrees to this | ||
Two formats for eInvoicing - do you think this is a good option or not? | Mainly participants think this should only be one format | ||
Validation is a central part of the standard - is the service providers ready for this in Poland? | YES! Broad agreement to this | ||
How is the public authorities in the different member states coping with more standards? | In general we hear that most authorities will continue to support more than one standard eg their own national standard and this new standard | ||
What do you think about the CIUS? Good thing or pandoras box? | There is a risk if everybody does their "own thing" and most will probably do, it will put an impediment to the wider adoption and interoperability of the standard. | ||