Slovenia VAT Records Requirements: Pre-Filled DDV-O Guide

From 2025-07-01, Slovenian VAT taxpayers must electronically submit two VAT record sets for each tax period: the evidence of calculated VAT and the evidence of VAT deduction. That is the core change behind the current Slovenia VAT records requirements, and it matters because the Financial Administration of the Republic of Slovenia (FURS) uses those submitted records, not just the final return, to prepare the DDV-O.

The timing is not optional if you want a Slovenia pre-filled VAT return. For the first live period, FURS stated that the pre-filled DDV-O for July 2025 would be generated from VAT records submitted by 2025-08-26, or by 2025-08-14 where the taxpayer also had to file RP-O; if that timing was missed, the taxpayer had to submit the DDV-O themselves, as explained in FURS guidance on VAT-record submission and pre-filled DDV-O deadlines. In practice, that means Slovenia VAT records 2025 is not just a reporting change. It is a deadline-driven data process.

This guide therefore focuses on the operational path from invoice and purchase data, to VAT records submitted through eDavki or approved tools, to the DDV-O that FURS can pre-fill. The main failure points are usually not theoretical VAT rules. They are document completeness, correct tax coding, reconciliation between source records and ledger figures, and submission timing. If any of those break down, the filing cycle becomes manual, slower, and harder to review.

Who Must Submit the Two Slovenian VAT Record Sets

If you are filing DDV-O for a Slovenian VAT period, these two record sets are part of that reporting workflow. This is not a special rule for one industry, a temporary onboarding exercise, or a one-off disclosure request. It sits inside the regular VAT reporting cycle under the ZDDV-1 framework.

In practice, finance teams need to distinguish between two separate record sets:

• The sales records, which capture the output-tax side of reporting and function as the evidence of calculated VAT.
• The purchase records, which capture the input side of reporting and function as the evidence of VAT deduction.

That distinction matters because the two datasets answer different compliance questions. The sales side shows transactions on which VAT was charged or otherwise reported. The purchase side shows transactions that may support input VAT recovery, subject to the normal deduction rules. When people refer to Slovenia VAT ledgers, they are usually talking about these two structured records together, not a single generic VAT file.

It is also important to treat these as formal electronic reporting records, not just internal bookkeeping ledgers kept on hand in case of audit. The Slovenia evidence of calculated VAT and VAT deduction must be organized in the format and category logic expected by FURS so it can feed the wider VAT reporting process. A chart of accounts export or a loosely labeled spreadsheet may help internally, but it is not the same thing as maintaining records that match the required VAT evidence structure.

For that reason, teams working under ZDDV-1 should align their internal terminology, report mapping, and review workflow with FURS record categories even if their ERP or accounting software uses different names. If one system says sales VAT register, another says tax journal, and a third says purchase book, the key compliance question is whether each field maps cleanly to the sales evidence of calculated VAT and the purchase evidence of VAT deduction expected for Slovenian filing. Clear category mapping reduces review friction and makes the downstream DDV-O process much easier to control.

What the Sales and Purchase Records Need to Contain

Slovenia's VAT records requirements are not just about producing two files at period end. Finance teams need two usable VAT ledgers: one built from outbound sales documents and one built from inbound purchase documents, each with enough detail to support the VAT position that will feed the return. In practice, that means every line in the records should trace back to a source document, a tax treatment, and the period in which the transaction belongs.

A useful way to think about the two required VAT record sets is this:

Record set	What it needs to prove
Sales record	Why output VAT was charged, not charged, corrected, or adjusted
Purchase record	Why input VAT is deductible, partly deductible, blocked, or deferred

For the sales-side record, teams generally need to capture the core invoice facts that explain calculated VAT on outbound transactions. That usually includes:

• Invoice number or other document reference
• Invoice date and, where relevant, the tax point or supply date
• Customer identification details
• Taxable amount by rate or treatment
• VAT amount by rate
• Total document amount
• Any exempt, reverse-charge, or special-regime classification applied
• Corrections linked to the original document, including credit notes, debit notes, cancellations, or price adjustments

The goal is not only to list sales invoices, but to preserve the logic behind the VAT treatment. If a transaction is zero-rated, exempt, outside scope, or subject to a specific domestic rule, the classification needs to be consistent in the VAT ledger so the downstream totals reconcile cleanly. A credit note without a clear link to the original invoice, or a correction posted in the wrong period, can distort both the record set and the pre-filled DDV-O figures that follow from it.

