Blog - E-invoicing & e-document exchange | Maventa

E-invoicing is becoming mandatory for SaaS: meet ViDA | Maventa

Written by Max Söderlund | 2.6.2026

 

Featuring Max Söderlund, Partner Manager, and Heikki Malkamäki, Managing Director at Maventa

By 1 July 2030, every invoice sent and received in cross-border B2B trade within the EU has to be an EN standard e-invoice. Paper and PDF invoices will be phased out. Companies trading across EU borders will only need to register their VAT once.

This is ViDA, the EU's VAT in the Digital Age reform. The 2030 deadline gets most of the headlines, but the practical pressure is closer than that. Member states are introducing their own mandates ahead of the EU-wide timeline, and the second wave of the reform, real-time digital reporting, is already on the calendar.

For SaaS companies serving European customers, ViDA is two things at once. It's a compliance deadline arriving sooner than 2030 suggests. It's also the foundation for a second layer of change that most teams haven't started thinking about yet.

The first wave: compliance

The first wave is what most teams have started thinking about. It's the part where the legal requirements arrive, businesses need a way to send and receive structured e-invoices, and software vendors either support that natively or watch their customers look elsewhere.

This wave is happening now. Belgium has been live with mandatory B2B e-invoicing since January 2026. Germany has required all businesses to be able to receive structured e-invoices since January 2025, with issuing obligations arriving for larger companies in January 2027 and extending to all businesses in January 2028. Other markets are sequencing their own rollouts in between. By the time the EU-wide deadline arrives in 2030, the largest European markets will already have been operating under e-invoicing mandates for several years.

For software vendors, the first wave is mostly a build-or-buy question. Either your product supports compliant e-invoicing through your own infrastructure, or it does so through a specialised provider. Both routes get you to the same outcome by the deadline. The choice has more to do with what your team wants to spend its engineering time on. The practical detail on what ViDA requires is worth a closer look for any product team scoping this onto a roadmap.

The second wave: real-time reporting

ViDA introduces digital reporting requirements that move VAT reporting close to real-time. This sit on top of the e-invoicing infrastructure already being built out: it's the digitalisation of VAT by tax authorities across the EU.

For tax authorities, this means a much faster view of what's happening in the market. Fraud cases that historically take years to surface and prosecute become visible in days. For businesses, it means the quality of VAT data becomes a shared responsibility with software vendors. Access points and other e-invoicing operators, the parts of the infrastructure that transmits structured data into national networks, take on real legal weight.

Compliance is the start, not the end

Once the compliance infrastructure is running, structured invoice data starts doing more useful work. It enables automated invoice approval, gives finance teams a real-time view of receivables and payables, and support working capital decisions. It also feed analytics and AI models with clean structured information that used to be locked inside PDFs.

This is where the long-term value sits. Software vendors that pick an e-invoicing provider built for both compliance and what follows, will be ready to capture it.

What this means for SaaS leaders?

There are three practical implications for SaaS businesses:

  • A multi-market approach is worth it even if you're focused on local growth right now. Plans change, customers expand and acquirers come looking. There's plenty of multi-market e-invoicing API providers available that track legislation across all of them for you.
  • Running your own Peppol Access Point is heavier commitment under ViDA. Access points handle critical pieces of e-invoicing infrastructure. Fines and sanctions are likely to follow compliance failures. 
  • Your choice of e-invoicing provider matters more than it might seem. Switching providers later on is expensive and slow. Choosing one already built for what comes next avoids the rebuild down the line.

Join the forerunners

Companies handling ViDA well are forerunners: they help their customers through the regulatory shift early, while preparing for what comes after. They build for compliance with the value layer already in view, and pick partners who think the same way.

ViDA brings compliance, automation, and finance infrastructure into the same conversation. The teams that plan for all of it will be compliant and well placed for what European e-invoicing turns into next.

Frequently asked questions about ViDA

What is ViDA?

ViDA, short for VAT in the Digital Age, is a legislative reform from the European Commission that modernises the EU's VAT system. It introduces mandatory e-invoicing and near real-time digital reporting for cross-border B2B transactions within the EU by 1 July 2030, allows member states for require e-invoicing for domestic transactions, and creates a single VAT registration for companies trading across EU borders.

When does ViDA take effect?

The EU-wide deadline for mandatory e-invoicing on cross-border B2B transactions is 1 July 2030. Several member states are already running their own mandates ahead of that timeline. 

What does ViDA mean for SaaS companies?

For SaaS companies serving European customers, ViDA turns e-invoicing into a product question. In markets that are already live, customers expect compliant e-invoicing through the software they use. Vendors that don't support it risk losing customers to vendors that do. The build window has effectively closed in some markets and is closing fast in others.

Should SaaS companies build or buy their e-invoicing capability?

Most software vendors find that partnering with a specialised provider is more sustainable than building in-house. Building yourself typically takes 12 to 24 months and requires ongoing engineering, security, and compliance investment to stay aligned with regulations across multiple markets. The f is worth a careful look before committing capacity to e-invoicing infrastructure.