What Italy’s SDI tells us about Europe’s need for tax engines

Tax and finance leaders in the US and Europe are approaching e-invoicing with almost opposite problems.  

US businesses understand the value of a tax engine having relied on them for years to manage domestic sales tax complexity, but many are still getting to grips with new international e-invoicing mandates.  

European leaders have it the other way around. They know the mandates in fine detail, and they understand where their business falls into scope in each market. What they remain skeptical about is whether a tax engine is actually necessary to meet their needs.  

Now, as we move into a world of accelerating mandates, real-time compliance and country-by-country rule changes this is a mistake European leaders can no longer afford to make.  

The E-Invoicing Readiness Gap  

Knowing the ins and outs of e-invoicing mandates and being ready for dealing with it are two very different things and what we are seeing in Italy right now is a clear example of that distinction.  

In Italy, mandatory B2B e-invoicing through SDI has been in force since 2019, built on a platform live since 2014, and even the smallest businesses have been in scope since 2024. And yet we still see first-pass rejection rates consistently running between 15 and 20%. We’re not talking about the early months of the mandate, when teething problems were expected like we see in other parts of the continent, this is a market where e-invoicing has been normal for years. But the leading cause of those rejections isn't a lack of knowledge about the mandate, it's simple master data errors. One wrong digit in a VAT ID or a legal entity name that doesn't match the tax authority's records and your cash is stuck. As I often put it: automation doesn't fix bad data, it exposes it. SDI is simply the magnifying glass.  

To me, this isn’t really a knowledge problem, it’s more of a legacy way of doing things that e-invoicing is overhauling in front of our eyes. Under the old model of periodic filing and post-audit reconciliation bad master data was a problem, for sure, but a manageable one. When you can go in after the fact and make manual changes there was always a time buffer available to make quick fixes before they cause any damage.  

But we now live in a world of real-time audits where every invoice is a compliance event and there is no slack left in the system.  

The implications of this run throughout businesses. For tax, the job shifts from monthly reconciliation to ‘get it right first time’. For finance, DSO becomes a data quality metric and month-end surprises no longer happen at month-end but are visible right now. For IT, master data governance is no longer a ‘someday’ project but a cornerstone for any business doing cross-border trade.  

These all add up to a different set of rules for doing business.  

Tax Engine ROI for E-Invoicing  

In this context, the business case for fixing this is straightforward, especially once you see the impact this is having in Italy, which is already a mature market for e-invoicing. In fact, the conversation shifts from being one about compliance to one about the damage that poor master data is already doing. We can now put a number on what it is costing businesses in Italy and what it could cost in countless other countries bringing in e-invoicing mandates imminently.  

The numbers are striking. Businesses operating with a proper tax data foundation process invoices at 15 times the rate of those managing compliance manually. They save €37 per invoice in processing costs, and can expect first-pass rejection rates to fall to around 5%, much lower than the 15-20% that we’ve seen in Italy. At scale, that really is a meaningful saving.  

But the solution here isn’t bolting a compliance layer on top of your existing system, otherwise tax determination and e-invoicing will still run in parallel and continue to cause issues with master data.  

Beyond Compliance: The Real Value of a Tax Engine  

We know the importance of good data, but we also know that businesses that treat master data readiness as a project with a start point and end point will find themselves back in the same position every time a mandate changes. As I’ve argued previously, ‘readiness’ here isn’t a box checking exercise, it’s the ability to be compliant even when the rules change.  

What's required is a disciplined system where tax-relevant data has clear ownership, a standardized taxonomy that everyone in the business works from, and quality enforced at the point of creation rather than corrected downstream. Where execution data such as destinations, formats, tax context or customer rules are treated as truly important master data and where performance is monitored continuously, not audited downstream in a bid to correct problems later.  

If I could say one thing to European leaders, it would be this: what a tax engine brings to your business is far more than just a compliance layer on top of your e-invoicing solution. It’s merging your tax determination and e-invoicing into one layer so that you get this right first time.  

The skepticism European leaders feel around investing in a tax engine isn't unreasonable. When you already understand the mandates, and you already have compliance infrastructure in place, I get that it feels like the job is already done. But as we have seen in Italy this isn’t the case, and complacence has a real, hard cost.  

The irony is that European businesses have already solved the harder half of this problem with their knowledge of mandates both live and upcoming. But European businesses also know that e-invoicing mandates are piling up thick and fast. They have the chance to solve the problems we’ve seen in Italy now before those same problems start to compound in dozens of other countries at once.