For the purchase-side record, the focus shifts from calculated VAT to deductible VAT. Here, the record needs to show why input VAT is claimable and whether the claim is full, partial, delayed, or not allowed. Teams usually need:

• Supplier name and identifying details
• Supplier invoice number or customs or import document reference where relevant
• Purchase document date and receipt or tax point details if they affect timing
• Taxable amount
• VAT amount
• The rate or treatment applied
• Evidence supporting deduction, such as a valid supplier invoice or import documentation
• Any partial deduction logic, non-deductible element, or business-use allocation
• Corrections, supplier credit notes, and period adjustments tied back to the original purchase entry

This is where document support matters most. A purchase document may show VAT, but that does not automatically make it deductible. The purchase-side VAT record has to reflect whether the business has the right evidence, whether the expense falls within deductible categories, and whether the claim belongs in the current reporting period. That is especially important for mixed-use costs, late-arriving invoices, and supplier documents with incomplete information.

Teams that also manage Western Balkan compliance can compare this with Serbia internal invoice requirements, where deduction timing can depend on preparing an internal invoice and sending it through SEF by a fixed deadline.

Before submitting the Slovenian VAT ledgers, teams should be checking three things:

• Completeness: all sales invoices, purchase invoices, credit notes, and adjustments for the period are captured
• Classification: each document has the correct VAT code, rate, and treatment
• Reconciliation: record totals agree to the accounting ledger, source documents, and any known period-end adjustments

Consistent tax coding is what keeps the two record sets usable. If sales invoices are coded one way in the ERP, credit notes another way in the accounting system, and purchase invoices manually adjusted in spreadsheets, reconciliation problems appear quickly. The most common trouble spots are corrected invoices, mixed-period documents, incomplete supplier details, and purchases where deduction depends on additional support rather than the invoice alone.

Document readiness matters before filing readiness. By the time a team prepares the Slovenian sales and purchase records, the underlying invoices and purchase documents should already be classified in a way that supports the VAT outcome. The same discipline appears in Kosovo purchase and sales book filing rules, where source documents also need to be structured and coded before submission.

---

How Timely Records Produce a Pre-Filled DDV-O

The timing sequence matters as much as the content of the records. For each VAT period, the finance team first prepares and reconciles the sales and purchase records, then submits both record sets electronically, then waits to see whether FURS generates a Slovenia pre-filled VAT return, and only after that reviews and completes the DDV-O filing workflow. A pre-filled return is available only when the records arrive early enough and the taxpayer has not already filed the DDV-O for that period.

The ongoing rule is straightforward: FURS can pre-fill DDV-O only when the VAT records are submitted at least three working days before the return deadline.

For the July 2025 go-live, the cutoff depended on whether RP-O was also required:

July 2025 situation	Latest record submission date for a pre-filled DDV-O
No RP-O filing for the period	2025-08-26
RP-O also required	2025-08-14

July 2025 therefore had two different cutoffs, with the earlier date applying where RP-O also had to be filed. Cross-border teams will recognize the same deadline discipline from Portugal's SAF-T billing-file deadlines.

A practical operating sequence looks like this:

1. Close the period and reconcile the sales and purchase records.
2. Submit both Slovenian VAT record sets electronically for the relevant period.
3. If the applicable cutoff is met, allow FURS to generate the pre-filled DDV-O in eDavki.
4. Review the generated return, complete any required checks, and finalize the filing.

Missing the pre-fill cutoff does not remove the VAT filing obligation. It only means FURS will not prepare the Slovenia pre-filled VAT return for that period, so the taxpayer must prepare and file the DDV-O manually by the legal deadline instead of relying on a generated version.

A pre-filled return should never be treated as no-touch. Before relying on a generated DDV-O, teams still need reconciled invoice data, reviewed purchase records, checked RP-O consistency where relevant, and confirmation that the submitted records actually reflect the VAT position for the period.

Using eDavki and miniBlagajna in the Submission Workflow

