NAV Online Számla Hungary E-Invoicing 2026: Real-Time Submission, Mandatory Compliance & E-Commerce Integration

1. NAV Online Számla — System Overview

Few EU member states moved as decisively to real-time e-invoicing as Hungary. While Italy, Poland (KSeF), Romania and Spain were still designing pilot schemes, Hungary's NAV Online Számla went live on 1 July 2018 with a hard B2B cutover and no soft-launch period. The system has since become the EU's most-cited reference implementation of a "continuous transaction control" (CTC) e-invoice model — and a template for the upcoming EU ViDA (VAT in the Digital Age) directive.

NAV (Nemzeti Adó- és Vámhivatal — National Tax and Customs Administration) operates the system at onlineszamla.nav.gov.hu. Every Hungarian VAT taxpayer — resident or non-resident with a Hungarian VAT number — must create a technical user in the portal, generate the four required credentials (login, password, signature key, exchange key), and either build a direct integration against the REST API or wire up an accredited ERP that handles it.

The numbers are large: by 2026 NAV processes over 600 million invoices per year from more than 600,000 active Hungarian taxpayers. The system serves both an enforcement role (rapid VAT-fraud detection) and a service role (pre-filled VAT returns, the NAV-OSA "online cash register" stream).

2. Real-Time Submission — Mandatory B2B (2018) + B2C (2021)

The Three-Step Mandate Rollout

Hungary's Online Számla obligation arrived in three distinct waves, each lowering the threshold until it covered virtually every taxable transaction:

• 1 July 2018 — B2B above HUF 100,000 VAT content. Any invoice between Hungarian VAT-registered businesses where the VAT component exceeded HUF 100,000 had to be reported in near-real-time.
• 1 July 2020 — All B2B invoices. The HUF 100,000 threshold was abolished; every business-to-business invoice issued under a Hungarian VAT number became reportable, regardless of value.
• 4 January 2021 — Full B2C + cross-border. The obligation extended to invoices issued to private consumers and to non-Hungarian customers (EU and third-country). This is the regime that applies in 2026, with no exemption thresholds.

The 5-Minute Rule

The headline service-level commitment of the system is 5 minutes from invoice issuance to NAV receipt. The clock starts at the invoiceIssueDate + invoiceIssueTime stamped on the document and ends when the manageInvoice REST endpoint returns a transaction ID. In practice most accredited ERPs (Számlázz.hu, Billingo) submit within 1–3 seconds; the 5-minute window is the regulatory hard cap, not the operational target.

The 5-minute clock can be paused only in two situations: (a) NAV's API is officially down (status published on the NAV portal), in which case Decree 23/2014 (VI. 30.) NGM Art. 13/A grants an extension of outage duration + 24 hours; and (b) the seller has applied for a "data exchange agent" status under specific exemptions — rare for e-commerce.

Manual vs Automated Submission

NAV does provide a manual web form in the Online Számla portal — taxpayers can paste invoice data by hand. At marketplace volumes this is unworkable: a mid-sized eMAG seller producing 200 invoices a day cannot manually round-trip each one within the 5-minute SLA. Automation is, in practice, mandatory above 10 invoices a day.

3. XML Format — NAV-Defined invoiceData v3.0 Schema

The XSD-Driven Architecture

NAV does not accept arbitrary XML — every submitted invoice must conform to the official invoiceData v3.0 XSD schema published by NAV under Decree 23/2014 (VI. 30.) NGM. The schema defines:

• Header — supplier identification (Hungarian VAT number / EU VAT number / third-country tax ID), customer identification, invoice number, issuance/completion/payment dates, currency code, exchange rate to HUF when issued in EUR/USD/etc.
• invoiceLines — line-by-line breakdown: product description, quantity, unit of measure, net unit price, VAT rate (27% / 18% / 5% / 0%), VAT amount, gross amount. Each line carries a lineNature tag (PRODUCT / SERVICE / OTHER) and an optional product-code identifier (VTSZ, SZJ, KN, CsK, EJ, TESZOR).
• invoiceSummary — totals: net, VAT and gross amounts per VAT rate, plus rounding line if applicable.
• invoiceReference — for modifying or cancelling a previously submitted invoice; carries the original invoice number and the modification type (MODIFY / STORNO).

