Check eVAT 2.0 XML in the browser

Load the file and we will show formal errors against the NAV eVAT 2.0 schema. The check runs in your browser, so the file does not leave your machine. NAV eVAT 2.0 XSD, pinned release 2.0.2 (2026-07-01, commit 21065b6b).

When to use it

What is this checker for?

What it finds

What it does not decide

A successful check does not mean NAV acceptance. This page helps you find formal errors in the file. NAV may still examine the return’s content and further business rules.

What do the three steps check?

XML structure

We check whether the XML is well-formed: no unclosed or mismatched tags, and no encoding problems. In practice, a large share of issues already surface here.

eVAT 2.0 identity

We only check the root element and namespace — that the file is actually an eVAT 2.0 analytics payload. An export from an earlier version fails here. Missing required children, such as declarationInfo, belong to the next, XSD step.

NAV schema validation

The file is compared with the pinned NAV eVAT 2.0 XSD: required elements, element order, allowed values and formats. Validation is performed by the widely used libxml2 engine.

What errors does it report, and how can they be fixed?

Every error the checker reports, in the order the three steps run. For schema errors the table also shows the pattern of the original libxml2 message, as it appears under technical validation detail, so a message copied from there can be looked up here.

Error types reported by the eVAT 2.0 XML checker, their causes and fixes
Reported errorStepTypical causeFix
The XML file is empty XML structure The file contains no XML, or only whitespace. Typically an interrupted or incorrectly saved export. Produce a new eVAT 2.0 export from the source system and check the file size.
Invalid character encoding XML structure The file cannot be read reliably as UTF-8 XML. It typically shows up at accented characters in a file saved with another code page (for example Windows-1250). Save or export the file again in UTF-8, and check that the XML declaration also states UTF-8.
Unclosed or mismatched XML tag XML structure An opening or closing tag is missing, or does not match its pair. This happens with truncated files or after manual editing. Fix the tags around the indicated line, then run the check again.
This is not an eVAT 2.0 XML file eVAT 2.0 identity The VatDeclarationData root element or the eVAT namespace is missing, or the file has no root element at all. Typically a file from a completely different data report. Confirm that an eVAT M2M 2.0 export was selected in the source system.
Legacy EAR 1.0 eVAT XML eVAT 2.0 identity The file uses the earlier eVAT namespace http://schemas.nav.gov.hu/EAR/1.0/data. The checker measures against the 2.0 schema, so a 1.0 file is not validated. Update the source system export to eVAT 2.0 format, then export again.
Different eVAT namespace eVAT 2.0 identity The root element is correct, but the namespace is not the 2.0 schema’s (http://schemas.nav.gov.hu/EAR/2.0/data). A common cause is a mistyped or manually edited namespace. Correct the root element namespace, or request a new eVAT 2.0 export from the source system.
Missing or misplaced required element
Element '…': Missing child element(s). Expected is ( … ).
Element '…': This element is not expected. Expected is ( … ).		 NAV schema (XSD) A required element is missing at this point, or the element order differs from the schema. The XSD prescribes a fixed sequence, so a correct element in the wrong place also fails. This also covers an element that does not belong where the schema expects another one. The name after “Expected is” is the element the schema expects. Add the expected element and review the element order in the affected section.
Unexpected element
Element '…': This element is not expected.		 NAV schema (XSD) The schema accepts no further element at this location — the message has no “Expected is” part. Often an internal custom field remains in the export, or the element name is misspelled. Check the element name, namespace and position, then the source system’s eVAT 2.0 export settings.
Invalid value (format, length or allowed set)
Element '…': '…' is not a valid value of the atomic type '…'.
Element '…': [facet 'pattern'] The value '…' is not accepted by the pattern '…'.
Element '…': [facet 'length'] The value has a length of '…'; this differs from the allowed length of '…'.		 NAV schema (XSD) The field value does not match the format, length or allowed set prescribed by the schema. Typical cases are date format, decimal places and enumerated code values. For a length mismatch the checker prints the expected and actual character count. Correct the value on the indicated line to the schema format, then re-export the XML.
Invalid value: tax number (taxNumber)
Element '{…}taxNumber': [facet 'length'] The value has a length of '…'; this differs from the allowed length of '8'.		 NAV schema (XSD) The full hyphenated tax number, or a value with a country code, was put in the tax number field. The schema accepts only the core number. The taxNumber field must contain only the eight-digit tax-number core, without space, hyphen or country code.
Other schema error NAV schema (XSD) The affected field or surrounding structure fails the schema for another reason. In that case the original schema message is shown under technical validation detail. Inspect the indicated line, then request a new eVAT 2.0 export from the source system if needed.

Web interface, XML upload or M2M: where does the checker help?

eVAT returns can be filed in three ways. The checker matters wherever you produce the XML yourself.

The three eVAT filing channels and the role of the XML checker
ChannelHow it worksRole of the checker
Web interface NAV compiles a tax-coded draft return from invoice, cash-register and customs data, which is reviewed, adjusted and approved on the interface. Usable below 100,000 invoices per return period. Not needed: no XML file of your own is produced.
XML upload The tax records produced in your own system are uploaded to the web interface as an XML file. Annex data must also be in the XML; it cannot be added afterwards. Before upload: the uploaded file follows the same eVAT 2.0 XSD the checker measures against.
Machine (M2M) connection The ERP or filing software sends document-level tax records over the machine interface, NAV validates them, and the system approves the draft by machine. During development and debugging: formal errors in the export can be caught before submission.

Detailed channel comparison with scenarios (Hungarian)

Frequently asked questions

Is the file uploaded anywhere?

No. The check runs in the browser: the browser reads the file, and schema validation also happens locally with libxml2 compiled to WebAssembly. The file contents never leave the machine — this can be verified on the Network tab of the browser developer tools.

Which schema does the checker use?

The pinned eVAT 2.0 XSD release published on NAV’s public eVAT repository (NAV eVAT 2.0 XSD, pinned release 2.0.2 (2026-07-01, commit 21065b6b)). We do not bundle a copy of the schema; we download this release from the NAV source. The page prints the validation basis both before and after the run.

If the file passes, will NAV definitely accept it?

No. This is a formal check: it tests whether the file matches the structure and formats in the schema. NAV also runs technical, processing and business validation with its own messages — collected on the eVAT validation messages page.

How large a file can it check?

The limit is the machine’s memory, not a server-side cap. Validation runs on a separate thread (Web Worker), so the interface does not freeze on larger analytics files.

Why does element order matter?

Because the XSD prescribes order, not only which elements may appear. A correct element therefore still fails if it is in the wrong place — one of the most common misunderstandings of schema errors.

Sources