Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

#ModulesYour choice
1Introduction to eInvoicing x
2The legal background
3The European norm and its content x
4Infrastructure based on the eDelivery DSI architecture x
5eInvoicing from a user perspective (including ordering and payments)
6Examples of early adopters of large scale eInvoicing – lessons learned
7Basic XML using examples from the EN-syntaxes + mapping/conversion considerationsx
8XML Validation mechanisms
9Understanding OASIS UBL 2.1 x
10Understanding UN/CEFACT CII D16Bx
11Funding and grants for e-Invoicing x
12Introduction to the eInvoice DSI resources and tools
13Introduction to CEF Digital and e-Invoice readiness checker

Participants feedback

...



Questions to/from the audience

QuestionResponseNo of feedback etcAction

Do you have a profile at CEF Digital?

Asked later just before the coffee break - only 1 has an account on CEF Digital

Did not ask due to timing

Do you see other areas where trainings or webinars could be of interest?

Did not ask due to timing

The European standard requires a very high level of information quality. Can this prove to be a challenge in your coming implementation?
  • Mainly technical validation - schemas
  • The problem could be that there is so many versions of how an invoice should be structured
  • The end-user might not even need the level of detail and the high level of data quality in the invoice itself
  • The approach is the only one - now we have a chance to use one standard and update what we have


2-3 participants
Validation is a central function in the European standard. Are the service providers ready for the technology?In Sweden when where not all service providers have full control of the user input in the invoice this can cause interruption to the invoice processOnly speaker input
CIUS – benefits and challenges, what is your opinion?

A Finnish CIUS is being prepared by the Tax authorities in Finland. The exact scope is unknown to the public yet.

In Sweden the CIUS will be a replica of the PEPPOL profile - in other words not very restricted. Same situation in Norway and Denmark.

There is a long list of codes which really isn't useful for the wider majority

Do not restrict your CIUS too much since it will be a burden to your interoperability both nationally and internationally

1 participant and speakers
Two formats – do you see this as primarily an opportunity or a challenge?

In payment industry only one is working and that was just the case...

What about versioning?

  • It has not been fully structured yet how to apply this - take PEPPOL as an example where they follow their own set of rules for life cycle management and this works. But we haven't seen the full landscape yet on how this will be applied.
  • There is a mechanism on how to update a standard where a committee decides how the new version should be.

It can be very difficult to update the standards once implemented - that is a drawback



Is CEF eDelivery/PEPPOL relevant for you?Some service providers are connected to PEPPOL.

Has anyone here applied earlier or intending to do so in this years call?No

What is your estimate for creating and implementing a CIUS?At the CEF Digital website there is a wiki with a list of CIUS projects where you can find very good help on how national legislation can affect the CIUS and cross-border transactions of eInvoicingQuestion from audience - answer from speakers
How many are connected to PEPPOL

(Question raised by the speaker)

3 participants

Service Providers
Are there acknowledgments between access points?Yes, the transport protocols (AS2/AS4) always acknowledge receipt. OpenPEPPOL is also developing an Invoice Response Message which can be used by the buyer to inform the seller that for example the order reference is incorrect.

Where can we find code list ISO 6523 and code list for Exemption reason code for VAT?No answer given in the workshop. Martin Forsberg will follow up.


Presentation

The presentation can be found here:

View file
nameHelsinki_Workshop_Final.pdf
height250