Skip to Content

Slovenian FURS Control

English | Slovenščina

License: AGPL-3 PMISuite/l10n-slovenia

Compare KIR/KPR downloaded from FURS with current Odoo tax-register lines in Odoo 18 Community. Identify differences for the same company and period, trace them to source documents, and retain the evidence behind each comparison. No earlier Odoo XML export is required.

Start with an accepted FURS VAT-book download, review document differences and column totals, then open the linked Odoo evidence to investigate. Comparison records are retained; comparing again creates a new record of the current state.

Documentation

Both manuals are available in English and Slovenian and include screenshots and detailed procedures.

Features

Document-level comparison

  • Compare issued and received VAT-book rows by register, document reference, and partner tax identity.

  • Identify matched documents, changed values, documents present only in Odoo or FURS, and ambiguous duplicates.

  • Review Odoo, FURS, and Odoo-minus-FURS totals for each monetary column, including DAVEK88. Equal totals do not hide document differences.

  • Open linked Odoo documents and tax-register lines directly from the results.

  • Compare again after Odoo changes, preserving each control separately.

Reviewed omitted-VAT corrections

Accounting managers can initiate a correction for fully omitted positive output VAT on eligible posted customer invoices, customer receipts, and advance VAT-on-receipt entries. The accountant confirms the full omission and selects a later, open reporting period.

The action updates reporting dates and correction fields and records the reason and control reference in the source document's chatter. Accounting dates, amounts, accounts, and reconciliation remain unchanged. Partial omissions, wrong amounts, input VAT, and negative corrections require separate accountant review. There is no automatic undo; follow the User Manual before applying a correction.

Preserved tax evidence

Retain the FURS file, captured Odoo values, and source links with company, period, filename, SHA-256 digest, creator, and creation time. Controls and evidence cannot be edited or deleted.

The existing DDV-O, KIR/KPR, RP-O, and PD-O XML report actions also preserve validated export snapshots. Validation failures stop the export; PDF exports do not create snapshots.

Getting started

  • Requires l10n_si_tax_addons and its dependencies on Odoo 18 Community.

  • Configure the company's VAT number with eight Slovenian taxpayer digits, optionally prefixed with SI, and configure tax mappings and Tax Dates.

  • Accounting users can compare their active, permitted companies. Corrections require accounting-manager access, enabled Slovenian accounting, and write access to the source document and journal items.

Follow the Administrator Manual for setup, then use this workflow:

  1. Download the accepted KIR/KPR state from eDavki using Pridobi podatke iz evidenc under Evidenci obračunanega DDV in odbitka DDV.

  2. Open Accounting > Reporting > Tax Reports > FURS Control > Import FURS Download, select the company, upload the file, enter its FURS reference, and confirm the accepted state.

  3. Click Compare with Current Odoo and review the differences and totals.

  4. Investigate source documents and apply an eligible correction where needed. Export and file through the normal reporting workflow, then compare again.

Scope and supported input

The importer accepts KIR/KPR XML using DDV_KIR_KPR_1.xsd, directly or in a ZIP containing exactly one unencrypted XML file. Upload and extracted content are each limited to 20 MiB. Status receipts (Povratnica) and standalone DDV-O, RP-O, or PD-O files are not accepted for new comparisons.

Comparison validates the schema, taxpayer, and period and reads the included books by Tax Date. It refreshes reporting allocations without changing accounting entries. Results capture that moment; Compare Current Odoo Again creates a fresh control against the same saved FURS download. Import a new file when the FURS state changes.

The module does not connect to FURS, submit reports, or verify digital signatures or portal acceptance. The operator confirms acceptance externally. KIR/KPR agreement does not establish agreement or acceptance of DDV-O, RP-O, or PD-O returns.

Bug Tracker

Report bugs on PMISuite Repository Issues. Include the report type, steps to reproduce, and exact error using synthetic or fully redacted data.

Credits

Authors

Contributors

  • Luxim d.o.o. - Matjaž Mozetič

Maintainers

LUXIM MATMOZ

Current maintainer:

sysadminmatmoz

Odoo Community Association

Luxim is an active member of OCA (Odoo Community Association).