SimplyX Blog

Expert insights on tax digitalization, NAV M2M developments, and the transition beyond ÁNYK.

eVAT

When is it really submitted? Approval, versions and self-revision in eVAT — A successful check is not yet submission: an eVAT return counts as submitted when the draft is approved. Who can approve it, which return counts on several channels, and when is a self-revision, correction or repair needed?
Error or warning? How to handle NAV’s eVAT feedback — Which NAV messages block an eVAT return, and which require review? A practical guide to errors, warnings and the changes NAV announced for October.
Testing an eVAT return safely on a closed period — Follow an eVAT return from preparation to NAV confirmation across all three filing channels, then test the process against a closed period already filed through ÁNYK.
Registration and permissions in eVAT: who sets up what in a company and in an accounting firm? — Primary, secondary and technical users, two interfaces, two permission levels: illustrated guidance on who can set up what in eVAT, and why an accounting firm needs a separate technical user for every client.
From VAT codes to NAV tax codes: how to map them for eVAT — Why internal VAT codes don’t match NAV’s standard tax codes, how a NAV code is built, and how to set up the mapping table — step by step, with the most common exceptions and practical cases.
Where does the return data come from? The eVAT XML in plain terms: content, data sets, mandatory elements — A practical guide to the eVAT return XML: its header, statements, transaction-level VAT records, summaries, supplementary sheets and attachments, including data sources and responsibilities.
Web interface, XML upload or M2M: which eVAT channel suits you? — There are three ways to file an eVAT return. This guide compares their legal conditions, workflow and M2M benefits, with a channel selector and practical cases for companies and accounting firms.
NAV proposes more time for eVAT: survey findings and self-assessment — NAV has reported the eVAT survey findings and proposed a gradual migration. What does more preparation time mean for companies and accounting firms?
eVAT M2M 2.0 in production: what changed on 3 August? — eVAT M2M moved to XSD 2.0 in production on 3 August 2026, with no parallel operation. We explain the break with the ÁNYK form model, the new attachment structure and the new analytics fields.
Hungary’s 2026 M-sheet tightening did not take effect: what companies should know — The mandatory M-sheet expansion planned for July 2026 did not take effect. What does this mean for eVAT M2M and corporate readiness?
eVAT M2M: What to Fix Before Migration — For many companies, the biggest eVAT M2M risk is not XML generation. It is whether the underlying VAT data, tax codes, controls, and manual processes are ready for machine-to-machine filing.
eVAT M2M 2.0: Why Last-Minute Preparation Is Not Enough — The eVAT M2M 2.0 documentation and XSD schemas are now public. But preparation is not just a developer task — without tax-code mapping, data quality, and a migration strategy, the risks are significant.
eVAT M2M 2.0: a new milestone in VAT filing — eVAT M2M is not just a new submission channel, but a new operating model: transactional data, unified NAV tax codes, and pre-submission validation. The May 2026 2.0 specification stabilizes this model.

ÁNYK transition

Hungary’s ÁNYK transition: NAV guidance and the new proposal — NAV proposes a gradual ÁNYK phase-out. Understand the proposed 2027–2028 timetable, choose between ONYA, NAV M2M and eVAT, and plan preparation for each obligation.
ÁNYK phase-out: gradual transition proposal and preparation — NAV proposes a gradual ÁNYK phase-out. Understand the proposed 2027–2028 timetable, choose between ONYA, NAV M2M and eVAT, and plan preparation for each obligation.

NAV M2M

NAV M2M and the gradual ÁNYK transition: an accounting guide — NAV proposes a gradual ÁNYK phase-out. Understand the proposed 2027–2028 timetable, choose between ONYA, NAV M2M and eVAT, and plan preparation for each obligation.