ViDA for UK SaaS: 2027, 2028 and 2030 VAT Deadlines Explained

Most SaaS founders have heard of ViDA — VAT in the Digital Age — and filed it away as a 2030 problem.

It isn't.

The EU adopted the core ViDA package in March 2025 (Directive 2025/516, Regulation 2025/517, and Implementing Regulation 2025/518). The EU has since moved from political agreement into implementation planning, with changes phasing in from 2027 through 2035. The first relevant deadline for many OSS/IOSS users is 1 January 2027. Founders who wait until 2030 to understand the data requirements will likely be rebuilding invoice and VAT workflows under pressure.

This post breaks down each phase in plain English: what changes, when it takes effect, and what UK and EU SaaS companies should be doing at each stage.

This article is for educational purposes only and does not constitute formal tax advice. For complex cases, consult a qualified accountant or tax adviser.

What is ViDA?

ViDA is the EU's most significant VAT reform in decades. The core aim is to modernise how VAT is reported and verified across EU member states — replacing paper-based and batch-reporting systems with structured, digital, often real-time data flows. The official Commission ViDA page summarises the full package and rollout schedule.

For SaaS companies, the most relevant changes are:

• Updates to how OSS (One Stop Shop) and IOSS (Import One Stop Shop) operate
• A redesigned VIES system for cross-border B2B validation
• New mandatory digital reporting requirements for intra-community B2B transactions
• Changes to single VAT registration rules

The reforms roll out in three main phases — 1 January 2027, 1 July 2028, and 1 July 2030 — with further harmonisation continuing through 2035, according to the official Commission ViDA rollout schedule.

---

January 2027 — The first relevant deadline

What happens: The first ViDA changes affecting OSS and IOSS processes begin to apply. For most SaaS companies, this is not the major digital reporting shift — it is a narrower operational update to OSS/IOSS rules and invoice and reporting data requirements.

This is a technical update to the implementing regulation that underpins how non-Union OSS works in practice, described by the Commission as minor legislative clarifications for OSS/IOSS users. The substantive changes — digital reporting, SVR, e-invoicing infrastructure — come later.

Some structured invoice data fields may become relevant depending on your invoice format and VAT setup. This is worth confirming with your accountant and invoicing provider before Q4 2026 — implementation timelines for invoice format changes are longer than they look.

What this means for UK SaaS using non-Union OSS

UK SaaS companies selling B2C digital services to EU customers typically use the non-Union OSS scheme (registered in one EU country, reporting VAT for all EU B2C sales through that single registration). The January 2027 changes are the right moment to:

• Confirm with your accountant which OSS/IOSS rules are changing and whether any apply to your current setup
• Check whether your invoicing system (Stripe, Xero, or a combination) will satisfy any new data field requirements for EU B2C invoices
• Ensure your OSS filing process is documented and not dependent on manual steps that a new requirement could break

What you do not need to do yet

The bigger ViDA changes — mandatory digital reporting, SVR, large-scale e-invoicing infrastructure — are not live in January 2027. If you are on non-Union OSS and your invoice format is standard, the immediate impact may be limited. But it is worth confirming rather than assuming.

---

July 2028 — The structural shift

This is the phase that changes how cross-border VAT works at an operational level. Several major changes take effect simultaneously.

1. Mandatory Single VAT Registration (SVR)

Currently, an EU business may need to register for VAT in multiple member states depending on their activity. SVR extends the OSS model so that a much broader range of cross-border supplies can be reported through a single registration rather than requiring multiple country-specific registrations.

For EU SaaS companies, this is largely positive — it should reduce compliance overhead. For UK SaaS companies already using non-Union OSS, the practical impact depends on how the SVR rules interact with the existing scheme in your OSS registration country.

2. VIES redesign and the shift away from EC Sales Lists

The existing VIES system — the EU's database for validating VAT registration numbers — is being redesigned as part of ViDA's broader cross-border VAT data infrastructure. In parallel, the ViDA reporting architecture will move away from today's EC Sales List-style reporting toward structured, transaction-level digital reporting.

This has direct implications for reverse charge workflows. Today, validating a customer's EU VAT ID against VIES is best practice but the underlying data quality is variable across member states. As VIES becomes a more centralised, authoritative system, the validation result you get back will carry more weight — and the expectation that you validated is likely to be higher.

If your current process involves manually checking VIES, or relying on Stripe's built-in VAT ID verification (which checks format, not VIES), July 2028 is the point at which that approach looks increasingly insufficient.

What you should be doing ahead of this:

• VIES validation for every B2B reverse charge transaction, with the result stored and timestamped against the transaction
• Re-validation on a schedule (30-day cache is a reasonable starting point given current VIES reliability)
• An audit trail that records the validation result at the time of each transaction

For more on why Stripe's built-in verification is not a substitute for VIES validation, see Why Stripe VAT ID Verification Is Not Enough for Reverse Charge.

3. Transfer of Own Goods (TOOG) rules

The TOOG rules apply where a business moves its own stock across EU borders — relevant mainly for businesses with physical goods inventory in multiple EU countries. For pure SaaS companies with no physical goods, this change is unlikely to affect you. Worth confirming with your accountant if you have any physical distribution operations.

4. Deemed-supplier rules for platforms

July 2028 also brings expanded deemed-supplier rules for digital platforms in the short-term accommodation and passenger transport sectors. This is specifically scoped to those industries. SaaS companies are not directly in scope here — but if your product serves platforms in those sectors, your customers may have new VAT obligations that affect how they use your invoicing and reporting data.

