Standard-first delivery
Implementation by phases
Verified business data
Odoo can be the central system for sales, purchasing, invoices and accounting data. However, installing the Croatian localisation alone does not prove that your information intermediary, certificates, product classifications, authorisations and operating procedures are configured correctly.
Who issues eInvoices from 2026, and who only receives them?
For VAT-registered businesses, the full eInvoice exchange obligation started on 1 January 2026. This includes issuing and receiving eInvoices for transactions covered by the Act and fiscalizing the prescribed data.
Income-tax or profit-tax payers outside the VAT system must be able to receive eInvoices from the same date. Their statutory obligation to issue them starts on 1 January 2027. The same distinction in deadlines is relevant to the groups of budget users described by the Act.
Receiving and issuing are not the same function. A company may be ready to receive a structured document without having configured the complete outgoing process. The assessment should therefore follow incoming and outgoing invoices separately.
The current overview and links to questions and answers are available on the official Croatian Tax Administration Fiscalization 2.0 page. The legal basis is the Fiscalization Act, Official Gazette 89/2025, while operational details are further regulated by the eInvoice Ordinance, Official Gazette 11/2026. For an overview without technical language, read the guide to what changes and for whom. If you are outside the VAT system, separately check when you must receive and when you must issue eInvoices.
What can Odoo support in the eInvoice process?
Odoo can connect data about partners, products, taxes, sales or purchase documents and accounting entries. In a well-configured process, an outgoing invoice is created from a confirmed business event, while exchange status and further processing have a clearly responsible person. An incoming invoice enters a controlled review, approval and posting flow.
The actual eInvoice exchange and fiscalization method depends on the available localisation, Odoo version, information intermediary and specific architecture. This is not a detail to assume. The supported format, authentication, statuses, error processing and archiving method must be checked.
Official Odoo 19 documentation lists Croatian electronic exchange through the l10n_hr_edi module and the mojeRačun provider. This is an important starting point, but it does not replace verification of the specific database, intermediary contract and entire process from issue to status processing.
A separate page provides an overview of Odoo Accounting for Croatia, while practical limitations of the standard solution are explained in Odoo fiscalization in Croatia. The complete operational flow for sales and purchase invoices is shown in How Odoo handles eInvoices in practice.
What should be checked before go-live?
First determine which legal entity and transaction type fall within the obligation. One database may contain several companies, while the same business may have B2B, B2C and foreign invoices. For every flow, you need to know whether eInvoicing, fiscalization in final consumption or another rule applies.
Then check master data. Croatian tax numbers, addresses, partner tax status, units of measure, taxes and product classifications must be consistent. An incorrect product classification will not become correct merely because the document was sent successfully.
The third step is responsibility. Who monitors rejected documents? Who reacts when the intermediary does not deliver an invoice? Who reconciles the accounting status with the operational status? Every exception needs an owner and a procedure.
Finally, run a test with representative documents. Include a standard domestic B2B invoice, a credit note or reversal, an invoice with several tax rates and at least one expected error. Confirm what the issuer sees, what the recipient sees and what the accountant sees.
Does Odoo assume responsibility for legal compliance?
No. Odoo and connected solutions can execute a configured process, transmit data and record statuses. They cannot assume responsibility for your tax classification, invoice content or internal decisions.
The final setup should therefore be checked with an accountant or tax adviser. The implementer verifies the technical and process flow. The accountant confirms the accounting and tax treatment for your situation. These two checks complement each other.
When do you not need a new ERP for Fiscalization 2.0?
If you issue few invoices, have a simple process and use an accounting service that already provides a suitable solution, a new ERP solely for eInvoices may not make economic sense. First check what you already pay for and where the actual gaps are.
ERP becomes relevant when the legal obligation is accompanied by a need to connect sales, purchasing, inventory, manufacturing or management reporting. In that case, the eInvoice is not an isolated add-on but part of a wider process.
Which errors should be tested before production?
Successfully sending one standard invoice is not a sufficient test. Deliberately use an invalid Croatian tax number or omit a mandatory value and check whether the responsible person receives an understandable notification. Send the document again after correction and verify whether a duplicate is created. Also test external-service unavailability so you know where the document waits and who sends it again.
Check whether Odoo can connect the original invoice, the message to the intermediary, the fiscalization status and a possible recipient rejection. Without that trace, an employee only knows that something failed, but not at which step the problem occurred. A good test record should allow the error to be explained without direct database access.
Finally, decide what happens outside working hours. An automatic retry may be useful, but a critical error must have an owner and a response deadline. This operating agreement is as important as the technical integration.
What does an initial Odoo assessment include?
The initial assessment covers the Odoo version and hosting, installed applications, legal entities, invoice types, existing localisation and selected information intermediary. The result should be a short list: what works as standard, what needs configuration, what requires integration and what the accountant must confirm.
Do not start with a large quotation. Start with one incoming and one outgoing flow and document the entire path, including an error and retry. This is the fastest way to separate real requirements from assumptions.
If you want to review your Odoo process for Fiscalization 2.0, send the system version, hosting type and a description of how invoices are issued. You will receive an assessment of the technical scope, with items that must be confirmed with your accountant clearly identified.
Start with one real process
A representative document reveals the real scope faster than a generic feature list.