Slovenia e-SLOG 2.0 e-Invoice
EN 16931 / UBL 2.1 e-SLOG invoicing for Odoo — delivered through UJP e-Račun and Peppol
Connect Odoo to the Slovenian e-SLOG 2.0 electronic invoice standard. Customer invoices and credit notes are built as EN 16931-compliant UBL 2.1 and delivered to the UJP e-Račun public-sector exchange or over Peppol for B2B and cross-border — ready for the 1 January 2028 mandatory B2B e-invoicing obligation in Slovenia.
UJP & Peppol delivery
Upload e-SLOG XML directly to the UJP e-Račun B2G exchange, or submit it to your Peppol access point for B2B and cross-border invoicing. Sandbox and production endpoints are editable; requests retry with exponential backoff and every call is logged.
UPN payment reference + QR
A Slovenian UPN payment reference (SIxx model with the recursive mod-10 check digit) and a UPN QR are generated and rendered to a PNG so the buyer can pay the printed invoice by scanning.
Accurate e-SLOG 2.0 document
Lines carry the EN 16931 VAT categories — 22% standard, 9.5% reduced, 5% super-reduced, zero-rated, exempt, reverse-charge, intra-EU and export — with payment means and credit-note referencing of the original invoice.
Real davčna številka validation
The official 8-digit Slovenian tax number with its mod-11 check digit is validated on the company and partners; the SI VAT-ID is derived as SI + the tax number for Peppol routing.
Business-rule validation
A Slovenian rule set layered on the engine's EN 16931-style core checks supplier/buyer tax numbers, line VAT categories, EUR currency, the SI country code and the routing endpoint before anything is sent.
Bring-your-own-key
Your UJP / Peppol API token or client certificate lives on the connection record, never in the module. Credentials are transmitted only to the endpoint you configure — nowhere else.
Guided onboarding
A wizard captures your Slovenian tax number, delivery channel and credentials, validates the tax number and leaves the company ready to issue e-SLOG invoices. An optional cron delivers posted documents to UJP / Peppol in batches.
Compatible with Odoo 18 and Odoo 19.
Disclosure
This module transmits invoice data only to the UJP e-Račun or Peppol access-point endpoint you configure. Your API token / client certificate and tax number are stored solely on your own database and are never sent anywhere else.
Screenshots
Si Invoice E Slog Generated
E Slog 2 0 E Invoice Documen
Update date: 2026-07-02