The Online Számla 3.0 REST API

Submission happens via the Online Számla 3.0 REST API rooted at https://api.onlineszamla.nav.gov.hu. The seven core endpoints are:

• tokenExchange — fetch a 5-minute exchange token, signed with the taxpayer's signature key
• manageInvoice — submit one or more invoiceData XML payloads (max 100 per batch)
• queryTransactionStatus — poll the processing status of a submitted batch (NOTIFIED / DONE / WARN / ABORTED)
• queryInvoiceData — fetch an invoice you previously submitted
• queryInvoiceDigest — list invoices by date range or counterparty (for audit / reconciliation)
• queryInvoiceChainDigest — return the full modification chain of a given invoice
• queryTaxpayer — validate a Hungarian VAT number in real time

SHA3-512 Signing and the Four Credentials

Every request is authenticated with four taxpayer-specific credentials generated in the Online Számla portal:

• Login name — the technical user's username
• Password — used in a hashed form, never sent plaintext
• Signature key (XML-DSig) — used to SHA3-512-sign each request hash
• Exchange key — used to AES-encrypt the exchange token

All payloads are wrapped in a strict XML envelope and signed using SHA3-512. NAV rejects any request whose signature does not match the recomputed digest within ~50ms. Building this from scratch is a several-week project; the value of an accredited ERP or Zunapro is to abstract the signature/retry/queue logic away from the seller's e-commerce stack.

4. NAV Portal vs ERP Integration — Számlázz.hu, Billingo, KBOSS

The Three Mainstream Hungarian ERPs

For 95% of Hungarian SME sellers the practical choice is between three accredited cloud invoicing platforms:

Számlázz.hu — Operated by KBOSS Kft., launched in 2006, Számlázz.hu is Hungary's #1 cloud invoicing platform with over 250,000 active SME users and roughly 40 million invoices issued per year. Its REST API (v3/szamla/agent) is the de-facto standard for Hungarian e-commerce integration. Plans start free for very low volumes and scale up to enterprise tiers; NAV submission is fully automatic and bundled into every plan.

Billingo — Founded in 2014 and acquired by Magyar Telekom in 2019, Billingo positioned itself as the modern, design-led alternative to Számlázz.hu. It serves 80,000+ Hungarian businesses in 2026, with particularly strong adoption among Shopify, WooCommerce and Shoprenter shops. The Billingo Public API v3 is the simplest Hungarian invoice API on the market and includes built-in NAV submission, modification, storno and PDF generation.

KBOSS Számla Agent — A separate KBOSS Kft. product, the Számla Agent is an enterprise-grade desktop / server agent that sits between an existing ERP (SAP, Microsoft Dynamics 365, Sage, Oracle) and NAV. It runs as a Windows service, monitors invoice tables, and pushes invoiceData XML to NAV on a schedule. Used by 10,000+ enterprises, mainly in manufacturing and wholesale.

Direct NAV Integration vs ERP — Decision Matrix

Zunapro Approach — One Adapter, Three Backends

Zunapro abstracts the choice: marketplace orders flow into a single Hungarian invoice queue; the seller picks whether each tenant's invoices are emitted via the Számlázz.hu connector, the Billingo connector, or direct NAV REST. The orchestrator handles retries, signature rotation, NAV downtime windows, and writes the returned 10-character NAV transaction ID back onto every order so the marketplace and the seller's panel always show the same compliance state.

5. Penalties — Up to HUF 1,000,000 per Missing Invoice

The Statutory Framework — Act CL of 2017 (Art. 220)

Penalties for failure to comply with Online Számla are set by Act CL of 2017 on the Rules of Taxation (Adózás Rendjéről szóló Törvény — Art tv.), Article 220. The default administrative fine is up to HUF 1,000,000 per missing invoice for businesses (legal entities) and up to HUF 500,000 per missing invoice for private individuals (sole proprietors — egyéni vállalkozó).

What Triggers a Penalty

• Late submission — invoiceData XML received after the 5-minute deadline (excluding officially declared NAV outage windows)
• Missing submission — invoice issued but never reported to NAV at all
• Incomplete data — required XSD fields blank or malformed (e.g. missing VAT rate, wrong customer ID)
• Inaccurate data — line totals don't reconcile to header total, or currency conversion missing for non-HUF invoices
• Failure to report modifications — a STORNO or modification invoice issued but the corresponding invoiceReference not pushed to NAV

