What companies need to know about Hungary eVAT

Hungary is continuing the digitalisation of its VAT reporting system through eVAT, known locally as eÁFA. The system gives businesses access to transaction-level data already held by Hungary’s National Tax and Customs Administration (NAV), with built-in validations designed to identify inconsistencies and reduce logical and formatting errors in VAT returns.

For businesses operating in Hungary, the move towards eVAT represents more than a change in how VAT returns are submitted. It brings tax reporting closer to the underlying transactional data, making data quality, reconciliation and accurate tax-code mapping increasingly important. Businesses can interact with eÁFA through a web interface or machine-to-machine (M2M) connection. For larger organisations with high transaction volumes, multiple systems or more complex VAT processes, M2M offers an opportunity to integrate VAT reporting more directly into existing technology and compliance workflows.

So, what does Hungary eVAT mean in practice, and what should businesses be doing now to prepare?

What is Hungary eVAT?

Hungary’s eVAT system, or eÁFA, is an electronic VAT reporting environment operated by NAV.

Rather than relying solely on information compiled independently by the taxpayer, eÁFA provides access to transactional data already available to the tax authority, including online invoice data, online cash-register receipts, simplified invoices and customs documentation data.

NAV highlights several benefits of using eÁFA, including:

• Direct access to transaction-level data held by NAV
• Validation checks designed to identify inconsistencies
• Reduced logical and formatting errors
• Greater digitalisation of VAT return processes
• Exemption from recipient-side M-sheet reporting when the relevant requirements are met

For tax teams, however, the significance of eVAT goes beyond the submission itself.

As VAT reporting becomes increasingly data-driven, businesses need greater confidence that the information held within their ERP and financial systems is complete, correctly classified and consistent with the information available to NAV.

Timeline: Who must switch and when?

The new rules apply equally to local Hungarian companies and foreign businesses operating under a Hungarian tax number. Deadlines depend on the size of the business rather than its country of origin. Following NAV’s October 2026 announcement, Hungary’s tax authority has proposed a phased transition from ÁNYK to eÁFA. Under the proposal, the largest businesses would move during 2027, while eÁFA would become mandatory for most VAT filers from 1 January 2028.

• 15 December 2026 (proposed): NAV officially notifies the largest taxpayers who must adopt the system in the first wave.
• 1 January – 31 December 2027 (Transition Year): Regular businesses must use eVAT but can freely choose between the manual Web Interface (Web-UI) and the automated Machine-to-Machine (M2M) connection.
• 1 July 2027 (proposed): The eVAT system becomes mandatory and exclusive for the selected large taxpayers
• 1 January 2028 (proposed): Full Mandatory eVAT. The eVAT system becomes the exclusive and mandatory filing method for all taxpayers across the board.

How does Hungary eVAT work? Two digital pathways

NAV automatically prepares a draft VAT return using digital data from the Real-Time Reporting (RTR) Online Invoice system, customs documents, and e-cash register data. Businesses can manage this draft through two different options.

Option A: The eVAT Web Interface (Web-UI)

This path is best for companies with low invoice volumes and simple transactions.

• Limit: Available only for businesses with fewer than 100,000 invoices per tax period.
• How it works: You log into the NAV portal, review the pre-populated draft, manually adjust your VAT deduction rights, and submit it directly from the browser.
• Control: It is a useful tool for cross-checking your internal accounting with NAV records.

Option B: The eVAT M2M Connection

This option is designed for companies with high invoice volumes and complex tax setups where automation is essential. It can also be used by smaller digitalised companies.

• How it works: Your ERP system connects directly to the NAV database via an API.
• Validation and Error Feedback: NAV automatically checks your data and reports errors back to your system before submission, allowing you to fix them instantly.
• Note: The full automated validation process can take 3 to 5 days, which must be factored into your monthly filing calendar.

For businesses planning M2M implementation, this makes ongoing technical monitoring important. Integrations need to account for changes to NAV specifications and schemas rather than treating eVAT implementation as a one-off project.

Is Hungary eVAT mandatory?

This is an important question for businesses planning their Hungarian VAT compliance strategy.

Hungary is moving towards greater use of eÁFA, but businesses should distinguish between the eÁFA functionality available today and proposed future transition requirements.

For businesses likely to be affected, preparation should begin before a mandatory transition occurs. ERP configuration, tax-code mapping, reconciliation processes and M2M development can all require significant preparation and testing.

Who should consider eVAT M2M?

Using the eÁFA web interface may be manageable for organisations with relatively simple reporting requirements.

However, M2M is likely to be particularly relevant to businesses with more complex VAT operations, including organisations that:

