E-invoicing compliance hospitality Europe is no longer a 2030 problem. The VAT in the Digital Age package adopted by the Council on 11 March 2025 set 1 July 2030 as the intra-EU B2B deadline, but the national mandates have already started cascading. Belgium went live on 1 January 2026. Poland follows in February. Greece in March. France in September. Germany completes its sender obligation by 2028. For a hotel group with properties in four or more EU markets, the next eighteen months will force a decision that AP teams have been able to defer for years: run country-by-country tactical compliance, or rebuild the AP architecture once for the whole EU footprint.
We think the right answer is the harder one, and we think it has to be made in 2026.
What ViDA requires for e-invoicing compliance hospitality Europe
ViDA is a three-pillar reform: digital reporting requirements, platform economy rules, and a single VAT registration. The pillar that touches procure-to-pay is the digital reporting requirement, which mandates that intra-EU B2B transactions move to structured e-invoicing under the EN 16931 standard from 1 July 2030, with transaction data reported to tax authorities within ten days.
The package also unlocked something that matters more in the short term. From 14 April 2025, Member States no longer need a derogation from Brussels to impose domestic B2B e-invoicing mandates. That removed the bottleneck that had slowed national rollouts, and it explains the 2026 to 2028 cascade now in flight. Legacy domestic reporting systems in place before 2024 (Italy, France’s e-reporting precursor) have until 2035 to align with the EU standard, but anything introduced after January 2024 must conform to ViDA by July 2030.
For hospitality, the implication is concrete. A 60-property group with operations in Belgium, France, Germany, Poland, Greece, and the Netherlands will face five or six distinct domestic mandates between 2026 and 2028, then a single intra-EU regime in 2030, then a final harmonisation milestone in 2035. AP cannot treat these as independent projects.
The 2026 cascade, country by country
Belgium moved first. B2B e-invoicing has been mandatory since 1 January 2026 via the PEPPOL network using EN 16931, with a three-month tolerance period that ended on 31 March. Paper and PDF invoices no longer satisfy VAT requirements for domestic Belgian B2B supply. Foreign suppliers selling into Belgian buyers must be PEPPOL-reachable.
Poland’s KSeF model is different. Large taxpayers (PLN 200 million in 2024 gross sales) joined the mandatory KSeF clearance regime on 1 February 2026, with all other VAT-registered entities following on 1 April 2026. KSeF is centralised: invoices route through the tax authority’s platform rather than a peer-to-peer network. Penalties for non-compliance are largely deferred to January 2027, but the receiving obligation begins immediately.
Greece’s myDATA approach is closer to a clearance CTC model. Mandatory B2B e-invoicing for resident large businesses (annual turnover above €1m) begins on 2 March 2026 with a two-month soft-launch period, and Phase 2 extends to remaining resident taxpayers from October 2026. Invoices transit the myDATA platform to receive a unique identifier before they are legally valid.
France’s revised timeline is the most consequential for groups with shared service centres. All businesses must be able to receive e-invoices from 1 September 2026, with issuance and reporting mandatory for large and mid-sized companies on the same date, and SMEs and micro-enterprises following in September 2027. The French model also shifted in October 2024 when the government abandoned the Portail Public de Facturation as a transmission channel, forcing taxpayers to choose a private accredited Plateforme de Dématérialisation Partenaire (PDP).
Germany’s sender obligation lands later but with the same structural impact. The receiving obligation has been live since 1 January 2025; mandatory issuance applies from 1 January 2027 to businesses above €800,000 in prior-year turnover, then extends to all businesses from 2028.
Country-by-country compliance: the tactical path
The first approach is to treat each mandate as a standalone project. Local finance teams pick a country-specific provider, plumb a single integration into the property-level or country-level AP system, and meet each deadline with the minimum viable architecture.
This path is faster to start. It is also the most expensive to operate beyond 2027.
The hidden cost is integration count, not licence cost. A group operating in five mandate countries ends up with five clearance or transmission channels, five sets of country format variants (Factur-X, XRechnung, FA(3), PEPPOL BIS 3.0, myDATA UID), and five operational runbooks. Each property AP team learns a different validation workflow. Master data (supplier VAT IDs, PEPPOL participant IDs, banking details) gets maintained in parallel across systems, which is where reconciliation breakdowns surface. When ViDA’s intra-EU regime activates in 2030, none of the country-specific work transfers cleanly to the cross-border digital reporting requirement. The group then runs a sixth project on top of the five existing regimes.
A useful framing: the country-by-country path optimises for the next deadline. The single-architecture path optimises for the next decade.
Single EU-wide AP architecture: the strategic path
The alternative is to redesign AP once, with the 2030 intra-EU regime as the target end state, and use the 2026 to 2028 national mandates as the forcing function.
In practice this means three commitments. First, standardise on EN 16931 as the single canonical invoice format across the group, with country-specific syntaxes (XRechnung, Factur-X, FA(3), UBL 2.1) generated as outbound variants from one master record. Second, default to PEPPOL as the transmission rail wherever the national mandate permits it, and integrate to centralised clearance platforms (KSeF, myDATA, the eventual French PDP network) only where the national model requires it. The PEPPOL network now counts 1.4 million registered companies globally and is the designated rail for Belgium, the Netherlands, and an expanding list of mandate countries, which makes it the closest thing the EU has to a default. Third, consolidate AP automation onto a single platform that abstracts the compliance layer from the operational layer, so AP teams in Brussels, Warsaw, Athens, Paris, and Berlin work the same exception queue regardless of which national regime cleared the invoice. We covered the rail decision in more detail in our analysis of PEPPOL as the default e-invoicing network for hospitality.
This is the harder path because it requires AP, IT, group tax, and procurement to agree on a target architecture before any single mandate forces the conversation. In a federated hotel group with property-level autonomy, that alignment is the project. The technology is the easier part.
The decision lens for 2026
Three tests separate groups that can defer this decision from groups that cannot.
The first is country count. A group with operations in two mandate countries can survive tactical compliance. A group with operations in four or more cannot, because the integration and master-data overhead compounds non-linearly.
The second is shared-service-centre maturity. A group that has already centralised AP into one or two regional hubs has the operating model to absorb a single-architecture redesign. A group with property-level AP is solving two problems at once: the compliance redesign and the underlying centralisation. That sequencing matters.
The third is M&A pipeline. Groups acquiring properties in mandate countries inherit whatever compliance posture the target chose. A single-architecture standard makes integration testable. Five country-specific regimes make it a finance integration project every time. The fourth, which we treat as a tie-breaker, is whether the group’s AP automation roadmap is currently in scope. The ViDA cascade is forcing AP modernisation to happen anyway. Groups that were planning to modernise procurement automation in 2026 to 2027 should absorb the compliance work into that programme rather than running it separately. That is also the right moment to settle the build-versus-outsource question we examined in our comparison of in-house procurement automation and BPO models for hospitality.
Our take
The country-by-country path is the default that hospitality AP teams will fall into if the architecture conversation does not happen in 2026. It is not wrong on any single deadline. It is wrong on the trajectory.
The cascade between Belgium in January 2026 and Germany’s full sender obligation in 2028 is the cheapest window the industry will get to redesign AP for an EU-wide reality. Once national regimes calcify around different platforms, providers, and operational habits, the cost of consolidation rises. ViDA’s intra-EU regime in July 2030 is the deadline. The 2026 to 2028 national cascade is the opportunity. They are the same project.
Procurement and finance leaders at hospitality groups with multi-country footprints should treat the next eighteen months as the architecture decision, not the compliance one.