xmlvalid
Sign in Open validator
E-invoicing Croatia

Croatian eRačun validator

Check an eRačun for Fiskalizacija 2.0 against the rules the Tax Administration publishes: the UBL 2.1 schema, EN 16931 and the Croatian HR-BR rules, with every finding on its line. Nothing is uploaded.

Check an invoice Try it with an example

Fiskalizacija 2.0 in short

Since 1 January 2026, VAT-registered taxpayers with their seat, residence or usual abode in Croatia send and receive eRačuni (structured electronic invoices) for domestic transactions, and report the data of incoming and outgoing eRačuni to the Tax Administration (Porezna uprava). Taxpayers outside the VAT system can receive eRačuni in the free MIKROeRAČUN application during 2026. The Tax Administration publishes a list of the information intermediaries that exchange eRačuni for businesses.

An eRačun follows EN 16931 with the Croatian specification and its extensions (HR CIUS 2025 with HR extensions), in UBL 2.1. Its specification identifier (BT-24) names both: urn:cen.eu:en16931:2017#compliant#urn:mfin.gov.hr:cius-2025:1.0#conformant#urn:mfin.gov.hr:ext-2025:1.0.

How to check an eRačun

  1. Open the validator with the eRačun invoice profile, or the credit note (odobrenje) one. An eRačun opened as a file picks the right one from its identifier.
  2. Paste the UBL or drop the file, then press Validate.
  3. Click a rule id for what it checks; the Croatian rules give their messages in Croatian, as published, with an English rendering under each finding and on each rule's page.

What is checked

The UBL 2.1 schema, then the EN 16931 rules (the current release of the official CEN artefacts, as the Tax Administration's guide asks) and its HR-CIUS-EXT-EN16931-UBL rules of 13 March 2026, in use since 15 March 2026. We compared our results with Saxon for Java on the Tax Administration's 20 example invoices and 62 altered ones: every rule was the same.

The Croatian rules check the OIB of the seller, the buyer and the operator with its check digit (HR-BR-9, HR-BR-53), an issue date from 2026 on (HR-BR-40), invoice numbers without spaces (HR-BR-1), the KPD classification of each line (HR-BR-25) and the Croatian tax categories and fiscal data in the UBL extensions.

The example invoices the Tax Administration published in December 2025 are dated 2025 and use a placeholder OIB, so the current rules reject them. The examples in our catalog are those invoices with 2026 dates and a seller OIB with a valid check digit.

Profiles to check with

  • Croatia eRačun Invoice (UBL): A Croatian eRačun for Fiskalizacija 2.0, checked against the UBL 2.1 schema, the EN 16931 rules and the Croatian rules (HR-BR-*) published by the Tax Administration. Validate
  • Croatia eRačun Credit Note (UBL): A Croatian eRačun credit note (odobrenje) for Fiskalizacija 2.0, checked against the UBL 2.1 CreditNote schema, the EN 16931 rules and the Croatian rules (HR-BR-*). Validate

Rules invoices break most

Each one has a page with what it checks, its test and, for many, how to fix it.

  • HR-BR-40: Datum izdavanja računa (BT-2) - (…) mora biti veći od 01.01.2026 i manji od 01.01.2100.
  • HR-BR-9: Račun mora sadržavati ispravan OIB operatera (HR-BT-5)
  • HR-BR-53: HR PDV identifikacijski broj (BT-31, BT-48, BT-63) ili porezni identifikator (BT-32) mora biti ispravan OIB
  • HR-BR-25: Stavka …: Svaki artikl MORA imati identifikator klasifikacije artikla iz sheme Klasifikacija proizvoda po djelatnostima: KPD (CPA) – listID „CG“, osim u slučaju...
  • HR-BR-1: Broj računa ne smije sadržavati bjeline (whitespace znakove)
  • BR-CO-15: Invoice total amount with VAT (BT-112) = Invoice total amount without VAT (BT-109) + Invoice total VAT amount (BT-110).

Questions

Is the eRačun uploaded?

No. The schema check and the rules both run in your browser. Only the API and URL monitors validate on our servers.

Does a valid result mean the eRačun will be accepted?

It means it passes the schema and the rules the Tax Administration publishes for its validator. Delivery and fiscalisation also depend on the intermediary and on data registered with the Tax Administration, which this check does not look up.

Why are the EN 16931 findings in English and the Croatian ones in Croatian?

Each set of rules keeps the messages its publisher wrote: CEN in English, the Tax Administration in Croatian. The validator shows each Croatian finding in English too, under the original.

Can I check invoices from code?

Yes: the API and the command-line client with --schema hr-eracun-invoice, or --schema auto for a folder of mixed invoices.

Official sources

Other countries