Hungary: Online Invoicing System v.1.1 support on Dynamics 365 for Finance and Operations

Applies to: Dynamics 365 for Finance and Operations

Introduction


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

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

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

1) XSDversion is updated from 1.0 to 1.1.

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

Table belowprovides references on previously published articles about implementation ofinteroperation with Hungarian Online Invoicing System:

Version of Dynamics 365 for Finance and Operations

Link on KB article

7.1

https://support.microsoft.com/help/4341611

7.2

https://support.microsoft.com/en-us/help/4341308

7.3

https://support.microsoft.com/en-us/help/4341482

8.0

https://support.microsoft.com/en-us/help/4341649/

Overview


Accordingto 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

- Some improvements in the package ofElectronic messages functionality setup

Implementation details


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

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

The change is implementedrespectively in all the formats included to the feature and new versions of theformat must be imported from the LCS portal:

Configuration name

Configuration type

Version

Invoices Communication Model

Model

 56

RTIR mapping

Model mapping (export)

 56.57

RTIR Invoice Data (HU)

Format XML (export)

 56.28

RTIR Token Exchange Request (HU)

Format XML (export)

 56.11

RTIR Manage Invoice Request (HU)

Format XML (export)

 56.15

RTIR Query Invoice Status Request (HU)

Format XML (export)

 56.10

RTIR Query Invoice Data Request (HU)

Format XML (export)

 56.9

Electronic Messages framework model

Model

 19

RTIR import model mapping

Model mapping (import)

 19.9

RTIR import format (HU)

Format XML (import)

 19.13

Latest versions of all of theformats must be imported from the Shared asset library of the LCS portal.

Thenew versions of the formats will be imported with Effective from datedefined as May 2, 2019. Starting from this date the new versions of the formatswill be used by the system during interoperation with Online Invoicing System.

Line expression indicator

New<lineExpressionIndicator> tag of type Boolean must be reported forinvoice lines in all the cases covered by the scope of the Online invoicingsystem on Dynamics 365 for Finance and Operations.

The<lineExpressionIndicator> tag must be reported with "true"value for natural units of measure. When unit of measure is not indicated foran invoice line, <lineExpressionIndicator> tag must be reported with"false" value.

Before starting using of thenew version of the report, user will need to setup Application specificparameters. Open Electronic reporting work-space, select latest importedversion of the RTIR Invoice Data (HU) format, select Configurations> Application specific parameters > Setup on the Actionpane, select UnitOfMeasureTypeLookup on Lookups fast tab for the latestversion of the format and define which units of measurement must be reported asnatural ("true" for Line expression indicator in Online invoicingsystem). Match all the units in your Legal entity. As for example, forkilometer you would add the following line:

- Lookupresult: "Natural"

- Line: 1

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

Important note! At the end of the list add the following twolines:

Lookup result

Line

Unit of measure

NONE

Must be penultimate

*Blank*

Other

Must be the last in the list

*Not blank*

When all the necessary correspondences are established, change "State" of the Application specific parameters configuration to "Completed" and save the configuration.

Line description

<lineDescription>tag must be reported when <lineExpressionIndicator> tag is reported.

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

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

Unit of measure

<unitOfMeasure>tag type is changed with version 1.1 and it must be reported with one of thevalue from enumerated list.

Before starting using of thenew version of the report, user will need to setup Application specificparameters. Open Electronic reporting work-space, select latest importedversion of the RTIR Invoice Data (HU) format, select Configurations> Application specific parameters > Setup on the Actionpane, select UnitOfMeasureLookup on Lookups fast tab for the latestversion of the format and establish the correspondence between the referenceunits of measurement and enumerated list of the Online invoicing system. As forexample, for kilometer you would add the following line:

- Lookupresult: "KILOMETER"

- Line: 1

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

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

UnitOfMeasureType

Description (hu)

Description (en-us)

PIECE

Darab

Piece

KILOGRAM

Kilogramm

Kilogram

TON

Metrikus tonna

Metric ton

KWH

Kilowatt óra

Kilowatt hour

DAY

Nap

Day

HOUR

Óra

Hour

MINUTE

Perc

Minute

MONTH

Hónap

Month

LITER

Liter

Liter

KILOMETER

Kilométer

Kilometer

CUBIC_METER

Köbméter

Cubic meter

METER

Méter

Meter

LINEAR_METER

Folyóméter

Linear meter

CARTON

Karton

Carton

PACK

Csomag

Pack

OWN

Saját mennyiségi egység megnevezés

Own unit of measure

Importantnote!You may skip adding all the "own" values to list, define "*Notblank*" for "OWN" Lookup result, this will mean that all theothers values will be reported as OWN. The "OWN" Lookup resultmust be mandatory added and be the last in the list.

When all the necessary correspondences are established, change "State" of the Application specific parameters configuration to "Completed" and save the configuration.

Unit of measure own

New <unitOfMeasureOwn> tag is added with version 1.1 and it must reportinformation about a unit of measure for which there is no value found from theenumerated list of <unitOfMeasure>. This tag must be reported when<unitOfMeasure> tag is represented with "OWN" value.

The new <unitOfMeasureOwn> tag is added to the ER format. Nospecific setup is needed.

TLS version change to 1.2

Nospecific changes are implemented to support this requirement. For versions 10UAT and PROD platform supports TLS 1.2 (Dev deployments currently support 1.0,1.1, 1.2). But in case of report submission problem due to the version of TLS,an IcM request need to be addressed, and the environment will be updated to TLS1.2.

Some improvements in thepackage of Electronic messages functionality setup (optionally for 7.3 and 10.0.2+ only)

New versionof the package providing predefined set of values in data entities involved inthe setup of Electronic messages for the process of interoperation withHungarian Online Invoicing System can be downloaded from the Data package section of Shared asset library of the LCS portal –

HU RTIR setup v3.zip”. This packageprovides the following changes in comparison with the previous version:

1.       New resulting status of “Technical error” type is added to theactions of “Electronic reporting import”type (Import token response, Import invoice response, Import status response).These statuses are added as initial for the following actions:

Action

Status added as initial

Reset EM status

Error token response importing;

Error invoice response importing

Generate status request

Error response import of status request

2.       The “HU RTIR setup v3.zip”package includes setup of Electronic reportingformats. For now, no additional setup of Electronic reporting configurations isneeded after importing of the package.

The newversion of the package is not mandatory for importing but recommended. Afterimporting if you import with “Truncate entity data”marked, you will need to setup again:

-         Executableclasses parameters (Tax > Setup > Electronic messages > Executableclass settings).

-         Webservices parameters (Tax > Setup > Electronic messages > Web servicesettings).

-         Batchsettings on Electronic message processing (Tax > Setup > Electronicmessages > Electronic message processing), if it was used.

-         Securityroles on Electronic message processing (Tax > Setup > Electronic messages> Electronic message processing), if it was used.