Croatia E-Invoicing Requirements: 2026 Guide

Croatia e-invoicing requirements changed materially on January 1, 2026. VAT-registered businesses established, resident, or ordinarily resident in Croatia must now issue and receive structured e-invoices for domestic transactions under Fiskalizacija 2.0. In practice, a Croatian entity can no longer treat paper or PDF-only domestic invoicing as sufficient on its own. It needs a structured exchange setup, a recognized connection path into the live ecosystem, and internal procedures for the related fiscalization and reporting layer.

That answer matters because many English-language explainers about Croatia still reflect the older public-sector story. Croatia already had eRacun obligations in the B2G context, but the live 2026 regime is broader: it reaches domestic B2B invoice exchange for VAT-registered businesses and sits inside a wider reform that also expands fiscalization in B2C. Those are connected reforms, not identical workflows. A finance team that understands only "Croatia has B2G e-invoicing" will miss what changed for private-sector domestic invoicing in 2026.

The regime is also no longer theoretical. In Croatian Tax Administration's January 2026 Fiscalization 2.0 update, the authority said the system had already recorded 304,726 e-invoice issuers and recipients and 3,312,238 fiscalized e-invoices. Those figures tell you this is now a live operating environment with real transaction volume, not a project that can be postponed until the next budget cycle.

If you are responsible for AP, AR, ERP, or shared-services support, the key takeaway is straightforward: older B2G-only guidance is incomplete, and a domestic Croatian invoice process now needs to account for structured exchange, routing, validation, and downstream handling from day one.

---

What changed between the old B2G model, the 2026 rollout, and the 2027 extension

The easiest way to understand Croatia's reform is to separate the legacy public-sector context from the new rollout phases.

Date	What changed	Why it matters
September 1, 2025	Testing, technical documentation, and access-point or intermediary readiness moved from theory into active preparation.	This was the point when businesses and service providers needed to start validating whether their systems could exchange and fiscalize e-invoices in the new model.
January 1, 2026	VAT-registered businesses established, resident, or ordinarily resident in Croatia became obliged to issue and receive structured domestic e-invoices.	This is the live B2B and B2G operating date that makes many 2025 advisory summaries outdated.
January 1, 2027	The broader regime extends further, including wider obligations affecting businesses outside the VAT-registered population.	Teams that rely on temporary workarounds in 2026 still need a plan for the next phase.

Before this reform, Croatia was already part of the European B2G e-invoicing conversation. That is why older materials often focus on public procurement, public-sector routing, and baseline structured-invoice rules. From a 2026 finance-operations perspective, that is only part of the picture. The new law pulls domestic B2B activity into the same live compliance environment and pairs invoice exchange with fiscalization and e-reporting expectations.

It also helps to keep three tracks separate:

• B2G e-invoicing: an existing public-sector context that did not disappear.
• B2B domestic e-invoicing: the major operational change for VAT-registered businesses from January 1, 2026.
• B2C fiscalization: related to the wider reform, but not the same as exchanging structured supplier invoices between businesses.

If you have followed Germany's EN 16931 B2B e-invoicing transition or Romania's RO e-Factura rollout and reporting deadlines, Croatia now belongs in the same mandate conversation. The difference is that Croatia's Fiscalization 2.0 model is especially workflow-heavy because it combines structured invoice exchange with a tax-facing fiscalization layer rather than treating file format compliance as the whole project.

---

Who must issue, who must receive, and which invoices are actually covered

The scope question is where most internal confusion starts. Croatia's 2026 mandate is not a blanket rule for every invoice a multinational group sends anywhere in Europe. It is a rule about domestic Croatian transactions and about the status of the relevant entity.

Use this practical scope map:

Scenario	What matters in 2026
VAT-registered Croatian business issuing a domestic B2B invoice	It must be able to issue a structured eRacun that fits the live Fiscalization 2.0 environment.
VAT-registered Croatian business receiving a domestic B2B invoice	It must also be able to receive and process the structured invoice, not just send one.
Croatian supplier invoicing a public body	B2G routing remains relevant, but it now sits inside a broader domestic e-invoicing environment rather than a separate legacy world.
Non-VAT business in 2026	It is not yet in the same broad issuer population as VAT-registered businesses, but it still needs to understand receipt-side tools and the 2027 expansion path.
Foreign parent with a Croatian subsidiary or Croatian VAT footprint	Scope should be mapped at entity and transaction level, not assumed from group policy.

Two points deserve emphasis. First, recipient readiness is a legal and operational issue, not an afterthought. If your team only focuses on outbound invoice generation, you can still fail in practice because inbound structured invoices need to be received, validated, routed, and reconciled in your AP process. Second, the local entity matters. A foreign shared-services team may own the process, but the Croatian status of the supplier or recipient determines whether the domestic e-invoicing obligation applies.

This is also why older "Croatia eRacun requirements" articles can mislead readers in 2026. They often answer the narrower question of public-sector structured invoicing. A finance team managing domestic sales and purchases between private-sector Croatian counterparties now needs a wider scope assessment that covers both sides of the transaction.

---

How the live Croatian workflow works: AMS, intermediaries, FiskAplikacija, and validator updates

For most teams, compliance becomes clearer once you stop thinking in legal definitions and start thinking in workflow steps.

