| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 1384 |
| Technical Name |
nexterp_sgr_account |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 1384 |
| Technical Name |
nexterp_sgr_account |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
Romania - SGR on Invoices
Automatic SGR deposit child line on account.move.line (manual invoices and refunds).
Overview
Automate the SGR deposit on customer invoices, vendor bills and credit notes. Whenever you add a beverage line to a draft invoice, an SGR child line appears underneath it with the right category, the current deposit rate and no taxes — exactly the way RetuRO requires it to show on the fiscal document.
A new company-level SGR Liability Account setting (typically Romanian 462 Creditori diverşi or 461 Debitori diverşi) becomes the default income and expense account on every product flagged Is SGR Product, so the 0.50 RON deposit books as a balance-sheet item rather than as revenue or cost.
If the invoice was generated from a sale order, purchase order or POS
order that already carries the SGR line, the module recognizes the
existing sibling and adopts it via sgr_parent_line_id rather than
creating a duplicate. The same applies to e-factura imports — turn the
per-document Auto-add SGR Lines toggle off and the upstream lines
are preserved untouched.
Built & supported by NextERP Romania
Romanian Odoo specialists, here for the long run — from implementation to localization and day-to-day production support.
What we do
Odoo Solutions
From quick-start rollouts to multi-company deployments and custom modules built for your processes.
Romanian Localization
SAF-T (D406), e-Factura, e-Transport, D300 / D390 / D394, ANAF integration, full chart of accounts and fiscal positions.
Our Services
Implementation, customization, migration, integration, support and consultancy — Romanian-speaking, SLA-backed.
Features
- Auto SGR child line on every draft invoice — adding a beverage
line to a customer invoice or vendor bill instantly appends a paired
account.move.linewith the matching SGR product, current deposit rate and zero taxes. - Parent/child sync — changing the parent line quantity, product
or UoM updates the SGR child; removing the parent removes the child
via
ondelete='cascade'. - No duplication on cross-module flows — when an invoice is created
from an SO/PO/POS that already carries an SGR line, the module adopts
the existing sibling through
sgr_parent_line_idinstead of inserting a second one. - SGR Liability Account company setting — points at the RO 462 / 461 account used as default income and expense on every Is SGR Product. Exposed in Settings → Accounting → Fiscal Localization.
- Onchange on product — flagging a product as Is SGR Product pre-fills its income and expense accounts with the SGR liability account, keeping deposits off P&L.
- Per-invoice opt-out — every
account.movecarries an Auto-add SGR Lines boolean (after Source Document), defaulting from the company setting. Disable on documents that already carry SGR lines from EDI / e-factura. - Tracks the SGR pair —
is_sgr_lineandsgr_parent_line_idfields onaccount.move.linemake the deposit easy to filter, reconcile and report on.
Configuration
1. Pick the SGR liability account
Open Settings → Accounting → Fiscal Localization → SGR Liability Account and pick the third-party account that should hold the deposit. For Romania the standard choices are:
- 462 Creditori diverşi — when the company is a net debtor of the system (typical retailer that owes deposits to consumers).
- 461 Debitori diverşi — when the company is a net creditor of the system (retailer that has handed over more empties than what is held at the till).
The same account is reused on both the income and the expense side so that the deposit flows as a balance-sheet item, never through revenue or cost accounts.
2. Apply it on SGR products
In Inventory → Products, open each product flagged Is SGR Product. Toggling the flag triggers an onchange that pre-fills Income Account and Expense Account with the company SGR liability account. Override per product only if you need a sub-account split (per category, per warehouse, etc.).
3. Default behavior on new invoices
Each account.move inherits the company-wide Auto-add SGR Lines
toggle from nexterp_sgr. The field appears on the invoice form right
after the Source Document column.
- Keep it enabled for manual invoices you key in by hand — the SGR child line is added under each beverage line automatically.
- Disable it on individual documents when the SGR lines are already pre-filled by an external system (EDI, e-factura import, sync from another ERP). The orphan SGR sibling will be adopted by its parent line on save, so you still keep the parent/child link.
How it works
Manual customer invoice or vendor bill
- Create the invoice in draft.
- Add a beverage line with a product that has an
sgr_product_idconfigured. On save, an SGR child line is appended immediately under it, with the matching SGR product, the deposit rate effective on the invoice date, no taxes, and the SGR liability account on both income and expense sides. - Change the parent quantity, product or UoM — the SGR child is recomputed. Remove the parent line — the SGR child is removed automatically via cascade.
Invoice generated from an SO, PO or POS order
When an invoice is created from a sale order, purchase order or POS
order that already carries an SGR line (because the corresponding
companion module added it on the source), the SGR sibling appears on
the invoice with is_sgr_line=True but no parent. On save, the module
recognizes it and writes sgr_parent_line_id on it — so the deposit
is paired with its beverage line without ever being duplicated.
Posting
On post, the SGR amount books on the SGR liability account (462 / 461) on both the debit and the credit side, while the beverage line books on its standard revenue or expense account. The deposit therefore flows through the balance sheet, not through the income statement.
Opt-out per document
If the SGR lines are pre-filled by an external source (e-factura import, EDI feed, ERP-to-ERP sync), untick Auto-add SGR Lines on the invoice header — the module then leaves the upstream lines alone and only links orphan SGR siblings to their parents.
Versions
19.0.1.0.0 (2026-05-25)
- Changelog tracking starts at this release.
Discover the NextERP suite
Other modules from the same publisher, built to work together.
NextERP Romania
Odoo implementation, customization, Romanian localization and long-term support since 2018.
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