UBL Validator
Validator

🇭🇺 Validate UBL Invoices for Hungary

UBLB2G MandatoryPeppol

UBL 2.1 is required for B2G in Hungary. Hungary uses a Real-Time Invoice Reporting (RTIR) model where all invoice data must be reported to NAV before delivery to the customer.

Quick Facts
Format
UBL 2.1
Standard
EN 16931
Mandate
B2G Only
Peppol
Connected

What We Validate

UBL 2.1 XML schema validation
EN 16931 business rules
Namespace and element structure
Code list validation
Party and address structure
Tax calculation rules
Invoice line consistency

Common UBL Errors

#1UBL-CR-001Invalid XML syntaxFix guide
#2UBL-CR-002Invalid namespaceFix guide
#3UBL-SR-01Namespace declaration requiredFix guide
#4UBL-SR-06Invalid date formatFix guide
#5UBL-CR-005Empty element not allowedFix guide

Hungary E-Invoicing Requirements

Phase
Status
Scope
RTIR (all invoices)
Live (Jul 2020)
All VAT-registered businesses — every invoice reported
NAV XML 3.0
Live (May 2025)
Version 3.0 mandatory (2.0 discontinued)
B2B e-invoicing (energy)
Live (Jul 2025)
Electricity and gas sectors
B2B e-invoicing (water)
Jan 2026
Water utilities
Full B2B mandate
2027+
Expected under ViDA
Validation engineNAV Online Számla (real-time API validation)
Required CIUSNAV XML 3.0 (for reporting); flexible formats for actual invoices
Routing identifierAdószám (tax number)
PeppolYes — consulting on Peppol for future B2B mandate

RTIR is not e-invoicing. The critical distinction: Hungary mandates real-time reporting of invoice data to NAV, not the exchange of structured e-invoices between parties. Your pipeline must report via the Online Számla API before delivering the invoice to the customer. The actual invoice can still be PDF. NAV XML 3.0 is mandatory from May 2025 — version 2.0 is discontinued.

FAQ

What is UBL 2.1?
UBL (Universal Business Language) 2.1 is an open XML standard for business documents developed by OASIS. It defines schemas for invoices, orders, and 60+ other document types.
Is UBL the same as Peppol?
No. UBL is the document format; Peppol is the network. Peppol BIS Billing is built on UBL 2.1 with additional business rules.
Should I use UBL or CII for EN 16931?
Both are valid syntaxes for EN 16931. UBL is more common internationally (Peppol uses it), while CII is used in hybrid formats like ZUGFeRD.
What are cbc: and cac: prefixes?
These are UBL namespace prefixes. cbc: (Common Basic Components) contains simple values, cac: (Common Aggregate Components) contains complex structures.
Which standards are built on UBL?
Peppol BIS Billing 3.0, XRechnung (UBL variant), A-NZ PEPPOL (Australia/New Zealand), and Singapore InvoiceNow all use UBL 2.1 as their base syntax. Our validator checks generic UBL compliance—use format-specific validators for additional business rules.

Validate your Hungary UBL invoices

Upload and validate instantly. Auto-fix common errors.

Try the Validator