Hungary outlines ViDA direction with mandatory e-invoicing model
Hungary has taken a clear step towards the EU’s VAT in the Digital Age (ViDA) agenda. The National Tax and Customs Administration (NAV) has published a conceptual framework that outlines how the country plans to move from continuous reporting to mandatory e-invoicing.
This direction does not come out of nowhere. Earlier, Hungary already signalled stricter controls and tighter compliance requirements, including changes expected from mid-2025. These developments were outlined in more detail in our previous update on stricter e-invoicing rules in Hungary.
While this is not yet final legislation, the direction is unambiguous. Hungary is preparing for a fundamentally different invoicing model, with direct implications for both finance and IT.
From reporting to structured e-invoicing
Hungary already operates one of the most advanced real-time reporting systems in Europe. That model will now evolve into something more structural.
The key change is that invoice data and reporting will no longer be treated as separate processes. Instead, the invoice itself becomes the data source. This confirms the trajectory described earlier, where Hungary was already preparing for mandatory e-invoicing combined with real-time reporting.
For B2B and B2G transactions, the structured invoice must be submitted to the tax authority as part of the data supply.
Mandatory e-invoicing is expected to apply to:
- Domestic B2B transactions
- Cross-border B2B transactions within the EU
- B2G transactions
Paper invoices will remain limited to B2C and non-EU transactions, but even then, they must originate from structured XML data.
XML becomes the legal invoice
One of the most important shifts is the legal status of the invoice.
Hungary will adopt a data-based invoice model aligned with the European EN 16931 standard, including local extensions. In this model:
- The XML file is the only legally valid invoice
- A human-readable version is optional for B2B
- Any mismatch between XML and visual representation requires cancellation and reissuance
This reflects a broader shift already visible in earlier Hungarian plans, where structured data is no longer just for reporting but becomes the legal foundation of the invoice itself.
Validation moves to the front of the process
Another structural change is where control takes place.
In the future model, invoicing software must validate:
- Mandatory invoice data
- Tax number accuracy
- Structural compliance
If validation fails, the invoice cannot be issued. This effectively shifts compliance checks from after-the-fact controls to real-time prevention.
All invoicing solutions will also require accreditation from NAV. Non-compliant systems risk penalties and loss of approval.
Buyer becomes part of compliance
Hungary goes further than many other EU countries by introducing buyer-side obligations.
Buyers will be required to:
- Report received invoices within five days
- Submit full invoice data for domestic transactions
- Provide additional status reporting with VAT returns
This builds directly on Hungary’s existing reporting model and extends it into a two-sided control mechanism.
For shared service centers and finance teams, this increases the importance of inbound invoice validation and process alignment.
Five-corner model with optional Peppol
Hungary is moving towards a five-corner model, involving both supplier and buyer systems alongside the tax authority.
Peppol will be supported as a transmission network, but not mandated. Instead, Hungary will continue to rely heavily on API-based connections with the tax authority.
Notably, non-secure channels such as email will no longer be allowed for B2B and B2G invoice exchange. Buyers must also be pre-identified before an invoice can be issued.
What this signals for Europe
Although this is still a conceptual framework, the direction is clear and consistent with broader EU developments.
Three trends stand out:
- Structured data becomes the legal and operational foundation of invoicing
- Validation shifts to the moment of invoice creation
- Buyers become active participants in compliance
Hungary is not an isolated case. These elements are increasingly visible in other national approaches to ViDA.
What companies should prepare for
Even without final legislation, this model requires early preparation.
Companies operating in Hungary or across Europe should assess:
- Whether current invoicing systems can support EN 16931 XML as the primary format
- How validation is handled today and what needs to shift to real-time controls
- The impact of buyer-side reporting on AP processes
- Readiness for API-based integration with tax authorities
E-invoicing is no longer just about digitising invoices. It is about restructuring the entire invoice lifecycle around validated, structured data.
Hungary shows what that future looks like in practice.
