EU VAT Compliance for Multinationals Through 2030

How OSS, e-invoicing, and ViDA change the compliance model and why accurate VAT determination at transaction creation matters

EU VAT compliance failures often begin before the return is prepared. They begin when a transaction is created in the ERP and the wrong VAT treatment is applied. If that error is not corrected, it can be repeated across thousands of invoices before it reaches a filing or an audit.

For multinationals, the direction of travel is clear. E-invoicing mandates and the EU's VAT in the Digital Age package are moving invoice data and digital reporting closer to the moment of issuance. Reliable compliance therefore requires three connected layers: correct VAT determination at source, country-specific e-invoicing integration, and reporting based on the same transaction record.

The central control

The accuracy of an e-invoice, digital report, or VAT return depends on the VAT treatment applied when the underlying transaction is created.

How EU VAT works for multinationals

The EU VAT Directive 2006/112/EC sets the framework implemented by all 27 EU member states. National rules still vary significantly, including VAT rates, exemptions, registration thresholds, filing calendars, return formats, and submission channels. There is no single EU VAT return.

A multinational must manage four connected obligations:

• Apply the correct VAT treatment when each transaction is created.
• Register and deregister accurately as business activity moves across borders.
• File complete and timely periodic returns in every country of registration.
• Meet real-time or near-real-time invoice reporting requirements as national mandates expand.

Only the first obligation is a tax engine question. It is also the obligation on which the other three depend. A return or real-time report built on incorrect determination remains incorrect, even when the data is delivered efficiently.

What OSS and IOSS simplify

OSS simplifies filing rather than tax determination

A business using OSS still needs to identify the customer's member state and apply the correct local VAT rate to every B2C transaction.

The One Stop Shop regime has operated since July 2021. It allows businesses selling to consumers across EU member states to register for VAT in one member state and file one quarterly OSS return covering their B2C EU sales. It replaced the previous distance-selling threshold regime, under which separate VAT registrations were required once sales to consumers in a country exceeded that country's threshold.

The Union OSS covers intra-EU distance sales of goods, including sales by non-EU sellers, and B2C services supplied by EU-established businesses. A separate Non-Union scheme applies to non-EU service providers. The Import One Stop Shop covers goods imported from outside the EU with an intrinsic value not exceeding EUR 150.

These schemes reduce the administrative burden of multi-country registration. They do not remove the need to determine the correct destination country and local VAT rate. They also require a detailed return that reconciles sales by country and rate. A multinational using OSS therefore still needs determination logic that can resolve the correct rate for 27 possible destinations on every B2C transaction.

Why e-invoicing raises the compliance stakes

E-invoicing mandates are spreading across EU member states, but the mandates are not uniform. Each mandate has two dimensions that multinationals must manage.

Transmission

Transmission is how the invoice travels. Depending on the country, an invoice may pass through a national clearance platform, a certified service provider, Peppol, or a direct exchange between trading parties. Formats, channels, certification requirements, and validation rules differ by country and change on national timetables. This is an integration and connectivity challenge.

Content

Content is what the invoice says. It includes the VAT treatment, VAT rate, exemption reference, counterparty identification, and transaction qualification embedded in the structured data. A structured invoice can clear a national platform while carrying the wrong VAT treatment. In that case, the error has been validated, timestamped, and placed in a tax authority's database.

Under paper and PDF invoicing, a determination error could sometimes be found during return preparation, reconciliation, or internal review before an authority saw it. Mandated e-invoicing sends transaction data to the authority at or near issuance. The window for downstream correction shrinks, and credit notes or corrective invoices create a visible trail through the same channels.

The treatment of invoice data also differs by regime. Some mandates currently focus on structured exchange between businesses. Others combine e-invoicing with near-real-time transactional reporting. A growing group of member states uses collected invoice data to produce pre-filled VAT returns. In those regimes, the business must validate and reconcile its records against the authority's version of the same transactions.

Three operational consequences

1. First-time-right determination becomes the control. When invoice data is transmitted at issuance, VAT treatment must be correct when the transaction is created. There is no downstream layer where errors can be corrected without creating a visible record.
2. One transaction record must support every output. The same transaction may feed an e-invoice in one country, a transactional report in another, and a pre-filled return in a third. Those outputs must remain consistent with each other and with the VAT return.
3. Reconciliation becomes continuous. Authorities increasingly hold transaction-level data and can match it against filings and counterparty data. Businesses need an internal capability to identify mismatches before the tax authority does.

ViDA timing and implications

The Council formally adopted the VAT in the Digital Age package on 11 March 2025, and it entered into force on 14 April 2025. ViDA is adopted law. Its measures apply progressively through 2035 across three pillars: digital reporting requirements, platform economy rules, and single VAT registration.

April 2025

Member states may require taxable persons established in their territory to issue e-invoices for domestic supplies without prior EU derogation.

This option does not extend to non-established businesses that are merely VAT-registered in the country.

1 January 2027

