Online invoice reporting

Requirement

The tax authorities of many countries require electronic invoice files.

The Hungarian tax authority requires that the invoicing software used by Hungarian tax payers has a direct data transfer with the authority. The sales invoice data must be reported in XML format in real time, without human intervention. The reporting must be done immediately after the preparation of the invoice.

The new invoiceData version 3.0 of the online invoice submission for Hungary is effective as of January 4, 2021, but the tax authority has granted a grace period until March 31, 2021.

In the initial solution for online invoicing developed for Hungary in 2018, only domestic B2B invoices should be reported to the Hungarian tax authorities,Nemzeti Adó és Vámhivatal or NAV.

The scope for this new version has been extended. The reporting now includes invoices issued to individuals (B2C transactions), and invoices issued for export and intra-community transactions.

Limitations

Invoicing from a fiscal representative in another country is currently not supported.

M3 solution

Users can submit their invoices electronically in the required format using LSP. This solution enables communication between M3 and the Hungarian tax authorities, as required by the NAV.

Each M3 customer who uses Infor Localization Services with the web services must obtain their own NAV credentials to be able to connect to the NAV API.

For each issued invoice and regardless of the invoicing function that has been used, an invoice BOD is created by M3 and can be viewed by users in 'Invoice Header. Open' (CMS500). Then, the invoice BOD is published, using ION, to LSP. The invoice XML file is created by LSP and sent to the NAV (Nemzeti Adó- és Vámhivatalhoz) server of the National Tax and Customs Administration of Hungary (NTCA).

The invoice data is submitted on request to the online invoice system NAV. An initial acknowledgment receipt of the electronic invoice is sent by the NAV. Any response, whether the invoice is accepted or rejected, is received by LSP and is optionally returned to M3 using the ProcessInvoice BOD. Connectivity to the NAV is supported through the API Gateway.

The ProcessInvoice BOD will update the invoices in M3 BE using the API INVBODMI.

Configuration guidelines

Program ID	Program name	Description or comment
CMS500	Invoice Header. Open	All created and recreated invoices are displayed. See NCR 11227 for details about the process. For details on the consumption of the ProcessInvoice BOD to enable feedback from external portals for eInvoicing, see NCRs 12061, 12200, 12201.

See "M3 configuration for electronic invoicing" in the Infor M3 Core Configuration Guide for Infor Localization Services Platform.