| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2966 |
| Technical Name |
l10n_rs_eotpremnice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2966 |
| Technical Name |
l10n_rs_eotpremnice |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Serbia e-Otpremnice
SEF electronic delivery notes (e-otpremnice) for Odoo — issue, send and track every goods movement on the Serbian e-Faktura platform
Connect Odoo to the Serbian SEF (Sistem e-Faktura) platform of the Ministry of Finance. Outgoing deliveries, internal transfers and customer returns become structured electronic delivery notes registered on SEF, where the receiver confirms receipt — ready for the e-otpremnice waves (public sector & excise goods from 1 Jan 2026; all private-sector B2B from 1 Oct 2027).
SEF submission & tracking
Register, send, refresh status and cancel (storno) delivery notes over the documented SEF public API. Demo and production endpoints are editable; requests retry with exponential backoff and every call is logged. The state machine tracks New → Sent → Approved / Rejected / Cancelled.
Accurate otpremnica document
Issuer and receiver parties identified by PIB, dispatch and delivery locations, per-line quantity with UN/ECE Rec.20 units of measure, movement purpose (sale / transfer / consignment) and transport details — serialised to a deterministic, canonical JSON document.
Real PIB checksum validation
The nine-digit Serbian PIB is validated with the official ISO 7064 MOD 11,10 check-digit algorithm on the company and partners, plus the eight-digit matični broj (APR registration number).
SEF invoice status sync
Record the SEF invoice id on a customer invoice and poll its clearance status, so the delivery-note and invoice flows share a single SEF connection and one status view.
Business-rule validation
A dedicated SEF e-otpremnice rule set — issuer/receiver PIB, RS country, positive quantities, units of measure, movement purpose and return-note referencing — runs before submission so errors surface in Odoo, not on the portal.
BYOK & private by design
Your SEF API key is held on the connection record and transmitted only to the SEF endpoint you configure. Nothing is bundled with the module and no data is sent anywhere else. An onboarding wizard, configuration model and optional batch crons complete the workflow.
Compatible with Odoo 18 & 19
Built on the shared e-Invoice Core Engine (deterministic JSON builder, declarative validation framework and BYOK REST transport with logging). No engine functionality is duplicated.
Screenshots
Outgoing Delivery With E Otp
Deliveries List E Otpremnica
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module