---

July 2030 — Digital reporting goes live

This is the change most people associate with ViDA, and it is the most significant for cross-border B2B operations.

What changes

From July 2030, mandatory digital reporting requirements (DRR) begin applying to cross-border B2B intra-community transactions. The requirement is real-time or near-real-time submission of structured invoice data directly to the relevant tax authority.

In practice, this means:

• Every B2B invoice for an intra-community supply (where you sell to a VAT-registered EU business in a different EU country) must be issued as a structured, machine-readable document
• The invoice data must be submitted digitally to the tax authority — not filed in aggregate at month-end, but transactionally
• Implementation guidance is still being finalised, so SaaS companies should treat 2027–2030 as the preparation window rather than waiting for the final deadline

The preparation window is now

The fact that digital reporting doesn't go live until 2030 does not mean the preparation work starts in 2029.

The data format requirements are expected to become clearer during the 2027–2030 preparation window. If your invoicing and data pipeline cannot generate structured invoice data at transaction level, this is a multi-year infrastructure project — not a two-month sprint.

The key question to ask now: can your current invoicing setup produce a structured, machine-readable invoice for every B2B transaction? If the answer is "we export from Stripe and clean it up in Xero at month-end," you already know the gap.

UK SaaS and the 2030 rules

The 2030 digital reporting obligation applies to intra-community EU B2B transactions. This means it applies to EU-registered businesses making those supplies — it does not directly apply to UK companies on non-Union OSS.

However, if you have any EU-based legal entity or plan to establish one before 2030, the digital reporting requirements will apply. And even for UK-only operations, the practical reality is that EU business customers will increasingly expect structured invoice data in return — because their own systems will be built around receiving it.

What about 2035?

The ViDA rollout continues past 2030. Member States with existing domestic real-time reporting systems have until 1 January 2035 to align those systems with the EU digital reporting standards. For most SaaS founders, the practical planning milestone remains 2030 — that is when cross-border B2B DRR begins. But if your customers include large EU businesses or public-sector entities with domestic e-invoicing requirements, the 2035 harmonisation is worth being aware of.

---

The guidance gap — what we don't know yet

It would be misleading to present ViDA as fully resolved. As of June 2026, there are still significant details outstanding.

The detailed technical guidance that translates the ViDA legal framework into practical implementation requirements is not yet final. Material guidance is expected through H2 2026 and into 2027, and the next key EU drafting session is 25 June 2026.

What this means in practice:

• The high-level deadlines are confirmed. 1 January 2027, 1 July 2028, and 1 July 2030 are locked.
• The detailed implementation requirements for some areas — particularly digital reporting data formats — are still being drafted.
• "Wait until the guidance is final" is a reasonable position for detailed technical implementation. It is not a reasonable position for understanding the scope, building internal awareness, or planning your systems roadmap.

The right posture right now is to know the shape of what's coming, identify which phases affect your business, and flag the questions you'll need to answer once the guidance drops.

---

A practical timeline

Date	What changes	Action
Now — Q3 2026	—	Identify which ViDA phases affect your business. Confirm OSS scheme setup with accountant.
Q4 2026	—	Check invoice data requirements ahead of January 2027. Engage invoicing/accounting software providers.
1 January 2027	OSS/IOSS operational rules updated. Some invoice data field requirements begin to apply.	Confirm with accountant and invoicing provider whether changes affect your setup.
2027–2028	EU guidance on 2030 digital reporting formats expected	Follow guidance publication. Plan data infrastructure requirements.
1 July 2028	SVR changes begin. VIES infrastructure evolves. Platform and TOOG-related rules take effect. DRR preparation continues.	Ensure VIES validation is automated and auditable for all B2B reverse charge transactions.
1 July 2030	Mandatory digital reporting for all cross-border B2B intra-community transactions	Structured invoice generation and real-time submission operational.
1 January 2035	Domestic real-time reporting systems across Member States harmonised to EU DRR standards	Relevant mainly if you have EU-entity operations or serve large EU enterprises with domestic e-invoicing requirements.

---

Where Clearkite fits

The ViDA reforms are fundamentally about data quality and auditability — the same problem Clearkite solves for today's Stripe-to-Xero workflow.

The July 2028 VIES changes strengthen the case for automated, stored VAT ID validation — moving it closer to a compliance expectation rather than just best practice. Clearkite validates every B2B transaction against VIES, stores the result with a timestamp, and links it to the transaction — so when the VIES infrastructure becomes more authoritative in 2028, the audit trail is already there.

The July 2030 digital reporting requirement makes structured, transaction-level invoice data a regulatory requirement. The first step in getting there is having clean, classified data at the transaction level — not a spreadsheet export from Stripe every month.

For a broader overview of how VAT classification currently works for UK SaaS on Stripe, see Stripe VAT for UK SaaS: A Practical Guide.

---

Don't wait for 2030 to start

ViDA is not a single deadline — it's a rolling compliance ladder with the first step on 1 January 2027. The companies that will handle the 2028 and 2030 changes without scrambling are the ones building clean VAT workflows now.

Know which phases apply to your business. Talk to your accountant before Q4 2026 about the January changes. And start asking whether your current Stripe-to-Xero pipeline can generate the transaction-level data that regulators will eventually require.

Get early access to Clearkite's Stripe-to-Xero VAT workflow →

---

Sources: European Commission — VAT in the Digital Age · Commission adoption announcement · Directive 2025/516 · Regulation 2025/517 · Implementing Regulation 2025/518 · KPMG ViDA summary