Slovakia introduces e-invoicing system and the “White List” of bank accounts
Ridvan Yigit
Founder & CEO | Tax Technology & Regulatory Reporting | Europe's VAT policy group | Experienced Software Engineer & Strategic Business Development Leader | TaxTechnologist
Slovakia was one of the first countries to introduce detailed electronic VAT reporting . In 2014, the kontrolny vykaz (control statement) requirement came into force. This is a local, XML-based sales and purchase listing report. A similar provision was introduced in the Czech Republic two years later, in 2016.
Therefore, it is no surprise that Slovakia is following current trends in digital taxation and is already imposing new obligations in 2022, namely, mandatory B2G, G2G, and G2B e-invoicing, as well as requiring that payments only be made to bank accounts registered in the special list provided by the tax administration.
Slovak e-invoicing system: Deadlines
Slovakia has decided to introduce a central e-invoicing system called Informa?ny Systém Elektronickej Fakturácie (IS EFA). The pilot phase is already in place, whereas the process of “going live” is divided into two parts:
IS EFA: Technical outline
The Slovak national e-invoicing framework consists of the following modules presented in the diagram below:
There are two main methods of entering invoices in the IS EFA system:
Many of the technical details are well-known from similar e-invoicing developments in other countries. In particular, the Slovak system relies on XML-format invoices in the UBL 2.1. standard, which is also in place in Serbia, for example. A dedicated API facilitates communication between different modules of the IS EFA.
The “White List” of bank accounts
Slovakia had decided to introduce another requirement to reduce tax fraud, which works similarly to the White List Poland obligation, providing a white list of taxpayers and bank accounts.
Starting from January 2022, the tax administration of Slovakia (Finan?ná správa) is to publish an updated list of all bank account numbers disclosed by companies daily. By the end of November 2021, Slovak VAT-registered taxpayers already had to provide tax authorities with all bank accounts that they use in their economic activities.
Most importantly, payment for an invoice must be made only to the supplier’s bank account as stated on the list published by tax authorities. Otherwise, a customer becomes jointly responsible for the supplier’s VAT liability. The only way of avoiding joint responsibility when making payment to an account not registered on the White List is to use a split-payment method.
It is possible to verify the bank account number of a company directly on the tax office website. What needs to be provided is the VAT ID number of the taxpayer. As a result, there is a list of bank accounts that this company uses. Another method is to download a “flat file” (in XML format) containing a list of all taxpayers and their respective bank accounts.
However, the third method of verifying taxpayers’ bank account numbers seems to be the most convenient, especially for large companies that make many payments daily and need to verify large accounts. There is a unique API published by the tax authorities called OpenAPI. As well as ascertaining bank account numbers, this API allows users to check other Slovak tax databases. For example, it is possible to confirm whether a particular Slovak VAT ID is valid.
Process changes are unavoidable.
Companies operating in Slovakia need to prepare for the requirements outlined above. Businesses operating in public procurement should already have an e-invoicing solution in place. However, other companies should already be preparing for the e-invoicing implementation. In practice, the introduction of a national e-invoicing IS EFA system will impact most business processes, in particular, AP and AR.
The requirement of verifying bank account numbers before making payments also needs to be reflected in company processes. Additional procedures will probably need to be designed and followed. Although there is a possibility to avoid joint and several liability by using the split-payment method, this cannot be considered a “workaround” solution. Split payment also has significant disadvantages. In particular, it has a negative cash-flow impact and is also more complex from a technical perspective.
To sum up, meeting new digital tax requirements, such as Slovak ones, requires the cooperation of multiple stakeholders and cannot be successfully implemented in a “silos” model. IT developers need to closely cooperate with finance departments (AP, AR, tax, and internal control), which also need to understand each other to make the required changes happen.
For further details, do not hesitate to comment or contact me.
+44 7833 537388 | [email protected]
Ridvan Yigit