Skip to content

Commit db46e21

Browse files
antoine162antoine162
committed
[ADD] Fiscal Localizations / Croatia
Document e-invoicing with MojEracun task-4925745
1 parent bcf73b2 commit db46e21

File tree

3 files changed

+122
-3
lines changed

3 files changed

+122
-3
lines changed

‎content/applications/finance/accounting/customer_invoices/electronic_invoicing/croatia.rst‎

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,18 +18,21 @@ e-invoicing in public procurement. Under these regulations, all businesses invol
1818
(business-to-government)` transactions are required to use electronic invoicing via the :abbr:`CIS
1919
(Central Invoice System)`, Croatia’s official platform for public sector e-invoicing. Croatia is
2020
also part of the Peppol network, facilitating standardized cross-border e-invoicing within the
21-
European Union. Furthermore, e-invoicing is increasingly encouraged for B2B transactions, promoting
22-
greater transparency and tax compliance.
21+
European Union. Furthermore, e-invoicing through the e-Račun platform is mandatory for B2B
22+
transactions starting from 1 January 2026.
2323

2424
Compliance with Croatian e-invoicing regulations
2525
================================================
2626

2727
Odoo Invoicing makes it easy for businesses to send, store, and ensure the integrity of their
2828
invoices. Here is how Odoo ensures compliance:
2929

30+
- **Integrations**: Odoo can send invoices and report payments to the e-Račun platform via an
31+
integration with third-party provider `mojeRačun <https://moj-eracun.hr>`_.
3032
- **Supported formats**: Odoo supports standard e-invoice formats, such as PDF with digital
3133
signatures and XML in :abbr:`UBL (Universal Business Language)` format, which are fully compatible
32-
with Croatia's :abbr:`CIS (Central Invoice System)` for public procurement transactions.
34+
with Croatia's :abbr:`CIS (Central Invoice System)` for public procurement transactions and
35+
e-Račun platform for B2B transactions.
3336
Additionally, Odoo enables transmission of e-invoices through any platform connected to the Peppol
3437
network, as the *Servis eRačun za državu* reached via Peppol, ensuring compliance with both
3538
Croatian and EU standards.

‎content/applications/finance/fiscal_localizations.rst‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,7 @@ Fiscal localization modules are available for the countries listed below.
159159
fiscal_localizations/canada
160160
fiscal_localizations/chile
161161
fiscal_localizations/colombia
162+
fiscal_localizations/croatia
162163
fiscal_localizations/denmark
163164
fiscal_localizations/ecuador
164165
fiscal_localizations/egypt

‎content/applications/finance/fiscal_localizations/croatia.rst‎

Lines changed: 115 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,115 @@
1+
=======
2+
Croatia
3+
=======
4+
5+
E-invoicing via mojeRačun
6+
=========================
7+
8+
Odoo can connect to the national eRačun platform via third-party provider `mojeRačun
9+
<https://moj-eracun.hr>`_ to send and receive e-invoices.
10+
11+
To make use of this integration, an account and `invoice package
12+
<https://portal.moj-eracun.hr/podrska/cjenik/>`_ from mojeRačun are needed. The rest of this
13+
documentation assumes that this is already the case.
14+
15+
.. _croatia/configuration:
16+
17+
Configuration
18+
-------------
19+
20+
Follow these steps to set up e-invoicing via mojeRačun in Odoo.
21+
22+
.. _croatia/configuration/company:
23+
24+
Company configuration
25+
~~~~~~~~~~~~~~~~~~~~~
26+
27+
Go to :menuselection:`Accounting --> Configuration --> Settings` and scroll down to
28+
:guilabel:`MojEracun E-invoicing`. Fill the :guilabel:`Username` and :guilabel:`Password` fields
29+
with the credentials provided by mojeRačun.
30+
31+
Ensure that the :guilabel:`Company ID (OIB or GIN)` and :guilabel:`Company Business Unit (PJ)`
32+
fields are correctly filled in.
33+
34+
Optionally, specify the :guilabel:`Incoming E-Invoices Journal` where invoices received via MER
35+
should be created. If unset, the default purchase journal will be used.
36+
37+
Set the :guilabel:`MojEracun Operating Mode` to :guilabel:`Production` to send and receive invoices
38+
on the production network.
39+
40+
Then click :guilabel:`Activate` to activate the connection with mojeRačun.
41+
42+
.. _croatia/configuration/journal:
43+
44+
Journal configuration
45+
~~~~~~~~~~~~~~~~~~~~~
46+
47+
Go to :menuselection:`Accounting --> Configuration --> Journal` and click the :guilabel:`Customer
48+
Invoices` journal to open its configuration.
49+
50+
In the :guilabel:`Fiscalization (HR)` section, fill the :guilabel:`Business premises label`,
51+
:guilabel:`Issuing device label`, :guilabel:`Business premises label (refund approval)`, and
52+
:guilabel:`Issuing device label (refund approval)` fields.
53+
54+
These fields are used to generate the :ref:`invoice name <croatia/sending/invoice-name>` in
55+
accordance with the Croatian standard. The :guilabel:`refund approval` fields are used for credit
56+
notes.
57+
58+
.. _croatia/sending:
59+
60+
Sending an e-invoice
61+
--------------------
62+
63+
When creating an invoice, the following configuration is needed to correctly send the invoice
64+
via mojeRačun.
65+
66+
.. _croatia/sending/invoice-name:
67+
68+
Invoice name
69+
~~~~~~~~~~~~
70+
71+
The invoice name must be in the form `{Journal code}-{Year}-{Sequence}/{Business premises label}/
72+
{Issuing device label}`. This format is suggested by default when creating the first invoice in
73+
a Sales journal where the :ref:`journal configuration <croatia/configuration/journal>` was performed
74+
as explained above.
75+
76+
If invoices in an existing journal must be sent via mojeRačun, the invoices of that journal must be
77+
resequenced to follow the correct format.
78+
79+
Product configuration
80+
~~~~~~~~~~~~~~~~~~~~~
81+
82+
The :guilabel:`KPD category` must be set on the product.
83+
84+
Fetching status updates
85+
~~~~~~~~~~~~~~~~~~~~~~~
86+
87+
Once an invoice has been sent, Odoo will periodically check for any updates to the invoice's status
88+
(e.g. rejection by MER, the eRačun system, or by the recipient). To manually check for updates,
89+
click the :guilabel:`MER: Fetch status` button.
90+
91+
Reporting a payment
92+
~~~~~~~~~~~~~~~~~~~
93+
94+
The Croatian government expects to be notified once payment has been received for an invoice. To
95+
send this notification, click the :guilabel:`MER: Report payments` button.
96+
97+
.. _croatia/receiving:
98+
99+
Receiving e-invoices
100+
--------------------
101+
102+
Odoo periodically checks for new invoices received via mojeRačun. New invoices received via
103+
mojeRačun appear in the :guilabel:`Incoming E-Invoices Journal` specified in the
104+
:ref:`croatia/configuration/company <settings>`.
105+
106+
Rejecting an invoice
107+
~~~~~~~~~~~~~~~~~~~~
108+
109+
To reject an incoming invoice, click the :guilabel:`MER: Reject eRacun` button. This notifies the
110+
eRačun system and the sender that the invoice is not accepted.
111+
112+
.. seealso::
113+
:doc:`Odoo electronic invoicing in Croatia
114+
<../accounting/customer_invoices/electronic_invoicing/croatia>`
115+

0 commit comments

Comments
 (0)