My Oracle Support Banner

E1: 74H: SoftwareId - Invoicing Programme ID Requested for Real-Time Invoice Reporting (RTIR) to the National Tax and Customs Authority (NAV) Hungary (Doc ID 2872654.1)

Last updated on MAY 26, 2022

Applies to:

JD Edwards EnterpriseOne Accounts Receivable - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

 On 1 July 2018, the Hungarian real-time invoice reporting (RTIR) obligation came into force for domestic eInvoices, and starting with 1st of January 2021 was amended to include intra-community transactions. Later, from 1st of April 2021, the National Tax and Customs Authority (NAV) introduced the mandatory “NAV Online 3.0”,  allowing for the companies to exclusively report the invoice XML file to NAV, which is then made available to customers as an electronic invoice.

If using a technology provider, the exported data from an Enterprise Resource Planning (ERP) system can be treated and transformed to the required format by the NAV, in accordance with the requirements specified by the NAV. 

For more details about the NAV Online Invoice System, see the link https://onlineszamla.nav.gov.hu/api/files/container/download/Online Szamla_Interfesz specifikacio_EN_v3.0.pdf.

In order to register the JD Edwards ERP instance to the National Tax and Customs Authority (NAV) for real-time invoice reporting, there is a request for the softwareId - Invoicing programme ID element, described on the document available on the above mentioned NAV Online Invoice System link, see pages 9, 10, 11: 

softwareId is an 18-length string used to identify the invoicing program used.

Recommendation for generating softwareId: The first two characters of the ID should be the country code of the software developer, as per ISO 3166 alpha-2. Additional characters of the identifier should include the tax registration number of the developer company, with the appropriate number of digits. If multiple software development companies are involved in the development of the invoicing program (or its individual modules), the identifier should include the data of one of them, based on mutual agreement.

The softwareId and the email address of the developer company (sofwareDevContact) are used to identify and notify the developer of potential operational problems.

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.