eVAT M2M: VAT returns, checks and ERP integration
Kovács András · Content updated: 15 October 2026
See in advance what NAV may flag – before you submit.
SimplyX checks your VAT analytics against NAV’s validation rules and compares them with Online Invoice data. Errors and differences are flagged on the affected line with a clear explanation, so before you submit you can decide what to fix.
You load the VAT analytics from your ERP or accounting software, and the mapping to NAV tax codes is set up once. You submit the return yourself from the SimplyX interface over eVAT M2M, and follow NAV’s feedback here too.
With these formerly manual steps automated, more time is left for investigating differences and for professional decisions, whether you handle one company or several businesses and accounting-firm clients.
- No XML, API or IT expertise needed
- Free consultation and trial
- 135 NAV messages explained in our error-code database
- 232 NAV tax codes in a searchable catalogue
- 8 parts migration guide from assessment to submission
- Weekly we track NAV’s developer notices
What SimplyX gives you for your Hungarian VAT return
SimplyX is a browser-based eVAT M2M platform that supports checking VAT analytics, managing NAV tax codes, submitting the return and following NAV’s feedback in one interface, for companies and accounting firms. No XML, API or M2M expertise is needed: SimplyX handles the technical side of the NAV connection. Tax decisions and submission stay with you; you submit the return yourself from the SimplyX interface.
Checks against NAV’s rules, before you submit
SimplyX checks your VAT analytics against NAV’s schema and validation rules and compares them with the Online Invoice data held by NAV. You fix discrepancies while there is still time, instead of preparing a new version after submission.
- Schema and rule checks in line with NAV’s latest notices
- Comparison with NAV Online Invoice data
- Partner tax number and EU VAT number (VIES) checks
Plain explanations instead of error codes
You see NAV’s errors and warnings tied to the affected line, with a clear explanation: what the message means, which line it concerns and what to do. No digging through NAV’s specification or developer forum.
- Blocking errors and warnings marked separately
- An explanation for every NAV message
- Jump straight to the affected line
Many companies’ returns in one place
Whether you manage a group of companies or accounting-firm clients, you do not have to open every return. SimplyX lists only the companies where you need to act; returns that are in order stay off the list.
- Returns awaiting approval or with errors
- Missing data as the deadline approaches
- Expired or missing NAV permissions
Also included
- VAT analytics from Excel, ERP or accounting software: Load the analytics exported from your existing system; SimplyX remembers the column mapping, so it does not need to be set up again next period.
- NAV tax-code mapping set up once: The mapping between internal VAT codes and NAV standard tax codes is reused in the next period, and new codes are flagged.
- Automatic check of the technical user: SimplyX automatically checks that the technical user’s data is valid, so access problems do not surface at submission.
- Approval and submission from SimplyX: You approve and submit the draft return over eVAT M2M. The system handles versions, and self-revisions remain traceable.
- NAV confirmation, status and tax account in one place: After submission, follow NAV’s confirmation, the return status and the tax account in the same interface.
- Roles, four-eyes approval, audit log: Per-company permissions, four-eyes approval (one person prepares, another approves the return) and a traceable log of user actions.
How to get started
- Free consultation: We agree on a time and show how your return would look in SimplyX.
- Test return during the trial: Prepare a return for a closed period and compare it with the one already submitted.
- Go live: Once the data handover and the NAV connection are set up and the test return succeeds, you can go live from the SimplyX interface.
What is eVAT M2M?
eVAT, called eÁFA in Hungarian, is NAV’s electronic VAT return system. M2M means machine-to-machine: a software connection between an ERP, accounting system or filing platform and Hungary’s NAV eVAT system. It is separate from Online Invoice reporting and general NAV M2M form submission.
eVAT M2M is not the same as general NAV M2M electronic form submission; it is the dedicated machine channel of the eVAT system. In this process, a company system or filing platform connects to NAV’s eVAT M2M interface, whose developer documentation and schemas are published in NAV’s official eVAT GitHub repository.
The NAV data side is equally important: through the machine connection, the taxpayer can retrieve tax-coded data from online invoice reporting, online cash registers, and customs document data, as well as the list of valid tax codes.
The taxpayer then submits, in the format and data structure published by NAV, the document-level data that serves as the basis for determining payable VAT and exercising deduction rights — in other words, the VAT record. This does not change the return frequency: a monthly filer still prepares and submits a return for the monthly period; what changes is that the underlying VAT analytics and validation are supported through a machine interface. The draft return generated from that VAT record can be approved by machine, and approval qualifies as submission of the return.
Web eVAT, XML upload, or eVAT M2M?
The right route depends on the obligation, data volume, source systems, and required controls.
| Channel | When can it fit? | Key consideration |
|---|---|---|
| Web eVAT | Lower document volumes and simpler VAT returns manageable in a browser | Less integration, with more manual review and approval. |
| eVAT XML upload | Your accounting software already produces the eVAT XML file | You upload the XML on NAV’s web interface; the check results and the submission are handled there too. No M2M connection needs to be built. |
| eVAT M2M | High data volumes, multiple entities, ERP, or an external filing platform | VAT records, NAV validations, statuses, and machine approval in one workflow. |
What does eVAT M2M do and require?
NAV’s eVAT M2M process is not just file upload: data retrieval, tax coding, VAT records, validation, and approval work together.
Retrieving NAV data
Transaction-based data available at NAV can be used in company systems: online invoice data, online cash register data, and customs document data.
Tax-code list and mapping
The list of valid tax codes can be downloaded. NAV-assigned tax codes can be reviewed and, where appropriate, amended based on the taxpayer’s decisions and the applicable rules.
VAT record upload
The taxpayer submits document-level data that forms the basis for determining payable VAT and exercising deduction rights.
Error/Warning validation
NAV runs checks on the uploaded data. Errors must be corrected before submission; warnings allow submission, but should be reviewed.
Approval and submission
An authorised user reviews and approves the draft return. Approval constitutes submission; the NAV acknowledgement and processing status can then be tracked.
eVAT M2M vs. web eVAT and ÁNYK
According to NAV’s information, for the relevant periods the VAT return obligation can be fulfilled via eVAT M2M, the eVAT web interface, or ÁNYK forms. If more than one return is submitted for the same period, the first submitted return qualifies as the taxpayer’s return.
On the eVAT web interface, the user supplements, modifies, and approves the VAT record in the browser. In eVAT M2M, the company system or platform prepares and uploads the VAT record, NAV validates it, and the resulting draft return can then be approved through the machine interface. It remains a period-based filing workflow, not a continuous filing obligation.
Who should use web eVAT, and who should use eVAT M2M?
Web eVAT can be practical for taxpayers with a small, manageable number of documents where supplementing NAV-known data in a browser is workable. eVAT M2M becomes relevant when the VAT return is prepared from ERP data, an accounting system, or VAT analytics assembled from multiple sources.
With higher document volumes, multiple entities, multiple ERPs, international transactions, frequent manual corrections, or complex deduction situations, the main question is not “is there XML”, but whether the VAT analytics content matches NAV standard tax codes, the eVAT 2.0 data structure, and the company’s approval process.
What professional preparation is needed?
eVAT M2M is both a technology and tax-process project. NAV validations help identify errors and inconsistencies, but do not replace professional review of the underlying data and taxpayer decisions.
- Review source data: ERP, invoicing, accounting, cash register, and import/customs data.
- Map NAV tax codes and internal tax codes, especially for special transactions.
- Reconcile Online Számla and accounting data before filing.
- Document the data and decisions related to exercising the deduction right: VAT actually deducted, deduction rate, apportionment, and deduction restrictions where relevant for the transaction.
- Define responsibility and approval workflows for Error/Warning messages.
Technical requirements and documentation
NAV publishes the eVAT M2M developer documentation, schemas, and examples in its official eVAT GitHub repository. In-house development is realistic if there is sufficient ERP, integration, and tax expertise, and the company is ready to track specifications, schemas, and process changes.
A specialized external platform can be useful when the goal is not only generating XML or the technical interface, but also managing VAT record preparation, validation feedback, status tracking, archiving, and multi-company controls in one workflow.
How do you prepare an ERP connection to eVAT M2M?
Before integration, identify which system prepares the VAT records, where tax review takes place and who approves submission. Producing XML is one step; reviewing the return and retaining evidence of submission are separate responsibilities.
- Data sources: identify systems, entities and filing periods.
- Tax codes: map the internal VAT codes actually used to NAV standard tax codes.
- Access: technical user, required permissions and separate test and production settings.
- Test return: reconcile a closed period with a previously filed return and document differences and test limitations.
- Production submission: professional approval, status checks and retrievable records.
What changed in eVAT M2M in autumn 2026?
NAV’s announcement of 15 October 2026 proposes a gradual ÁNYK phase-out by return and form. The largest companies would move to mandatory eVAT during 2027; no exact start date has been specified, and 1 January 2027 is not fixed. For most VAT filers, including SMEs, the proposed start is 1 January 2028. Personal income tax and corporate income tax returns would remain fileable in ÁNYK during 2027. This is a proposal, not final legislation; the precise scope and dates require further official announcements.
NAV’s 31 August announcement describes new and amended ERROR validations from 1 September. It also schedules WARNING changes for October. Announced changes and checks confirmed to be in operation must be distinguished; an older downloaded code list does not capture subsequent changes.
On 3 October, NAV published A60 M2M schemas and validation descriptions on a separate development branch. The announcement anticipates further specification updates and testing access. This is developer preparation, not confirmation of production availability. Check the current NAV announcement and the schema version before implementation.
How does SimplyX support an eVAT M2M implementation?
SimplyX is a platform supporting tax workflows for companies and accounting firms. Its eVAT M2M solution is designed to bring VAT records, NAV validation feedback, submission statuses and multi-company tasks into one workflow.
Implementation discussions start with data sources, ERP or accounting-system capabilities and approval responsibilities. Data transfer, integration scope, ownership and go-live conditions need to fit your operations. Tax decisions and professional approval of the return remain with the designated team members.
Frequently asked questions
Is the mandatory eVAT start date fixed?
NAV’s announcement of 15 October 2026 proposes a gradual ÁNYK phase-out by return and form. The largest companies would move to mandatory eVAT during 2027; no exact start date has been specified, and 1 January 2027 is not fixed. For most VAT filers, including SMEs, the proposed start is 1 January 2028. Personal income tax and corporate income tax returns would remain fileable in ÁNYK during 2027. This is a proposal, not final legislation; the precise scope and dates require further official announcements.
Are eVAT and eÁFA the same system?
Yes. eÁFA is the Hungarian name of NAV’s electronic VAT return system; eVAT is used in developer documentation and English-language guidance. M2M refers to its machine-to-machine channel.
How should we start an eVAT M2M implementation?
Assess the filing channel, data sources and owners first, then prepare tax-code mapping, permissions and a test return for a closed period. Record go-live conditions and status checks separately. SimplyX’s eight-part migration guide and 32-point checklist provide practical support.
What is eVAT M2M?
eVAT M2M is the machine-to-machine connection of the eVAT system. The taxpayer can retrieve NAV data through a machine interface, upload the VAT record, receive validation feedback, and approve the generated draft return electronically through the M2M interface.
Does approving the draft return count as submission?
Yes. According to NAV’s information, approving the draft return generated from the VAT record is equivalent to submitting the return.
What do Error and Warning messages mean?
NAV’s validation service may send Error and Warning messages. With an Error, the return can only be submitted after the error is corrected. With a Warning, submission is not blocked, but the VAT record and return data may be incorrect, so review is recommended.
Is solving only XML development enough?
No. The interface and schema are only the technical layer. eVAT M2M also requires tax-code mapping, VAT records, correct representation of data related to exercising deduction rights, validation handling, and approval responsibility.
Does every company need to migrate to eVAT M2M?
Not necessarily. Web eVAT may be suitable for manageable document volumes and simpler workflows, subject to the service’s current limits and the taxpayer’s integration needs. eVAT M2M is relevant where VAT returns are assembled from ERP, accounting-system, larger VAT-analytics, or multi-entity data.
What records should be retained after submission?
Keep the final data, return version, approval and submission result together in retrievable records. Availability on NAV’s interface does not replace your own documentation; align retention with company policies and applicable requirements.
How does SimplyX help prepare an eVAT M2M return in Hungary?
Before submission, SimplyX checks the VAT analytics against NAV’s rules and Online Invoice data, and flags issues on the affected line with a clear explanation. The mapping to NAV tax codes is set up once. The user submits the return from the SimplyX interface over eVAT M2M and follows NAV’s feedback in the same place; several companies can be handled in one interface.
Can SimplyX work with an existing ERP or accounting system?
Implementation starts with the VAT records available from the existing system. The exported data and format need to be reviewed before agreeing how to transfer them. The connection depends on the capabilities of the ERP or accounting software in use.
Related articles
- When is it really submitted? Approval, versions and self-revision in eVAT
- Error or warning? How to handle NAV’s eVAT feedback
- Testing an eVAT return safely on a closed period
- Registration and permissions in eVAT: who sets up what in a company and in an accounting firm?
- From VAT codes to NAV tax codes: how to map them for eVAT
- Where does the return data come from? The eVAT XML in plain terms: content, data sets, mandatory elements
- eVAT migration in practice — 1. NAV asks about eVAT: where do you stand?
- eVAT migration in practice — 2. Web interface, XML upload or M2M?
- eVAT migration in practice — 3. Where does the return data come from?
- eVAT migration in practice — 4. From VAT codes to NAV tax codes
- eVAT migration in practice — 5. Registration and permissions
- eVAT migration in practice — 6. A test return without live risk
- eVAT migration in practice — 7. Error or warning?
- eVAT migration in practice — 8. When is it really submitted?
Primary professional sources
- NAV: preparing for eVAT
- NAV: the eVAT machine-to-machine connection (Hungarian)
- NAV: the eVAT web interface (Hungarian)
- NAV eVAT M2M 2.0 interface specification
- NAV eVAT developer documentation
- Hungarian VAT Act, section 184(2)–(3): ways of filing (njt.hu, Hungarian)
- NAV ÁNYK transition knowledge base
- NAV developer forum · Test environment limitations
- NAV · 2026-10-15 · ÁNYK / eÁFA
- NAV · Validation changes · 31 August 2026
- NAV · A60 schema publication · 3 October 2026
Free tools and references
- eVAT migration in practice — An eight-part guide from assessment to submission with an interactive process map.
- Migration checklist — 32 checkpoints, owners, deadlines and a go-live decision. Fill in and save.
- eVAT M2M registration step by step — Technical user, two permission levels, signature and exchange keys, and the developer test setup.
- eVAT XML validator — Checks against the NAV 2.0 schema in your browser; the file never leaves it.
- eVAT error messages — All current validation messages, searchable, from the NAV specification and announcements.
- Standard tax code list — All 232 NAV standard tax codes, searchable, from the official catalogue.
- NAV M2M guide — The general machine interface — a different channel from eVAT M2M.
- Online Invoice RTIR M2M — A separate Online Invoice data connection for enterprise systems; it is not the NAV M2M filing channel.
- ÁNYK route chooser — Three questions to identify the right filing channel.