How do I move from ÁNYK to eVAT?

First choose the filing channel (web interface, XML upload or eVAT M2M), then clarify where the return data come from and who is responsible for them. Next, map your internal VAT codes to NAV’s standard tax codes, set up users and permissions, and test on a closed period already filed in ÁNYK. Finally, learn how to handle NAV’s error and warning messages and when a return counts as submitted. The parts of the series follow this order.

Who is the series for?

Corporate tax and finance teams migrating their own VAT return, and accounting firms handling returns for several clients. Where the steps differ, the articles show the company and the firm view separately.

Which filing channels does the series cover?

The guide covers the web interface, XML upload and M2M connections. Choose a channel based on data sources, filing volume and automation needs. Part two compares the options.

What should I prepare for a test return?

Prepare data for a closed, previously filed period, its VAT analytics, your tax code mapping and the return needed for comparison. Run the test in the test environment. Part six explains the process.

Where should an accounting firm start?

Start with the readiness self-assessment and channel choice. Then clarify data sources, responsibilities and permissions for each client. Parts three and five cover these tasks.

Article series

eVAT migration in practice

An eight-part practical guide to moving from ÁNYK to eVAT, Hungary’s electronic VAT system, for corporate tax and finance teams and for accounting firms.

The series takes you through choosing a filing channel, preparing data and tax codes, setting up permissions, testing a return and handling NAV feedback.

8 parts · 8 available

Start with the self-assessment View the migration process

Professional author: Kovács AndrásPage updated: 5 October 2026

STEP BY STEP

The eVAT migration process

The walkthrough takes you through each migration step. Select any step to view its details and open the related guide.

From preparation to submission · 8 steps

1. step · Assessment and planning

Assess readiness

Expected outcome

Identified gaps and agreed next actions.

Open the guide

Required documentation

Readiness assessment, responsibilities and implementation schedule.

Related checklist items

1 / 8

Where should you start?

Choose the question that matters most to you right now.

Parts of the series

If you are just starting the migration, read the parts in order. If you are looking for an answer to a specific question, go straight to the relevant part.

Assessment and planning

Assess readiness and choose the right filing channel.

Data and access

Prepare data sources, tax codes and user permissions.

Testing and submission

Test the process in the test environment and prepare to handle NAV feedback.

The steps of an eVAT migration

Migration involves assessing readiness, choosing a filing channel, preparing data and tax codes, setting up access, and then testing and checking the submission process. Use the outcomes below to track progress.

The steps of an eVAT migration
Task	Expected outcome	Guide
1. Assess readiness	Identified gaps and agreed next actions.	Part 1
2. Choose a filing channel	A channel suited to your company or client portfolio.	Part 2
3. Identify data sources and owners	Documented data sources and clear responsibilities.	Part 3
4. Map VAT codes	Checked NAV tax code mapping, including exceptions.	Part 4
5. Set up users and permissions	Access suited to each task and designated owners.	Part 5
6. Prepare a return in the test environment	A documented comparison with a previously filed period.	Part 6
7. Process NAV feedback	Corrected errors and evaluated warnings.	Part 7
8. Submit and follow up	Verified submission status and retrievable records.	Part 8

Fill in the migration checklist

32 checkpoints, owners, deadlines and a go-live decision. Fill in, save and print in your browser.

Download a blank checklist

Related tools

Frequently asked questions

How do I move from ÁNYK to eVAT?: First choose the filing channel (web interface, XML upload or eVAT M2M), then clarify where the return data come from and who is responsible for them. Next, map your internal VAT codes to NAV’s standard tax codes, set up users and permissions, and test on a closed period already filed in ÁNYK. Finally, learn how to handle NAV’s error and warning messages and when a return counts as submitted. The parts of the series follow this order.
Who is the series for?: Corporate tax and finance teams migrating their own VAT return, and accounting firms handling returns for several clients. Where the steps differ, the articles show the company and the firm view separately.
Which filing channels does the series cover?: The guide covers the web interface, XML upload and M2M connections. Choose a channel based on data sources, filing volume and automation needs. Part two compares the options.
What should I prepare for a test return?: Prepare data for a closed, previously filed period, its VAT analytics, your tax code mapping and the return needed for comparison. Run the test in the test environment. Part six explains the process.
Where should an accounting firm start?: Start with the readiness self-assessment and channel choice. Then clarify data sources, responsibilities and permissions for each client. Parts three and five cover these tasks.

Author and professional sources

Professional author: Kovács András

The technical explanations in the series draw on the NAV sources below. Individual articles also link to the sources supporting specific statements.

The specification is a versioned document; the developer forum changes continuously. Check current technical details against the relevant article and its linked NAV source.

Ready to apply the guide to your own processes?

If eVAT M2M suits your operations, let’s discuss data connections, permissions and the next steps of implementation.

Discuss your eVAT integration Explore SimplyX eVAT M2M