E-invoicing by country

E-invoicing in Hungary: mandates, formats, sending and receiving

Dynafis combines invoice validation, recipient capability, country profiles and evidence for Hungary. The permitted route is determined per legal entity, transaction and environment; NAV Online Invoice is only one part of the overall process.

What applies in this country?

Hungary requires NAV Online Invoice/RTIR for reportable invoices. Peppol may exchange invoices but does not satisfy NAV real-time reporting. Peppol is a voluntary exchange rail in Hungary and does not satisfy NAV Online Invoice/RTIR. Dynafis therefore treats NAV reporting, modification and annulment as a separate rail with technical user, token, signature and reconciliation.

Who is affected?

The profile distinguishes B2B, B2G, B2C and cross-border. Scope also depends on establishment, tax registration, recipient type, public procurement and cross-border context.

Networks and portals

Relevant networks and portals include NAV Online Invoice and Peppol. Dynafis validates NAV XML 3.x and Peppol BIS Billing 3.0 and the addressing schemes 9910 as separate concerns.

Networks and portals
  • NAV Online Invoice
  • Peppol
Formats and profiles
  • NAV XML 3.x
  • Peppol BIS Billing 3.0
Identifiers
  • 9910
What Dynafis supports today

Dynafis includes the country profile and technical rails. Production requires complete legal-entity setup, credentials, connection testing and provider evidence.

Coverage boundaries

The support status describes Dynafis technical coverage, not a blanket legal or tax approval. National reporting, fiscalization, archive or signature duties may apply in addition to invoice exchange.

Sending process
  1. 01

    Determine legal entity, transaction type and recipient country

  2. 02

    Validate recipient ID, scheme and document profile

  3. 03

    Freeze the canonical invoice and run the country preflight

  4. 04

    Execute the permitted exchange, clearance and reporting rails

  5. 05

    Reconcile provider statuses, receipts and evidence

Receiving process
  1. 01

    Retrieve from Peppol, the national platform or a partner connector

  2. 02

    Store the legal original separately from the transport artifact

  3. 03

    Validate profile, sender, totals and correction references

  4. 04

    Assign the document to the correct legal entity in the shared inbox

Corrections and status
  1. 01

    Reference the original and profile version unambiguously

  2. 02

    Choose credit note, correction, replacement or cancellation only when supported

  3. 03

    Reconcile status history, reporting and evidence together

For accountants and multi-client work

For accountants and multi-client work

Accounting firms configure Hungary per client and legal entity. Credentials, provider accounts, documents and production approvals never inherit between clients; month-end checks remain traceable per legal entity.

For accountants and multi-client work
FAQ
Is e-invoicing mandatory in Hungary?

Hungary requires NAV Online Invoice/RTIR for reportable invoices. Peppol may exchange invoices but does not satisfy NAV real-time reporting. The exact scope must be assessed for the legal entity and transaction.

Is Peppol sufficient for Hungary?

Not automatically. Peppol may be an exchange rail, but it replaces national clearance, reporting or fiscalization such as NAV Online Invoice and Peppol only when the active country profile explicitly permits it.

What does Dynafis support for Hungary today?

Dynafis includes the country profile and technical rails. Production requires complete legal-entity setup, credentials, connection testing and provider evidence.

Sources and review status

Reviewed: · hu-nav-online-invoice-2026.07.29