Versions Compared

Key

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

...

More than 20 participants on site and more than 50 participants online through YouTube across sectors of industry, banking, public authorities and standardisations mainly from Finnish market. 

Questions to/from the audience

...

Do you have a profile at CEF Digital?

...

Did not ask due to timing

...

Did not ask due to timing

...

  • 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

...

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

...


YouTube video of workshop


Presentation

View file
nameHelsinki 2019 WS_MF_CVR.pdf
height250


Pictures from the workshop

...

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

...

(Question raised by the speaker)

3 participants

...

Image AddedImage AddedImage AddedImage AddedImage Added