Slovenia VAT Invoice Requirements: 2026 Guide

A full Slovenia VAT invoice generally needs the invoice date, a unique sequential number, supplier and customer details, a description of the goods or services, the supply date when it differs from the invoice date, the taxable amount, the VAT rate, and the VAT amount. Simplified invoices are generally limited to invoices that do not exceed EUR 100 excluding VAT. Most invoice records must be kept for 10 years, while invoices connected with real-estate transactions must be kept for 20 years.

Those are the core Slovenia VAT invoice requirements, but the operational detail matters. A finance team still needs to know when full customer details are mandatory, when a simplified invoice stops being acceptable, how self-invoicing should be set up, how corrections should point back to the original invoice, and what changes when records are stored outside Slovenia.

This guide stays tightly focused on invoice content, issuance edge cases, and retention controls. It is not a broader Slovenia VAT registration or filing guide. The goal is to give an English-language operator reference that can be used to issue, review, or configure invoices correctly, while keeping separate topics such as reverse charge, e-invoicing mandates, and fiscal verification in their proper lanes.

Article 82 checklist for a standard Slovenia VAT invoice

For a standard VAT invoice, the cleanest way to read Article 82 is as a field checklist. This is the fuller document format businesses should expect when invoicing taxable persons and non-taxable legal entities that need the complete set of VAT particulars. Each item supports a concrete compliance or bookkeeping need: identifying the parties, fixing the tax point, showing how VAT was calculated, and leaving an auditable trail from commercial document to VAT records.

Required field	What it should show in practice	Why it matters
Invoice date	The date the invoice is issued	Establishes when the document was created and helps support the VAT timeline
Unique sequential number	A number from a sequence that identifies the invoice once	Prevents duplicate or missing invoices in the accounting trail
Supplier details	Supplier name and address	Identifies the issuer clearly for audit and commercial review
Supplier VAT ID	The supplier's Slovenian or other relevant VAT identification number	Links the invoice to the taxable person that issued it
Customer details	Customer name and address where a full invoice is required	Shows who received the supply and supports deduction review
Customer VAT ID where relevant	The customer's VAT number when the transaction type requires it	Matters especially for business-to-business VAT treatment
Description of goods or services	The nature of what was supplied, and quantity or extent where relevant	Lets the invoice support both commercial review and tax analysis
Supply date	The date the goods were delivered or the services completed, if different from the invoice date	Fixes the tax point when issue date and supply date are not the same
Taxable amount	The net amount before VAT	Shows the base on which VAT is calculated
Unit price or discounts where relevant	Pricing detail needed to understand the taxable amount	Helps reviewers trace how the invoice total was built
VAT rate	The applicable VAT percentage	Shows which tax treatment was applied
VAT amount	The tax charged for the supply	Confirms the amount posted to VAT accounts

In practice, the most common failures are not exotic legal issues but missing operational details: a supply date left off when services were performed earlier, customer details omitted on a business invoice, or discounts embedded in totals without enough clarity to reconstruct the taxable base. Those are the errors that create friction later, when the invoice is reviewed for deduction, matched to a purchase order, or checked during an audit.

Not every Slovenia invoice charges VAT in the same way. If a transaction is exempt or falls under a reverse-charge rule, the invoice may need a legal reference or specific wording instead of a VAT amount. That issue should be handled precisely rather than improvised, which is why it helps to separate the standard field checklist from the special-case wording covered in Slovenia reverse-charge invoice requirements under Article 76a.

---

When simplified invoice rules apply in Slovenia

Slovenia allows a simplified invoice for lower-value transactions, but the threshold matters. As a general rule, the simplified format is limited to invoices that do not exceed EUR 100 excluding VAT. Once that threshold is exceeded, or once the commercial context calls for fuller identification and tax support, the safer assumption is that a standard Article 82 invoice is required.

A simplified invoice still needs enough information to identify the transaction and the tax treatment. In practical terms, it should still show:

• the supplier's identity
• the invoice date
• what goods or services were supplied
• the VAT amount, or the information needed to calculate it

That is why a simplified invoice should be treated as a reduced-data format, not as an informal receipt. It is meant to remove some administrative burden on low-value transactions, not to weaken the audit trail.

One Slovenia-specific nuance is easy to miss. If a taxable person wants to rely on a simplified invoice to deduct input VAT, the buyer's name and address should also be shown. That turns a seemingly simple low-value invoice into a document that still needs deliberate template design, especially in point-of-sale or mixed business-to-consumer and business-to-business environments.

