Hungary

Hungary is now available as a country in LN. Various Hungarian requirements are supported.

Master data

These features are supported:

  • Entry of organization number and VAT registration number for the company, suppliers, and customers according to the format and control methods used in Hungary
  • Business partner tax number – local tax number
  • Zero tax categorization

Country specific reporting

With the report designer, you can personalize these reports to fit your business or local regulatory requirements:

  • Balance sheet, profit and loss, cash flow statement
  • Trial balances
  • User-defined cost center analysis, contribution analysis
  • Budget/actual comparison in any time frame

General ledger

These features are supported:

  • The most commonly used chart of accounts
  • Multiple accounting dimensions
  • Foreign currency revaluation
  • Debit/Credit handling (Tartozik/Követel)
  • Multiple taxonomies
  • Intercompany with trade and logistics
  • Periodic revaluation of open balances in foreign currencies to account for unrealized currency gains or losses
  • A standard general ledger interface to upload transactions from spreadsheet files or other legacy systems
  • Print trial balances by account or dimension
  • External integration to export financial documents, general ledger balances and general ledger movements
  • Year and period closing routines

Accounts receivable

These features are supported:

  • Invoicing requirements
  • VAT on prepayments
  • Open item reports and account statements

Accounts payable

These features are supported:

  • VAT and customs invoices connection for foreign supplies
  • VAT date handling on delivery
  • Accrual VAT accounting for invoices and unreceived goods
  • Prepayments
  • Open item reports and account statements

Sales invoicing

These features are supported:

  • The Hungarian invoice layout includes invoice date, due date and delivery date
  • Online upload of Hungarian invoices to the tax authority’s portal

Tax management

These features are supported:

  • XML audit report of Sales invoices
  • VAT report1 – Inland sale and purchase detailed reports
  • VAT report2 - Inland sale and purchase for special (commodity codes) items
  • Calculation of VAT according to laws in Hungary
  • Tax declaration through configuration
  • The attributable VAT calculation for EU purchases and the self-assessment or “tax shift” requirement for non-domestic, non-EU supplier services
  • EU triangulation, EU simplified triangulation, and fiscal representation from a VAT, EU sales, and Intrastat perspective
  • Intrastat Reporting
  • Sales Listing EU

Fixed assets

These features are supported:

  • Straight, user defined and declining depreciations
  • Fixed asset catalogue
  • Increased FA value
  • Reduced economic lifetime
  • Printing of historical values and other reports

Current assets

Valuation methods for inventory are supported, which include FIFO, LIFO, Moving Average Unit Cost (MAUC), Lot costing, and Standard cost.

SHA3 support

The Hungarian tax authority will modify the invoice upload method with strict SHA3-512 hash usage. To support this, you can select the applicable hash usage in the Hash Algorithm field of the Payment/Receipt Method (tfcmg0540m000) session.

EKAER

EKAER is an electronic system operated by the Hungarian state tax and customs authority and is intended to monitor compliance with the tax obligations arising from the transportation of goods on public roads from a member state of the European Union to the territory of Hungary or vice versa, or in the context of internal trade, inside the territory of Hungary. An EKAER number identifies a product unit that is transported from a consignor to (multiple addresses of) a single consignee in a single motor vehicle, via a certain route.

Companies are required to send the Hungarian authorities a digital document for each address delivery that leaves the premises. This document includes information such as the contents of the shipment and the carrier. To avoid sending incorrect information or resending a document many times, the shipment should be more or less final.

An official unique sequence number (EKAER code) is issued by the authorities and attached to the EKAER file. This number is also printed on shipping documents. It is important that the transport operator or transport organizer is informed about the EKAER number.

In LN, the EKAER procedure is applicable if these conditions are met:

  • The Hungary check box is selected in the Implemented Software Components (tccom0100s000) session.
  • The EKAER Implemented check box is selected in the Hungarian Parameters (lphun0100m000) session.
  • At least one of these conditions applies:
    • The ship-from country belongs to the European Union and the ship-to country is Hungary.
    • The ship-from country is Hungary and the ship-to country is in the European Union.
    • Both the ship-from country and the ship-to country is Hungary.

To support the EKAER procedure in LN, an additional communication activity has been added to the shipping process. For loads and shipments, a trade card is applicable. Trade cards, which are displayed in the Trade Cards (lphun4135m000) session, include the required shipping information to decide whether to send an EKAER request to the authorities.

In the loads and shipment sessions of the Hungarian Localization module, such as lphun4140m000, lphun4640m000, and lphun4130m000, data can be modified. In this way, the EKAER request can be influenced. If all the data on the trade card is correct, the EKAER request can be sent.

The data that is required to decide whether to request an EKAER number is gathered during the freezing of a load and stored in new tables in the Hungarian Localizations (lphun) module. Based on this data, the transport administrator determines if an EKAER number is required.

The response from the government authorities can be a failure or a success. In the case of a failure, the data must be modified and an update of the trade card / EKAER request is sent. If the response is a success, the transport administrator can still decide that changes are required. Several updates of the EKAER request can be sent. If the result is correct and accepted, the request can be finalized. The EKAER number is then stored on the shipment, also in LN Warehousing, and the warehousing procedure can continue.

Alternatively, an EKAER request can be skipped. If it is skipped, the Trade Card Complete check box is selected on the LN Warehousing shipment and the procedure can continue.
Note: 
  • Loads for which an EKAER number is requested must be frozen in LN Warehousing.
  • If an EKAER number is available, the load and shipment(s) can be confirmed in LN Warehousing.