For Slovenia eDavki VAT records submission, eDavki is the official control point once the sales and purchase records are ready. Teams submit the two VAT record sets there, track filing status, and review how the records align with DDV-O. miniBlagajna can also sit upstream in the workflow because FURS has indicated it can support keeping and submitting the required VAT records, but neither tool replaces the need for complete source documents, correct VAT coding, correct period allocation, and period-end review. If you also need the point-of-sale rules on when an invoice must receive FURS confirmation, our guide to Slovenia fiscal verification of invoices explains the seller duties, buyer checks, and miniBlagajna fallback path.

FURS has also highlighted an eDavki submission review, sometimes described as a traffic-light view, for checking whether the VAT records were successfully filed and whether they are aligned with DDV-O. Teams should perform four checks each cycle:

• Confirm both record sets show as submitted for the correct tax period.
• Check record completeness against the sales ledger, purchase ledger, and any manual adjustments.
• Compare the resulting figures with the DDV-O draft and investigate any mismatch before final filing.
• Resolve exceptions quickly, including rejected submissions, missing records, and items flagged as inconsistent with the return.

eDavki is the submission and control point for the live filing cycle, while miniBlagajna is relevant only to the extent it helps you maintain and transmit accurate records into that official process.

---

Building a Monthly Slovenia VAT Records Workflow

A workable period-end process for Slovenia VAT records requirements starts well before the submission deadline. Even if your business does not file monthly, the same control points apply to each VAT period. The strongest teams treat the sales and purchase records as a controlled data flow, not as a last-minute tax extract. That means collecting source invoices, credit notes, and purchase documents throughout the period, capturing the required fields in a consistent format, assigning the correct VAT treatment, and resolving exceptions before the records are submitted. If that discipline is in place, the pre-filled DDV-O becomes easier to review. If it is missing, finance teams are forced into manual corrections under deadline pressure. If you also need to confirm how invoices must be exchanged before they ever feed these VAT ledgers, our guide to Slovenia's budget-user e-invoicing rules and 2028 B2B timeline covers that separate compliance layer.

A practical recurring workflow usually follows six steps. First, collect and register all source documents for the period, including sales invoices, cancellation documents, credit notes, supplier invoices, import or customs support, and any records needed to support deductions. Second, capture the required invoice and purchase data fields with stable document references so each line in the VAT records can be traced back to the underlying evidence. Third, classify each transaction using the correct VAT code and tax treatment, especially for reverse charge cases, exemptions, intra-EU activity, and adjustments. Fourth, reconcile the records against the general ledger, subledgers, and open document lists so missing or duplicated items are identified early. Fifth, submit the two record sets within the required timetable. Sixth, verify whether a pre-filled DDV-O is available and review it critically rather than assuming it is complete or accurate.

The biggest breakdowns are operational rather than legal. Late document capture, inconsistent tax coding, and unreconciled credit notes or unsupported purchase-side evidence all weaken the records before submission and increase the chance that the pre-filled DDV-O will still need manual correction.

To reduce those risks, controllers and senior bookkeepers should build explicit period controls into the process. Lock a cut-off date for routine document intake, but keep an exception queue for late-arriving items that need tax review before inclusion or deferral. Require mandatory document references so every VAT-record entry can be traced to an invoice number, supplier document, or adjustment note. Assign review ownership across finance operations, for example document capture by AP and AR staff, tax coding review by a senior bookkeeper, and final reconciliation sign-off by the controller or outsourced reporting lead. Maintain a short audit trail for each exception, especially when the team overrides a default VAT code, includes a late credit note, or decides that purchase-side evidence is not yet sufficient for deduction.

Teams already handling Lithuania's i.SAF-T audit-file requirements will recognize the same need for standardized source capture, field mapping, and exception handling before submission.

Control points for each Slovenia VAT reporting cycle:

• Confirm all sales invoices, credit notes, and purchase documents for the period have been captured or placed in a reviewed exception queue.
• Check that required fields and document references are complete and traceable to source evidence.
• Review VAT coding consistency across similar transaction types and investigate unusual tax treatment.
• Reconcile sales and purchase records to ledgers, tax accounts, and adjustment documents before submission.
• Verify that purchase-side evidence supports any input VAT claimed.
• Submit both VAT record sets on time and retain proof of submission.
• Review any pre-filled DDV-O line by line and investigate differences before filing.
• Retain a clear audit trail showing who reviewed exceptions, reconciliations, and final return readiness.