NAV's Real-World Escalation Pattern

In practice NAV issues a warning letter first for small isolated omissions — typically 1–3 missing invoices in a quarter. From around 10 unreported invoices in a quarter NAV moves to formal fines, and at 50+ omissions or systematic non-reporting the case escalates to a full VAT audit, possible loss of VAT-deduction rights, and tax-warehouse / OSS status review. Cross-border sellers who under-report can also lose access to the OSS One Stop Shop scheme, forcing per-country VAT registration in every EU member state.

Practical Mitigation

The cheapest insurance against the HUF 1M penalty is automated submission with a persistent retry queue. Zunapro keeps a 90-day rolling audit log of every NAV interaction (request payload, response code, transaction ID, signature key version) so that — even if NAV later raises a query — every submission can be reconstructed and demonstrated.

6. ÁFA 27% Auto-Calculation and Multi-Rate Handling

Hungary — The EU's Highest Standard VAT

Hungary's standard VAT rate is 27% (ÁFA — általános forgalmi adó), the highest in the European Union, set by Act CXXVII of 2007 on Value Added Tax (Áfa törvény). The rate has stood at 27% since 1 January 2012 and there are no announced plans to lower it.

Two reduced rates apply to specific categories:

• 18% reduced rate — milk and certain dairy products (under Annex 3/I, point 1 of the Áfa törvény), commercial accommodation services (hotels, holiday rentals), and some bakery products
• 5% super-reduced rate — printed and electronic books, medicines on the official list, certain medical aids, district heating (távhő), commercially built new housing below specific square-metre thresholds, and live-music event tickets
• 0% / exempt — intra-EU exports under the OSS regime, exports to third countries, certain financial services, healthcare, education

The Marketplace Multi-Rate Problem

An eMAG.hu or Vatera order often contains lines at different VAT rates — a single basket might combine a 27%-rate accessory with a 5%-rate book. The invoiceData XML must split the lines correctly and reconcile each VAT-rate bucket in the invoiceSummary. Manual calculation at marketplace volumes is impractical and error-prone.

Zunapro's master catalog tags every SKU with its Hungarian ÁFA rate at import time. When a marketplace order arrives, the system:

