Here, you can share your questions, ideas, experiences and best practiceson eInvoicing policy.
It is your turn to speak out to shape the future of eInvoicing!
Your contributions will provide the key inputs for coming policy discussions.
How to contribute?
Scroll down to reach the "comment section" of the page
Click on the square "Write a comment" (written in English or in the language selected in your setting)
Write your comment and click on "Save"
Your comment will appear automatically in the list
How to reply to a comment?
Scroll down to reach the "comment section" of the page to see the other members' comments appearing
Click on the "Reply" button (written in English or in the language selected in your setting) corresponding to the comment to which you would like to react
Write your comment and click on "Save"
Your comment will appear automatically in the list and the author of the initial comment will receive a notification
Many work groups, organisations, at national and international level including mirror committees etc... are in place where often the same people discuss sometimes partly overlapping but also sometimes the same topics. This creates often confusion for the outside world (read the market). Maybe time from a policy perspective to reflect on this and optimize our time and effort. Just a thought.
Thanks Paul SIMONSfor your comment! If you have any additional information or hyperlinks to access this on-going work of these groups/ organisations, we would be happy to have a look and cooperate.
The main obstacle to generalizing eInvoicing is the insufficient interoperability between the many systems involved in the invoicing processes. This situation makes wide-scale automation of the invoice processing overly complex and, consequently, unaffordable. Although it derives from many intertwined legal, semantic and connectivity factors, the main factor is that fragmentation provides operators with a protection of their market share. It can also become a source of revenues, that they quite legitimately are inclined to reinforce. In this business context, the markets are not likely to reduce the fragmentation unless an external factor modifies the situation.
Directive 2014/55/EU creates the opportunity (but no obligation) for the private sector to extend their outbound eInvoicing to the public sector, if they adopt the EN. This policy decision certainly contributes to the growth of the market. It also provides a standard for cross-sectors invoicing, which is key to the defragmentation. However it will not suffice to overcome the commercial drivers against interoperability.
The Peppol interoperability framework provides the ingredients to standardize the landscape and thereby reduce the fragmentation, while safeguarding fair competition and innovation. However, as explained above, since defragmentation jeopardizes their business model, we might expect many operators to be reluctant to comply with the framework. Additionally, eInvoicing and EDI traditionally operate in sectoral silos, so their main customers (mainly corporate segment) are generally not suffering from the lack of interoperability, so they are not likely to motivate their service providers to reconsider their business model. In this context, mandating compliance with Peppol should be an option to consider for the policy makers. Additionally, such mandate would be the way to let all actors upgrade their systems in synch. This would minimize the total costs of the upgrade, help the fair sharing of the upgrade costs, and eliminate speculation in the market.
Another option for policy makers, is to mandate the use of a central exchange platform. This strategy obviously speeds up eInvoicing generalization. However, it also eliminates competition, which affects the expected cost savings. Additionally, it brings the fragmentation at the cross-borders level. Those two aspects do not fit in the European single market strategy. Additionally this approach is not scalable.
In conclusion, mandating compliance with Peppol should be carefully considered, for it overcomes the risk of additional cross-borders fragmentation, and limits the market effects that complicate interoperability, without impairing fair competition and associated cost savings for our economy and benefits for our governments. Mandating at European level would be consistent with the rest of the European program in favor of eInvoicing and the digital single market.
Having worked as an EDI service provider for longer than forever, I have experienced many facets of this specialist business activity. I think that Peppol has a lot going for it and is a more advanced open architecture than traditional EDI networks. Now that the Peppol infrastructure is largely in place, it would be good to see it utilised more. This needs to be driven by policy - EU leadership please!
Peppol service providers are passionate solution providers that get the dream of a single connected digital market. It is frustrating that political follow-through is not proactively in place. Peppol is scalable and deep in capability.
The e-invoicing directive was a great step forward for EU B2G. It has potential but not momentum.
Where is the political commitment to leverage Peppol and the e-invoicing directive? Where are the signals to the market?
Food for thoughts: Mandatory digitization and standardization of business electronic communication in all sectors and business relations
Directive 2014/55 / EU imposes on Purchasing Authorities (PA) the obligation to the reception of e-invoices complying with the European Norm (EN). The implementation of this obligation required preparation (including financial expenses) on the PA’s side. However, there was no obligation to issue such e-invoices by Suppliers. Thus, if no Supplier in public contract sends e-invoices compliant with the EN to the PA, then the expenditure on implementing the Directive’s obligation will not pay off and the planned benefits from the implementation of the PA’s obligations will not be achieved.
The implementation of Directive 2014/55 / EU resulted in a limited appearance of IT solutions using EN as a result of demand from PA's.
Suppliers already use e-invoicing solutions to some extent in B2B relation, however these are solutions in other than directive’ standards or often non-standardised at all. The implementation of solutions dedicated only to B2G transactions is inefficient for business when using other solutions in B2B relation. Making B2G e-invoicing mandatory is also often seen as imposing new obligations on business, what most governments want to avoid due to fear of losing political support. However, these fears contradict the expectations and beliefs formulated in the preamble to Directive 2014/55 / EU, concerning the proven benefits of e-invoicing in business, exceeding the costs of its implementation and maintenance by business entities.
Currently, one of the most important reasons for business reluctance to implement e-invoicing is the fact that the IT industry (IT system providers) is defending itself against standardization because it believes that its non-standardized system protects their interests (Serge Libert mentions this). It is more difficult for a user of non-standardized solutions to change their IT system because it is impossible to replace a non-standard IT system without incurring large costs of change. However, this approach of IT companies is wrong, standardization may widen the market for them because the business will be more willing to invest in proven and standardized systems. However, the IT industry does not acknowledge this.
The large number of non-interoperable electronic data exchange standards offered on the market is the reason for their low level of application. In this case, the competition rules do not work in the sense that this competition does not meet the needs of the market and even eliminates these needs. So this is an example of an anomaly caused by a lack of cooperation in the IT sector.
The IT sector should follow the very competitive telecom industry, which uses common standards for all equipment manufacturers and operators, without which the mobile telecom market would be much shallower. There are technical standards required for many industries, the purpose of which is to promote access to certain goods for all users. An example is technical standards for transport routes and standards required in the construction of means of communication (trains, buses, trams, cars), which allows users adapted to these standards to safely and effectively use these goods.
Is the narrowly understood interest of individual IT companies in avoidance of IT standardization of higher value than the social interest of accessing standardized, secure and effective methods of business communication? Are non-standardized (often not fully disclosed to users) communication solutions safe for their users? Such solutions often remain outside social control, but they can easily be a tool of hidden, unlawful control over the user.
It is necessary to consider introducing consumer and business protection measures in the form of legal requirements for IT system and service providers, including standardization and certification requirements for particularly sensitive business processes and the protection of consumers' rights or interests. Such protection measures should be mandatory, however, protecting the public interest, they should not unnecessarily narrow the creative potential of the IT industry (i.e. they should mainly protect users against illegal activities).
Food for thoughts: Real-time tax reporting & e-invoicing
Many countries implement electronic tax reporting systems within their countries, several countries have built their system based on the SAF-T standard ("an international standard for the electronic exchange of reliable accounting data from organizations to a national tax authority" defined by the OECD ). This standard is different from the e-invoicing standards used e.g. in EDI or in public deliveries in the EU. These systems are becoming mandatory for VAT payers.
The application of separate standards of the tax reporting process and the e-invoicing process constitutes for the taxpayers an increased cost of operating these systems, which is not making taxpayers happy.
The elimination of independent handling of e-invoicing and tax reporting systems and discrepancies arising between them requires the integration of both processes. This integration has a technical dimension (
see 'technical - tax reporting & e-invoicing') and tax and ultimately economic through more effective reporting (see 'economy - tax reporting & e-invoicing').
Achieving full tax control through the mechanisms of reporting data from invoices is possible only by becoming the electronic invoicing of all business transactions mandatory, i.e. invoices in B2G, G2B, B2B and B2C relations.
Whilst I believe that the vision of the European Commission for realisation of an ultra-competitive single digital market has made tangible progress and that the e-invoicing directive is a significant pillar achievement (only mandated across the entire public sector less than 2 months ago), there remains more policy work ahead.
European enterprises are served by more than 10,000 software companies in the EU (https://www.crunchbase.com/hub/european-union-software-companies). The software industry is vitally important to the European economy besides being dynamic and responsive to the needs of a very diverse portfolio of customers. I would suggest that we need to look beyond the self-interests of software companies to explain why we are not there yet.
Getting there represents a major challenge and will require a multi-faceted coordinated approach. It would be great to see further evidence that member states and their public sector agents really appreciate the strategic contribution they can make to the future digitisation of the European economy. There is a lot to play for and the potential rewards are mouth-wateringly attractive. SMEs can be incentivised in many ways to go digital. Practical steps would be to reward them with faster payment cycles (lower debtor days) when dealing with the public sector and with large corporates. SME working capital costs can be reduced significantly by trending back towards the old cash on delivery business model and these savings will more than compensate for any increased IT costs.
Awareness building and education are also very important.
E Invoicing monitoring (from a statistic and eInvoicing adoption analysis point of view) at the B2G and B2B levels is a topic that isn't clearly stated in the eInvoicing Directive. Also enlarging the monitoring scope to fraud prevention and cyber security.
Monitoring is a contentious topic...and it's important to be clear on why it is desired, and what will the data be used for, and by whom.
In a B2G context, the government side will always know about 1 side of the transaction, and from there should be able to infer the sender side. They also know the actual levels of electronic vs manual trade, so should be able to infer the trends. I dont think the Directive has any reason to legislate for this kind of monitoring.
Regarding fraud prevention and cybersecurity, these are 2 very different dimensions which do overlap with usage, but I for me these are more BAU operational things that any business must plan for. Business Controls in an eInvoicing world are not less important than in snail mail , fax or email.
Cybersecurity is already a key feature of existing einvoicing infrastructure, and some countries like Singapore have introduced deeper KYC requirements that must be met before registering Peppol IDs. I'm not sure where is the gap you would want to address in the Directive?
First, it must be said that a lot has been done already. We have a Semantic Norm which is now implemented in most public entities in Europe on reception, with only 2 syntaxes (+EDIFACT), with more and more EU Members making it mandatory on the sending side.
We have CEF e-delivery Building Blocks, which should help to solve the delivery and discovery layers of interoperability, implemented thanks to Access Points which are mainly Service Providers.
We have made reports, especially on interoperability, identifying what need to be improved, but also regarding the impact of the diversity of Clearance / CTC / Realtime tax report for companies.
CT434 has identified a list of Amendments to the EN16931, necessary to address most of what was forgotten, especially to address most B2B business cases.
Some EU countries have started to implement a mandate for B2B invoices.
On the payment side, ERPB has worked on Request to Pay messages (including enrollment and validation).
But, there is about 25% of electronic invoices, and only 40% in a full structured form, 60% simple PDF (study deloitte, 2018). We may try to understand why. It is certainly more because it is easier especially for SMEs to provide it than because of lack of interoperability between SPs. And the fact that most SPs have developed solutions to handle PDF invoices is also a sign that it fits a need.
The Covid-19 shows that paper invoices are really difficult to process when people are not at the office and more and more companies and Shared Service Centers are asking for e-invoices (PDF or structured invoice, filled on Buyer’s portals).
It is certainly time to accelerate e-invoice deployment and more generally supply chain e-documents and data, at least for B2B in addition to B2G (and why not anticipating B2C).
There is then an urgency to set up a task force and a few resources (compared to what will be provided to face the economic crisis) in order to:
Finish the job on the EN16931 with amendments within the end of THIS 2020 year (making sure that we will not face an IPR issue again), in order to support the B2B mandates prepared in many EU Members.
Harmonize the CTC / Clearance obligation in EU, with pragmatism, at least by giving guidance in collaboration with TAXUD, harmonizing the mandatory e-invoice information to be sent to Tax administrations on a realtime basis if needed, and if possible, reduce the orchestration options to the 3 main observed (CTC, Clearance with previous approval, Clearance with previous approval and sending), without jeopardizing the existing e-invoice exchanges.
Integrate REALLY the SMEs needs and constraints in our thought. Currently, solutions are built around large companies’ needs (Buyer-centric / Vendor-centric, and more generally “application-centric”), pushing constraints to their suppliers or clients and then multiplying the procedures, the portals, the follow up means to get status information on e-invoice treatment process or just to get the invoices for supplier-centric solutions. Onboarding SMEs implies simplicity and added value for them also, including payment acceleration, which means certainly to switch data / document / global supply chain transaction centric and extend 4-corner model to business status exchange / sharing:
As SMEs mainly use PDF, hybrid documents is certainly an easier first step than moving to full structured (and especially while the EN16931 cannot handle all specific business cases). This must be developed as a complement to full structured documents in order to replace at least the Paper and simple PDF invoices rapidly with a core set of data necessary for automation (and potentially for CTC / Clearance).
SME’s also need information on e-invoice process : implementing Invoice Message Response through 4-corner model is certainly a must. It could become an obligation at least for the first status (invoice received and compliant).
For addressing and rooting, most working groups on interoperability already recommend the use of CEF e-delivery building blocks, and national platforms may also play a role in certain countries as a complement. This should be taken in account also, but there is no need to force a specific implementation.
Support pilots and experimentations on transaction-centric solutions, with DLT, blockchain, smart-documents sharing, … including new payment solutions.
Following interoperability report, and complementary initiatives like the GIF (Global Interoperability Framework) or the FNFE-MPE Interoperability Charter, define guidance on interoperability, including CTC / Clearance obligation, to be recommended to service providers, solution editors and national platforms.
A lot have been done, but a lot still need to be done to reach 100% of e-invoices (Directive 2006/2010 definition), for B2B and B2G at least.
Thank you Cyrille SAUTEREAU for your comment and status on on-going eInvoicing projects. Your points related to (1) a standard creation for clearance and tax reporting and (2) mandating eInvoicing for B2B/B2C transactions enrich the ideas mentioned by Tadeusz RUDNICKI .
Linking eInvoicing to payments is indeed part of digital procurement innovations. This would require (among other aspects) the involvement of new stakeholders such as credit institutions.
Today, the EC works on enhancing SMEs involvement in digital projects. One of the on-going initiatives is the SME Digital innovation challenges encouraging SMEs to re-use CEF building block in their activities (eInvoicing and eDelivery included).”
I did not exactly request an global e-invoicing Mandate for B2B/B2C as it remains a decision of each Member State in the rhythm and perimeter they want, but I think that when they want to implement it, this should be done in a coordinated and aligned way in order to make it simple for end users. Globally, each EU Member State faces the same issues and solutions should be found among a very restricted list of scenarios.
Regarding SMEs, I do think that they represent the challenge to reach a critical mass as they send and receive more than 50% of invoices, and are dealing mainly with paper or simple PDF. A program for SME Digital Innovation is a good thing to get pioneers, but for the large majority of SMEs, CEF e-delivery is far from their day to day and knowledge. They need simplicity and continuity in their business process : send invoices from their sales management solutions with the structured information they manage (with no obligation to redesign deeply their information system), follow the process through e-invoice status response, get paid or refinanced easily and faster, ... I think we should take in account the fact that simple PDF is developing faster than full structured invoice. Our conclusion is that we need hybrid documents to fill the gap. The use of CEF building blocks is more the matter of solution providers than final users, and needs to be used under an interoperability governance which guarantees the freedom of choice of solution or solution provider for SMEs.
Regarding payments, ERPB is currently working on Request to Pay messages, and Enrollment and Activation messages and procedures (participating to KYS / KYC normal obligations). This could also be part of the solution. Coordination would be necessary. Same with upstream working groups and standardisation on procurement (order to delivery).
There are a number of tools available to the public sector to drive e-invoicing adoption by SMEs.
1) It would not be a big deal for public sector bodies to begin to use the invoice level response message (e.g. as already defined in Peppol Billing process for business interoperability processing). This would provide a standardised responsive means for suppliers to remain informed on invoice processing progress.
2) Public sector bodies could start sending standardised purchase order messages (e.g. as already defined in Peppol ordering process for business interoperability processing).
3) Incentivise SME supplier by promising faster payment. Australia got this straightaway as a powerful tool by committinng to 5 day payment rather than current 26 days
4) Signal that mandating in B2G is on the horizon (12 months or longer)
5) Signalling that e-invoicing will be adapted for B2B.
6) Signal a commitment to Peppol which is very open, robust, scalable and well managed. I just had a look at the Peppol website. My estimate is that there are 286 certified Peppol access point providers. Most support AS4. I don't get the policy reticence. The openness of Peppol certainly doesn't favour the Peppol access point providers - supply far outweighs demand and my understanding of economics suggests that this situation cannot prevail as is. If there is market demand then this will drive supply.
In summary, my view is that the public sector needs to become more proactive and take advantage of this opportunity that it has helped create but now doesn't seem to want to feed. Perhaps I just don't get politics
If you look at what has happened in France, we have a mandate for B2G sending and receiving. We have a Platform ChorusPro which have already processed more than 100 millions invoices for Public Sector (and private on the sending side). Peppol is connected but most of the invoices are centralized directly in ChorusPro (including via Service Providers which are Peppol access Point but are connected outside Peppol which does not bring added value for this). More than 550 000 private companies are connected and referenced (directly and / or through Service Providers). Hybrid invoices are allowed or PDF + data extraction approved by the suppliers (which come to the same result). ChorusPro gives a "definite exchange date" to the supplier, which is the start for payment delay (with an impact on it). Different Status messages through API are provided. B2B mandate is in preparation. Globally it is all your points except the last one : it is done without Peppol. On the same time, it only represents less than 5% of B2B/B2G invoices. And B2B e-invoices are currently exchanged through EDI solutions or Service Providers' platform, outside Peppol also, with much more unstructured PDF form (increasing rapidly) than full structured (especially from or to SMEs).
It does not mean that Peppol can not play a role for interoperability and adoption, but it shows that this is not the only solution for success, and it would be also a signal to understand why it is not used so widely : governance, dependent of Service Providers which are most of the Peppol Access Points with potential flows and are interconnecting directly (and maybe there is also a governance issue there !), absence of invoice status response (it is just starting, which is a good thing), absence of Enrollment / Activation process (governance again, invoice and more generally supply chain business exchange should be bidirectional with mutual acceptation, which means with a capability for Corner 1 and 4 to decide if they want to exchange documents via Peppol, and same for Corner 2 and 3, for compliance reason for instance. Open doesn't mean absence of control by end users).
Peppol is an implementation of CEF e-delivery Building Blocks, with specific rules in each Peppol Authority area (including on invoice format). It is an interesting option, but there are alternatives and other solutions already in place. It has also to be taken in consideration.
Chorus Pro is a success for France. We have customers that are suppliers to French public sector and we connect them to Chorus Pro. We also connect these customers to Swedish public sector bodies via Peppol and to American public sector bodies through other networks.
We have helped major buyer entities build portals (functionally equivalent to Chorus Pro) that are functionally rich and can be rolled out quickly to drive adoption.
All these efforts create silos of e-trading activity. I thought that the European Commission was interested in creating a single digital market across Europe and that this had the support of Member States.
(Disclosure: I am not involved in running of Peppol and can't comment on the politics and governance at the highest levels although our company is a service provider member).
It may be interesting to note the research findings into "What is it that makes a platform successful?"
There are three suggestions from Boncheck and Choudary (2013); Connection, Gravity, and Flow. Bonchek, M., & Choudary, S. P. (2013). ‘Three elements of a successful platform strategy’. Harvard Business Review, 92(1–2)
It is important that new suppliers and customers can easily make contact with the platform
The platform must be attractive to customers and suppliers so as to build critical mass around the product or service in question
The platform must make it convenient and cheap for consumers and suppliers to interact
At this stage in the development of sizable public sector initiatives (e.g. PEPPOL, CEF) it would be beneficial if the Commission could reiterate the challenges these and other initiatives are designed to overcome. Whilst some of the challenges are well within the public sector domain and therefore quite obviously translate to policy objectives, others stem from defined instances of market failure which can be demonstrated based on objective data and analysis. It would be helpful for the Commission to restate these specific instances and the policy objectives it has derived from it; based on this summary, it will be easier to define success criteria and measure economic impact on undertaken actions. Such reiteration of the policy objectives would make the whole debate more effective and transparent, and more easily supported by all stakeholders, as it would clarify what we are trying to achieve. A couple of examples:
There are several discussions in this EU policy arena around new technologies such as block-chain – before debating whether such technologies should be taken into account in public policy and other governmental initiatives, we need to understand what technologies are used and function today and what problems would be better solved (or objectives met) with new or emerging technologies.
SME-SME invoicing is presumably an example of ‘market failure’ where e-invoicing is not working in a smooth and automated manner, and where it would be good with a clear policy objective to amend this situation.
Various forms of Continuous Transaction Controls have in the last couple of years made its entrance in the EU. While it will be difficult to ensure full alignment while moving at the pace desired by Member States, the Commission must at a minimum move quickly to ensure that the regimes that are rolled out do not substantially contradict each other and as a result create a barrier to trade. One such example of clear and actionable measure to ensure a bare-minimum alignment is to recommend that ICC Practice Principles for Implementation of Continuous Transaction Controls or similar guidelines are adopted and followed.
Thank you Anna Nordén. As suggested inCyrille SAUTEREAU 'scomment and to summarise your points in view of identifying key topics for our online session: Youpoint out the need of a policy base for (1) eInvoicing adoption by SMEs and EC's onboarding activities, adapting to SMEs' needs and (2) the Continuous Transaction Controls (CTC). You mention also the lack of policy guidance in technology usage among the EU Member States (e.g. Blockchain) generating system incompatibilities.
Thanks Solene DRUGEOT for your comment. I don't think I managed to explain my thoughts clearly enough.
As regards the request for a clarification of policy objectives this is not about SME needs or technology (these were just examples), but a request that we more explicitly restate the goals of and reasons for all our exercises so that we can better define success criteria. The key concept here is to be more explicit in defining the drivers behind CEF etc activities in terms of 1) which areas of economic activity according to objective analysis or data are not optimally functioning in order to meet 2) which public policy objectives. Having a consensus around which instances of ‘market failure’ we are trying to address, and why, is always very helpful to keep projects on track and to test proposed follow-up activities against a robust standard.
The CTC bullet is a separate point, asking the Commission to keep an eye on the various initiatives in the Member States.
The European E-invoicing Service Providers Association (EESPA) looks forward to the debates and reflections on policy and designs for the future of e-invoicing, as promoted by the CEF Digital team.
EESPA now has 83 members and is very active as a community in delivering compliant e-invoicing and supply chain automation solutions. Interoperability lies at the heart of what we do and we are currently engaged in the project to embrace CEF e-Delivery to underpin our member-to-member interoperability transactions on behalf of customers. We will base this on our EESPA Model Agreements and will be using the EN 16931 as the core of our exchange standard. EESPA members currently exchange hundreds of millions of invoices to complement the transactions carried out through members’ own supplier networks.
Our members are also key participants in the OpenPEPPOL community and they also interoperate with important national infrastructures, such as Chorus Pro (France) and SdI (Italy) just to name two: a complex picture, but reflective of the diverse preferences of national communities both in the public and private sectors and the reality that no single infrastructure can address all aspects of e-invoicing. E-invoicing adoption is a ‘devil is in the detail’ activity and it is the efforts of service providers and their clients that bring these various infrastructures and many other solutions to life. The sheer diversity of clients, providers and solutions means that there are many moving parts to be navigated.
EESPA was pleased to be associated as a contributor and in an editorial capacity with the EMSFEI WG 4 paper on Interoperability and Transmission and feel that we must all work harder to deliver the vision and practices set out in that document.
Continuous Transaction Controls for VAT reporting at Member State level is a growing topic of interest and we would welcome the opportunity to debate this issue with a view to achieving more harmonization in this area based on some agreed principles. We think this can be done without compromising the objectives of tax administrations and the mandating of e-invoicing, whilst also harnessing the economic benefits of supply chain efficiency as a whole and respecting single market principles.
The policy achievements of the EU on e-invoicing are impressive and find tangible expression as the Directive 2014/55/EU and the EN 16931 which have been successfully implemented. It would be great to track progress and issues as they arise. We would like to see an acceleration of efforts in CEN/TC 434 to bring enhancements so as to support one of the original objectives of the core EN to support the wider private sector adoption of e-invoicing.
We are currently working with OpenPEPPOL and other international associations to develop a Global Interoperability Framework, which is planned to be published shortly for consultation. We would welcome the opportunity to present this to the EMSFEI. and other interested parties. Our mission is to convince promoters of interoperable frameworks (global, national, regional, sectoral) to use a common set of tools and standards, whilst leaving room for local needs and profiles.
The COVID-19 pandemic can act as a catalyst for the promotion and adoption of paperless digital processes such as e-invoicing. We should seize that opportunity.
Clarifies the targetpicture of the e-commerce value chain and in particular the e-invoice. Make sure that the benefits are highlighted from all different angles and needs, different memberstates see different benefits of the digital purchasing process, control, efficient processes, quality, security, traceability, etc. Work with the targetpicture long-term as different countries and regions have different conditions. Important to have a long-term attitude and the stability of the solution, to avoid constant changes that, for example, cause different systemsuppliers to make upgrades in their services too early or too often.
Agree. And that is why there is an urgence to work on harmonization on CTC/Clearance + Extend the EN16931 to allow its deployment for all B2B business cases + interoperability framework + invoice message response + hybrid documents, under a priority of 100% of e-invoice (directive 2006/2010 definition) taking in account first SMEs for critical mass adoption and supporting first payment acceleration, focusing on the minimum invoice data needed for process automation and tax administration to lower Vat gap.
Otherwise, solutions will be designed apart as a lot of stakeholders feel the necessity to move on fast, especially after the COVID-19 pandemic, and with more and more diversity through Member Sates, which means complexity for end users and solutions, and finally the slow adoption we face since the last years (25% of e-invoices only).
In Sweden we have had e-invoicing many years before the directive came. We started with e-procurement, the order-invoice process but many started with only e-invoicing process. According to a Swedish regulation 2008 all government agencies were mandated to receive e-invoices. For municipalities and regions there has not been any law or regulation but they started with e-invoicing early. The incentive was an efficient process and also cost effective. Due to a survey 2017 (based mainly of statistics from 2016) 87 % of the 290 municipalities and 100 % of the 20 regions had introduced e-invoicing ( structured electronic invoices, not including PDF invoices).In average 56 % of their invoices was received in structured electronic formats.
Now, after the law came into force, regulating that both governmental agencies and authorities, municipalities and regions shall receive e-invoices, e-invoicing has of course increased. And the Swedish law also stipulates that suppliers to public sector also must send e-invoices based on public procurements made after April 1, 2019.
From November 2019 it is also mandatory for contracting authorities and entities to be registered in Open Peppol and be able to receive e-invoices also via this communication. The e-invoicing standard that are recommended to be used for public sector and their suppliers is PEPPOL BIS Billing 3, since this is the e-invoice that fulfill the requirements of the European standard/ EN. The recommendation is from SFTI, a cooperation between the governmental sector and the local and regional sector. Now almost all municipalities and regions are registered in Open Peppol, but so far they still receive most of the invoices via the VAN operators network as they did before. But the interest of using Peppol is increasing. We notice it from their interest of knowing more; we frequently organize education about e-invoicing and Peppol ( both the invoice and the infrastructure).
Firstly, I would like to acknowledge the continued good work of the CEF team and the excellent contributions made in the comments in this space by my colleagues, most of which I concur with and support in terms of warranting further consideration.
On behalf of the eInvoicing Ireland team, I have provided more detail below but in summary, I think this is a good opportunity for eInvoicing stakeholders in general to:
Re-examine/re-state our Policy objectives
It is now a good time to re-examine the main objectives of the Directive and remind ourselves of the benefits and outcomes we are trying to deliver.
Identify, share and acknowledge what has been achieved
Monitoring and reporting on progress across EU member states and sharing success stories and positive developments.
Identify and manage risks and threats that have the potential to impact our ability to achieve our objectives
Focusing eInvoicing Stakeholders work on identifying and mitigating/managing risks to the Directive achieving its objectives may help us to take targeted actions that need to be taken to protect the investment made is eInvoicing by the Commission and all Member States.
(e.g. Inadequate political will or centralised supports; Availability and ease of PDF/email; Lack of support for EN in new Financial / ERP applications and implementations; Lack of joined up objectives and measures in common and related policy areas – Procurement; Tax; Digital; Green.)
Background to Ireland
The majority of invoice processing in the Irish public sector is distributed across a number of sector specific finance shared service centres. In addition to this a significant number of contracting authorities also process invoices independently. eInvoicing is not mandatory for the sender in Ireland.
For the most part, the national approach has resulted in a Peppol-based eInvoicing capability being established across the Public sector. The establishment of a European Standard and the implementation of the eInvoicing Directive across all member states is a great achievement and milestone on Europe’s Digital journey.
Shared experiences and ideas for the future of eInvoicing
However, in the absence of a mandate, there is now a challenge for Contracting Authorities to drive the uptake of European Standard eInvoicing among suppliers. This is due to a number of reasons but most commonly cited ones include:
Lack of a mandate means effort is required to convince and support suppliers to adopt EU standard eInvoicing.
Lack of awareness by suppliers of EU standard eInvoicing and related delivery channels (e.g. Peppol)
Perceived admin, technical and cost overhead for suppliers to adopt EU standard eInvoicing, in particular SMEs which will be required to establish a connection (e.g. Peppol) other than email to deliver their eInvoices.
The ubiquitous availability of PDF via email as an option for suppliers to send invoices electronically is seen as an easy option to avoid paper (as opposed to implement eInvoicing)
The option to on-board suppliers to a ‘Register with a Buyer Portal’ approach is seen as more attractive to Contracting Authorities who do not have capacity to advice, persuade and support suppliers in adopting EU standard eInvoicing.
Invoice processing for many Contracting Authorities is not provided for by Finance Shared Services centres. Many of these Contracting Authorities have very low volumes of invoices and very, very low volumes of invoices related to contracts above EU thresholds and therefore find it difficult to establish a business case for EU standard eInvoicing, other than for legal compliance.
Limited centralised supports to assist Contracting Authorities drive uptake of EU standard eInvoicing among suppliers.
For those public bodies eager to drive the uptake of eInvoicing among suppliers, there are very few if any mechanisms to them to easily identify which suppliers already have a capability for EU standard eInvoicing and therefore could be quick wins to create momentum.
In facing these challenges, some Shared Service Centres and individual Contracting Authorities are favouring the promotion of their Finance system buyer-portals and PDFs via email to drive the uptake of eInvoicing with suppliers. This has the potential to weaken or even undermine the national approach at an early stage.
Mandating the submission of eInvoices and applying eInvoicing clauses within procurement contracts are examples of measures that stakeholders regularly seek from a national approach to support the uptake of eInvoicing among suppliers.
Areas that might be considered to help the future of eInvoicing include:
Re-examine/re-state our Policy objectives
It is now a good time to re-examine the main objectives of the Directive and re-extol the benefits.
Identify and manage risks and threats that have the potential to impact our ability to achieve our objectives
(e.g. Inadequate political will or centralised supports; Availability and ease of PDF/email; Lack of support for EN in new Financial / ERP applications and implementations; Lack of joined up objectives and measures in common and related policy areas – Procurement; Tax; Digital; Green.)
Placing a strong focus on monitoring eInvoicing implementations and compliance across and within Member States will send an important signal to Public Administrations that continued compliance is necessary and may help to provide a better basis on which to drive uptake of European Standard eInvoicing among suppliers. There may be benefits to articulating any potential implications of non-compliance.
Strengthen and join-up eInvoicing’s position within eProcurement policy and establish explicit links with other related policy areas (e.g. Green). This could be in the form of providing clear guidance on how the uptake of suppliers submitting European Standard eInvoicing should be supported or possibly encouraged within Procurement competitions (e.g. should support for the EU eInvoicing standard & CEF delivery building blocks be a mandatory functional requirement for all new Financial Systems procured by EU member state Contracting Authorities). The relevance of eInvoicing to the Green deal could be explored and highlighted if appropriate.
Consider signalling eventually EU mandate for submission of eInvoices by business to Public Sector. This would provide stronger guidance on the EU’s direction of travel and help generate benefits and justify investment. After 1 year of purchasing a service and not receiving any invoices, many contracting authorities will wonder why they should continue to incur this cost. The current crisis has ensured that cost management will be very much a priority in the years ahead.
Explore ways to increase awareness among suppliers
Many suppliers are unaware of the European roadmap on eInvoicing, Peppol and the relevance of eInvoicing to their business. Sharing examples of national approaches to supporting suppliers and establishing enduring models to sustain and increase eInvoicing may be helpful in that regard. (SME Digital innovation challenges are a good example of such an initiative.
Assess in greater detail the reasons why other non-Paper options for invoice processing continue to dominate
What are the attributes of that make these other options (e.g. PDF via email) so attractive. How can similar attributes be established to enable EU standard eInvoicing – e.g. native support for the EN and CEF delivery building blocks in financial apps)
Consider Targeted engagement with key stakeholder groups beyond traditional eInvoicing forums and community
Consider targeted communications to business representative bodies, financial systems providers, accountancy bodies, finance and tax authorities as well as other policy areas such as Procurement, Tax, Digital, Green. To help provide practical and joined up guidance on what we are all aiming to achieve and identify real steps that can help to move us forward together.
Consider Digital Targets for Member States
Consider whether the application of Digital Targets (similar to Green targets) might prompt Member States to be more ambitious in taking steps to making EU Standard eInvoicing the predominant method of invoice processing. Targets would enabled the Commission to focus on outcomes rather than implementation choices such as whether to use a specific delivery network.
I support this well articulated and balanced review of eInvoicing landscape in Ireland. I think that the various recommendations have much merit.
As part of a broader communications and outreach strategy, I believe service providers would be more than willing to participate in promotional activities.
e-Invoicing is an important tool in the digitalisation of both B2G and B2B processes with the potential to deliver a considerable economic uplift.
The intrinsic value of e-invoice payload does not seem to be fully appreciated as a source of insight into economic activity.
Now that the EN directive directive in combination with the choice of Peppol for eDelivery and digital business process evolution, there is now a great opportunity to leverage these achievements to realise transformational change.
What are the attributes of that make these other options (e.g. PDF via email) so attractive : this is the key question.
For us (France, French National Forum) the main reason is simplicity and availability. An invoice can contain a lot of information, some for compliance reason to different regulation without any use for automation, some for business reason (marketing, operational details) which are first useful in case of manual process (for instance in case of dispute), some are managed by ERPs or Sales management solutions as structured data (so easy to provide in that form), some are managed as "free text".
The EN16931 was built under the constraints to fit with Public sector needs and capabilities to process them as there is an obligation to do it. To do so, we stated structurant assumptions such as 1 invoice 1 delivery 1 order, but also choices on business terms. The result is that we are missing some invoices that does not fit with the core. It is not a very big deal if we stay on an obligation to receive. It becomes more complex if we add an obligation to send as there is no solution for ALL invoices. And extension to B2B is much more complex and is the real target because B2G invoices represents only a few percent of invoices for companies.
By trying to transform all invoices in full structured invoices through the EN16931, we face at the same time the difficulty for all companies, especially SMEs, to provide all their invoices in such full structured format, and the difficulty for companies which are using additional business fields or business cases to restrain themselves to the core invoice.
In addition, using only secure exchange network like PEPPOL means a certain maturity and / or the use of 1 or many service providers to reach the different networks of counterparts.
Then, in order to stick in a full structured invoice process compliant to the EN16931, the only solution is to fill invoices manually in multitudes of Buyer's Portal, which is just a major change and a step backward for companies (including SMEs).
Apart from that, it is easy for any company to create a pdf invoice and to send it by email. And the Covid-19 pandemic showed that this way is the best and fast to handle business continuity when paper is not processable because not send or received, and when received in paper, people at home cannot process them.
It is then not a surprise that PDF invoice sent by email is so attractive, especially when SMEs are involved : Simple and available rapidly.
And this why if we want at the same time to have invoice process automation, which needs invoice data in a structured form, but not too much invoice data for simplicity and availability, and the possibility to reach rapidly 100% of paperless invoices for the benefit of all, we consider that a pragmatic solution is to propose hybrid documents as a first step to replace simple pdf. If we add most of the EN16931 Amendments proposed by CEN TC434 working group, we are close to be able to manage all business cases in B2B / B2G, with the invoice data necessary for automation. It means that we have a "playing field" sufficient to reach 100% invoices in a pdf form + a minimum mandatory information in a structured from at least useful for process automation and for Clearance / CTC needs, in addition to full structured invoices which remains the final target . On top of that, the market and the end users will have all the freedom to provide more structured information or even full structured information, and develop innovation and more added value.
Switch priorities : 100% paperless and more than 80% touchless with pragmatism, flexibility and lean process, instead of 100% full structured and finally a slow adoption.
100% paperless ahead of 100% structured sounds like a great thing, but I think it hides a few unpalatable truths...
There is a perception that pdf by email is BAU and more or less free of additional cost using existing business tools.
BUT
The sender of the invoice really only cares about getting paid (fast)(er)
If they must invest to facilitate that they will, but they dont have the insight to evaluate the choices they are being given - this is where public policy should be guiding them towards understanding choice implications.
For example the Australia plan to pay sub $1M Peppol-received invoices within 5 days can encourage and nudge as opposed to compel.
Businesses in a manual trade position today will need to make a change either way, I think it's wrong to encourage anything less than fully structured and touchless for those who can.
Unless pdf content is structured, and forced to be complete, then it will require manual administration on the receiver side, possibly return emails, phone calls, to get to completion.
Receiver side processing practice may still require printing and manual review regardless of how received.
The tools that will make a structured, rule driven compliant pdf are generally NOT free.
In cost comparison with SME-focused tools that make eg Peppol docs via webportal, or Peppol integration via SME accounting packages, the strucured pdf is not necessarily cheaper.
If you want to enjoy the full benefits of hybrid pdf as a receiver, then you need non-standard software too.
In my admittedly biased view, the beneficiary of structured pdf by email are the vendors of the software needed to make it, rather than Buyer or Seller.
We need to have a diversity of tools that help both sellers and buyers both B2G and B2B transact in a structured, touchless, frictionless way.
If public policy aligns with this - rewarding sensible choices, and if introducing CTC, then doing so in a compatible fashion, then everyone wins.
Decades of business have made a large diversity of information in invoices. Switching all this in full structured way is just a nightmare. Restricting it to a core set of data is a huge change for all companies and solutions. The challenge is to find a way to transform paper and simple pdf invoices in machine processable formats, with flexibility in order to reduce manual processing and accelerate payments. The target should be "what percentage of automation is reachable rapidly on the basis of ALL invoices and not only the ones that can be switched in full structured, and taking in account also the manual processing on the sending side and for SMEs".
With respect to Blockchain, finally there are signs of movement toward Interoperability, but I believe getting this to a BAU state is a long way off. In the meantime, Blockchains represent 3 corner models, which we're already moving past with electronic trade interoperability as embodied in Peppol, EESPA, BPC, etc.
In my view the most sensible deployment of Blockchain for the medium-term is for value-added tangential use cases, such as smart contracting, KYC verification, smart financing, permissioned sharing of data elements with external parties to name a few. For sure there is lots of room for innovation and invention there still.
I think it would be a big step backwards however if we delayed interoperability, automation of the Order through Invoice process for Blockchain to catch up, in the hope it can do something different.
I believe we'll never get to only 1 way of doing things as that would again be a market and business restriction, but doing everything different is not working and we need change.
Thank you Ger CLANCYfor this very valuable comment - I suggest to keep this conversation open and invite other commentators to share their points related to this comment on the Technical page.
Having just spent 60 hours studying blockchain (i.e. distributed ledger technology) and its various applications including cryptocurrencies as part of a Dublin City University online course, I think blockchain has great potential in specialised areas. The reality is that it is an over-hyped immature technology with relatively few commercially proven use cases.
1) Introduce the “digital by default” principle in the VAT Directive and tax legislation in general The VAT Directive originates from an age when most invoices were “analogic”, i.e. on paper or – even if electronic - not structured. Now digital (i.e. structured) invoices should be considered the normality (also because it's straightforward to transform a structured invoice in a human readable one when needed, but not the opposite). A “digital by default” principle should overcome the equal treatment principle, introduced in the last revision of the VAT Directive. Continuous Transaction Controls (CTC) are effective ways to fight tax frauds and were made possible thanks to digitalization. Their use should be encouraged however fragmentation of requirements on the data that is requested by tax authorities to the business operators creates burdens especially for SMEs and – consequently – obstacles to the single market. Common standards should be defined and their support mandated to tax authorities, to avoid unjustified burdens on economic operators. EN 16931 can be the basis to define the information needed for CTC and standardized ways to extract automatically from EN 16931 based invoices (or direct use of invoices) can greatly simplify the task. The development of an European standard for B2C invoices has been recently approved by CEN/TC 434 and its availability can extend to B2C the same concepts. EN 16931 was possible thanks to the existence of a harmonized legal framework, the VAT Directive. The development of the standard put also the light on some national level specificities that still exist after 50 years of legislative efforts at European level, reflected in CIUS and Extensions that have been developed: they should be analysed and the result fed back to the policy level to improve harmonization and support “digital by default” principle. To achieve this, EMSFEI should liaise with the VAT expert group to give to TAXUD the proper inputs. These initiatives are expected to further greatly promote the use of structured e-invoicing in the private sector.
2) Extend Directive 55/2014 to include the transmission level To further increase the adoption of Directive 55, the support of a baseline standard at the transmission level should be made mandatory for public authorities to receive invoices. This can be easily extended to support full digitalization of the supply chain documents. The CEF eDelivery building block and Peppol (that is spreading not only in Europe but also internationally) should be the technical basis, provided that they are fully based on international standards and compliance with eIDAS Regulation requirements guaranteed.
3) Systematic and reinforced use of international and European standards The standardization system is global and the use of standards is of paramount importance for fair competition, it should be avoided that the European enterprises are regulated outside Europe. Many European initiatives such as Peppol are kept in high consideration outside Europe and – when relevant – standards developed in Europe should find their way in the international context. The standardization framework is addressed at policy level by the EU Regulation 1025/2012. In this framework the IPR issues should addressed to find a viable and definitive solution, taking into account that any obstacle to the use of standards create in the medium and long term additional costs
Andrea CACCIA I agree wholeheartedly there needs to be alignment, harmonization or at least recognition of mutual interests dependencies between the VAT Directive and eInvoicing legislation, especially taking the impact on the invoice issuer / taxpayer into account.
The worst possible outcome would see each country coming up with non-interoperanble, incompatible CTC pathways, "because they can" despite the standardisation of the Order - Invoicing flows. The taxation policymakers may not know nor care about the invoice flow standardisation, and without proper education (ie from EU / Member states), then they may easily take a deliberately different approach.
On the baseline transmission in 55/2014 I also agree in general, but there are depandencies here. For example Portugal is using PT-CIUS as a payload, which is structually derived from EN, and not very far from Peppol BIS. For transport, they will use individual AS2 connections and not use Peppol network at all. In order to register a divergent doc type in the Peppol network, it must be sponsored + managed via a country-level Peppol Authority, and if there is no PA, then its not possible.
Therefore if Portugal wanted to send /receive their docs in Peppol today, they cannot.
Until there is a way of getting national requirements reflected into and supported by the eDelivery / Interoperability Network especially if there is not a Peppol Authority, then there is a risk of fragmentation in spite of the Directive.
Lastly, the IP approach to the EN was poor, and was not supportive to desires to extend the EU standards globally. Not running into this situation in future should be foundational to any changes to current policy.
Just to clarify better the concept of baseline transmission, it needs to be further developed of course but the basic idea is on one hand to recognize what is already used but on the other hand to avoid to introduce a general obligation to use Peppol. I mean that there should be some baseline protocol that is guaranteed to be available, like today public authorities must guarantee to accept EN 16931 invoices expressed in one of the 2 syntaxes. For example AS4 is the same technology used for Peppol but implementing it does not necessairly means to use Peppol.
Agreed. For example, in Germany federal government is saying XRechnung (German Peppol variant) to be delivered via Peppol, whereas some federal states have only made email delivery possible for the XRechnung. Or in Italy, we have lots of clients receiving orders and sending despatch advices in Peppol for several years, but its crazy that the Invoice must be in a different doc format, and using a different network. In their own individual bubbles, all of those individual things maybe make sense, but from a supplier perspective having to naviigate all of them is horrible.
I know there is work afoot in Italy to converge Peppol + SDI for Invoices, but I'd rather try to avoid such situations cropping up at all if possible.
"… to avoid to introduce a general obligation …". I agree that obligations must be avoided in all possible ways, for they often lead to distortions in the market. As my main background is economist, market efficiency is the focus of my contribution to the debate. A lot has been written on the topic. In this literature however, even the most liberal thinkers agree that regulation is also essential to market efficiency. The problem is to define the right policy. In the present case, as I tried to articulate in my first comment, the drivers in the market lead to a severe market inefficiency. The industry cannot be blamed for this. The customers cannot be blamed for this. Nor are these groups responsible to articulate the response. The situation requires a more global approach than the actors in these groups can be asked to have. With directive 2014/55 the policy makers agreed to mandate semantic interoperability to a group of customers (the governments of Europe). So obligation is not tabou. The question is what obligation will unlock the current obstacles to a wider automation of the supply chain operations (where the invoice plays a central role).
When discussing Peppol, the main problem is that it is too often narrowed down to the transmission aspects. your comment gives this impression. Peppol indeed addresses the transmission, but it also addresses semantic, legal and organizational aspects, in line with the European Interoperability framework (EIF). That gives him the unique attribute: comprehensiveness. As I and many others stressed, the obstacles derive from a combination of intertwined complexity factors. To my best knowledge, Peppol provides the best response to this. It provides flexibility, scalability (both in size and functions), balanced collaboration/competition. It gives all stakeholders (industry, customers and policy makers) a voice in the agora that is required to meet and align. Peppol is far from perfection. But it keeps improving. This is probably the most disrupting, and thereby misunderstood aspect of Peppol. The improvement derives from the constant combination of the 3 main stakeholders in joined efforts. Organizing this constant interaction, overcoming the conflicts, is indeed a big challenge. It requires a lot of vision and willingness to understand the others point of view. After 5 years of practice, I can only confirm that it is not a walk in the park, but it works! This leads to a shift in the market where, as Ger stressed, Peppol only creates a framework for all IT-players to compete fairly and deploy their innovation without breaking interoperability. Also countries can keep supporting their local markets and specificities within the framework., thereby avoiding fragmentation and associated costs for the IT industry and their customers. For all these reasons, I suggest policy makers to consider mandating Peppol. The obligation is needed to synchronize actors, and thereby minimize and fairly share the costs that the alignment to this common framework will involve. The current urgency to move away from paper creates a unique context to have the right debate about this and seize the right opportunities together.
Peppol has developed very significantly since its inception as a large scale European project in 2008 with a big pan European public procurement vision. This vision includes e-invoicing and much more. It is still not the finished products but it ticks many more boxes than any other prevailing ecosystems I'm aware of. If anything, it is too heavily biased towards the interests of the public sector.
The technical architects behind it are seasoned business interoperability practitioners and the governance structure looks right albeit that it is over represented by Scandinavian public sector - but that will change and is changing. Germany is now taking Peppol seriously and will exert an accelerating EU market adoption influence.
The government of Singapore, Australia and New Zealand have recognised what the EU has achieved.
Europe is demonstrating leadership in many areas (e.g. standards, PSD2, GDPR, SEPA, instant payments, e-invoicing and even Peppol), It's not often that Europe gets a head start on USA in terms of software technology, it would be great to support the European software providers in our home market to help create scaling opportunities.
@Serge : create a mandate to use Peppol as THE interoperability framework is too late as there are already alternatives in place with significant flows. In addition, it would be close to be monopolistic, concentrating innovation on very few hands, which creates huge governance issues. In addition, it is not yet so idealistic and improvements are needed : it remains juxtaposition of networks with specificities on formats or business rules per region, it does not handle bi-directionnal exchanges (which mutual acceptance and control of end users through the network => see the work made by ERPB on Enrollment and Activation), it is built on CEF e-delivery which is the disruptive technology and can be implemented separately with another governance. In addition, I think that paper is about to be replaced by PDF first (and exchanged via email in addition !! the nightmare of IT/EDI experts!). It has to be taken in consideration also in the big picture of interoperability / Clearance / CTC / SMEs adoption, in order to bring pragmatic solutions and added value for ALL.
On the same time, I agree with Ken's last sentence. Europe is demonstrating leadership in this area, and we should be careful not to jeopardize it. I think it should be done more by improving what needs to be improved in order to build "natural adoption" and "shared added value" that trying to force the use of Peppol as is with mandates.
Agree, and that is why we need to promote solutions and Standards to replace simple PDFs, with the more structured information possible, taking in account SMEs capabilities and without forcing them to fill invoices manually on Buyer's portals or complete invoice information extracted from their simple PDF invoices.
Cyrille SAUTEREAU What we're talking about is replacing an unstructured pdf that a business can make for free with bau tools, with a structured pdf that in most cases they'll need to buy new software to make.
The productivity benefit (if there is one) will maybe be on the receiver side, or it may just perpetuate manual handling on both ends, but add cost. I cannot agree that this is a logical first step on a path towards automation, other in very specific cases. The primary beneficiary is the software vendor.
Re Peppol, I fully agree that its B2G history brings limitations for widescale B2B application (so far), but Peppol is now driving a lot of interest among businesses globally, and including for B2B applications.
I believe this will be a driver for innovation and increased demand, which will in turn drive innovation and demand. I dont see a great difference between a government mandate to use Peppol, and a B2B relationship requiring a specific format, but the interoperability of the Peppol / CEF model is the way forward, and for me perpetuating pdf of any kind is the equivalent of a step backwards.
Ger CLANCY I have the feeling to repeat constantly myself. Let's try another way. SMEs are using sales solutions (and for most of them, it is word or excel) that are NOT dealing with ALL invoice information as data. It means that that use free text for part of the information and structured data for other. All this finish on paper or PDF. Creating an hybrid document with the data available is not a big deal for solutions (even excel can do it if necessary, or Libreoffice, ...), but create a full structured invoice means changing for a solution than can do it. And, for your information, SAP, IBM, ... are no the only solutions or affordable for every SME. Then there is 3 solutions:
decide that an invoice is only composed with current mandatory fields (and it is already too much), with no additional requirements available, so that SMEs can step in rapidly => not realistic
decide that all companies MUST be able to manage more than 100 business term in an invoice => there you loose SMEs for years or you force them to finish on portals
find another solution based on what is available as data for majority of SMEs (and sales software solutions dedicated to this market) + what they are used to provide on a semi-manual process, with a focus on mandatory invoice data for what is needed for process automation. This will simplify all business rules or extra data (including some legal fields) which need to be present for compliance or in case of manual process. The real question : as it is complex for SMEs to provide all invoice information as structured data, and as only a few are necessary for process automation, why should it be forgotten to think about a more pragmatic approach. The current consequence is still a lot of paper and the simple PDF (which growing fast and faster than structured with the Cavid-19.
I think it is important to prioritize the target : paperless and the more automation and find the solution for it, than prioritize the solutions : full structured and Peppol for all and observe the results.
Thank you for these reactions. Let me clarify some points
1/ The main point of my suggestion is not Peppol. It is the market failure that we face, caused by the increasing fragmentation on the market and the subsequent lack of level playing field. in fine, it drives the enterprises to use a suboptimal technology( pdf/email). As I also mentioned in my initial comment, this situation also leads many national policy makers to the decision of installing and mandating national platforms - most of the times with a B2G scope (up to now only Italy went beyond that scope). In the absence of a suitable solution on the market , national policy makers have not much other options than to copy the model used by large private buyers in the past. Unfortunately, each new implementation keeps increasing the market fragmentation. 10 years ago, the paper “ Reaping the benefits of e-invoicing in Europe ” already warned us of the fatal long-term consequences of these national strategies on the growth of eInvoicing and, more generally, on the Digital Single Market.
No wide scale adoption of eInvoicing is possible in this situation, so overcoming that situation is the top priority of all of us (policy makers, industry, and their customers). Is there another framework than Peppol better suited for this? Or a combination? I trust that the policy makers will be able to make a well informed decision here.
2/ The disruptive character of Peppol is not technological, it is organizational – its ability to let policy makers, users and service providers meet and align. Peppol is aligned with the European Interoperability Framework (EIF – formerly known as European Interoperability Reference Architecture - EIRA), it encompasses legal, organizational, semantic and technical aspects of interoperability. The interaction between stakeholders is mainly addressed in the legal and organizational layers. The organizational layer provides the flexibility that is needed to cope with the reality of eInvoicing: a complex, evolutive endeavor.
3/ Peppol is a project that took place several years before the CEF program was launched so it cannot really be narrowed down to an implementation of CEF components. On the other hand, due to its ability to address change, it adopted the EN in its semantic layer, and CEF e-Delivery specifications in its technical layer - almost seamlessly. (And I agree that CEF e-Delivery also significantly feeds interoperability )
4/ Regarding your comment on the possible monopolistic character of Peppol, as Ken mentioned there are 286 Access Points, most of them are service providers. It rather looks like it stimulates competition, as it is mentioned in its statutes. Additionally, as I tried to articulate, the vision of Peppol is not to concentrate innovation, but on the contrary to help building the level playing field that is required for accelerating technological break-through. All service providers are free to offer whatever features and added value as long as they don’t jeopardize interoperability.
I hope these clarifications help better situate my suggestions.
Sharing the EESPA Executive Committee's message to the Market...
Covid-19 and the urgency of adopting paperless supply chain automation to accelerate payments to cash-strapped small suppliers
Today’s circumstances demand radical action to keep the wheels of commerce turning and supply chains delivering. For this to happen there must be timely electronic invoicing, and certainty and acceleration of payments, especially to small suppliers.
Never have the arguments been so persuasive for removing paper and its replacement by safe and reliable digital processes for e-business and automated supply chains. There is current evidence of delays to invoice processing caused by remote working and the logistical handling of paper-based documents. Current dislocations act as a catalyst to digitize, as we will live with these new conditions for some time to come. E-invoicing provides full legal and commercial certainty, and is easy to use. Tools for its implementation are in common use. Service providers are a major influence on the stimulation of e-invoicing volumes.
As a trade association, EESPA represents 83 e-invoicing and supply chain automation specialists operating throughout Europe and beyond. A 2018 statistical survey among a group of EESPA members reported an annual volume of nearly 2 billion invoices. With recent growth trends, we estimate that our community is now handling an annual volume of over 3 billion invoices. We have members located near all business enterprises and they are willing to talk and demonstrate solutions.
Digital service providers play a key role in capturing and exchanging transactions generated from multiple clients in many diverse sectors. The result is the delivery of tangible benefits to the trading eco-system through:
Digitizing Purchase-to-Pay (P2P) and Order-to-Cash (O2C) processes. Service providers can directly help businesses and public administrations and their suppliers, to reduce costs, increase efficiency and improve data quality and transparency. By delivering accurate and timely data, service providers help businesses make better decisions and eliminate the need for re-keying and data cleansing projects, whilst reducing cost and the risks of dislocation. Time to payment can be radically improved. Both larger economic enterprises and small and medium-sized businesses receive such benefits as does society through enhanced performance and competitiveness.
Removing trade and frictional barriers through the dematerialization of the entire chain of e-business transaction types exchanged between trading parties. These include purchase orders, logistics, invoices, and many other business documents. Service providers can connect businesses irrespective of their technical capabilities and act as trusted intermediaries that enable private sector enterprises and public administrations to transact easily, securely and transparently with each other. Buyers and suppliers can reap the benefits of electronic procurement and invoicing, efficient on-boarding to access digital services, and improvement in the certainty and timeliness of payments.
Through facilitating open data exchange, transactional data can be conveyed seamlessly between trading parties and their chosen service providers. With global reach we enable a trading environment with many fewer barriers. When working together as a community, it should be emphasized that there is a commitment to streamlining service provider collaboration to accelerate true interoperability and to make the on-boarding and activation of clients even smoother and more transparent, within the scope of client preferences and mandates. Service providers fuel the transaction flow through interoperable infrastructures such as the EESPA Model Interoperability Agreements, PEPPOL, and many national delivery networks, such as Chorus Pro in France and Sistema di Interscambio (SdI)in Italy. Member States use a variety of delivery networks and infrastructures for e-invoicing and related transactions. EESPA is engaged in many projects to enhance the smooth running of these infrastructures based on ‘state of the art’ tools and standards.
Value-added lies in the delivery processes and applications for the benefit of clients, not simply in the transport of transaction data; pure delivery of data can already work in a frictionless manner based on the technologies of the Internet. The real value proposition goes further and offers: end-to-end reach and interoperability, fiscal and contractual compliance, high automation levels, improved security and integrity, data validation and transformation, analytics and spend visibility, traceability, and potentially supply chain financing. Many businesses suffer from poor data quality, which impedes progress towards more powerful management controls, higher customer and supplier satisfaction, and better government reporting; indeed poor data quality often results from supply chains using an incompatible mix of both paper and digital processes.
Service providers are working closely with governments to eradicate business, technical and other barriers to digital processing. They support the digital policies of the European Union to automate the procurement activities of all public administrations in all Member States, as well as in the private sector. They play a key role supporting the central role of invoicing in generating tax revenues and supporting tax reporting processes. With a growing emphasis on ‘continuous transaction controls’ for VAT reporting at individual Member State level , service providers are closely engaged in helping their customers to navigate through the widely differing demands of such systems. By being at the forefront of digitization they generally make a key contribution to business, societal and environmental benefits, which lie at the heart of public policy in this area.
Many commercial enterprises and public administrations have some experience of digital processes in the supply chain. The real benefits come with critical mass and the ability to quickly respond to changing circumstances with agility and focus, including urgent situations. Service providers can discuss scale adoption as well as targeted programs to meet challenges in specific situations using well-targeted messages and case studies.
Please think about taking action today to protect trading integrity and create a valuable platform for the future.
Some contribution into discussion from Finnish idealism point of view.
I like to start with some experience. In Finland our Central Government is able get about 90% of their purchase invoices in structured format. I have opinion that level is not an outcome from any specific infrastructure. It have reached through service providers and banks interoperability network where banks network is multilateral and non-bank service providers work on bilateral connection basis. Saying this I don’t argue at all that this level of usage could not be reached with other infrastructure frameworks as well. I don’t believe that thinking that one size fits all is the best possible approach.
One factor for high e-invoicing usage in Finland is that infrastructure and practice covers different segments B2B/B2G/B2C. It is very often that invoice issuers don’t send invoices only to one segment customers, but they have customers in all segments. It is very efficient for the issuer that they can use one and same infrastructure and invoice distribution method for all their customer segments.
Consumer invoicing might be one of the very important directions in EU to further enhance e-invoicing practice. Addressing is another important topic to concentrate more. ISO-6523 maintenance seems not working best possible way. Neither does CEF EAS code list look very robust including large number of arbitrary PEPPOL addresses.
Local – Global
Efficient public sector is really important. However, I don’t believe that public sector is the key driver for Europe competitiveness and success. Main thing is how our corporates are competitive in Global market. EU level standardization is very important and help our corporates to be competitive, but they face quite different demands outside. In many industries there are existing and well established infrastructures, standards and de-facto standards.
I believe it is good for our corporate competitiveness when EU is able to further harmonize e-invoicing and related areas (VAT reporting, bookkeeping, archiving) practices.
One challenge in current EN practice is that one can see growing diversity in EN standards country level implementations. It is possible to end-up into situation where we have country based islands even though internally those island practices are based on same standards.
Good regulation – bad regulation
Regulation is often quick mean to achieve results. However, it is also often the case that regulation that is good and needed in one place is perhaps not suitable at all in other place. In best situation regulation is guiding into wished direction and it is widely accepted among those whose operations and behavior are impacted. In Finland we for example take a step further when implementing Directive of e-invoicing in public procurement into our local legislation. In our local law it was stated that buyer have right to get an EN standard contents electronic invoice. The law does not mandate to use electronic invoicing, but it gives buyers more power to demand electronic invoices and still leave freedom for trading parties to agree.
One can obviously say that this is not good enough to fight against VAT gap and tax fraud with this kind of guiding regulation. Very true, but it depends what is the citizens (corporate and persons) attitude towards taxes. If the attitude is that taxes are good for me and society at large it is very different from attitude where taxes shall be avoided by all means. As a consequence it is obvious that there is need for different type and level of regulation.
Standardization
CEN-TC434 have done very good work and it represent continuity and solid basis for standardization. E-invoicing is such a basic operation that it requires trusted foundation.
From this point of view CEF role in certain EN code set maintenance and its’ status as a project is not best possible. It is also important to realize quite an important responsibility at those code list maintenance. Some small looking changes from capital to small case letters etc. may cause huge amount of useless work in ERP systems.
Lets consider a problematic persona in the journey to e-invoice. Xavier, an owner of a small auto shop, a school drop out, 50 years old. He is silly, but he can use a mobile. With all the probability, he receives text or WhatsApp messages and replies to them. He takes pictures and organize them. So, silly Xavier is a genius, an expert, if we consider the skills level required to deal with e-invoice.
e-invoice mess should be transparent to users: two buttons are enough
Has Xavier any idea of the myriad of companies, formats and protocols the email follows between his flat and his girlfriend next door? No, Xavier needs help with all that mess. He uses an app that hides the complexity of the email ecosystem. In fact, we can almost say that to swim in the e-invoice sea he only needs two buttons in the procurement/financial apps he already uses, one to send, one to receive. From Xavier eyes -- and this post is all about eyes we should care about -- the current offer it's not attractive! Far from it!
SW houses are also ready for e-invoice, and they are a key player
And of course EasySoft, the sw house that makes the POS that Xavi uses, is also ready for e-invoice, they are waiting for their moment. Their day will arrive when the cost and effort to link to e-invoice is minimum, and the cost of not linking is their slowly dead. We cannot expect thousands of sw houses to participate in e-invoice if the required investment and risk is high. This is a key take away. Those who care about concurrence must look at this zone of the market in first place. It's here, in the financial/procurement/sailing area that we will see blood. This is where we find diversity, where we find jobs. And those actors are the ones that will spread the e-invoice message to the most remote places. Therefore we must focus on creating an e-invoice environment for EasySoft as clear and attractive as water in the desert.
We need to things:
1) A building. (Building blocks are not enough)
Xavi can say "Ok, I will email you that" but he shouldn't say "Ok, I will e-invoice you", because nobody knows the meaning of "e-invoice you". The email ecosystem is here a good analogy of what is missing. We miss a whole, to whom you are (or not) part. Like email or Peppol. Of course e-Invoice and e-delivery are relevant achievements, but they must merge in ONE thing for us to move on. And this merge is urgent to stop divergent strategies (AS2, PDF, …).
2) Shrink transaction costs associated with the use of e-invoice to email levels
Be it the huge financial costs associated with Messaging Services Handlers. Be it the technical complexity to start using EN for the SW houses. All this must be compressed.
And,
We all know that e-invoice will be universally adopted. And we know why: (1) paper invoices nail commercial conversation to the paper world, preventing it to fly in the digital air and, (2) paper or digital images of invoices put humans doing things they are bad at, and prevent computers of doing things they are good at. And we also know that EN will be involved. Has we also know that if the move takes place in the coming years, EU will drive the process, hopefully collaborating with others areas of the world.
Email is a definitive proof that if you have data structured you have it visible and printable. No need to handle both, side by side (a extremely dangerous approach, by the way). There is no pdf inside emails, and you can see them, print them.
We don't to have to make Xavier aware of e-invoice: the minute invoice will be attractive to operators, someone will tell them, we can count on it.
The so called social apps are a definitive proof that an huge adoption does not depends on an universally mandatory regime or obligation. People jump into Facebooks, twitters and the like just because they want. Some buy, others not.
There's no need for alignment between fiscal rules and e-invoice. Fiscal rules must rewrite themselves in e-invoice terms. (This a hard one).
Sorry, for my English, for being so long, for being late
Further to today's very interesting and well organised discussion on future of e-invoicing, I'd like to share my contribution to the topic "
SMEs and private sector onboarding" for further comment.
I remember a discussion some years ago between the European Commission and service providers when e-invoicing in Europe accounted for about 10% of total volume. The Commission put forward the view that service providers had failed to deliver mass adoption of e-invoices and that public sector intervention was necessary to accelerate this process. I understand that e-invoicing now accounts for about 20% of total volume. I do not know what proportion of B2G invoicing is now based on the European norm. I know that in Ireland the volume is very low. I think that the target should be 100%. This should be a priority as well as use of standardised invoice status feedback.
Economic activity insights through the analysis of pervasive e-invoice data could make a significant contribution to future public policy decisions.
The European SME landscape is big and diverse with 23 million SMEs employing less than 10 staff. It is served by more than 10,000 software companies and several hundred e-invoicing service providers.
SMEs should be incentivised to adopt digital business practice. This requires public sector investment.
Potential incentives might include faster payment cycles in both public and private sectors resulting in lower working capital requirements for SMEs. Awareness building of benefits is another key activity that could be funded.
A recent IMF paper estimated that the European shadow economy accounts for 15-35% of GDP across member states. The GDP of the EU in 2018 was estimated at €16.6 trillion. A 2% reduction of shadow economy activity through mass adoption of SME e-invoicing would yield €70 billion in additional taxes (assuming an average of 21.3%).
Some member states have achieved very high levels of private sector participation in their B2G and B2B e-invoicing initiatives. What SME focused research exists and what does this research tell us?
Thank you very much to CEF team for organizing this webinar. As Ken, I'd like to share my contribution to the topic.
SMEs and private sector onboarding" for further comment.
Despite the European Norm and the obligation to receive it for all public entities in Europe, we have seen that it does not automatically create a massive move to send.
It is because invoices are created by the Senders. And I see 2 main reasons for this low adoption:
First, B2G invoices are only a few percent of invoices sent by Private Sectors Entities. In the Suppliers’ eyes, especially for SMEs, it is just an additional channel for a small percentage of their invoices, in addition to what they try to do for their large private Buyers.
Second, Companies, and especially SMEs are far to be able to provide a full structured e-invoice, only because they do not manage all their invoice information as data, but only a part of it.
99% of companies are SMEs. And they send and receive more than 50% of invoices in Europe. Clearly, without them, it is not possible to get the critical mass needed for a large adoption of e-invoices for the benefit of ALL.
The Covid-19 crisis emphasized the need to switch paperless and potentially touchless, not only for invoices, but also for the whole supply chain processes. Minds are ready and it must be simple and efficient for SMEs.
Then, if we agree that there is NOW an urgent need to focus on B2B and SMEs adoption of electronic invoices, with a special focus on the sending side, what is the fastest way to reach this objective taking in account the capabilities of SMEs:
First, Support 100% sending B2B / B2G ability by adding common extension to the European Norm only to address ALL CURRENT B2B business cases. We are not far from it and it can be done as an option to be used by public entities, only to allow B2B adoption.
Secund, Find a better solution than simple PDF invoices sent by email. Hybrid documents based on EN16931 compliant invoice data subset are a pragmatic one for companies that are only able to manage a part of their invoice information as structured data.
Third, Include in interoperability networks and frameworks, simple and affordable solutions for SMEs to connect, taking in account their capabilities and knowledge, such as email gateways or opensource API (first and last mile).
Fourth, Promote added value for Suppliers, such as invoice response message through 4 corner model interoperability networks, which are key for treasury forecast and payment acceleration (including financial services and dynamic discounting).
And finally Think about incentives, payment delay reduction, obligation to send on B2G, or through B2B mandate in parallel to CTC / Clearance models, which need to be harmonized in order to avoid the creation of new barriers for private companies.
First and foremost, I would like to thank you again for all these quality contributions and debates. Based on your inputs, the CEF eInvoicing team was able to tailor the June 2020 Open Session about eInvoicing Transmission, the European Standard on eInvoicing and SMEs and Private Sector onboarding.
I am pleased to announce the publication of an article on "eInvoicing transmission" on CEF Digital. This article is based on your major contributions and involvement in this series of activities. I particularly would like to thank Charles BRYANT, Cyrille SAUTEREAU, Maarten DANIELSand Martin FORSBERGwho have greatly contributed to the writing of this article.
The CEF eInvoicing team is now organising a second Open Session about SMEs and Private Sector onboarding. It is scheduled for 24 November! We aim to go deeper into the topic. Following the same scenario as for the June session, we opened an online contribution page : https://ec.europa.eu/digital-building-blocks/sites/x/iQSIEQ . I kindly invite you to share your concrete projects, use cases, and lessons learnt in the comments! Looking forward to tailoring this November Open Session together with you!
50 Comments
Paul SIMONS
Many work groups, organisations, at national and international level including mirror committees etc... are in place where often the same people discuss sometimes partly overlapping but also sometimes the same topics. This creates often confusion for the outside world (read the market). Maybe time from a policy perspective to reflect on this and optimize our time and effort. Just a thought.
Solene DRUGEOT
Thanks Paul SIMONSfor your comment! If you have any additional information or hyperlinks to access this on-going work of these groups/ organisations, we would be happy to have a look and cooperate.
Serge LIBERT
The main obstacle to generalizing eInvoicing is the insufficient interoperability between the many systems involved in the invoicing processes. This situation makes wide-scale automation of the invoice processing overly complex and, consequently, unaffordable. Although it derives from many intertwined legal, semantic and connectivity factors, the main factor is that fragmentation provides operators with a protection of their market share. It can also become a source of revenues, that they quite legitimately are inclined to reinforce. In this business context, the markets are not likely to reduce the fragmentation unless an external factor modifies the situation.
Directive 2014/55/EU creates the opportunity (but no obligation) for the private sector to extend their outbound eInvoicing to the public sector, if they adopt the EN. This policy decision certainly contributes to the growth of the market. It also provides a standard for cross-sectors invoicing, which is key to the defragmentation. However it will not suffice to overcome the commercial drivers against interoperability.
The Peppol interoperability framework provides the ingredients to standardize the landscape and thereby reduce the fragmentation, while safeguarding fair competition and innovation. However, as explained above, since defragmentation jeopardizes their business model, we might expect many operators to be reluctant to comply with the framework. Additionally, eInvoicing and EDI traditionally operate in sectoral silos, so their main customers (mainly corporate segment) are generally not suffering from the lack of interoperability, so they are not likely to motivate their service providers to reconsider their business model. In this context, mandating compliance with Peppol should be an option to consider for the policy makers. Additionally, such mandate would be the way to let all actors upgrade their systems in synch. This would minimize the total costs of the upgrade, help the fair sharing of the upgrade costs, and eliminate speculation in the market.
Another option for policy makers, is to mandate the use of a central exchange platform. This strategy obviously speeds up eInvoicing generalization. However, it also eliminates competition, which affects the expected cost savings. Additionally, it brings the fragmentation at the cross-borders level. Those two aspects do not fit in the European single market strategy. Additionally this approach is not scalable.
In conclusion, mandating compliance with Peppol should be carefully considered, for it overcomes the risk of additional cross-borders fragmentation, and limits the market effects that complicate interoperability, without impairing fair competition and associated cost savings for our economy and benefits for our governments. Mandating at European level would be consistent with the rest of the European program in favor of eInvoicing and the digital single market.
Ken HALPIN
Having worked as an EDI service provider for longer than forever, I have experienced many facets of this specialist business activity. I think that Peppol has a lot going for it and is a more advanced open architecture than traditional EDI networks. Now that the Peppol infrastructure is largely in place, it would be good to see it utilised more. This needs to be driven by policy - EU leadership please!
Peppol service providers are passionate solution providers that get the dream of a single connected digital market. It is frustrating that political follow-through is not proactively in place. Peppol is scalable and deep in capability.
The e-invoicing directive was a great step forward for EU B2G. It has potential but not momentum.
Where is the political commitment to leverage Peppol and the e-invoicing directive? Where are the signals to the market?
Tadeusz RUDNICKI
Food for thoughts: Mandatory digitization and standardization of business electronic communication in all sectors and business relations
It is necessary to consider introducing consumer and business protection measures in the form of legal requirements for IT system and service providers, including standardization and certification requirements for particularly sensitive business processes and the protection of consumers' rights or interests. Such protection measures should be mandatory, however, protecting the public interest, they should not unnecessarily narrow the creative potential of the IT industry (i.e. they should mainly protect users against illegal activities).
Food for thoughts: Real-time tax reporting & e-invoicing
see 'technical - tax reporting & e-invoicing') and tax and ultimately economic through more effective reporting (see 'economy - tax reporting & e-invoicing').
Ken HALPIN
Whilst I believe that the vision of the European Commission for realisation of an ultra-competitive single digital market has made tangible progress and that the e-invoicing directive is a significant pillar achievement (only mandated across the entire public sector less than 2 months ago), there remains more policy work ahead.
It is reported that there were 25 million SMEs in EU in 2018( https://www.statista.com/statistics/878412/number-of-smes-in-europe-by-size/#:~:text=Number%20of%20small%20and%20medium,the%20European%20Union%20in%202018&text=There%20were%20estimated%20to%20be,employed%20fewer%20than%20nine%20people. Eurostat says that micro and small enterprises made up 98.8% of all enterprises in EU in 2015 (https://ec.europa.eu/eurostat/web/products-eurostat-news/-/EDN-20181119-1). Part of the strength of the European economy can be attributed to its sophistication and non-heterogeneity.
European enterprises are served by more than 10,000 software companies in the EU (https://www.crunchbase.com/hub/european-union-software-companies). The software industry is vitally important to the European economy besides being dynamic and responsive to the needs of a very diverse portfolio of customers. I would suggest that we need to look beyond the self-interests of software companies to explain why we are not there yet.
Getting there represents a major challenge and will require a multi-faceted coordinated approach. It would be great to see further evidence that member states and their public sector agents really appreciate the strategic contribution they can make to the future digitisation of the European economy. There is a lot to play for and the potential rewards are mouth-wateringly attractive. SMEs can be incentivised in many ways to go digital. Practical steps would be to reward them with faster payment cycles (lower debtor days) when dealing with the public sector and with large corporates. SME working capital costs can be reduced significantly by trending back towards the old cash on delivery business model and these savings will more than compensate for any increased IT costs.
Awareness building and education are also very important.
ΕLENA YIANOULATOU
E Invoicing monitoring (from a statistic and eInvoicing adoption analysis point of view) at the B2G and B2B levels is a topic that isn't clearly stated in the eInvoicing Directive. Also enlarging the monitoring scope to fraud prevention and cyber security.
Ger CLANCY
Monitoring is a contentious topic...and it's important to be clear on why it is desired, and what will the data be used for, and by whom.
In a B2G context, the government side will always know about 1 side of the transaction, and from there should be able to infer the sender side. They also know the actual levels of electronic vs manual trade, so should be able to infer the trends.
I dont think the Directive has any reason to legislate for this kind of monitoring.
Regarding fraud prevention and cybersecurity, these are 2 very different dimensions which do overlap with usage, but I for me these are more BAU operational things that any business must plan for.
Business Controls in an eInvoicing world are not less important than in snail mail , fax or email.
Cybersecurity is already a key feature of existing einvoicing infrastructure, and some countries like Singapore have introduced deeper KYC requirements that must be met before registering Peppol IDs.
I'm not sure where is the gap you would want to address in the Directive?
ΕLENA YIANOULATOU
Monitorıng (B2G ) ıs refering to statıstıcs in order to evaluate eInvoicing adoption. Some Countries based on Peppol, some other in other tools.
So, in order governments, to make future decisions/polıcy according and to these data, maybe is better to be clearly stated.
Otherwise, it could be done by natıonal ınıtıatıve.
About Cyber Securıty and fraud from the sıde of technology I can't talk in depth because I'm economist!
But good practıces e.g. deeper KYC requirements that must be met before registering Peppol ID that you mention ıs food for thoughts.
But they may already be on track and don't need any further actions.
Thank you very much for the ınformatıon.
Cyrille SAUTEREAU
First, it must be said that a lot has been done already. We have a Semantic Norm which is now implemented in most public entities in Europe on reception, with only 2 syntaxes (+EDIFACT), with more and more EU Members making it mandatory on the sending side.
We have CEF e-delivery Building Blocks, which should help to solve the delivery and discovery layers of interoperability, implemented thanks to Access Points which are mainly Service Providers.
We have made reports, especially on interoperability, identifying what need to be improved, but also regarding the impact of the diversity of Clearance / CTC / Realtime tax report for companies.
CT434 has identified a list of Amendments to the EN16931, necessary to address most of what was forgotten, especially to address most B2B business cases.
Some EU countries have started to implement a mandate for B2B invoices.
On the payment side, ERPB has worked on Request to Pay messages (including enrollment and validation).
But, there is about 25% of electronic invoices, and only 40% in a full structured form, 60% simple PDF (study deloitte, 2018). We may try to understand why. It is certainly more because it is easier especially for SMEs to provide it than because of lack of interoperability between SPs. And the fact that most SPs have developed solutions to handle PDF invoices is also a sign that it fits a need.
The Covid-19 shows that paper invoices are really difficult to process when people are not at the office and more and more companies and Shared Service Centers are asking for e-invoices (PDF or structured invoice, filled on Buyer’s portals).
It is certainly time to accelerate e-invoice deployment and more generally supply chain e-documents and data, at least for B2B in addition to B2G (and why not anticipating B2C).
There is then an urgency to set up a task force and a few resources (compared to what will be provided to face the economic crisis) in order to:
A lot have been done, but a lot still need to be done to reach 100% of e-invoices (Directive 2006/2010 definition), for B2B and B2G at least.
Solene DRUGEOT
Thank you Cyrille SAUTEREAU for your comment and status on on-going eInvoicing projects. Your points related to (1) a standard creation for clearance and tax reporting and (2) mandating eInvoicing for B2B/B2C transactions enrich the ideas mentioned by Tadeusz RUDNICKI .
Linking eInvoicing to payments is indeed part of digital procurement innovations. This would require (among other aspects) the involvement of new stakeholders such as credit institutions.
Today, the EC works on enhancing SMEs involvement in digital projects. One of the on-going initiatives is the SME Digital innovation challenges encouraging SMEs to re-use CEF building block in their activities (eInvoicing and eDelivery included).”
Cyrille SAUTEREAU
Thank you Solene.
I did not exactly request an global e-invoicing Mandate for B2B/B2C as it remains a decision of each Member State in the rhythm and perimeter they want, but I think that when they want to implement it, this should be done in a coordinated and aligned way in order to make it simple for end users. Globally, each EU Member State faces the same issues and solutions should be found among a very restricted list of scenarios.
Regarding SMEs, I do think that they represent the challenge to reach a critical mass as they send and receive more than 50% of invoices, and are dealing mainly with paper or simple PDF. A program for SME Digital Innovation is a good thing to get pioneers, but for the large majority of SMEs, CEF e-delivery is far from their day to day and knowledge. They need simplicity and continuity in their business process : send invoices from their sales management solutions with the structured information they manage (with no obligation to redesign deeply their information system), follow the process through e-invoice status response, get paid or refinanced easily and faster, ... I think we should take in account the fact that simple PDF is developing faster than full structured invoice. Our conclusion is that we need hybrid documents to fill the gap. The use of CEF building blocks is more the matter of solution providers than final users, and needs to be used under an interoperability governance which guarantees the freedom of choice of solution or solution provider for SMEs.
Regarding payments, ERPB is currently working on Request to Pay messages, and Enrollment and Activation messages and procedures (participating to KYS / KYC normal obligations). This could also be part of the solution. Coordination would be necessary. Same with upstream working groups and standardisation on procurement (order to delivery).
Ken HALPIN
There are a number of tools available to the public sector to drive e-invoicing adoption by SMEs.
1) It would not be a big deal for public sector bodies to begin to use the invoice level response message (e.g. as already defined in Peppol Billing process for business interoperability processing). This would provide a standardised responsive means for suppliers to remain informed on invoice processing progress.
2) Public sector bodies could start sending standardised purchase order messages (e.g. as already defined in Peppol ordering process for business interoperability processing).
3) Incentivise SME supplier by promising faster payment. Australia got this straightaway as a powerful tool by committinng to 5 day payment rather than current 26 days
4) Signal that mandating in B2G is on the horizon (12 months or longer)
5) Signalling that e-invoicing will be adapted for B2B.
6) Signal a commitment to Peppol which is very open, robust, scalable and well managed. I just had a look at the Peppol website. My estimate is that there are 286 certified Peppol access point providers. Most support AS4. I don't get the policy reticence. The openness of Peppol certainly doesn't favour the Peppol access point providers - supply far outweighs demand and my understanding of economics suggests that this situation cannot prevail as is. If there is market demand then this will drive supply.
In summary, my view is that the public sector needs to become more proactive and take advantage of this opportunity that it has helped create but now doesn't seem to want to feed. Perhaps I just don't get politics
Cyrille SAUTEREAU
If you look at what has happened in France, we have a mandate for B2G sending and receiving. We have a Platform ChorusPro which have already processed more than 100 millions invoices for Public Sector (and private on the sending side). Peppol is connected but most of the invoices are centralized directly in ChorusPro (including via Service Providers which are Peppol access Point but are connected outside Peppol which does not bring added value for this). More than 550 000 private companies are connected and referenced (directly and / or through Service Providers). Hybrid invoices are allowed or PDF + data extraction approved by the suppliers (which come to the same result). ChorusPro gives a "definite exchange date" to the supplier, which is the start for payment delay (with an impact on it). Different Status messages through API are provided. B2B mandate is in preparation. Globally it is all your points except the last one : it is done without Peppol. On the same time, it only represents less than 5% of B2B/B2G invoices. And B2B e-invoices are currently exchanged through EDI solutions or Service Providers' platform, outside Peppol also, with much more unstructured PDF form (increasing rapidly) than full structured (especially from or to SMEs).
It does not mean that Peppol can not play a role for interoperability and adoption, but it shows that this is not the only solution for success, and it would be also a signal to understand why it is not used so widely : governance, dependent of Service Providers which are most of the Peppol Access Points with potential flows and are interconnecting directly (and maybe there is also a governance issue there !), absence of invoice status response (it is just starting, which is a good thing), absence of Enrollment / Activation process (governance again, invoice and more generally supply chain business exchange should be bidirectional with mutual acceptation, which means with a capability for Corner 1 and 4 to decide if they want to exchange documents via Peppol, and same for Corner 2 and 3, for compliance reason for instance. Open doesn't mean absence of control by end users).
Peppol is an implementation of CEF e-delivery Building Blocks, with specific rules in each Peppol Authority area (including on invoice format). It is an interesting option, but there are alternatives and other solutions already in place. It has also to be taken in consideration.
Ken HALPIN
Chorus Pro is a success for France. We have customers that are suppliers to French public sector and we connect them to Chorus Pro. We also connect these customers to Swedish public sector bodies via Peppol and to American public sector bodies through other networks.
We have helped major buyer entities build portals (functionally equivalent to Chorus Pro) that are functionally rich and can be rolled out quickly to drive adoption.
All these efforts create silos of e-trading activity. I thought that the European Commission was interested in creating a single digital market across Europe and that this had the support of Member States.
(Disclosure: I am not involved in running of Peppol and can't comment on the politics and governance at the highest levels although our company is a service provider member).
It may be interesting to note the research findings into "What is it that makes a platform successful?"
There are three suggestions from Boncheck and Choudary (2013); Connection, Gravity, and Flow. Bonchek, M., & Choudary, S. P. (2013). ‘Three elements of a successful platform strategy’. Harvard Business Review, 92(1–2)
Anna Nordén
Solene DRUGEOT
Thank you Anna Nordén. As suggested in Cyrille SAUTEREAU 's comment and to summarise your points in view of identifying key topics for our online session: You point out the need of a policy base for (1) eInvoicing adoption by SMEs and EC's onboarding activities, adapting to SMEs' needs and (2) the Continuous Transaction Controls (CTC). You mention also the lack of policy guidance in technology usage among the EU Member States (e.g. Blockchain) generating system incompatibilities.
Anna Nordén
Thanks Solene DRUGEOT for your comment. I don't think I managed to explain my thoughts clearly enough.
Charles BRYANT
The European E-invoicing Service Providers Association (EESPA) looks forward to the debates and reflections on policy and designs for the future of e-invoicing, as promoted by the CEF Digital team.
EESPA now has 83 members and is very active as a community in delivering compliant e-invoicing and supply chain automation solutions. Interoperability lies at the heart of what we do and we are currently engaged in the project to embrace CEF e-Delivery to underpin our member-to-member interoperability transactions on behalf of customers. We will base this on our EESPA Model Agreements and will be using the EN 16931 as the core of our exchange standard. EESPA members currently exchange hundreds of millions of invoices to complement the transactions carried out through members’ own supplier networks.
Our members are also key participants in the OpenPEPPOL community and they also interoperate with important national infrastructures, such as Chorus Pro (France) and SdI (Italy) just to name two: a complex picture, but reflective of the diverse preferences of national communities both in the public and private sectors and the reality that no single infrastructure can address all aspects of e-invoicing. E-invoicing adoption is a ‘devil is in the detail’ activity and it is the efforts of service providers and their clients that bring these various infrastructures and many other solutions to life. The sheer diversity of clients, providers and solutions means that there are many moving parts to be navigated.
EESPA was pleased to be associated as a contributor and in an editorial capacity with the EMSFEI WG 4 paper on Interoperability and Transmission and feel that we must all work harder to deliver the vision and practices set out in that document.
Continuous Transaction Controls for VAT reporting at Member State level is a growing topic of interest and we would welcome the opportunity to debate this issue with a view to achieving more harmonization in this area based on some agreed principles. We think this can be done without compromising the objectives of tax administrations and the mandating of e-invoicing, whilst also harnessing the economic benefits of supply chain efficiency as a whole and respecting single market principles.
The policy achievements of the EU on e-invoicing are impressive and find tangible expression as the Directive 2014/55/EU and the EN 16931 which have been successfully implemented. It would be great to track progress and issues as they arise. We would like to see an acceleration of efforts in CEN/TC 434 to bring enhancements so as to support one of the original objectives of the core EN to support the wider private sector adoption of e-invoicing.
We are currently working with OpenPEPPOL and other international associations to develop a Global Interoperability Framework, which is planned to be published shortly for consultation. We would welcome the opportunity to present this to the EMSFEI. and other interested parties. Our mission is to convince promoters of interoperable frameworks (global, national, regional, sectoral) to use a common set of tools and standards, whilst leaving room for local needs and profiles.
The COVID-19 pandemic can act as a catalyst for the promotion and adoption of paperless digital processes such as e-invoicing. We should seize that opportunity.
Lars Engberg
Clarifies the targetpicture of the e-commerce value chain and in particular the e-invoice. Make sure that the benefits are highlighted from all different angles and needs, different memberstates see different benefits of the digital purchasing process, control, efficient processes, quality, security, traceability, etc. Work with the targetpicture long-term as different countries and regions have different conditions. Important to have a long-term attitude and the stability of the solution, to avoid constant changes that, for example, cause different systemsuppliers to make upgrades in their services too early or too often.
Cyrille SAUTEREAU
Agree. And that is why there is an urgence to work on harmonization on CTC/Clearance + Extend the EN16931 to allow its deployment for all B2B business cases + interoperability framework + invoice message response + hybrid documents, under a priority of 100% of e-invoice (directive 2006/2010 definition) taking in account first SMEs for critical mass adoption and supporting first payment acceleration, focusing on the minimum invoice data needed for process automation and tax administration to lower Vat gap.
Otherwise, solutions will be designed apart as a lot of stakeholders feel the necessity to move on fast, especially after the COVID-19 pandemic, and with more and more diversity through Member Sates, which means complexity for end users and solutions, and finally the slow adoption we face since the last years (25% of e-invoices only).
Kerstin WISS HOLMDAHL
In Sweden we have had e-invoicing many years before the directive came. We started with e-procurement, the order-invoice process but many started with only e-invoicing process. According to a Swedish regulation 2008 all government agencies were mandated to receive e-invoices. For municipalities and regions there has not been any law or regulation but they started with e-invoicing early. The incentive was an efficient process and also cost effective. Due to a survey 2017 (based mainly of statistics from 2016) 87 % of the 290 municipalities and 100 % of the 20 regions had introduced e-invoicing ( structured electronic invoices, not including PDF invoices).In average 56 % of their invoices was received in structured electronic formats.
Now, after the law came into force, regulating that both governmental agencies and authorities, municipalities and regions shall receive e-invoices, e-invoicing has of course increased. And the Swedish law also stipulates that suppliers to public sector also must send e-invoices based on public procurements made after April 1, 2019.
From November 2019 it is also mandatory for contracting authorities and entities to be registered in Open Peppol and be able to receive e-invoices also via this communication. The e-invoicing standard that are recommended to be used for public sector and their suppliers is PEPPOL BIS Billing 3, since this is the e-invoice that fulfill the requirements of the European standard/ EN. The recommendation is from SFTI, a cooperation between the governmental sector and the local and regional sector. Now almost all municipalities and regions are registered in Open Peppol, but so far they still receive most of the invoices via the VAN operators network as they did before. But the interest of using Peppol is increasing. We notice it from their interest of knowing more; we frequently organize education about e-invoicing and Peppol ( both the invoice and the infrastructure).
Declan MCCORMACK
Firstly, I would like to acknowledge the continued good work of the CEF team and the excellent contributions made in the comments in this space by my colleagues, most of which I concur with and support in terms of warranting further consideration.
On behalf of the eInvoicing Ireland team, I have provided more detail below but in summary, I think this is a good opportunity for eInvoicing stakeholders in general to:
It is now a good time to re-examine the main objectives of the Directive and remind ourselves of the benefits and outcomes we are trying to deliver.
Monitoring and reporting on progress across EU member states and sharing success stories and positive developments.
Focusing eInvoicing Stakeholders work on identifying and mitigating/managing risks to the Directive achieving its objectives may help us to take targeted actions that need to be taken to protect the investment made is eInvoicing by the Commission and all Member States.
(e.g. Inadequate political will or centralised supports; Availability and ease of PDF/email; Lack of support for EN in new Financial / ERP applications and implementations; Lack of joined up objectives and measures in common and related policy areas – Procurement; Tax; Digital; Green.)
Background to Ireland
The majority of invoice processing in the Irish public sector is distributed across a number of sector specific finance shared service centres. In addition to this a significant number of contracting authorities also process invoices independently. eInvoicing is not mandatory for the sender in Ireland.
For the most part, the national approach has resulted in a Peppol-based eInvoicing capability being established across the Public sector. The establishment of a European Standard and the implementation of the eInvoicing Directive across all member states is a great achievement and milestone on Europe’s Digital journey.
Shared experiences and ideas for the future of eInvoicing
However, in the absence of a mandate, there is now a challenge for Contracting Authorities to drive the uptake of European Standard eInvoicing among suppliers. This is due to a number of reasons but most commonly cited ones include:
In facing these challenges, some Shared Service Centres and individual Contracting Authorities are favouring the promotion of their Finance system buyer-portals and PDFs via email to drive the uptake of eInvoicing with suppliers. This has the potential to weaken or even undermine the national approach at an early stage.
Mandating the submission of eInvoices and applying eInvoicing clauses within procurement contracts are examples of measures that stakeholders regularly seek from a national approach to support the uptake of eInvoicing among suppliers.
Areas that might be considered to help the future of eInvoicing include:
It is now a good time to re-examine the main objectives of the Directive and re-extol the benefits.
(e.g. Inadequate political will or centralised supports; Availability and ease of PDF/email; Lack of support for EN in new Financial / ERP applications and implementations; Lack of joined up objectives and measures in common and related policy areas – Procurement; Tax; Digital; Green.)
Many suppliers are unaware of the European roadmap on eInvoicing, Peppol and the relevance of eInvoicing to their business. Sharing examples of national approaches to supporting suppliers and establishing enduring models to sustain and increase eInvoicing may be helpful in that regard. (SME Digital innovation challenges are a good example of such an initiative.
What are the attributes of that make these other options (e.g. PDF via email) so attractive. How can similar attributes be established to enable EU standard eInvoicing – e.g. native support for the EN and CEF delivery building blocks in financial apps)
Consider targeted communications to business representative bodies, financial systems providers, accountancy bodies, finance and tax authorities as well as other policy areas such as Procurement, Tax, Digital, Green. To help provide practical and joined up guidance on what we are all aiming to achieve and identify real steps that can help to move us forward together.
Consider whether the application of Digital Targets (similar to Green targets) might prompt Member States to be more ambitious in taking steps to making EU Standard eInvoicing the predominant method of invoice processing. Targets would enabled the Commission to focus on outcomes rather than implementation choices such as whether to use a specific delivery network.
Ken HALPIN
I support this well articulated and balanced review of eInvoicing landscape in Ireland. I think that the various recommendations have much merit.
As part of a broader communications and outreach strategy, I believe service providers would be more than willing to participate in promotional activities.
e-Invoicing is an important tool in the digitalisation of both B2G and B2B processes with the potential to deliver a considerable economic uplift.
The intrinsic value of e-invoice payload does not seem to be fully appreciated as a source of insight into economic activity.
Now that the EN directive directive in combination with the choice of Peppol for eDelivery and digital business process evolution, there is now a great opportunity to leverage these achievements to realise transformational change.
Anna Nordén
Declan, you've drafted the agenda for Tuesday's discussions it seems!
Cyrille SAUTEREAU
What are the attributes of that make these other options (e.g. PDF via email) so attractive : this is the key question.
For us (France, French National Forum) the main reason is simplicity and availability. An invoice can contain a lot of information, some for compliance reason to different regulation without any use for automation, some for business reason (marketing, operational details) which are first useful in case of manual process (for instance in case of dispute), some are managed by ERPs or Sales management solutions as structured data (so easy to provide in that form), some are managed as "free text".
The EN16931 was built under the constraints to fit with Public sector needs and capabilities to process them as there is an obligation to do it. To do so, we stated structurant assumptions such as 1 invoice 1 delivery 1 order, but also choices on business terms. The result is that we are missing some invoices that does not fit with the core. It is not a very big deal if we stay on an obligation to receive. It becomes more complex if we add an obligation to send as there is no solution for ALL invoices. And extension to B2B is much more complex and is the real target because B2G invoices represents only a few percent of invoices for companies.
By trying to transform all invoices in full structured invoices through the EN16931, we face at the same time the difficulty for all companies, especially SMEs, to provide all their invoices in such full structured format, and the difficulty for companies which are using additional business fields or business cases to restrain themselves to the core invoice.
In addition, using only secure exchange network like PEPPOL means a certain maturity and / or the use of 1 or many service providers to reach the different networks of counterparts.
Then, in order to stick in a full structured invoice process compliant to the EN16931, the only solution is to fill invoices manually in multitudes of Buyer's Portal, which is just a major change and a step backward for companies (including SMEs).
Apart from that, it is easy for any company to create a pdf invoice and to send it by email. And the Covid-19 pandemic showed that this way is the best and fast to handle business continuity when paper is not processable because not send or received, and when received in paper, people at home cannot process them.
It is then not a surprise that PDF invoice sent by email is so attractive, especially when SMEs are involved : Simple and available rapidly.
And this why if we want at the same time to have invoice process automation, which needs invoice data in a structured form, but not too much invoice data for simplicity and availability, and the possibility to reach rapidly 100% of paperless invoices for the benefit of all, we consider that a pragmatic solution is to propose hybrid documents as a first step to replace simple pdf. If we add most of the EN16931 Amendments proposed by CEN TC434 working group, we are close to be able to manage all business cases in B2B / B2G, with the invoice data necessary for automation. It means that we have a "playing field" sufficient to reach 100% invoices in a pdf form + a minimum mandatory information in a structured from at least useful for process automation and for Clearance / CTC needs, in addition to full structured invoices which remains the final target . On top of that, the market and the end users will have all the freedom to provide more structured information or even full structured information, and develop innovation and more added value.
Switch priorities : 100% paperless and more than 80% touchless with pragmatism, flexibility and lean process, instead of 100% full structured and finally a slow adoption.
Ger CLANCY
100% paperless ahead of 100% structured sounds like a great thing, but I think it hides a few unpalatable truths...
There is a perception that pdf by email is BAU and more or less free of additional cost using existing business tools.
BUT
Cyrille SAUTEREAU
Ger,
Decades of business have made a large diversity of information in invoices. Switching all this in full structured way is just a nightmare. Restricting it to a core set of data is a huge change for all companies and solutions. The challenge is to find a way to transform paper and simple pdf invoices in machine processable formats, with flexibility in order to reduce manual processing and accelerate payments. The target should be "what percentage of automation is reachable rapidly on the basis of ALL invoices and not only the ones that can be switched in full structured, and taking in account also the manual processing on the sending side and for SMEs".
Ger CLANCY
With respect to Blockchain, finally there are signs of movement toward Interoperability, but I believe getting this to a BAU state is a long way off.
In the meantime, Blockchains represent 3 corner models, which we're already moving past with electronic trade interoperability as embodied in Peppol, EESPA, BPC, etc.
In my view the most sensible deployment of Blockchain for the medium-term is for value-added tangential use cases, such as smart contracting, KYC verification, smart financing, permissioned sharing of data elements with external parties to name a few. For sure there is lots of room for innovation and invention there still.
I think it would be a big step backwards however if we delayed interoperability, automation of the Order through Invoice process for Blockchain to catch up, in the hope it can do something different.
I believe we'll never get to only 1 way of doing things as that would again be a market and business restriction, but doing everything different is not working and we need change.
Solene DRUGEOT
Thank you Ger CLANCYfor this very valuable comment - I suggest to keep this conversation open and invite other commentators to share their points related to this comment on the Technical page.
Ken HALPIN
Having just spent 60 hours studying blockchain (i.e. distributed ledger technology) and its various applications including cryptocurrencies as part of a Dublin City University online course, I think blockchain has great potential in specialised areas. The reality is that it is an over-hyped immature technology with relatively few commercially proven use cases.
Andrea CACCIA
1) Introduce the “digital by default” principle in the VAT Directive and tax legislation in general
The VAT Directive originates from an age when most invoices were “analogic”, i.e. on paper or – even if electronic - not structured. Now digital (i.e. structured) invoices should be considered the normality (also because it's straightforward to transform a structured invoice in a human readable one when needed, but not the opposite). A “digital by default” principle should overcome the equal treatment principle, introduced in the last revision of the VAT Directive.
Continuous Transaction Controls (CTC) are effective ways to fight tax frauds and were made possible thanks to digitalization. Their use should be encouraged however fragmentation of requirements on the data that is requested by tax authorities to the business operators creates burdens especially for SMEs and – consequently – obstacles to the single market. Common standards should be defined and their support mandated to tax authorities, to avoid unjustified burdens on economic operators. EN 16931 can be the basis to define the information needed for CTC and standardized ways to extract automatically from EN 16931 based invoices (or direct use of invoices) can greatly simplify the task.
The development of an European standard for B2C invoices has been recently approved by CEN/TC 434 and its availability can extend to B2C the same concepts.
EN 16931 was possible thanks to the existence of a harmonized legal framework, the VAT Directive. The development of the standard put also the light on some national level specificities that still exist after 50 years of legislative efforts at European level, reflected in CIUS and Extensions that have been developed: they should be analysed and the result fed back to the policy level to improve harmonization and support “digital by default” principle.
To achieve this, EMSFEI should liaise with the VAT expert group to give to TAXUD the proper inputs.
These initiatives are expected to further greatly promote the use of structured e-invoicing in the private sector.
2) Extend Directive 55/2014 to include the transmission level
To further increase the adoption of Directive 55, the support of a baseline standard at the transmission level should be made mandatory for public authorities to receive invoices. This can be easily extended to support full digitalization of the supply chain documents. The CEF eDelivery building block and Peppol (that is spreading not only in Europe but also internationally) should be the technical basis, provided that they are fully based on international standards and compliance with eIDAS Regulation requirements guaranteed.
3) Systematic and reinforced use of international and European standards
The standardization system is global and the use of standards is of paramount importance for fair competition, it should be avoided that the European enterprises are regulated outside Europe. Many European initiatives such as Peppol are kept in high consideration outside Europe and – when relevant – standards developed in Europe should find their way in the international context. The standardization framework is addressed at policy level by the EU Regulation 1025/2012. In this framework the IPR issues should addressed to find a viable and definitive solution, taking into account that any obstacle to the use of standards create in the medium and long term additional costs
Ger CLANCY
Andrea CACCIA I agree wholeheartedly there needs to be alignment, harmonization or at least recognition of mutual interests dependencies between the VAT Directive and eInvoicing legislation, especially taking the impact on the invoice issuer / taxpayer into account.
The worst possible outcome would see each country coming up with non-interoperanble, incompatible CTC pathways, "because they can" despite the standardisation of the Order - Invoicing flows.
The taxation policymakers may not know nor care about the invoice flow standardisation, and without proper education (ie from EU / Member states), then they may easily take a deliberately different approach.
On the baseline transmission in 55/2014 I also agree in general, but there are depandencies here. For example Portugal is using PT-CIUS as a payload, which is structually derived from EN, and not very far from Peppol BIS. For transport, they will use individual AS2 connections and not use Peppol network at all.
In order to register a divergent doc type in the Peppol network, it must be sponsored + managed via a country-level Peppol Authority, and if there is no PA, then its not possible.
Therefore if Portugal wanted to send /receive their docs in Peppol today, they cannot.
Until there is a way of getting national requirements reflected into and supported by the eDelivery / Interoperability Network especially if there is not a Peppol Authority, then there is a risk of fragmentation in spite of the Directive.
Lastly, the IP approach to the EN was poor, and was not supportive to desires to extend the EU standards globally.
Not running into this situation in future should be foundational to any changes to current policy.
Andrea CACCIA
Just to clarify better the concept of baseline transmission, it needs to be further developed of course but the basic idea is on one hand to recognize what is already used but on the other hand to avoid to introduce a general obligation to use Peppol. I mean that there should be some baseline protocol that is guaranteed to be available, like today public authorities must guarantee to accept EN 16931 invoices expressed in one of the 2 syntaxes. For example AS4 is the same technology used for Peppol but implementing it does not necessairly means to use Peppol.
Ger CLANCY
Agreed.
For example, in Germany federal government is saying XRechnung (German Peppol variant) to be delivered via Peppol, whereas some federal states have only made email delivery possible for the XRechnung.
Or in Italy, we have lots of clients receiving orders and sending despatch advices in Peppol for several years, but its crazy that the Invoice must be in a different doc format, and using a different network.
In their own individual bubbles, all of those individual things maybe make sense, but from a supplier perspective having to naviigate all of them is horrible.
I know there is work afoot in Italy to converge Peppol + SDI for Invoices, but I'd rather try to avoid such situations cropping up at all if possible.
Serge LIBERT
"… to avoid to introduce a general obligation …". I agree that obligations must be avoided in all possible ways, for they often lead to distortions in the market. As my main background is economist, market efficiency is the focus of my contribution to the debate. A lot has been written on the topic. In this literature however, even the most liberal thinkers agree that regulation is also essential to market efficiency. The problem is to define the right policy. In the present case, as I tried to articulate in my first comment, the drivers in the market lead to a severe market inefficiency. The industry cannot be blamed for this. The customers cannot be blamed for this. Nor are these groups responsible to articulate the response. The situation requires a more global approach than the actors in these groups can be asked to have. With directive 2014/55 the policy makers agreed to mandate semantic interoperability to a group of customers (the governments of Europe). So obligation is not tabou. The question is what obligation will unlock the current obstacles to a wider automation of the supply chain operations (where the invoice plays a central role).
When discussing Peppol, the main problem is that it is too often narrowed down to the transmission aspects. your comment gives this impression. Peppol indeed addresses the transmission, but it also addresses semantic, legal and organizational aspects, in line with the European Interoperability framework (EIF). That gives him the unique attribute: comprehensiveness. As I and many others stressed, the obstacles derive from a combination of intertwined complexity factors. To my best knowledge, Peppol provides the best response to this. It provides flexibility, scalability (both in size and functions), balanced collaboration/competition. It gives all stakeholders (industry, customers and policy makers) a voice in the agora that is required to meet and align. Peppol is far from perfection. But it keeps improving. This is probably the most disrupting, and thereby misunderstood aspect of Peppol. The improvement derives from the constant combination of the 3 main stakeholders in joined efforts. Organizing this constant interaction, overcoming the conflicts, is indeed a big challenge. It requires a lot of vision and willingness to understand the others point of view. After 5 years of practice, I can only confirm that it is not a walk in the park, but it works! This leads to a shift in the market where, as Ger stressed, Peppol only creates a framework for all IT-players to compete fairly and deploy their innovation without breaking interoperability. Also countries can keep supporting their local markets and specificities within the framework., thereby avoiding fragmentation and associated costs for the IT industry and their customers. For all these reasons, I suggest policy makers to consider mandating Peppol. The obligation is needed to synchronize actors, and thereby minimize and fairly share the costs that the alignment to this common framework will involve. The current urgency to move away from paper creates a unique context to have the right debate about this and seize the right opportunities together.
Ken HALPIN
Peppol has developed very significantly since its inception as a large scale European project in 2008 with a big pan European public procurement vision. This vision includes e-invoicing and much more. It is still not the finished products but it ticks many more boxes than any other prevailing ecosystems I'm aware of. If anything, it is too heavily biased towards the interests of the public sector.
The technical architects behind it are seasoned business interoperability practitioners and the governance structure looks right albeit that it is over represented by Scandinavian public sector - but that will change and is changing. Germany is now taking Peppol seriously and will exert an accelerating EU market adoption influence.
The government of Singapore, Australia and New Zealand have recognised what the EU has achieved.
Europe is demonstrating leadership in many areas (e.g. standards, PSD2, GDPR, SEPA, instant payments, e-invoicing and even Peppol), It's not often that Europe gets a head start on USA in terms of software technology, it would be great to support the European software providers in our home market to help create scaling opportunities.
Cyrille SAUTEREAU
@Serge : create a mandate to use Peppol as THE interoperability framework is too late as there are already alternatives in place with significant flows. In addition, it would be close to be monopolistic, concentrating innovation on very few hands, which creates huge governance issues. In addition, it is not yet so idealistic and improvements are needed : it remains juxtaposition of networks with specificities on formats or business rules per region, it does not handle bi-directionnal exchanges (which mutual acceptance and control of end users through the network => see the work made by ERPB on Enrollment and Activation), it is built on CEF e-delivery which is the disruptive technology and can be implemented separately with another governance. In addition, I think that paper is about to be replaced by PDF first (and exchanged via email in addition !! the nightmare of IT/EDI experts!). It has to be taken in consideration also in the big picture of interoperability / Clearance / CTC / SMEs adoption, in order to bring pragmatic solutions and added value for ALL.
On the same time, I agree with Ken's last sentence. Europe is demonstrating leadership in this area, and we should be careful not to jeopardize it. I think it should be done more by improving what needs to be improved in order to build "natural adoption" and "shared added value" that trying to force the use of Peppol as is with mandates.
Ken HALPIN
In Ireland, paper has been replaced by PDFs almost entirely. This has saved suppliers lots of postage and printing costs.
PDF processing will keep IT companies busy and accounts payable staff employed for many years to come.
E-invoicing has several advantages over PDFs. Key ones are standardisation and information rich (information is the oil of 21st century).
In my opinion PDFs are a tactical response to a strategic problem.
Cyrille SAUTEREAU
Agree, and that is why we need to promote solutions and Standards to replace simple PDFs, with the more structured information possible, taking in account SMEs capabilities and without forcing them to fill invoices manually on Buyer's portals or complete invoice information extracted from their simple PDF invoices.
Ger CLANCY
Cyrille SAUTEREAU What we're talking about is replacing an unstructured pdf that a business can make for free with bau tools, with a structured pdf that in most cases they'll need to buy new software to make.
The productivity benefit (if there is one) will maybe be on the receiver side, or it may just perpetuate manual handling on both ends, but add cost. I cannot agree that this is a logical first step on a path towards automation, other in very specific cases.
The primary beneficiary is the software vendor.
Re Peppol, I fully agree that its B2G history brings limitations for widescale B2B application (so far), but Peppol is now driving a lot of interest among businesses globally, and including for B2B applications.
I believe this will be a driver for innovation and increased demand, which will in turn drive innovation and demand.
I dont see a great difference between a government mandate to use Peppol, and a B2B relationship requiring a specific format, but the interoperability of the Peppol / CEF model is the way forward, and for me perpetuating pdf of any kind is the equivalent of a step backwards.
Cyrille SAUTEREAU
Ger CLANCY I have the feeling to repeat constantly myself. Let's try another way. SMEs are using sales solutions (and for most of them, it is word or excel) that are NOT dealing with ALL invoice information as data. It means that that use free text for part of the information and structured data for other. All this finish on paper or PDF. Creating an hybrid document with the data available is not a big deal for solutions (even excel can do it if necessary, or Libreoffice, ...), but create a full structured invoice means changing for a solution than can do it. And, for your information, SAP, IBM, ... are no the only solutions or affordable for every SME. Then there is 3 solutions:
I think it is important to prioritize the target : paperless and the more automation and find the solution for it, than prioritize the solutions : full structured and Peppol for all and observe the results.
Serge LIBERT
Thank you for these reactions. Let me clarify some points
1/ The main point of my suggestion is not Peppol. It is the market failure that we face, caused by the increasing fragmentation on the market and the subsequent lack of level playing field. in fine, it drives the enterprises to use a suboptimal technology( pdf/email). As I also mentioned in my initial comment, this situation also leads many national policy makers to the decision of installing and mandating national platforms - most of the times with a B2G scope (up to now only Italy went beyond that scope). In the absence of a suitable solution on the market , national policy makers have not much other options than to copy the model used by large private buyers in the past. Unfortunately, each new implementation keeps increasing the market fragmentation. 10 years ago, the paper “ Reaping the benefits of e-invoicing in Europe ” already warned us of the fatal long-term consequences of these national strategies on the growth of eInvoicing and, more generally, on the Digital Single Market.
No wide scale adoption of eInvoicing is possible in this situation, so overcoming that situation is the top priority of all of us (policy makers, industry, and their customers). Is there another framework than Peppol better suited for this? Or a combination? I trust that the policy makers will be able to make a well informed decision here.
2/ The disruptive character of Peppol is not technological, it is organizational – its ability to let policy makers, users and service providers meet and align. Peppol is aligned with the European Interoperability Framework (EIF – formerly known as European Interoperability Reference Architecture - EIRA), it encompasses legal, organizational, semantic and technical aspects of interoperability. The interaction between stakeholders is mainly addressed in the legal and organizational layers. The organizational layer provides the flexibility that is needed to cope with the reality of eInvoicing: a complex, evolutive endeavor.
3/ Peppol is a project that took place several years before the CEF program was launched so it cannot really be narrowed down to an implementation of CEF components. On the other hand, due to its ability to address change, it adopted the EN in its semantic layer, and CEF e-Delivery specifications in its technical layer - almost seamlessly. (And I agree that CEF e-Delivery also significantly feeds interoperability
)
4/ Regarding your comment on the possible monopolistic character of Peppol, as Ken mentioned there are 286 Access Points, most of them are service providers. It rather looks like it stimulates competition, as it is mentioned in its statutes. Additionally, as I tried to articulate, the vision of Peppol is not to concentrate innovation, but on the contrary to help building the level playing field that is required for accelerating technological break-through. All service providers are free to offer whatever features and added value as long as they don’t jeopardize interoperability.
I hope these clarifications help better situate my suggestions.
Charles BRYANT
Sharing the EESPA Executive Committee's message to the Market...
Covid-19 and the urgency of adopting paperless supply chain automation to accelerate payments to cash-strapped small suppliers
Today’s circumstances demand radical action to keep the wheels of commerce turning and supply chains delivering. For this to happen there must be timely electronic invoicing, and certainty and acceleration of payments, especially to small suppliers.
Never have the arguments been so persuasive for removing paper and its replacement by safe and reliable digital processes for e-business and automated supply chains. There is current evidence of delays to invoice processing caused by remote working and the logistical handling of paper-based documents. Current dislocations act as a catalyst to digitize, as we will live with these new conditions for some time to come. E-invoicing provides full legal and commercial certainty, and is easy to use. Tools for its implementation are in common use. Service providers are a major influence on the stimulation of e-invoicing volumes.
As a trade association, EESPA represents 83 e-invoicing and supply chain automation specialists operating throughout Europe and beyond. A 2018 statistical survey among a group of EESPA members reported an annual volume of nearly 2 billion invoices. With recent growth trends, we estimate that our community is now handling an annual volume of over 3 billion invoices. We have members located near all business enterprises and they are willing to talk and demonstrate solutions.
Digital service providers play a key role in capturing and exchanging transactions generated from multiple clients in many diverse sectors. The result is the delivery of tangible benefits to the trading eco-system through:
Many commercial enterprises and public administrations have some experience of digital processes in the supply chain. The real benefits come with critical mass and the ability to quickly respond to changing circumstances with agility and focus, including urgent situations. Service providers can discuss scale adoption as well as targeted programs to meet challenges in specific situations using well-targeted messages and case studies.
Please think about taking action today to protect trading integrity and create a valuable platform for the future.
EESPA Members are listed on our web-site https://eespa.eu/membership-list/
Marcus Laube and Bengt Nilsson, EESPA Co-Chairs
tapani TURUNEN
Some contribution into discussion from Finnish idealism point of view.
I like to start with some experience. In Finland our Central Government is able get about 90% of their purchase invoices in structured format. I have opinion that level is not an outcome from any specific infrastructure. It have reached through service providers and banks interoperability network where banks network is multilateral and non-bank service providers work on bilateral connection basis. Saying this I don’t argue at all that this level of usage could not be reached with other infrastructure frameworks as well. I don’t believe that thinking that one size fits all is the best possible approach.
One factor for high e-invoicing usage in Finland is that infrastructure and practice covers different segments B2B/B2G/B2C. It is very often that invoice issuers don’t send invoices only to one segment customers, but they have customers in all segments. It is very efficient for the issuer that they can use one and same infrastructure and invoice distribution method for all their customer segments.
Consumer invoicing might be one of the very important directions in EU to further enhance e-invoicing practice. Addressing is another important topic to concentrate more. ISO-6523 maintenance seems not working best possible way. Neither does CEF EAS code list look very robust including large number of arbitrary PEPPOL addresses.
Local – Global
Efficient public sector is really important. However, I don’t believe that public sector is the key driver for Europe competitiveness and success. Main thing is how our corporates are competitive in Global market. EU level standardization is very important and help our corporates to be competitive, but they face quite different demands outside. In many industries there are existing and well established infrastructures, standards and de-facto standards.
I believe it is good for our corporate competitiveness when EU is able to further harmonize e-invoicing and related areas (VAT reporting, bookkeeping, archiving) practices.
One challenge in current EN practice is that one can see growing diversity in EN standards country level implementations. It is possible to end-up into situation where we have country based islands even though internally those island practices are based on same standards.
Good regulation – bad regulation
Regulation is often quick mean to achieve results. However, it is also often the case that regulation that is good and needed in one place is perhaps not suitable at all in other place. In best situation regulation is guiding into wished direction and it is widely accepted among those whose operations and behavior are impacted. In Finland we for example take a step further when implementing Directive of e-invoicing in public procurement into our local legislation. In our local law it was stated that buyer have right to get an EN standard contents electronic invoice. The law does not mandate to use electronic invoicing, but it gives buyers more power to demand electronic invoices and still leave freedom for trading parties to agree.
One can obviously say that this is not good enough to fight against VAT gap and tax fraud with this kind of guiding regulation. Very true, but it depends what is the citizens (corporate and persons) attitude towards taxes. If the attitude is that taxes are good for me and society at large it is very different from attitude where taxes shall be avoided by all means. As a consequence it is obvious that there is need for different type and level of regulation.
Standardization
CEN-TC434 have done very good work and it represent continuity and solid basis for standardization. E-invoicing is such a basic operation that it requires trusted foundation.
From this point of view CEF role in certain EN code set maintenance and its’ status as a project is not best possible. It is also important to realize quite an important responsibility at those code list maintenance. Some small looking changes from capital to small case letters etc. may cause huge amount of useless work in ERP systems.
João Trigo
A few thoughts
People are ready for e-invoice
Lets consider a problematic persona in the journey to e-invoice. Xavier, an owner of a small auto shop, a school drop out, 50 years old. He is silly, but he can use a mobile. With all the probability, he receives text or WhatsApp messages and replies to them. He takes pictures and organize them. So, silly Xavier is a genius, an expert, if we consider the skills level required to deal with e-invoice.
e-invoice mess should be transparent to users: two buttons are enough
Has Xavier any idea of the myriad of companies, formats and protocols the email follows between his flat and his girlfriend next door? No, Xavier needs help with all that mess. He uses an app that hides the complexity of the email ecosystem. In fact, we can almost say that to swim in the e-invoice sea he only needs two buttons in the procurement/financial apps he already uses, one to send, one to receive. From Xavier eyes -- and this post is all about eyes we should care about -- the current offer it's not attractive! Far from it!
SW houses are also ready for e-invoice, and they are a key player
And of course EasySoft, the sw house that makes the POS that Xavi uses, is also ready for e-invoice, they are waiting for their moment. Their day will arrive when the cost and effort to link to e-invoice is minimum, and the cost of not linking is their slowly dead. We cannot expect thousands of sw houses to participate in e-invoice if the required investment and risk is high. This is a key take away. Those who care about concurrence must look at this zone of the market in first place. It's here, in the financial/procurement/sailing area that we will see blood. This is where we find diversity, where we find jobs. And those actors are the ones that will spread the e-invoice message to the most remote places. Therefore we must focus on creating an e-invoice environment for EasySoft as clear and attractive as water in the desert.
We need to things:
1) A building. (Building blocks are not enough)
Xavi can say "Ok, I will email you that" but he shouldn't say "Ok, I will e-invoice you", because nobody knows the meaning of "e-invoice you". The email ecosystem is here a good analogy of what is missing. We miss a whole, to whom you are (or not) part. Like email or Peppol. Of course e-Invoice and e-delivery are relevant achievements, but they must merge in ONE thing for us to move on. And this merge is urgent to stop divergent strategies (AS2, PDF, …).
2) Shrink transaction costs associated with the use of e-invoice to email levels
Be it the huge financial costs associated with Messaging Services Handlers. Be it the technical complexity to start using EN for the SW houses. All this must be compressed.
And,
Sorry, for my English, for being so long, for being late
Francesca POGGIALI
GS1 in Europe is really willing to contribute to this interesting debate.
We prepared a document which is publicly available here
https://www.gs1.eu/news/european-commission-re-launches-eivoincing-dialogue
For those who want to read more about GS1, please visit https://www.gs1.eu/
For the EDI strategy https://www.gs1.org/docs/EDI/GS1_EDI_strategy_2018-2020.pdf
Looking forward to your comments to our document.
Ken HALPIN
Further to today's very interesting and well organised discussion on future of e-invoicing, I'd like to share my contribution to the topic "
SMEs and private sector onboarding" for further comment.
I remember a discussion some years ago between the European Commission and service providers when e-invoicing in Europe accounted for about 10% of total volume. The Commission put forward the view that service providers had failed to deliver mass adoption of e-invoices and that public sector intervention was necessary to accelerate this process. I understand that e-invoicing now accounts for about 20% of total volume. I do not know what proportion of B2G invoicing is now based on the European norm. I know that in Ireland the volume is very low. I think that the target should be 100%. This should be a priority as well as use of standardised invoice status feedback.
Economic activity insights through the analysis of pervasive e-invoice data could make a significant contribution to future public policy decisions.
The European SME landscape is big and diverse with 23 million SMEs employing less than 10 staff. It is served by more than 10,000 software companies and several hundred e-invoicing service providers.
SMEs should be incentivised to adopt digital business practice. This requires public sector investment.
Potential incentives might include faster payment cycles in both public and private sectors resulting in lower working capital requirements for SMEs. Awareness building of benefits is another key activity that could be funded.
A recent IMF paper estimated that the European shadow economy accounts for 15-35% of GDP across member states. The GDP of the EU in 2018 was estimated at €16.6 trillion. A 2% reduction of shadow economy activity through mass adoption of SME e-invoicing would yield €70 billion in additional taxes (assuming an average of 21.3%).
Some member states have achieved very high levels of private sector participation in their B2G and B2B e-invoicing initiatives. What SME focused research exists and what does this research tell us?
Cyrille SAUTEREAU
Thank you very much to CEF team for organizing this webinar. As Ken, I'd like to share my contribution to the topic.
SMEs and private sector onboarding" for further comment.
Despite the European Norm and the obligation to receive it for all public entities in Europe, we have seen that it does not automatically create a massive move to send.
It is because invoices are created by the Senders. And I see 2 main reasons for this low adoption:
99% of companies are SMEs. And they send and receive more than 50% of invoices in Europe. Clearly, without them, it is not possible to get the critical mass needed for a large adoption of e-invoices for the benefit of ALL.
The Covid-19 crisis emphasized the need to switch paperless and potentially touchless, not only for invoices, but also for the whole supply chain processes. Minds are ready and it must be simple and efficient for SMEs.
Then, if we agree that there is NOW an urgent need to focus on B2B and SMEs adoption of electronic invoices, with a special focus on the sending side, what is the fastest way to reach this objective taking in account the capabilities of SMEs:
Solene DRUGEOT
Dear colleagues,
First and foremost, I would like to thank you again for all these quality contributions and debates. Based on your inputs, the CEF eInvoicing team was able to tailor the June 2020 Open Session about eInvoicing Transmission, the European Standard on eInvoicing and SMEs and Private Sector onboarding.
I am pleased to announce the publication of an article on "eInvoicing transmission" on CEF Digital. This article is based on your major contributions and involvement in this series of activities. I particularly would like to thank Charles BRYANT, Cyrille SAUTEREAU, Maarten DANIELSand Martin FORSBERGwho have greatly contributed to the writing of this article.
The CEF eInvoicing team is now organising a second Open Session about SMEs and Private Sector onboarding. It is scheduled for 24 November! We aim to go deeper into the topic. Following the same scenario as for the June session, we opened an online contribution page : https://ec.europa.eu/digital-building-blocks/sites/x/iQSIEQ . I kindly invite you to share your concrete projects, use cases, and lessons learnt in the comments! Looking forward to tailoring this November Open Session together with you!
Best wishes!