Hungary digital VAT compliance · SAP integration

Hungary RTIR integration for SAP

How should SAP teams implement Hungary RTIR compliance?

Hungary RTIR compliance in SAP requires teams to extract the correct invoice and tax data, transform it to the active NAV Online Számla schema, validate before submission, and retain every authority response. The design must also control corrections, cancellations and idempotent retries, with reconciliation back to the original SAP document.

Turn SAP invoice data into controlled NAV Online Számla submissions—with validation, authority-response handling and a clear operating model for corrections, cancellations and retries.

2.0

New: NAV published the eVAT M2M 2.0 specification

NAV published the 2.0 interface specification and refined XSDs for Hungary’s eVAT machine-to-machine connection. The 2.0 data structure is available in the test environment from July 2026. RTIR and eVAT M2M are separate controls, but SAP teams should govern their data and reconciliation together.

See the SAP M2M impact →

The control objective

Reporting an invoice is only the first half of compliance

A workable RTIR design must preserve the chain from the SAP source document to the NAV response. The difficult cases are rejected submissions, technical retries, modifications and cancellations—not the happy-path XML generation.

01

Govern the source

Identify the invoice, tax and master-data fields that determine the NAV payload and keep the extraction traceable to the SAP document.

02

Control every response

Separate transport failures, validation errors and authority warnings. Each needs a different owner and recovery decision.

03

Reconcile the outcome

Make unresolved reporting failures visible before downstream VAT preparation and eVAT reconciliation.

SAP-to-NAV operating flow

A controlled submission lifecycle

The final architecture depends on the SAP release, deployed components, invoice processes and customer landscape. The control sequence should remain explicit in every design.

ExtractRead relevant SAP invoice, tax and master data.
MapBuild the NAV payload, including modification operations.
ValidateRun structural and business-rule checks before submission.
SubmitTransmit through the approved technical channel.
ResolveStore responses and route warnings, errors and retries.

Where implementations become fragile

Common delivery gaps

  • Assuming a successfully transmitted payload is an accepted invoice report.
  • Retrying without checking whether NAV already processed the original request.
  • Treating warning messages as technical noise instead of operational evidence.
  • Handling amendments and cancellations outside the original invoice chain.
  • Leaving rejected items unresolved until VAT return preparation.

S4FN delivery focus

Evidence before architecture

  • Confirm the SAP release, edition, installed components and company-code scope.
  • Map the actual invoice scenarios before choosing integration points.
  • Define response, retry and reconciliation ownership with Finance and Basis.
  • Connect RTIR controls with the eVAT M2M data and return process.
  • Translate confirmed gaps into implementation and test work packages.

Compatibility and technical scope

Confirm fit against the real landscape

Compatibility is assessed from system evidence. A generic product label is not enough to determine the supported deployment or the required remediation.

SAP ECCRelease and installed components are verified during the technical review.
SAP S/4HANAEdition, release and installed components are verified during the technical review.
Functional scopeFI, SD, tax configuration, billing scenarios, master data and company-code scope.
Technical scopePayload generation, validation, credentials, connectivity, response persistence, monitoring and replay controls.
NAV operationsOriginal invoices, modifications, cancellations, warnings, errors and controlled retry handling.
Delivery modelConfirmed during technical review based on the customer landscape and the selected S4FN or SAP integration components.

Important: RTIR invoice reporting and eVAT M2M are not interchangeable. RTIR reports transaction data to Online Számla; eVAT M2M supports machine-to-machine VAT return data exchange. Their shared SAP data dependencies make coordinated testing and reconciliation essential.

Current references

Verify against the authority package

NAV specifications and validation rules can change. Confirm the active technical package and the supported SAP scenario before implementation or release.

Review Hungary RTIR against your SAP evidence

Start with the release, company-code scope, invoice scenarios, installed components and current NAV integration. We will identify the practical next step before proposing implementation work.

Regulatory content checked: 15 July 2026. Confirm the current legal scope, NAV technical package and SAP-supported scenario before implementation.

S4FN - Solutions for Finance
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.