1. Looks up the rate per SKU from the master catalog
2. Computes line-level net / VAT / gross (rounded per NAV's rounding rules)
3. Groups lines into summaryByVatRate buckets for the XML summary
4. Submits the invoiceData payload within the 5-minute window

Currency Handling — HUF, EUR, USD

For invoices issued in EUR, USD or other foreign currencies, NAV requires the seller to record an HUF equivalent calculated at the MNB (Magyar Nemzeti Bank) official mid-rate for the invoice issue date. The XML carries both the original currency amount and the HUF-equivalent amount per VAT-rate bucket. Zunapro fetches the MNB daily rate at 11:15 CET (MNB's publication time) and applies it automatically.

7. Marketplace Integration — eMAG.hu, Vatera, Allegro HU

The Marketplace Invoice Reality

A widespread misconception among new Hungarian e-commerce sellers is that "the marketplace handles invoicing". It does not. eMAG Marketplace Hungary, Vatera (Allegro Group), AliExpress Hungary, Wish Hungary and every other platform operating under Hungarian VAT explicitly place the invoicing obligation on the seller. Each B2C or B2B order under a Hungarian VAT number must produce a Hungarian-compliant invoice — and that invoice must be pushed to NAV Online Számla within 5 minutes.

eMAG.hu — Hungary's #1 Marketplace

eMAG is the largest Romanian-headquartered marketplace, founded in 2001 in Bucharest and launched in Hungary as eMAG.hu in 2013. By 2026 eMAG.hu serves 4M+ Hungarian customers and is the dominant Hungarian marketplace by volume — comparable in market share to Allegro in Poland or Trendyol in Turkey. eMAG Marketplace Hungary uses its own MARKETPLACE API for order pull, product upload and order status updates. Invoices are not issued by eMAG on the seller's behalf — the seller must generate the invoice (typically via Számlázz.hu / Billingo) and provide a PDF link back via the eMAG order endpoint.

Vatera — The Hungarian Auction-Heritage Marketplace

Vatera launched in 2000 as Hungary's first major online auction platform and was acquired by the Allegro Group in 2017. Following Allegro's 2024 launch of allegro.hu, Vatera continues to operate as a separate brand focused on the auction and second-hand long-tail. Buy-Now listings dominate today (auctions are <10% of volume), but the brand's heritage shoppers remain. NAV Online Számla applies identically: every Vatera order requires an invoice with same-day NAV push.

Allegro.hu, AliExpress HU, Wish HU

• Allegro.hu — launched 2024 as part of Allegro Group's CEE expansion. Same Allegro API as the Polish marketplace, with HUF / EUR pricing and Hungarian-language listings. Invoicing obligation rests with the seller; NAV Online Számla push required.
• AliExpress Hungary — the Alibaba subsidiary's Hungarian storefront. Cross-border sellers using AliExpress's IOSS scheme still need Hungarian-compliant invoices when they hold a Hungarian VAT number.
• Wish Hungary — declining footprint but still present; same invoice-by-seller rule.

The Zunapro Marketplace Flow

The end-to-end flow Zunapro orchestrates is:

1. Marketplace order pull — eMAG / Vatera / Allegro.hu webhooks land in Zunapro
2. Invoice draft — Zunapro composes the Hungarian invoice with SKU-level ÁFA rates, currency conversion and customer data
3. ERP push — invoice posted to Számlázz.hu / Billingo (or direct NAV) — REST round-trip ~1–3s
4. NAV submission — the invoiceData XML is signed and pushed to onlineszamla.nav.gov.hu
5. Transaction ID — NAV's 10-character transaction ID is stored on the order and the marketplace order is updated with the invoice PDF URL

8. EKAER — Road Freight Pre-Notification for Risk Goods

What EKAER Is

EKAER (Elektronikus Közúti Áruforgalom Ellenőrző Rendszer — Electronic Road Freight Trade Control System) is Hungary's mandatory pre-notification regime for road transport of risk-classed goods. Introduced on 1 January 2015 as one of the EU's first real-time VAT-fraud control schemes, EKAER is operated by NAV at ekaer.nav.gov.hu and requires every qualifying shipment to be registered before the truck starts moving — with a 15-character EKAER number that must be carried with the cargo and presented to roadside enforcement on request.

The January 2021 Scope Reform

EKAER originally applied to virtually all B2B road freight crossing Hungarian borders. Following European Commission infringement pressure (EU's freedom-of-movement rules), Hungary narrowed the scope from 1 January 2021 to risk-product categories only. In 2026 EKAER covers:

• Risk foods — meat, dairy, sugar, certain oils as listed in Annex 1 of EKAER Decree 13/2020 (XII.23.) PM
• Other risk products — fuels, certain chemicals, building materials in defined HUF-value thresholds
• Bulk transports above 2,500 kg or HUF 1,000,000 cargo value within risk categories

Standard e-commerce parcels (clothing, electronics, accessories) are outside the 2026 EKAER scope. Most cross-border online sellers shipping into Hungary via DHL, GLS, FoxPost or Magyar Posta therefore do not need EKAER — but bulk B2B wholesale movements still do.

How an EKAER Notification Works

Before the truck loads, the consignor opens an EKAER notification in the portal (or via API), populating:

• Sender + consignee tax IDs
• Origin + destination addresses
• Goods description, VTSZ customs code, gross weight, cargo value
• Vehicle registration plate + planned arrival window

NAV returns the 15-character EKAER number. The notification can be modified (vehicle plate change, weight tolerance) up to the moment the shipment arrives. Penalty for missing or inaccurate EKAER: up to 40% of cargo value.

EKAER + Online Számla — How They Interact

EKAER and Online Számla are independent regimes with no direct technical link, but they share data. NAV cross-references EKAER cargo data against Online Számla invoice lines to detect VAT fraud (under-declared goods, ghost invoices, missing exports). For sellers operating in risk categories, having a single Zunapro panel that simultaneously emits the NAV invoice and the EKAER notification from the same order record is a major risk-reduction lever.

9. Cross-Border — IOSS + OSS for EU and Third-Country Sales

OSS (One Stop Shop) — EU B2C Above Distance-Selling Threshold

From 1 July 2021 the EU replaced the country-by-country distance-selling thresholds with a single EUR 10,000 EU-wide threshold. Any Hungarian seller whose total cross-border B2C sales into other EU member states exceed EUR 10,000 in the calendar year must collect VAT at the buyer's country rate. Rather than register for VAT in 26 other countries, the seller can register for OSS (One Stop Shop) via NAV's KAFTA portal and file a single quarterly OSS return covering all EU member states.

IOSS (Import One Stop Shop) — Imports Below EUR 150

IOSS applies to imports of goods from third countries (non-EU) with a consignment value at or below EUR 150. Under IOSS, the seller collects EU VAT at checkout (at the buyer's-country rate), and files a single monthly IOSS return covering all EU consignments. The benefit: customs clearance becomes near-instant, no surprise duty/VAT charges on delivery, and Hungarian shoppers experience the order as a domestic purchase.

How NAV Online Számla Sits Alongside OSS and IOSS

OSS and IOSS are separate VAT return regimes — they file aggregated EU VAT to NAV, but they do not replace the Online Számla obligation. The Hungarian invoice still has to be issued and pushed to Online Számla. The relationship is:

• Domestic HU B2C — issue invoice at 27% (or applicable rate) → push to NAV Online Számla → file in standard Hungarian VAT return
• EU cross-border B2C under OSS — issue invoice at the destination-country VAT rate → push to NAV Online Számla (cross-border flag in XML) → file aggregated OSS return quarterly
• Third-country B2C under IOSS — issue invoice with IOSS VAT rate → push to NAV Online Számla → file aggregated IOSS return monthly
• Outside OSS / IOSS — country-by-country VAT registration required; Hungarian Online Számla still applies if invoice issued under Hungarian VAT number

Zunapro Cross-Border Routing

Zunapro tags each order at intake with the correct regime — HU domestic / OSS / IOSS / non-EU — based on the buyer's shipping address, the consignment value and the seller's VAT registration profile. The invoice is generated with the right VAT rate, pushed to NAV Online Számla with the cross-border flag set, and aggregated into the appropriate OSS / IOSS export at month-end.

10. The Future — Peppol UBL 2.1 + EU ViDA

Why Peppol Matters

Peppol (Pan-European Public Procurement Online) is a four-corner e-invoice exchange network that uses the UBL 2.1 standard and the Peppol BIS Billing 3.0 specification. Originally developed for public-sector procurement, Peppol is now the EU's preferred format for cross-border B2B e-invoicing and the technical backbone of the upcoming EU ViDA (VAT in the Digital Age) directive.

Hungary's Peppol Commitment

Hungary committed at the EU Council level to accept Peppol BIS Billing 3.0 as an alternative submission format for cross-border B2B invoices. The NAV roadmap published in Q1 2026 targets:

• H2 2026 — NAV operates a Peppol Access Point that accepts inbound UBL 2.1 and converts to invoiceData v3.0 for internal processing
• 2027 — Outbound conversion: invoices submitted in NAV's invoiceData format can be routed to a foreign buyer via Peppol in UBL 2.1
• 2028 — Full ViDA alignment: real-time digital reporting harmonised across all EU member states, with Peppol as the default technical layer

What Peppol Changes for Hungarian Sellers

For domestic-only sellers, very little — invoiceData v3.0 remains the primary format. The win is for cross-border B2B sellers: a single UBL invoice can simultaneously satisfy NAV (HU), KSeF (PL), FatturaPA (IT) and Chorus Pro (FR) without per-country adapter logic. By 2028 the same single invoice should clear all EU member states' digital reporting requirements.

Zunapro's Peppol Roadmap

Zunapro's UBL output module is in active development. The architecture mirrors the existing NAV adapter: invoices generated from marketplace orders are emitted simultaneously in invoiceData v3.0 (for NAV) and UBL 2.1 (for Peppol Access Point delivery to non-Hungarian buyers). The seller chooses per-customer or per-marketplace whether to enable Peppol routing.

Hungarian Legal Framework 2026 — Where to Find the Rules

Primary Legislation

• Act CXXVII of 2007 on Value Added Tax (Áfa törvény) — defines the 27% / 18% / 5% rates, the scope of taxable transactions, and the underlying invoice obligation. Available at njt.hu (the National Legislation Database).
• Act CL of 2017 on the Rules of Taxation (Art tv.) — defines the Online Számla reporting obligation in Articles 7 and 220, including penalty structure.
• NAV Decree 23/2014 (VI. 30.) NGM — the technical decree that defines the XML schema, the 5-minute deadline, the API endpoints and the credential format. Updated annually; the latest amendment ahead of the 2026 Peppol integration was published in Q1 2026.
• EKAER Decree 13/2020 (XII. 23.) PM — defines the risk-product categories and the 2021 scope reform.

NAV Operational Guidance

• onlineszamla.nav.gov.hu — official taxpayer portal; technical-user generation, XSD downloads, downtime status, FAQ in Hungarian + English
• nav.gov.hu — main NAV site; tax rates, OSS/IOSS guidance, English-language landing page for foreign sellers
• ekaer.nav.gov.hu — EKAER portal and risk-product list

Consumer Protection — GDPR, 14-Day Withdrawal, 2-Year Warranty

• GDPR — Hungarian data-protection authority is NAIH (Nemzeti Adatvédelmi és Információszabadság Hatóság). Online Számla data is processed by NAV under its own legal basis but seller-side customer data remains the seller's GDPR responsibility.
• 14-day right of withdrawal — Hungarian consumers may return any distance-purchased product within 14 days, no reason required (EU Directive 2011/83/EU, transposed by Government Decree 45/2014 (II. 26.) Korm.).
• 2-year statutory warranty (kellékszavatosság) — Hungarian civil law (Ptk. Section 6:163) imposes a mandatory two-year statutory warranty on consumer goods, independent of any commercial guarantee.

How to Start with NAV Online Számla — 2026 Step-by-Step

1. Decide Your Hungarian VAT Footprint

• Hungarian resident SME — full Hungarian VAT registration via NAV ONYA, Online Számla mandatory
• EU seller using OSS — keep your home-country VAT registration, file Hungarian B2C VAT via OSS, but Online Számla applies once you hold a Hungarian VAT number for any other reason
• Non-EU seller — appoint a Hungarian fiscal representative; once a Hungarian VAT number is issued, Online Számla submission is mandatory from invoice 1

2. Choose Your Invoicing Path

• Számlázz.hu — Hungary's #1 cloud invoicing; lowest setup friction, fully NAV-automated, free for very low volumes
• Billingo — modern API-first alternative, Telekom-backed, strong Shopify / WooCommerce ecosystem
• KBOSS Számla Agent — desktop / server agent for SAP / Dynamics enterprises
• Direct NAV REST — for high-volume sellers (500+/day) or unusual ERP setups; Zunapro can run this in-place

3. Generate NAV Technical-User Credentials

1. Sign in to onlineszamla.nav.gov.hu with your Hungarian Client Gate (Ügyfélkapu) identity
2. Open "Felhasználók" → "Új technikai felhasználó"
3. Set login name and password; the system generates the signature key and exchange key
4. Download all four credentials and store them in your password manager (Zunapro accepts them in encrypted-vault format)

4. Connect Marketplaces and Webshop

With NAV credentials in hand, connect eMAG.hu, Vatera, Allegro.hu, AliExpress HU, your Shoprenter / WooCommerce / Shopify shop, and any wholesale ERP into the Zunapro Hungary module. Each connector ships with default category mappings and ÁFA-rate inference; the seller confirms with a few clicks.

5. Run the Test-Mode Round-Trip

Zunapro emits a test-mode invoice against NAV's sandbox (api-test.onlineszamla.nav.gov.hu). When the test returns a NAV transaction ID — typically within 2 seconds — the seller toggles production mode. From that point onward every marketplace order automatically generates an invoice, pushes it to NAV within the 5-minute SLA, and stores the transaction ID on the order record.

6. Monitor and Audit

Zunapro's NAV dashboard surfaces submission latency, retry queue depth, signature-key expiry, NAV downtime windows and the 90-day rolling audit log. For accountants and external auditors, the entire NAV interaction log exports as a signed PDF or CSV ready for tax-return reconciliation.

NAV Online Számla FAQ 2026