Login

Regulatory updates - Hungary

Get the latest news and updates on e-invoicing, e-ordering, e-archiving and indirect tax regulatory requirements.

Get the latest news and updates on e-invoicing, e-ordering, e-archiving and indirect tax regulatory requirements for Hungary.
2025-01-23

New timeline for electricity and gas suppliers to issue e-invoices

Hungary has recently amended two decrees to enforce energy and gas suppliers to issue only e-invoices.

2024-12-23

Hungarian electricity and gas suppliers must issue e-invoices

Hungary has amended two decrees that will be enforced from 1 January 2025. Such decrees establish concrete e-invoicing requirements for gas distribution companies and energy traders.

2024-12-18

New data reconciliation procedure from 2025

The main purpose of the data reconciliation procedure for the Hungarian Tax Authority (NAV) is to regularly compare the data from the real-time invoice reporting system with the information on the VAT returns, in particular the M sheets, submitted by companies.

Country Specifications

E-Invoicing/CTC Model:

RTIR and Post-audit

Mandatory Infrastructure:

– RTIR: Online Szamla

e-Invoice: No infrastructure

Mandatory Format:

– NAV XML version 3.0 for e-invoicing via Online Számla

– N/A for the rest

Mandatory for Issuing:

– RTIR: All suppliers

e-Invoice: No explicit requirements

Mandatory for Receiving:

Buyer’s consent required

eSignature:

Not Required

Archiving Period:

– Standard: 5 years

– Accounting purposes: 8 years

Archiving Abroad:

Allowed under conditions

Pagero Regulatory Atlas

Contact us

Book a free consultation to find out more about how we can help you streamline your business with a solution that suits your specific needs.

Navigate e-invoicing in Europe with Pagero

Find out how to leverage automation and comply with Europe’s vast diversity of CTC and e-invoicing regulations through a single connection to the Pagero Network.

Solution page

Stay up-to-date with our Compliance Monitor

Receive an in-depth report with country-specific requirements