From an operations perspective, the key control is to decide the invoice type before issuance. If the amount may cross the EUR 100 limit, or if the customer needs a document robust enough for VAT deduction and downstream bookkeeping, it is better to issue the full version from the start rather than retrofit missing fields later.

Self-invoicing, foreign-currency invoices, and correction documents

Generic VAT guides often mention self-invoicing in a sentence and move on. In Slovenia, that is not enough. If the customer issues the invoice on the supplier's behalf, the process should sit on a written agreement between the parties, and the workflow should address the relevant notification requirement to FURS before the arrangement is treated as routine.

That matters because self-invoicing is not just a label on the document. A business needs a clear approval process for who may issue the invoice, how the supplier confirms the content, and how numbering and retention stay controlled when the recipient creates the document. The invoice should also make clear that it is a self-invoicing document, so the audit trail reflects how the document was created.

Foreign currency adds another control point. The commercial invoice can be issued in a non-EUR currency, but the VAT position still has to be supportable in EUR for Slovenian accounting and tax purposes. In practice, that means defining a consistent conversion method, typically by reference to the exchange-rate approach the business uses for Slovenian VAT calculations, often anchored to the relevant Bank of Slovenia reference rate, rather than leaving currency translation to ad hoc spreadsheet work.

Correction documents need the same discipline. A credit note or debit note should identify the original invoice clearly enough that a reviewer can trace what changed, when it changed, and whether the VAT treatment also changed. If the original invoice relied on exemption wording, reverse-charge wording, or another special reference, the correction document should preserve that logic accurately rather than treating the note as a fresh standalone invoice.

Electronic invoices, language expectations, and related Slovenia rules

Invoice content rules answer one question, format and transmission rules answer another. Slovenia generally treats electronic and paper invoices as equivalent if the business can preserve authenticity of origin, integrity of content, and readability for the whole retention period. The compliance test is not whether the document was sent as a PDF, XML file, or paper sheet, but whether the record remains trustworthy and accessible later.

Language is similar. Slovenian is the safest default for local administration, but in practice many cross-border businesses use bilingual or English-supporting documentation where the commercial reality requires it. The real control point is whether the invoice and its supporting records remain understandable enough for tax review, internal controls, and audit follow-up.

It is also important not to merge separate compliance regimes into one idea of a "valid invoice." A document can contain all the right VAT fields and still raise separate questions about public-sector routing, platform standards, or point-of-sale reporting. Those obligations sit outside the field checklist covered here, which is why Slovenia e-invoicing requirements deserves its own treatment for teams dealing with mandated electronic submission channels.

The same distinction applies to fiscal verification. Cash-register reporting, miniBlagajna workflows, and invoice-content compliance overlap in day-to-day operations, but they are not the same rule set. Keeping those boundaries clear helps teams design invoice templates and document controls that solve the right problem instead of overloading one document with every Slovenia compliance obligation at once.

---

Retention periods, storage abroad, and final compliance checks

Retention is not a side note to invoice compliance in Slovenia. According to SPOT's accountancy rules for Slovenia, businesses trading in Slovenia must generally store incoming and outgoing invoices for 10 years, while invoices connected with the sale of real estate must be kept for 20 years. That rule should shape archive design from the start, because an invoice that was correct on issue date is still a compliance failure if it cannot be produced years later.

Storage outside Slovenia needs extra care. If invoice records are stored abroad, the business should address the FURS notification requirement and make sure the tax authority can access the records online without delay. In practice, that means thinking beyond file backup: where the archive is hosted, who can retrieve records, how fast they can be exported, and whether the document remains readable together with its supporting data.

Electronic storage is acceptable, but only if it preserves authenticity, integrity, readability, and retrieval throughout the retention period. That is where template design and recordkeeping meet. A weak numbering sequence, an unclear correction trail, or inconsistent customer-identification rules can create problems long after the invoice was sent.

The best final check is operational. Before relying on a Slovenia invoice template at scale, confirm which transactions need a full Article 82 invoice, which can use the simplified format, how self-invoicing is approved, how foreign-currency values are translated into EUR for VAT support, and how credit notes refer back to the original document. Those checks belong inside broader invoice processing workflows, especially when invoice data later feeds archiving, deduction support, and the controls behind Slovenia VAT records requirements.