Slovenia Postponed Import VAT: Article 72 Guide

Slovenia postponed import VAT means a VAT-registered importer accounts for import VAT through the DDV-O return instead of funding that VAT upfront at customs. In practice, the finance team reconciles the customs declaration with the supplier invoice, reports the self-assessed import VAT in DDV-O field 26, and includes the related import tax base in field 31.

That changes the cash-flow pattern, but it does not make the compliance work disappear. For a business with full input VAT recovery, the import VAT can be neutral in the same reporting cycle because the output-side self-assessment and the input-side recovery are handled through the return. Where recovery is restricted, only partial, or delayed by weak documentation, the economics are different.

The real operational question is therefore not just whether Article 72 exists. It is whether the importer can tie the import entry, the VAT base, and the supporting documents into a clean DDV-O workflow. That is where Slovenia import VAT self-assessment becomes either straightforward or messy for AP, accounting, and ERP teams.

Who can use Article 72, and why Slovenia stands out in Europe

This workflow matters to businesses that are VAT-registered in Slovenia and import goods into the country, along with the accountants, customs teams, and ERP specialists who have to turn import data into a correct VAT return. In current practice, the important question is not whether a business can find a separate application form for postponed accounting. It is whether the importer is correctly set up to report import VAT through DDV-O and support that reporting with the right customs evidence.

Current official DDV-O guidance frames the issue around self-assessed import VAT reported in field 26 with the related tax base in field 31. That makes the practical regime return-driven rather than approval-driven: the real work sits in DDV-O preparation, document matching, and controls around the customs entry.

That is one reason Slovenia feels different from several other European systems. In many jurisdictions, postponed accounting is discussed as an election, approval, or authorization problem. In Slovenia, finance teams usually experience it as a reporting and reconciliation problem instead.

It also helps to separate import VAT self-assessment from domestic reverse-charge rules. Article 72 deals with import VAT being handled through the VAT return; it is not the same mechanism covered in Slovenia Article 76a reverse-charge invoice requirements, which applies to a different set of domestic transactions. Treating those rules as interchangeable is an easy way to misconfigure tax codes or misread the return.

DDV-O fields 26 and 31 are the center of the import VAT workflow

The return mechanics are the part most summary pages skip, even though they are what the finance team actually works with. According to the Slovenia DDV-O instructions for import self-assessment, Slovenia's DDV-O instructions say field 26 is used for VAT charged on the grounds of self-assessment from import, and the tax base for those imports is included in field 31. That is the core reporting logic behind Article 72 in practice.

Field 26 carries the VAT amount that the importer self-assesses on imported goods. Field 31 carries the taxable base connected with those imports, with the customs document supplying the underlying values. The operational check is simple to describe even if it takes discipline to execute: the VAT amount in field 26 and the import base in field 31 should both trace back to the customs record, not just to whatever appears on the supplier invoice.

For a fully deductible importer, the same reporting period will often include the corresponding input claim, which is why the regime is described as cash-flow friendly. That effect depends on having full recovery rights and complete support. If the business is partly exempt, has blocked input VAT, or misses the deduction side of the entry, the return no longer produces a clean zero-net result. Teams already tightening their evidence around DDV-O preparation will usually want the broader controls described in the Slovenia DDV-O records and pre-filled VAT return guide as well.

The documents behind the VAT entry: customs declaration, invoice, and support files

The customs declaration, often referred to in practice as the DUT or carinska deklaracija, is the primary import-VAT evidence. It tells the finance team what entered the country, which importer was declared, which customs values were used, and what VAT base was assessed. The supplier invoice matters too, but it does not replace the customs entry. Import VAT reporting works only when those documents are read together.

That is also why the numbers do not always match line for line. Official customs guidance explains that VAT at import is charged on a base formed from the customs value of the goods plus customs duties and other charges payable at import, not simply the supplier's commercial invoice amount. Freight, insurance, valuation adjustments, and duty can all change the tax base. A clean file therefore links the customs declaration to the supplier invoice and any supporting freight or customs-cost evidence instead of assuming one document will tell the whole story.

Importer identification belongs in that same record set. The Financial Administration of the Republic of Slovenia states that economic operators involved in customs activities must first register for an EORI number, so missing or incorrect EORI data can create problems before the VAT return is even prepared. Teams that want this handoff to be repeatable usually treat customs and invoice matching as part of broader invoice data extraction workflows, especially when they are also standardizing a customs broker document-processing workflow across high-volume imports.

---

Typical bookkeeping entries and when the cash-flow benefit is real

The bookkeeping flow is easier to control when it is split into the documents that create each number. The supplier invoice establishes the commercial purchase. The customs entry establishes the import tax base and any duty. The VAT return then carries the self-assessed import VAT. Trying to force all three into a single invoice-style posting usually hides the reconciliation points that matter.

A typical fully deductible importer will often book the workflow along these lines:

• Debit purchases or inventory and credit the supplier liability for the commercial invoice amount.
• Debit customs duty, freight, insurance, or other landed-cost accounts and credit the customs broker, carrier, or customs payable account for those import charges.
• Debit recoverable import VAT and credit import VAT payable, or the equivalent VAT control accounts used in the ERP, for the self-assessed amount reported in DDV-O field 26, subject to the business's actual recovery rights.

The account names vary by chart of accounts, but the control logic does not. The customs declaration should support the VAT base, the return should carry the self-assessed amount, and the deduction entry should only be taken to the extent the importer is entitled to recover it.

The benefit is real because the business does not have to fund import VAT at the border and wait to recover it later through the return. But the headline is only accurate when the deduction is fully available and posted in the same cycle. A partially exempt importer, or one that fails to connect the customs record to the deduction claim, will still feel a cost or timing effect. That is why Slovenia import VAT accounting entries should be designed around reconciliation first and convenience second.

Common mistakes in Slovenia import VAT reporting

Most filing problems come from data mismatches rather than from misunderstanding the headline rule. A missing EORI number, the wrong commodity code, or the wrong customs-value basis can distort the import entry before accounting ever sees it. Exchange-rate mistakes create the same kind of downstream problem, especially when teams assume the supplier invoice currency treatment is automatically the same as the customs valuation treatment.

Another frequent error is to report the output side of the import VAT but miss or mis-time the deduction side. That turns a cash-flow-neutral process for a fully deductible business into an avoidable cost or reconciliation break. The opposite problem also happens: teams try to deduct import VAT from invoice data alone, without a customs declaration that supports the amount actually reported in DDV-O.

Mismatch does not always mean error, though. The customs VAT base can legitimately differ from the supplier invoice because it may include duty, freight, insurance, or other valuation components. The control is not to force the numbers to match, but to explain and document the difference. For affected goods, CBAM can add another layer of reporting attention, but it should be treated as an adjacent compliance issue, not as the center of the Slovenia Article 72 workflow.

Why Slovenia's model is easier than application-based postponed accounting systems

The shortest comparison is this: in countries where postponed accounting is framed as an approval or opt-in regime, the first compliance question is often whether the business qualifies for the mechanism at all. In Slovenia, the more useful question is usually what evidence and return logic the importer needs in order to report import VAT correctly. That makes the workflow feel less like a permission exercise and more like an accounting-control exercise.

That difference matters for multinational teams. A process built for France, Italy, or Belgium may start with authorization status and only then move into return mechanics. In Slovenia, the return mechanics and document linkage deserve attention from the start. The practical advantage is not that the work disappears. It is that the work moves toward DDV-O reporting, customs-document reconciliation, and record retention rather than an extra access step.