eBolovanje — sick leave from the portal, payroll and the claim to RFZO

From 1 January 2026 sick notes (doznake) no longer arrive on paper: the doctor opens sick leave electronically, and the employer sees it on the state portal eBolovanje – Poslodavac (the sick-leave portal on eUprava, the eGovernment portal). The portal has no programmatic access (API), so duplo works with the files the portal provides and asks for — and does everything else around sick leave itself: the lines in the payroll run, the tax return under the right codes, the certificate of earnings for RFZO (the National Health Insurance Fund) and the deadline for the claim. The module is part of Payroll (Kancelarija plan), at no extra charge.

Who is obliged and from when

• All employers with at least one employee from 1. 1. 2026 — registration on the portal and collecting sick notes; claims for the calculation and reimbursement of compensation electronically from 1. 4. 2026.
• Sole traders with employees from 1. 1. 2027.
• A flat-rate taxpayer or a company without employees has no obligation.

Who bears the compensation: for the first 30 days of sick leave the employer (at least 65 % of the average salary of the previous 12 months; 100 % for an injury at work), from the 31st day RFZO — the employer pays the compensation out and then claims it from RFZO with a request on the portal, within 15 days of the salary payment for that month. For the care of a child under three RFZO bears the compensation from the first day.

What duplo does

1. Importing sick leave — on the portal you choose a period and click „Izvezi podatke“ (Export data; XML or JSON), then import the file in Payroll → Sick leave. The programme matches the sick leave with employees by JMBG (personal ID number), shows what is new and what has changed (extension, closure, cancellation) and imports only the matched records. You may import the same file several times.
2. Lines in the payroll run — when you add an employee to a run, the programme suggests the sick-leave lines itself from the records, by calendar day: up to the 30th day borne by the employer, from the 31st day RFZO, hours = working days × weekly hours fund / 5, hourly rate the average of the previous 12 months; the same hours are taken off regular work. You edit the lines like any others.
3. PPP-PD under the right codes — sick leave goes into the return under its own income type code (202 up to 30 days, 201 injury at work, 204 and 205 borne by RFZO), with the exact number of calendar days from the records, not under salary (101).
4. Certificate of earnings for RFZO — on the employee card the programme fills in the certificate of earnings for the 12 months before the sick leave from your closed payroll runs and provides it as XML exactly following the structure of the portal, together with a ZIP of payslips per month that the portal asks for with the first claim.
5. Deadline and claim status — as soon as the sick leave passes the 30th day, the programme marks it “to be filed”; when you close the run for that month, it calculates the deadline (payment date + 15 days). The Payroll page carries a reminder of how many sick-leave records await a claim and which deadline is nearest, and on the sick-leave page you record that the claim was filed, decided (OZ-10), paid or rejected.

Step by step — sick leave that passes 30 days

1. Import the export from the portal (Payroll → Sick leave → “Import the export from eUprava”). Repeat after every new sick note — the programme warns you on the employee’s page in the run when the last sick note expires before the end of the month.
2. Create the payroll run for the month as usual; the sick-leave lines are already there. Check them (a public holiday that falls within the sick-leave days is not paid separately — reduce the public-holiday hours by hand).
3. Close the run and create the PPP-PD; the sick leave is in the return under its own code.
4. Pay the salaries. On the sick-leave page you see the deadline for the claim (payment + 15 days).
5. On the employee card download the certificate of earnings (XML) and the payslips (ZIP), then file the claim for calculation or reimbursement on the portal and attach the files. The claim is signed with a qualified certificate.
6. On the sick-leave page enter the status “filed” with the date; when RFZO decides (OZ-10) and pays, update the status.

What is kept and what is not

The period, status, cause (code and name), number of days and the history of actions from the portal. The diagnosis, the LBO (health insurance number) and the health card number are neither read nor stored — the accountant does not need them, and they are a special category of data. The export file itself is not kept. An employee’s sick leave is seen only by those who see payroll (the super admin, administrator and accountant; a team member does not).

What the module does not do (yet)

• It does not connect to the portal (there is no API) — you download the export, and upload the claim and the files yourself.
• The allocation of compensation by cause (percentage and who bears it) is the programme’s suggestion under the Labour Law (Zakon o radu) and the Health Insurance Law (Zakon o zdravstvenom osiguranju) — confirmed by your accountant; a cause the programme does not recognise gives no lines.
• One claim status per sick leave (the first claim); sick leave that lasts several months requires a claim for every month — record them in the note.
• Sick leave borne by RFZO is still posted in the books as a salary cost (520); the receivable from RFZO is posted by the accountant with a manual journal entry.
• Maternity leave, subsidies and accelerated length of service are done with your accountant.