• Process high volumes of invoices
• Operate multiple ERP or finance systems
• Have complex VAT deduction rules
• Manage numerous tax codes
• Process significant cross-border transactions
• Want to reduce manual intervention in VAT reporting
• Need stronger reconciliation between ERP and tax-authority data

For these organisations, automation can create significant efficiencies, but only if the underlying data is sufficiently accurate.

Data Reconciliation: The power of pre-populated returns

Instead of simply reporting internal data, companies must cross-check their own records with the real-time invoice data already submitted to NAV by their trading partners.

1. Identifying missing data: If a supplier failed to report an invoice, it will not appear on the NAV draft. Reconciliation allows companies to recognize these gaps immediately.

2. Managing tax rights: NAV sees incoming invoices but does not know if a company is legally allowed to deduct the VAT (e.g. restrictions on company cars or entertainment). Companies must match these invoices with the correct legal deduction codes.

3. Two-way control: For larger enterprises, this matching process could happen entirely between the company ERP system and the NAV API, allowing the software to query the NAV database and pull all invoice data submitted by suppliers.

Key financial and compliance benefits of Hungary eVAT

While moving to a more data-driven VAT model introduces implementation work, it can also create opportunities to improve the compliance process.

NAV identifies digitalisation, transaction-level data access and automated validation among the advantages of eÁFA. For tax teams, broader benefits can include:

• Permanent exemption from the M-lap: Businesses using eVAT are fully exempt from filing the domestic invoice-by-invoice listing (M-lap). This eliminates a massive administrative burden.
• Zero self-correction penalties (M2M Only): No self-correction penalties apply if you submit an amendment within 15 days of the original filing or deadline.
• Audit moratorium (M2M Only): For companies with a reliable taxpayer status, NAV cannot initiate audits for 15 days post-deadline, giving a safe window to correct mistakes.

The true challenge: Tax code mapping

The biggest risk of the eVAT M2M transition is not technical, it is the tax logic. Companies must match their internal ERP tax codes to the standard state tax code structure used by NAV.

This is not a simple IT translation. Choosing the correct NAV code depends on multiple variables:

• The partner’s tax status (domestic, EU, or non-EU)
• The exact place of supply and transaction direction (sale or purchase)
• Specific local VAT deduction rules

Incorrect mapping creates inaccurate tax data, causing validation failures. This leads to faulty tax returns or a complete rejection of the submission by NAV. This risk is highly critical for firms using multiple ERP systems or handling complex cross-border transactions.

How should companies prepare for Hungary eVAT?

Businesses do not need to wait for mandatory deadlines to begin assessing their readiness. A practical eVAT preparation programme should include the following steps.

1. Identify your Hungarian VAT registrations

Establish which entities and VAT registrations could be affected and understand how VAT returns are currently prepared for each.

2. Map your existing VAT process

Document where VAT data originates, how it moves between systems and where manual intervention currently takes place.

3. Review your ERP tax codes

Identify the tax codes currently used for Hungarian transactions and assess whether they consistently reflect the correct VAT treatment.

4. Assess data quality

Look for missing fields, inconsistent classifications, duplicate records and other issues that could cause validation or reconciliation problems.

5. Reconcile against NAV data

Compare internal transaction records with the data available to Hungary’s tax authority and investigate discrepancies.

6. Decide whether Web Interface or M2M is appropriate

Consider transaction volumes, ERP complexity, internal resources and the level of automation required.

7. Review M2M technical requirements

Businesses planning an M2M connection should monitor NAV’s latest technical specifications. NAV published version 2.0 of its eÁFA M2M interface specification in May 2026, alongside updated XSDs and testing arrangements.

8. Build testing into the project

Do not assume that a successful technical connection means the VAT process is ready. Test different transaction types, edge cases, validations and reconciliation scenarios.

9. Establish ownership

Successful implementation is likely to require input from tax, finance, ERP, IT and data teams. Establish responsibility early rather than treating eVAT as a tax-only project.

10. Continue monitoring NAV guidance

Technical requirements and implementation guidance can evolve. Businesses should maintain an ongoing process for reviewing NAV updates and assessing their impact.

Hungary’s move towards increasingly digital VAT compliance will require businesses to think beyond the VAT return itself.

The real challenge sits further upstream, in the ERP systems, tax codes, transaction data and reconciliation processes that ultimately determine what appears on the return. For organisations operating at scale, preparing early creates an opportunity to identify those weaknesses before they become compliance problems.

Fintua helps businesses bring VAT compliance, reconciliation and reporting processes together, giving tax teams greater visibility and control over the data behind their returns.

For businesses assessing their readiness for Hungary eVAT, this can start with reviewing existing VAT processes, identifying data gaps and assessing whether current tax-code mappings and reconciliation controls can support the move towards eVAT M2M.

Talk to Fintua about preparing for Hungary eVAT.