Croatia Public-Sector E-Invoicing: Supplier Guide

Croatia public sector e-invoicing is mandatory when you invoice a Croatian public body through the public procurement workflow. Croatian public entities have had to accept EN 16931-compliant electronic invoices since December 1, 2018, and suppliers have had to issue them since July 1, 2019 through Servis e-Racun za drzavu. When the invoice is delivered through Peppol to a Croatian public procurement recipient, the routing format suppliers need to use is 9934: buyer's OIB.

That headline answer matters because many English-language summaries blur together two different topics: the long-standing Croatian B2G model for public bodies, and the broader domestic B2B reform timetable that followed later. If your customer is a ministry, municipality, hospital, school, agency, or another public-sector contracting body, the immediate question is not whether a PDF can be emailed. It is whether your invoice has been created as a structured public procurement e-invoice and sent through the correct exchange path.

Croatia's rules are also wider than many suppliers expect. According to the European Commission's Croatia eInvoicing country page, the obligation extends beyond classic EU-threshold public procurement to certain below-threshold goods and services under EUR 26,540, works under EUR 66,360, and direct-award purchase orders. That means a supplier can be inside the mandate even when the transaction does not look like a large formal tender from the outside.

The practical job for you is straightforward: confirm the recipient is in the Croatian public-sector workflow, prepare an EN 16931-compliant invoice, choose the right submission route, and make sure the routing data points to the buyer correctly. The rest of this guide breaks those steps down so you can send the invoice correctly the first time.

Which Croatian Public-Sector Invoices Fall Within the Mandate

The safest way to think about scope is to start with the customer, not the headline value of the contract. If you are billing a Croatian public procurement entity or another public-sector body operating inside this workflow, structured e-invoicing rules are likely relevant. In practice that can include central government bodies, local authorities, hospitals, schools, agencies, and other entities that purchase goods or services under public procurement rules.

This is where many suppliers go wrong. They assume the obligation only matters for large procurement exercises that crossed EU thresholds. Croatia's model is broader than that. The public-sector regime can also reach certain lower-value purchases and direct-award procedures, so a purchase order from a public body should not be treated as ordinary domestic B2B invoicing just because the amount is modest or the buying process felt informal.

The legal backdrop is Croatia's implementation of the public procurement e-invoicing framework under Directive 2014/55/EU and the national Act on eInvoicing in Public Procurement. You do not need to master every legal article to work correctly as a supplier, but you do need to understand the operational consequence: if the recipient sits inside the Croatian public procurement process, the invoice has to follow the structured public-sector route rather than your usual ad hoc submission method.

That is why the best qualifying question is not, "Was this a big tender?" It is, "Is this customer receiving invoices as a Croatian public procurement entity?" Once the answer is yes, the rest of your workflow changes. The invoice format, sending channel, and routing identifiers all matter in ways they do not for an ordinary business customer.

How Servis e-Racun za drzavu, FINA, and Peppol Work Together

Servis e-Racun za drzavu is the Croatian public-sector service used for exchanging compliant electronic invoices with public entities. From a supplier's perspective, it is the operational environment that matters once you know the customer is in scope. The key point is that Croatia's B2G model is not just "send any electronic invoice." It is a structured exchange process tied to public-sector receiving workflows.

FINA is central to how that process works in practice. English-language guides often mention Croatia's public e-invoicing rules without explaining who supports the exchange infrastructure, onboarding paths, or recipient lookup steps. That missing operational layer is why suppliers can understand the mandate in principle but still be unsure how to deliver the invoice in reality.

Peppol also sits inside the Croatian model. Croatian state beneficiaries have used the Peppol network for receiving and sending e-invoices since 2019, which makes interoperability easier for cross-border and multi-jurisdiction suppliers already working with structured invoice standards. At the same time, Peppol is not a substitute for Croatia-specific setup details. You still need the correct recipient routing information and a compliant structured invoice, typically aligned with EN 16931 and Peppol BIS Billing 3.0 expectations.

This combination of a national public-sector service plus an interoperable exchange network is one reason Croatia can confuse suppliers who are used to simpler country summaries. If you want a useful comparison point, how another EU public-sector workflow combines Peppol with a national route shows that the same broad building blocks can still produce country-specific submission rules. Bulgaria's public-sector supplier workflow through CAIS EPP and Peppol is another good comparison because it shows the same need to confirm the exact authority route before sending. Lithuania's SABIS, portal, and Peppol public-buyer workflow is another useful reference if you need to compare how a neighboring public-sector mandate handles supplier submissions after a national platform transition. For Croatia, the important takeaway is that once your recipient is in the public workflow, channel choice and routing discipline matter just as much as the invoice data itself.

