What is an eInvoice and why do you need it?
An eInvoice, or electronic invoice, is an invoice that is issued, sent, and received in a structured electronic format. This format allows for automatic processing without paper or manual data entry. Folowing the implementation of the Fiscalization Act from January 1, 2026, all taxpayers registered in the VAT register with their headquarters, residence, or habitual abode in the Republic of Croatia will be required to send and receive eInvoices for domestic transactions.
Tax Authority is responsible for Fiscalization 2.0. More information can be found on its official website https://porezna.gov.hr/fiskalizacija/bezgotovinski-racuni.
We suggest to watch our webinar with the full details of the scoope of the Fiscalization law (currently only in croatian) https://www.youtube.com/watch?v=89uvg8bgfWI
How to prepare?
1. Link your list of goods and services with the Classification of Products by Activity of the Republic of Croatia, 2025.
2. Choose an information intermediary
3. Sign a contract with the information intermediary
4. Authorize the information intermediary in the Fiscalization and eReporting Application (FiskApplication)
5. Start using eInvoice exchange systems
Once everything is set up, you can start using the intermediary’s solution for creating, sending, and receiving eInvoices, as well as for fiscalization. This significantly automates business operations, speeds up processes, and saves resources – with proper preparation, the eInvoice can be an opportunity to modernize your business model.
Each exchanged eInvoice can be downloaded and delivered to your accountant, unless your accountant is already integrated with the intermediary – in which case, everything is handled automatically.
By December 31, 2025, eInvoice recipients must provide and confirm their address for locating the final receiving address of eInvoices via the Metadata Services Directory (AMS).
Submitting data to AMS can be done:
To ensure timely preparation for upcoming business changes, the Tax Administration continuously publishes documents available in the ‘Documentation’ section. Please note that documents are periodically updated to adapt to the development of IT solutions for secure and accurate eInvoice exchange.
Classification of goods and services in eInvoices
Selected questions on the classification of products by activity
In the eInvoice/Documentation section, selected questions on the classification of products by activity (CPA) are published.
About the Classification of Products by Activity of the Republic of Croatia, 2025 (CPA 2025)
CPA 2025 is the central product classification and statistical standard used for the collection and publication of product-level data and for international data exchange. It is fully aligned with the Statistical Classification of Products by Activity – CPA 2.2 of the European Union.
You can find more information regarding KPD classification codes in document that Croatian Tax Authority published on a web site from of Tax Authority .
Diagram of F 2.0 from ERP & MER standpoint
Flow of eInvoice exchange between ERP system of a supplier through MER to the customer:
Supplier creates XML of the eInvoice inside ERP system. ERP sends XML to MER system
MER system pings AMS and checks if the customer is registered in AMS. Based on the answer from AMS, MER initiate sending to fiscalization system or rejects document from further processing.
In case customer is registered in AMS, MER will validate XML before sending it to fiscalization system. If XML fails on validation, MER rejects document from futher processing.
In case XML and AMS registration is OK, MER will send eDocument metadata to fiscalization first, then send it to the Access point of the customer.
Supplier ERP system pulls status of the fiscalization if previous step is succesfully executed
In case fiscalization is successful, MER sends document to the access point of the customer. ERP only pulls status of the sent eInvoice periodically (to get information in case customer rejected eInvoice).
In case fiscalization failed, or in case customer is not registered in AMS, MeR sets status of sent eInvoice to Unsucessful.
Supplier needs to send XML of eInvoice via API to eReporting system. MER then initiates sending an XML to eReporting system and sets status of the send document as successful eReporting. Supplier sends invoice to the customer via other methods.
Supplier sends payment information via ERP system to MER who sends it to TaxAuthority system.