...
Much focus on "technical" aspects (standards, formats) from the buyers. Better to let the service provider offer solutions and focus on benefits
Invoice issuing system often have bad data quality or rudimentary structured data - this can be a challange when creating the e-invoice which requires high level of structure data
Extension will create problems and cause unnessary cost, if they become common
Important that service providers takes responsibility about interoperability and to explain to their customers that "customized implementations" and specific requirements (extensions, CIUS) comes with a cost related to interoperability and onboarding
XSLT for transformation from CII to UBL would be great to have and it would be implemented if it has good enough quality
Negative invoice is seen as a problem. In Sweden, CreditNotes have always been used for crediting.
The PEPPOL CIUS is a step forward, the documentation looks very good. An improvement to existing documentation for PEPPOL BIS and Svefaktura
It is often not the technical aspects that halts/limits e-Invoice adoption, it is lack of knowledge (on the buyer/seller side)
Implementation can be a problem for some ERP systems
Some thinks that very few extensions and CIUS will be used in Sweden (as PEPPOL is/will be mandates for public sector)
To much focus on eInvoice is taking away the focus on the whole procurment process (catalogue, order, delivery). This has traditionally been important in Sweden but lately, only invoice.
More trainings will be necessary
Invoice Response message is important and should be prioritized
Those who have invested in PDF-only solutions will have big issues next year with the new law
Validation rules should be multi-lingual
Pictures from the workshop
...