ViDA single VAT registration: what implementing regulation 2026/1869 means for your systems

The technical blueprint for ViDA single VAT registration is now on the table. With Implementing Regulation (EU) 2026/1869, adopted on 27 July 2026 and published in the Official Journal on 28 July 2026, the European Commission has set out how the One Stop Shop, the Import One Stop Shop and the new scheme for the transfer of own goods will work operationally. The regulation entered into force twenty days after publication, in mid-August 2026. For anyone who builds software, maintains integrations or owns VAT processes, this is not background reading. It is a development document.

The fact that it appeared in the middle of summer explains why it is still absent from many roadmaps. That is a problem, because the first application date is closer than most planning assumes.

Why this matters if you work with e-invoicing

At first glance this looks like a file for the tax department. Registration, returns, One Stop Shop: not words that usually surface in an integration project. There is still a good reason to read it as a Peppol Serviceprovider, ERP vendor or integrator.

The regulation standardises exactly the data that also appears on an e-invoice and that has to be correct in Peppol exchange: VAT identification numbers, fixed establishment details, VAT group status, status as an electronic interface. That is master data. Getting it in order now for the registration changes of January 2027 also does the groundwork for the digital reporting obligations that follow later this decade. Treat this regulation as something for tax specialists only, and in 2028 you will discover that the same master data does not line up with your invoicing flows.

Two pillars that are constantly confused

ViDA, VAT in the Digital Age, is not a single measure but a package with several pillars. Two of them are routinely mixed up in practice, and that leads to planning errors.

The single VAT registration pillar

This pillar covers where and how often a business has to register for VAT, and how it files returns. Implementing regulation 2026/1869 belongs here. The objective is that a business operating in several member states can handle that through one registration instead of a handful of local ones. The relevant dates fall in 2027 and 2028.

The digital reporting requirements pillar

This pillar covers e-invoicing and digital reporting: exchanging structured invoices and supplying transaction data to the tax authority. This is where Peppol sits. The cross-border obligation within the EU only starts on 1 July 2030. Member states may move ahead nationally in the meantime, and they are doing so. The ViDA state of play by country shows how widely that pace varies, and the first stage of Spain’s ViDA implementation is a concrete example.

Why the distinction matters: the deadlines are years apart, the systems are different systems, and in most organisations different project teams own them. A tax team working on OSS registration in 2027 is not automatically the same team that has to connect the Peppol accesspoint in 2030. Treat the two tracks as one project and your scope will be wrong. Keep them entirely separate and you will miss the overlap in master data.

What ViDA single VAT registration changes technically

Implementing regulation 2026/1869 amends Implementing Regulation (EU) 2020/194 and thereby implements the ViDA directive, Council Directive (EU) 2025/516 of 11 March 2025. One point is essential to understand: the regulation does not introduce new VAT policy. It sets the operational and technical rules that make the policy workable.

The core changes:

• A fourth scheme. Alongside the existing non-Union scheme, Union scheme and import scheme comes the scheme for the transfer of own goods. That is a new registration type with its own data set.
• Revised definitions. These reflect the broadened scope of the Union OSS.
• Updated formats. Both the electronic registration formats and the VAT return formats have been adjusted.
• Harmonised data exchange. Member states exchange data through central electronic systems, with harmonised status codes for registrations, exclusions and corrections.
• Mandatory pre-filling. Where registration data is already available in national databases, it must be pre-filled.
• Fully replaced annexes. The annexes have not been amended but replaced by new standardised electronic message formats that all member states will use.

The annexes are the real work

That last point deserves emphasis, because summaries tend to reduce it to a subordinate clause. Annex I, which contains the identification data, gains a full new column G for the transfer of own goods scheme. Sections have also been restructured for VAT group status, previous OSS registrations, status as an electronic interface, and a cross-reference to article 284, the small business scheme, has been added.

New data fields being introduced: VAT group status, an electronic interface indicator for platforms, additional VAT identification references, website details, identification data for the transfer of own goods, and more extensive information on fixed establishments and intermediaries.

For a software vendor, a fully replaced message format means not an adjustment but a rebuild of the OSS integration. That is a development budget and a test cycle, not a configuration change that fits in a maintenance window. If your 2027 planning contains a line along the lines of “update OSS formats”, you are probably underestimating the scale.

Pre-filling shifts the work, it does not remove it

The obligation on member states to pre-fill registration data from national databases is usually presented as a reduction in burden. In part it is: less retyping, fewer keying errors, faster registration.

But liability for the accuracy of that data remains entirely with the taxable person. That changes the nature of the work. Where a staff member previously entered data and naturally consulted the source while doing so, they will now be presented with a completed screen that looks finished. Pre-filled fields invite clicking through. If a fixed establishment address is outdated in the national database, or a VAT group status no longer holds, that becomes your problem from that moment on, not the member state’s.

This calls for a different process: an explicit review step with a named owner, rather than a data entry step. Organisations thinking about this now can attach that review to the periodic master data review many businesses already run for their invoicing data.

Digital taxpayer identity: the underlying structure

Behind the individual changes sits a larger movement. From the limited registration changes in January 2027, expanded from July 2028, an EU-level taxpayer profile effectively comes into being. It brings together VAT numbers in multiple countries, fixed establishment details, marketplace status, bank account details and previous registrations.

