Hungary: Online Invoicing System v.1.1 support on Dynamics AX 2012 R3

Introduction

As of 1 July 2018, National Tax and Customs Administration of Hungary announced that companies in Hungary obliged to supply data of their invoices issued through electronic platform of Online Invoicing System.

On March 12, 2019, National Tax and Customs Administration of Hungary published information about introduction of a new version 1.1 of the formats supported by Online Invoicing System. The new version of the formats must be effective since May 2, 2019.

It is officially announced on https://onlineszamla.nav.gov.hu/  the following changes must be supported:

1) XSD version is updated from 1.0 to 1.1.

2) Version of transport layer security (TLS) protocol update to TLS 1.2.

Table below provides references on previously published articles about implementation of interoperation with Hungarian Online Invoicing System:

Overview

According to the latest requirements the following changes were considered:

-  Version of the request is changed to "1.1" which becomes effective from May 2, 2019.

-  Line expression indicator

-  Line description

-  Unit of measure

-  Unit of measure own

-  TLS version change to 1.2

Implementation details

This section of the article provides details of investigation and implementation of the required changes in Hungarian Online Invoicing System.

Version of the request is changed to "1.1" which becomes effective from May 2, 2019.

The change related to the version of the request is provided to the XML files which system generates during interoperation with Hungarian Online Invoicing System.

To switch from using of 1.0 version of request to the version 1.1, open General ledger > Setup > Sales tax > External > Online invoicing system parameters, find in Other group of fields Request version parameter, select "1.1".

Line expression indicator

Before starting using of the new version of the report, user will need to setup Online invoicing system classifier for Unit of measurements defined in the Legal entity. Open General ledger > Setup > Sales tax > External > Online invoicing system classifiers and define which units of measurement must be reported as natural ("true" for Line expression indicator in Online invoicing system). Match all the units in your Legal entity.

If this setup is not done all the unit of measure will be reported as non-natural (“Line expression indicator” tag will report “false”).

Line description

Previously this field in the report was optional and when there was no value in the related line of the invoice, this tag was not reported. Version 1.1 of the report requires this tag to be reported when <lineExpressionIndicator> tag is reported.

For the cases when there is no value in the related line of the invoice, this tag will indicate voucher of the related invoice, but it is recommended to define description in all the lines of the invoices of all the types (excepting the invoices posted from a sales order - for this case <lineDescription> tag will report item as it was implemented before).

Unit of measure

Before starting using of the new version of the report, user will need to setup Online invoicing system classifier for Unit of measurements defined in the Legal entity. Open General ledger > Setup > Sales tax > External > Online invoicing system classifiers and establish the correspondence between the reference units of measurement and enumerated list of the Online invoicing system. Match all the units in your Legal entity. and establish the correspondence between the reference units of measurement and enumerated list of the Online invoicing system. As for example, for kilometer you would add the following line:

-  Unit of measure: "km" (value from Units of your Legal entity)

-  Online invoicing classifier: "KILOMETER"

Match all the units in your Legal entity for which you can find related value in the enumerated list:

If this setup is not done all the unit of measure will be reported as “OWN”.

Unit of measure own

The new <unitOfMeasureOwn> tag is added to the XML report. This tag is reported when “UnitOfMeasure” tag is “OWN”. No specific setup is needed.

TLS version change to 1.2

The hot fix provides specific changes to support this requirement. TLS version 1.2 will be used for interoperation with the Online Invoicing System.

<exchangeRate> tag's value calculation is changed

In Online invoicing system <exchangeRate> tag’s value must report currency exchange rate from the CurrencyCode of the invoice to CurrencyCode in the TaxCode of the first tax transaction of the invoice on Date of VAT register of the invoice.

This hot fix provides the following algorithm of exchange rate identification:

Definitions:

A = CurrencyCode of the invoice (for example EUR or HUF)

B = CurrencyCode in the TaxCode of the first tax transaction of the invoice {it is supposed that all tax transactions by the same invoice must have the same CurrencyCode in related tax codes setup} (for example HUF)

Algorithm:

IF A = B

THEN exchangeRate = “1”

ELSE exchangeRate = Currency exchange rate of the type defined as “Accounting currency exchange rate type” in the Ledger setup from A to B on the Date of VAT register of the invoice

With this change to avoid potential “INCORRECT_SUMMARY_DATA_INVOICE_VAT_AMOUNT_HUF” warning (p.206 of “Invoice Data Reporting, Description of the REST API Interface & Developer’s Documentation”) which is described as following:

“Issues a warning if the output VAT amount in the aggregate invoice in the invoice’s currency and the VAT amount in HUF do not correspond based on the exchange rates indicated in the line items.  Calculation: in the case of currencyCode<>”HUF”, the VAT amount in each line item (lineVatAmount) must be multiplied by the exchange rate value in the line item (lineExchangeRate), and the total of these products amounts to the invoice VAT amount in HUF (invoiceVatAmountHUF).  Tolerated deviation: 1% of the invoiceVatAmountHUF element, but at least 1 unit.”

calculation of the following tags’ values is also changed respectively:

- <lineVatAmountHUF> is calculated as <lineVatAmount> multiplied by exchangeRate

- <vatRateVatAmountHUF> is calculated as <vatRateVatAmount> multiplied by exchangeRate

- <invoiceVatAmountHUF> is calculated as <invoiceVatAmount> multiplied by exchangeRate

Be aware: reported values in <lineVatAmountHUF>, <vatRateVatAmountHUF>, <invoiceVatAmountHUF> tags may differ from the values stored in the tax transactions in some cases due to following reasons:

-          Exchange rate on transaction date and exchange rate on Date of VAT register are different.

-          Accounting currency and currency defined for the sates tax code are different and triangulation exchange rate (which used on posting: document currency > accounting currency > tax code currency) on posting moment may differ from the exchange rate from document currency to tax code currency on Date of VAT register.

These aspects should be under user control and may require corrective tax transactions.

Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:

https://mbs.microsoft.com/support/newstart.aspx

You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

Partners

https://mbs.microsoft.com/partnersource/resources/support/supportinformation/Global+Support+Contacts

Customers

https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htm

In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.