1. Choose your connection model. Croatia publishes certified information intermediaries that can provide exchange, fiscalization, e-reporting, and metadata services. In practice, many businesses will work through one of these providers because the law is not asking finance teams to improvise their own routing model from scratch.

2. Set up the participant and routing layer. When teams search for "Croatia AMS directory e-invoice," they are usually trying to understand how the ecosystem identifies who can receive e-invoices and through which path. AMS is part of that live routing and participant-management layer, so onboarding is not just a formatting exercise.

3. Prepare the structured invoice and validation logic. Croatia sits inside the EN 16931 ecosystem, and the technical documentation around UBL 2.1-based XML schemas and validators matters operationally. Your ERP or invoicing platform needs to produce data that passes the current technical rules, not the version someone screenshotted from a 2025 webinar.

4. Handle the fiscalization side as well as the exchange side. A Croatia information intermediary e-invoice setup is not only about transporting the file. The wider process also covers fiscalization and reporting obligations, which is why businesses need clear ownership between tax, ERP, AR, and AP teams.

5. Monitor the live tools after go-live. Official Croatian Tax Administration pages kept publishing updates in January, February, and March 2026, including validator and XML schema changes scheduled for mid-March. That matters because the implementation job continues after launch.

FiskAplikacija sits in this wider environment as a free tax-administration application for reviewing fiscalized data, statuses, authorizations, and related reporting information. It is useful context even when your main exchange route runs through an intermediary, because finance teams still need visibility into what the tax-facing system says happened.

Teams familiar with Hungary's real-time invoice reporting model will recognize the need to keep tax-facing interfaces current. Croatia adds another layer by tying that operational discipline to structured domestic e-invoice exchange, which is why implementation owners need both technical and process controls.

---

KPD codes, MIKROeRacun, and the 2027 change for non-VAT businesses

Some of the most useful Croatia-specific details are the ones generic compliance summaries barely mention.

The first is KPD 2025, Croatia's product and service classification. During the preparation period, the Croatian Tax Administration told businesses to link their goods and services to the KPD 2025 nomenclature, with e-invoice item data tied to the correct classification code at a level of at least six digits. That means "Croatia KPD invoice codes" is not a side issue for master-data teams. It affects how invoice lines are categorized, how ERP data is maintained, and whether issued documents are ready for the local reporting environment.

The second is MIKROeRacun. Croatia's official guidance positions MIKROeRacun as a free state-supported access option for smaller businesses that are not in the VAT system. During 2026, the tool is mainly about receiving e-invoices and fiscalizing their receipt. From January 1, 2027, it also supports issuing and fiscalizing issued e-invoices. That makes Croatia MIKROeRacun 2026 a bridge for smaller entities, not a reason for VAT-registered businesses to delay their main implementation.

There is also a practical edge case here. The Tax Administration published guidance in December 2025 for taxpayers exiting the VAT register, including how eligible businesses could activate MIKROeRacun as they moved into that non-VAT position. For accountants and bookkeepers, that means the 2026 to 2027 transition is not only about new companies. It can also affect existing clients whose VAT status changes.

Put differently, KPD mapping and MIKROeRacun planning sit close to the real work of onboarding suppliers, preparing master data, and handling exceptions. They are exactly the kind of country-level details that a legal summary often leaves out, but an implementation team cannot.

---

What finance teams should change now in AP, ERP, and downstream invoice-data controls

If Croatia is already live in your business, the right response is an implementation checklist, not another slide about upcoming reform.

• Map your in-scope entities and flows. Identify which Croatian entities are VAT-registered, which domestic transactions they issue, which they receive, and where B2G activity still follows a distinct routing path.
• Confirm the exchange model. Decide whether each entity will work through a certified intermediary, another approved connection model, or a state-supported tool where applicable.
• Review ERP output and inbound handling together. Outbound XML generation is only half the job. AP teams need a defined way to receive, validate, reject, approve, archive, and reconcile inbound structured invoices.
• Assign ownership for validator and schema changes. Somebody needs to monitor technical notices and keep interfaces current when the Croatian Tax Administration publishes updates.
• Prepare for KPD and master-data dependencies. Classification, product data, tax logic, and supplier onboarding all need local ownership.
• Separate legal compliance from downstream review work. Structured exchange improves consistency, but it does not remove the need to check invoice content, handle credit notes, resolve mismatches, or export data for shared-services controls.

That last point is where many projects go wrong. A compliant routing setup does not automatically give finance teams usable analysis data across every document that still enters the process. If your group continues to receive PDFs, credit notes, vendor statements, or mixed supporting files alongside Croatian e-invoices, invoice data extraction workflows for e-invoice compliance can still help normalize those records into Excel, CSV, or JSON for review, reconciliation, and exception handling. Invoice Data Extraction is useful in that downstream layer because it can process invoices, credit notes, vendor statements, and other finance documents into structured outputs, but it is not a Croatia transmission network, AMS directory, or mandated information intermediary.

For most teams, the next sensible move is to combine legal-scope confirmation with workflow testing: verify who is in scope, verify how invoices move, verify how exceptions are handled, and then make sure the resulting data still lands in a format your AP, controller, and accounting teams can work with every day.