This is more than an administrative clean-up. It means tax authorities in different member states look at the same picture of your business, built from data exchanged automatically between them through central registers or trusted sharing tools. Inconsistencies between what you registered in one country and what is known in another become visible in a way that was not previously possible.

For anyone following enforcement practice, this is a familiar pattern: better data first, then better detection, then tighter enforcement. How differently member states already handle that is set out in our comparison of fines and soft landing periods for e-invoicing obligations in Europe.

What changes in practice from 1 July 2028

The most tangible effect sits in the transfer of own goods scheme. Today, moving stock from a warehouse in one member state to a warehouse in another is a deemed intra-Community supply and acquisition, which in principle triggers a local VAT registration in the country of arrival. For webshops holding stock in several countries, fulfilment models and businesses that reposition inventory based on demand, those registrations pile up.

From 1 July 2028, many of those businesses will no longer need multiple VAT registrations for cross-border storage or repositioning. Those transfers are reported through a single EU VAT registration. That removes registrations, local returns, local advisers and local deadlines.

The parties feeling this most strongly: OSS and IOSS users, marketplaces acting as deemed supplier, logistics providers, and the software vendors that have to support all these flows.

Timeline: three dates to keep apart

• 1 January 2027 to 30 June 2028. Article 2 of regulation 2026/1869 applies. This covers the first, more limited set of registration changes. This is the date most often overlooked right now.
• 1 July 2028. Articles 1 and 3 apply. The full new message formats, the transfer of own goods scheme and the expanded pre-filling take effect here. This is the date on which single VAT registration genuinely takes effect for many businesses.
• 1 July 2030. By way of contrast: this is when the cross-border digital reporting obligation within the EU starts. That is the other ViDA pillar, covering e-invoicing and Peppol. This date is unrelated to the two above.

The practical meaning of that first date: at the time of writing, 1 January 2027 is less than four months away. For an organisation that first has to run an impact assessment, then free up internal budget, then align with a vendor, that is a tight schedule. For a software vendor that has to get the change into a release and test it with customers, it is tighter still.

What to do now

For the business owner or finance manager

1. Map which member states you are VAT registered in, and why. Make explicit for each registration whether it exists because of stock movement, because of local sales, or for another reason. Only registrations in the first category may fall away from July 2028.
2. Check your master data now, not in 2028. VAT numbers, fixed establishment addresses, VAT group status, and whether you qualify as an electronic interface. These are the fields the new Annex I asks for.
3. Appoint an owner for reviewing pre-filled data. Record who signs off on accuracy and how frequently it is checked. The liability stays with you.
4. Ask your software vendor about their 2026/1869 planning. Specifically: when does support for the new registration formats arrive, when for the transfer of own goods scheme, and is a test environment available. A vendor unfamiliar with the regulation is a signal in itself.
5. Quantify what dropping registrations saves you. Reduced compliance costs, fewer local advisers, fewer filing deadlines. That is the business case with which you free up internal budget for the work that precedes it in 2027.
6. Keep the two ViDA tracks separate in planning, but share the master data. Do not merge the registration changes and the e-invoicing programme into one project, but make sure both teams draw from the same master data source.

For the software vendor or integrator

1. Read the annexes, not the summary. The replaced annexes contain the message formats. That is where the actual development work sits, and it is larger than the article text suggests.
2. Plan a rebuild, not a patch. Assume a full revision of the OSS integration, including data model, validations and error handling against the new status codes for registrations, exclusions and corrections.
3. Model the fourth scheme as its own entity. Transfer of own goods sits alongside the non-Union, Union and import schemes, with its own column G in Annex I. An implementation that treats it as a variant of the Union scheme will break on the differing data set.
4. Add the new fields to your data model. VAT group status, electronic interface indicator, additional VAT identification references, website details, extended data on fixed establishments and intermediaries. Check whether your current schema can store these at all.
5. Build pre-filling as a proposal, not as established fact. Show pre-filled fields visibly as pre-filled, with an explicit confirmation step and an audit trail of who approved what. Your customer carries the liability; your interface should reflect that.
6. Extend one master data source into your e-invoicing module. The same VAT numbers, fixed establishments and platform status return in the reporting pillar. Two separate sources means double maintenance and guaranteed divergence.
7. Treat 1 January 2027 as a hard release date, not a target. Work backwards from it including a customer test period. That means development has to be running now.

What this means for your planning

With implementing regulation 2026/1869, ViDA single VAT registration has moved from a policy intention to a set of concrete message formats with firm application dates. For businesses the gain is real: from July 2028, many will lose the VAT registrations that existed only because stock crossed a border. For software vendors and integrators the task is equally real: replaced annexes mean a rebuild, and the first deadline falls on 1 January 2027. Keeping both tracks apart in planning while bringing the master data together in one source saves you a second migration in 2030.

Want to know which vendors and Peppol Serviceproviders are ready for these changes? Compare the options in our overview of Peppol suppliers.

Sources

1. VATupdate, Commission Implementing Regulation (EU) 2026/1869: new technical rules for OSS, IOSS and the ViDA transfer of own goods scheme
2. TaxSpoc, EU ViDA implementing regulation 2026/1869: OSS and transfer of own goods
3. CB Consulting & Management, article-by-article analysis of the fourth OSS scheme
4. vatcalc, EU unveils digital taxpayer identity for ViDA single VAT registration
5. vatcalc, EU ViDA transfer of own goods reduces VAT registrations