The first refinements to the platform deemed-supplier rules and the OSS and IOSS schemes apply.

Review affected platform and scheme processes before the effective date.

1 July 2028

The single VAT registration pillar applies. It extends OSS to additional B2C flows, introduces a scheme for cross-border transfers of own goods, and adds a broader mandatory reverse charge where the supplier is neither established nor VAT-registered in the member state and the customer is identified there.

This creates a deregistration opportunity, especially for cross-border stock movements. Member states may apply the platform economy rules from this date; those rules become mandatory in January 2030.

1 July 2029

The call-off stock simplification's register and recapitulative-statement provisions are removed as the transfers-of-own-goods scheme takes over that function.

Processes relying on the current call-off stock provisions will need to align with the new scheme.

1 July 2030

Mandatory structured e-invoicing and near-real-time digital reporting apply to intra-EU B2B transactions.

VAT treatment must be accurate when the invoice is issued because transaction-level data will reach authorities shortly after issuance.

1 January 2035

Member states with domestic real-time reporting regimes in place, or authorised, before 2024 must harmonise them with the EU standard.

The Directive allows this deadline to be revisited following the interim evaluation.

What the timeline means for multinationals

The single VAT registration pillar simplifies where a business registers. It does not simplify the VAT treatment of the underlying transactions. Fewer registrations can place more transaction types into fewer returns, concentrating the determination burden. OSS-style consolidation works only when the rate and treatment for each destination country are correct.

The digital reporting requirements pillar will send invoice data for intra-EU transactions to authorities shortly after issuance and at transaction level. At enterprise volume, that reporting can be reliable only when VAT treatment is determined correctly at the source in the ERP, rather than corrected later in a reporting tool. Determination at source makes real-time reporting accurate as well as fast.

Common EU VAT compliance failures

For large multinationals, frequent failure points fall into five categories.

Intra-EU supplies exempted without all conditions

Exempting an intra-Community supply with right of deduction, which UK and Irish practice calls zero-rating, requires more than proof of transport. Since the 2020 quick fixes, the customer's valid VAT identification number, communicated to the supplier, and a correct recapitulative statement are substantive conditions of the exemption itself rather than formalities. Transport evidence, such as CMR documents, transport records, or customer confirmation, is the evidential layer on top. If any of the three elements is missing, the exemption is exposed, and the error can compound across every shipment on the same flow.

Services place-of-supply errors

B2B services are generally taxable where the customer is established. Exceptions apply to immovable property services, admission to events, passenger transport, and the short-term hire of means of transport. A common misconception runs in the other direction: digital TBE services have special place-of-supply rules only for B2C transactions. In B2B transactions, they follow the general rule. Misclassification is common when the service type is ambiguous or bundled.

Destination-country VAT after the threshold

Suppliers established in a single member state benefit from the EUR 10.000 EU-wide B2C threshold. Once that threshold is exceeded, destination-country VAT applies from that point onward. A company that continues charging domestic VAT instead of accounting for destination-country VAT through OSS or local registration can build up under-assessment risk in every destination country.

Triangulation omitted or applied incorrectly

When goods move from Country A to Country C but are supplied through a party in Country B, the triangulation simplification may apply. It applies only if the intermediate party actively invokes it and the invoice includes the required references. Getting this wrong typically results in unexpected VAT registrations or assessments.

E-invoicing channel and content failures

Sending invoices outside a mandated channel, such as using a PDF where a clearance platform or certified provider is required, generally means that the invoice has not been validly issued in that jurisdiction. Consequences differ by regime. Clearance models invalidate the invoice, while reporting models penalise the omission. In both cases, the root cause is usually wrong or incomplete transaction data feeding the invoice at determination.

The infrastructure multinationals need

Reliable EU VAT compliance requires three layers that work in sequence.

Determination at source

Resolve VAT treatment correctly when each transaction is created in the ERP, across every flow and jurisdiction where the business operates.

Creates the VAT result used downstream

E-invoicing integration

Route invoices through country-specific clearance or exchange channels in the required formats.

Uses the VAT result in the structured invoice

Reporting

Produce accurate country-specific VAT returns, OSS filings, and digital reports from the underlying transaction data.

Uses the same transaction data in filings and reports

The layers are distinct, but the second and third layers can be only as accurate as the first. An e-invoice that clears through SdI or KSeF with the wrong VAT treatment remains an error. A real-time report based on incorrect data reports that error faster.

Where Taxmarc fits

Taxmarc operates at the first layer. It is a global indirect tax determination engine built natively inside SAP. It resolves VAT treatment when the transaction is created, providing the foundation on which e-invoicing and reporting solutions depend. As authorities gain near-real-time visibility, the cost of incorrect determination moves from a year-end correction toward per-transaction exposure. Determination at source is therefore the first layer to address.

About the author

Peter Boerhof has more than 25 years of indirect tax experience across in-house, advisory, and tax technology roles. He is a former member of the EU VAT Expert Group.