Slovenia Fiscal Verification of Invoices: 2026 Guide

Slovenia fiscal verification of invoices is the regime for invoices and receipts issued for cash payments, where the Financial Administration of the Republic of Slovenia, FURS, receives confirmation data as the document is being issued. The legal basis is the Act on Fiscal Verification of Invoices, adopted on 15 July 2015 and in force since 2 January 2016. Since that start date, the standard model has been real-time verification: cash-register systems send invoice data to FURS during issuance, not later as a batch upload.

For most readers, the key point is that this is an issuance workflow. It is not mainly a cash-register shopping exercise, and it is not generic POS advice. The real compliance questions are: when the rules apply, what must happen at the moment the invoice is issued, and which official fallback paths remain compliant if you issue only a small number of cash invoices.

In plain English, the workflow looks like this:

• If a transaction falls within the regime, the invoice must be issued at the time required by the rules, and the issuance data must be fiscally verified with FURS in real time through the regular electronic route.
• The seller must issue the invoice, hand it to the buyer, and display the required notice about invoice issuance and retention obligations.
• The buyer must accept the invoice and keep it after leaving the premises.
• Lower-volume issuers are not limited to a full retail setup. Official paths such as eDavki and miniBlagajna support smaller-scale issuance, and a pre-numbered invoice book can still fit into the framework, but invoice-book entries must be verified through eDavki within 10 days.

That is the practical core of Slovenia fiscal receipt requirements: FURS wants visibility at the moment a cash invoice is created, while still allowing official lower-volume and fallback methods. The rest of this guide stays focused on that workflow, when it applies, what happens in real time, and how the compliant fallback paths work.

When Fiscal Verification Applies and When the Invoice Must Be Issued

Under the official FURS framing, fiscal verification applies to a supply of goods or services for payment with cash. That makes the first compliance question straightforward: does this sale fall into Slovenia's cash-payment regime, or is it part of a different invoicing flow?

The timing rule follows from that scope. When a cash payment falls inside the regime, the invoice must be issued when the goods or services are supplied or when the cash is received. In ordinary trading, that means the invoice is not a later back-office document. It is part of the live transaction.

Under the standard cash-register route, invoice data is sent to FURS for real-time invoice confirmation during issuance. That is why Slovenia cash register requirements are really about control at the moment of issue, not a later upload or reconciliation step.

It also helps to separate fiscal verification from Slovenia's wider e-invoicing track. Fiscal verification is a point-of-sale or cash-issuance control. Public-sector and future B2B e-invoicing mandates are separate topics with different triggers and workflows. If you need that broader context, Slovenia's budget-user and 2028 e-invoicing rules cover that separate roadmap.

Before each sale, ask one practical question: Does this transaction require verified issuance now, or is it part of a different invoicing process? If it is a cash-paid supply inside the fiscal-verification regime, issue and verify the invoice at that point. If it belongs to another invoicing track, keep the workflows separate.

What Sellers Must Do at the Point of Sale and What Buyers Must Do Next

Once a cash invoice or receipt is created, the compliance job is not finished. In Slovenia, the point-of-sale workflow includes duties for both sides of the transaction.

For the seller, the practical rule is straightforward:

• Issue the invoice.
• Hand it over to the buyer.
• Display the required notice in a visible place, stating that the seller must issue and hand over the invoice and that the buyer must accept and keep it.

That means the process is not complete just because a receipt was printed or generated on screen. At a shop counter, bar, restaurant table, kiosk, or service desk, staff must make sure the invoice actually reaches the customer. Leaving it on the counter without handing it over, or treating the receipt as optional, creates compliance risk.

The buyer also has a legal duty. After leaving the premises, the buyer must accept and keep the invoice and show it on request. This buyer obligation to keep the invoice is part of the same control system as fiscal verification itself. It is not just personal recordkeeping, and it does not apply only to business buyers. In plain terms, once a customer receives the receipt, they should take it with them and retain it after departure in case of inspection.

For day-to-day operations, this is the key takeaway: issuing the invoice, physically or electronically handing it over, displaying the notice, and the buyer keeping the invoice are all part of one compliance sequence. They are legal steps tied to the sale, not optional housekeeping tasks for later.

How miniBlagajna and eDavki Support Lower-Volume Issuers

If you issue a relatively small number of cash invoices, Slovenia gives you lighter official channels, but they still sit inside the same compliance workflow. For smaller issuers, the practical question is which official route fits the job while keeping the invoice inside the FURS verification process.

miniBlagajna is FURS's official tool for smaller issuers who do not want a full cash-register software setup. Its role is operational: you use it to issue the invoice through an official channel that supports the fiscal-verification process, rather than treating it as a separate software category. The official materials also position it as broader than a simple cash-invoice screen: it can issue fiscally verified cash invoices, prepayment invoices, and reverse-charge invoices, and it can help maintain or submit VAT records.

eDavki sits alongside that workflow as the tax administration portal for verification and related submission steps, especially when your process does not revolve around a larger retail or hospitality register environment. If you also need the recordkeeping side, our guide to Slovenia VAT records and eDavki submission workflow explains where those obligations connect.

This is not a niche fallback that no one uses. On 24 November 2023, Slovenia's Financial Administration said 30,000 taxpayers were already using the MiniBlagajna application in the Financial Administration's MiniBlagajna update. The same 2023 update also highlighted support for non-cash issuance scenarios and invoice output with a QR payment code.

That update describes what the tool can do. It does not replace the core trigger explained earlier: fiscal verification still turns on whether the transaction falls inside Slovenia's cash-payment rules. Tool choice also does not change the handover and retention duties already covered above.

When a Pre-Numbered Invoice Book Is Allowed and How the 10-Day Rule Works

A pre-numbered invoice book is an official fallback path, not a way to sit outside fiscal verification. In Slovenia, pre-numbered invoice book verification still feeds back into the same control system: you issue the invoice from the book, then you verify the entry electronically through eDavki.

In practice, this is the route to think about when you are using the permitted fallback or lower-volume paper-based path, not the standard live electronic route. If you can issue and confirm electronically through a cash-register system or miniBlagajna, that is the more direct workflow. The book matters when you still need a compliant issuance path but have to bring the invoice back into eDavki afterward.

The point most businesses need to remember is the deadline. If you are using the pre-numbered invoice book route, the invoice-book entries still have to be verified through eDavki within 10 days. That keeps the fallback method inside the same control framework as the normal real-time process, even though the reporting step happens later.

In practice, there are three paths to distinguish:

• Standard real-time cash-register confirmation: invoice data goes to FURS during issue, and confirmation happens immediately.
• miniBlagajna for lower-volume issuers: you use the official lighter FURS tool to issue fiscally verified invoices through the approved workflow.
• Pre-numbered invoice book for fallback situations: you issue from the book first, then complete the required eDavki verification within the allowed period.

Keep this workflow separate from broader Slovenia invoicing topics such as VAT content rules, numbering policy outside the fiscal-verification handoff, or archiving. If you need wider Slovenia context, use the e-invoicing and VAT-records articles linked above. Multi-country teams should also avoid assuming nearby regimes work the same way. For example, Slovakia's eKasa receipt and QR-code rules use a different receipt-control model.

A quick compliance check keeps the decision path clear:

• Can you issue and verify electronically at the point of sale? Use the standard real-time confirmation flow.
• Do you issue a low volume of cash invoices and want the official lighter tool? Use miniBlagajna.
• Are you relying on the fallback book route? Issue from the pre-numbered invoice book, then complete the eDavki verification within 10 days.
• What duty never changes? The invoice still has to reach the buyer at the time of issue.