| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 1668 |
| Technical Name |
l10n_ro_account_payment_disposal |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 1668 |
| Technical Name |
l10n_ro_account_payment_disposal |
| License | OPL-1 |
| Website | https://www.nexterp.ro |
| Versions | 18.0 19.0 |
Romania - Payment Disposal
Add payment_disposal field in view
Overview
Adds a single Payment Disposal
(is_l10n_ro_payment_disposal) boolean field on every Romanian
account.bank.statement.line, visible in the standard bank
reconciliation list and form views provided by account_accountant.
The flag is used downstream by other Romanian Enterprise modules (typically the Dispoziție de plată / încasare report packages) to single out bank-statement lines that correspond to a payment disposal document, so they can be filtered, listed or printed separately from regular bank transactions.
This module is intentionally minimal: it does not ship a report, a sequence or any business logic. It just exposes the field and makes it editable from the same screens where the bank statement is normally reviewed.
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
is_l10n_ro_payment_disposalfield — boolean stored onaccount.bank.statement.linethrough thel10n.ro.mixin. Defaults to false; can be ticked manually or set programmatically by a matching rule / API call.- Visible in bank reconciliation — the field is added to the
account_accountantwidget views (view_bank_statement_line_tree_bank_rec_widgetandview_bank_statement_line_form_bank_rec_widget), right after the partner column. - Hidden on non-Romanian companies — the standard
is_l10n_ro_recordcheck from the mixin keeps the column invisible in list and the field invisible in form when the active company is not Romanian. - Pure data carrier — no compute, no constraint, no automation. The module is meant to be installed alongside a payment-disposal report or wizard that consumes the flag.
Configuration
There is no module-level setting. Install the module on a company
with a Romanian Chart of Accounts (the is_l10n_ro_record check
relies on it) and the Payment Disposal column appears on the bank
reconciliation views as soon as you open the bank statement.
1. Verify the field is visible
Open Accounting → Dashboard, click any bank journal's Reconcile button, or Accounting → Customers → Bank Transactions. The list view should show a Payment Disposal checkbox column right after Partner.
2. Multi-company
The column is rendered per company. On non-Romanian companies
(is_l10n_ro_record = False) it is hidden — no per-company opt-in is
needed.
How it works
Open any bank statement (Accounting → Customers → Bank Transactions or the Reconcile widget) and tick the Payment Disposal checkbox on the lines that correspond to a Dispoziție de plată / încasare. Save.
The flag is persisted on account.bank.statement.line.is_l10n_ro_payment_disposal.
Other Romanian Enterprise modules can then:
- filter the bank statement list by this flag,
- generate a payment-disposal printout from the marked lines,
- include / exclude these lines from cash-book or treasury reports.
This module by itself does not print anything — pair it with the relevant payment-disposal report module from the suite.
Versions
19.0.1.0.0 (2026-05-24)
- 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