Hungary RTIR: SAP Integration Guide

Hungary pioneered real-time invoice reporting in Europe: RTIR (Real-Time Invoice Reporting) through NAV’s Online Számla system has been mandatory since July 2018 and now covers effectively every invoice issued under Hungarian VAT rules. For SAP teams, the 2026 agenda is not the reporting obligation itself — it is the hardening around it: stricter validation rules, the transition of VAT returns to the eVAT machine-to-machine (M2M) channel, and receipt-data reporting on the horizon.

Executive Summary

Mandate name	Hungary Real-Time Invoice Reporting (RTIR) via NAV Online Számla
Current status (as of July 2026)	Mandatory since July 2018 and broadly expanded from January 2021. Use the current NAV Online Invoice 3.0 interface specification; blocking validation changes have applied since 15 September 2025.
Who is affected	Invoice data within Hungarian VAT invoicing and reporting rules, including modification and cancellation documents. VAT registration alone is not a universal scope test.
Business risk	Under sections 224 and 229 of Act CL of 2017, the general maximum is HUF 400,000 for a natural-person taxpayer and HUF 1,000,000 for a non-natural-person taxpayer, multiplied by the number of affected invoices or equivalent documents.
SAP impact	SD billing, FI invoices, tax codes, customer master data, XML 3.0 generation, immediate machine-to-machine submission, and NAV response/error handling.
Recommended next step	Review current Online Invoice 3.0 validation rules and plan the transition from ÁNYK to eÁFA web or M2M filing.

What Is the RTIR Requirement?

RTIR was introduced to close Hungary’s VAT gap by giving the tax authority (NAV, Nemzeti Adó- és Vámhivatal) invoice-level data at the moment of issuance. It launched in July 2018 for B2B invoices above a VAT threshold; the thresholds were removed in stages, and since January 2021 the obligation covers effectively all invoices issued under Hungarian VAT rules, including B2C and cross-border sales invoices.

The mechanics matter for system design: when a billing system issues an invoice, the invoice data must be transmitted to the Online Számla platform immediately and without human intervention, as structured XML in schema version 3.0. NAV validates each submission and responds — warnings flag data-quality issues, errors block the report. Unlike clearance systems such as Poland’s KSeF, RTIR is a reporting regime: the invoice itself remains legally valid between the parties, but the data must reach NAV. Buyers can also retrieve their suppliers’ reported invoice data from NAV, which many companies use for accounts-payable reconciliation.

Business Impact for Finance and Tax Teams

• Penalty exposure: the statutory maximum follows the taxpayer category: HUF 400,000 for a natural person or HUF 1,000,000 for a non-natural person, multiplied by affected invoices or documents.
• Validation hardening: since 15 September 2025, several checks that previously produced warnings now block submissions. Data-quality gaps that were tolerated for years surface as same-day operational incidents.
• The eVAT M2M transition: NAV retires the ÁNYK filing program at the end of 2026; after ÁNYK retires, VAT returns move to eÁFA; both the web interface and M2M route remain available, with M2M suited to high-volume and complex filers. Because NAV builds the draft return on RTIR data, invoice-reporting quality now flows directly into the VAT return.
• M-sheet changes in flux: additional granularity in the domestic purchases listing (M-sheet) was scheduled for VAT periods from July 2026, but on 25 June 2026 the government announced it intends to prevent the stricter rules from taking effect. Confirm the final state before building — this is a moving target.
• What’s next: from 1 September 2026, receipt-data reporting extends Hungary’s real-time model to receipts (non-connected systems get a maximum of three days), and Hungary has signalled a longer-term move toward mandatory structured e-invoicing in line with the EU’s VAT in the Digital Age (ViDA) programme, reported for around 2030.

How This Impacts Your SAP Environment

• Billing-to-XML mapping: SD billing and FI invoice data must map to the schema 3.0 structure, including tax-code classification, exchange rates, and the modification/cancellation document chains (MODIFY and STORNO reports must reference the original correctly).
• Master data: Hungarian tax numbers and EU VAT identifiers on customer master records must be complete and correctly formatted — a common source of blocking errors under the tightened validation.
• No batch window: “immediately, without human intervention” means submission, token handling, retry logic, and sequencing sit in the billing-critical path — a Basis and integration design topic, not an end-of-day job.
• Exception ownership: WARN responses need review; ERROR responses block the report and need same-day correction tied back to the SAP source document.
• eVAT M2M readiness: M2M registration through the NAV customer portal, API scope, and reconciliation between RTIR data and the draft VAT return should be planned before the ÁNYK shutdown at the end of 2026.

How S4FN Supports RTIR Compliance

S4FN provides an SAP-native RTIR workflow that reads SAP billing and master-data fields, maps them to the schema 3.0 structure, validates before submission, and tracks NAV responses and exceptions inside an SAP-aligned process — see the Hungary RTIR integration for SAP product page. For the VAT-return side of the transition, S4FN also supports an eVAT M2M workflow review. Exact scope, deployment, and connectivity should be confirmed during technical review.

Official sources

• NAV — current Online Invoice guidance
• Hungary — Act CL of 2017

Regulatory content verified: 10 July 2026.

Verified on: 10 July 2026. Confirm the current legal scope, authority technical package and SAP-supported scenario before implementation.