---

Use 9934 and the Buyer's OIB to Route the Invoice Correctly

One of the most useful Croatia-specific details for suppliers is the routing format 9934: buyer's OIB. The OIB is the Croatian personal identification number or entity identifier used across administrative workflows, and in this context it helps point the invoice at the correct public-sector recipient. That detail is easy to miss if you rely on broad country pages that explain the mandate but not the delivery mechanics.

Routing deserves its own attention because a structurally valid invoice can still fail operationally if it is addressed incorrectly. You can have the right EN 16931 content, use the correct sending channel, and still create delays or rejection if the buyer identifier does not match the public recipient's expected routing data. That is why Croatian public procurement invoice routing should be treated as a separate check, not an afterthought.

Before sending, work through a short verification list:

• Confirm the customer is a Croatian public procurement recipient that can receive structured e-invoices.
• Confirm you have the correct buyer OIB for that recipient and that the address format is set as 9934: buyer's OIB where required.
• Confirm the invoice content is structured and aligned with the expected standard rather than a flat PDF attachment.
• Confirm your chosen route, whether direct, portal-based, or intermediary-led, matches the recipient's setup.

Suppliers that already work across Europe will recognize the pattern: the standard defines the invoice, but local routing rules determine where it lands. That is one reason Finland's EN 16931, Finvoice, and public-sector e-invoicing model is a helpful comparator. The Croatian version is distinctive because the buyer's OIB and the 9934 addressing format are the practical details that keep a public-sector invoice from going astray.

Sending Options for Low-Volume Suppliers, ERP Integrations, and Intermediaries

Croatia's public-sector workflow is usable by more than one type of supplier. If you only send occasional invoices to public bodies, a self-registration or portal-based path is often the most realistic route. FINA's supplier guidance is useful here because it shows that low-volume issuers do not necessarily need a full ERP project before they can send compliant invoices. That option matters for accountants, small vendors, and international suppliers that only need to invoice a Croatian public body from time to time.

If you invoice Croatian public entities regularly, the better fit may be ERP or web-service integration. That gives finance teams a repeatable process, reduces manual handoffs, and makes it easier to keep structured invoice generation consistent across departments or legal entities. The practical decision is less about company size and more about volume, repeatability, and whether your existing systems already support the required data and exchange steps.

There is also a middle path: using an information intermediary or service provider. That can make sense when you need the public-sector exchange handled correctly but do not want to own every technical connection point yourself. For cross-border suppliers especially, an intermediary can be a practical way to bridge from an existing invoicing setup into the Croatian workflow without rebuilding the full connection internally.

Whichever route you choose, do one last operational check before sending: use the relevant public register or onboarding information to confirm that the recipient can receive e-invoices and that you are addressing the invoice through the right path. A Croatia supplier portal e-invoice process can be perfectly adequate for low volume, while an integrated or intermediary route is usually better for sustained invoice traffic. The right choice is the one that keeps the invoice compliant, correctly addressed, and repeatable for your team.

---

How Croatia's Public-Sector Workflow Differs From the 2026 B2B Reform

Croatia's public-sector e-invoicing workflow is not new. Public bodies have been receiving structured invoices since late 2018, and suppliers have been issuing them since mid-2019. That timeline is separate from Croatia's later domestic B2B reform agenda, which is why public-sector guidance becomes confusing when broad country explainers mix both topics into one page.

Keep the distinction clean when you plan your invoicing process. If you are billing a Croatian ministry, municipality, hospital, school, or another public procurement body, the established B2G route is the workflow that matters right now. If you need the wider domestic context on fiscalization and the broader mandate rollout, see Croatia's broader 2026 e-invoicing and Fiscalization 2.0 rules. That topic is related, but it does not replace the supplier steps required for a public-sector invoice.

Use this short checklist before you send:

• Confirm the customer is a Croatian public-sector recipient in scope.
• Prepare a structured invoice that complies with EN 16931.
• Choose the correct submission route, whether portal, integration, or intermediary.
• Use the correct 9934: buyer's OIB routing data where the public-sector workflow requires it.

If those four checks are in place, you are focused on the right problem. The goal is not to memorize every Croatia reform headline. It is to send a structured invoice that reaches the right public recipient without avoidable routing or format errors.