Romania - Localization Config
This module allows you to install and configure all the localization modules related to Romania. Some of the modules will load data at install.
For Romanian companies, you will have a dedicated page in Configuration, from where you cna install rest of the modules, or set up some added fields for localization.
* All changes added by the Romanian localization will only apply for companies that have the “Use Romanian Accounting” checkbox set.
* All menus and fields are visible in the interface if you are working on a Romanian company, otherwise the are hidden.
Table of contents
Installation
To install this module, you need to:
clone the branch 19.0 of the repository https://github.com/OCA/l10n-romania
add the path to this repository in your configuration (addons-path)
update the module list
search for “Romania - Localization Config” in your addons
install the module
Usage
Companies
You can complete dedicated fields for Romanian companies, like “Share Capital”, “CAEN Code”.
From Romanian page from Configuration, you can define new properties for your company, depending on the modules that you have installed.
Partners
You can complete dedicated fields for Romanian partners, like “VAT Subjected”, “CAEN Code”, “E-invoicing”.
You can input also partners without VAT country code, but you need to select also the country.
Products
Use different taxes for “Service” products, they are defined in the Chart of Accounts, but here we set up the default taxes used.
Bank Accounts
Tick the “Ro Print in Report” fields if you want the bank account to be printed in reports. The flag only marks the accounts; it is up to each report to filter the bank accounts on it.
** This applies also for company bank accounts, there you can use also the related field from Account Journal to mark them.
Changelog
20.0.0.10.0
Removed the banks and report_address_company QWeb templates (views/common_report.xml). They were an example left over from a report override that no longer exists, no module in the repository calls them, and res.partner.bank.currency_id, which banks filtered on, is gone in Odoo 20.0. The “Ro Print in Report” fields are kept - they are the configuration the reports read.
19.0.0.8.1
Fix a foreign tax ID being silently prefixed with its country code on every save, which made it impossible to store the number in its local form. A Hungarian 11-digit adószám (26173247-2-08) became HU26173247-2-08 on create, and removing the prefix brought it back on the next write. Since VIES only recognises the 8-digit EU form (HU26173247), the intra-Community check kept answering unassigned, vies_valid stayed unset and the intra-Community fiscal position was never selected, so the invoice was taxed at the domestic rate instead of being exempt.
The cause was _split_vat deducing the country code from a database lookup (search([("vat", "=", vat)])): during create/write the record is already stored when _check_vat runs, so it matched itself and _run_vat_checks re-attached the prefix. The country code is now taken from the record being parsed, and only for a bare numeric CUI, so writing a Romanian CUI without the RO prefix keeps working.
Dropping the lookup also removes one search per _split_vat call - the method is used by _compute_l10n_ro_vat_number and by several core and Enterprise localisations - and the non-deterministic result when the same vat string existed on partners from different countries (limit=1 picked one arbitrarily).
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Fekete Mihai <feketemihai@nexterp.ro>
-
Dorin Hongu <dhongu@gmail.com>
Adrian Vasile <adrian.vasile@gmail.com>
-
Anastasescu Răzvan-Ioan <razvan@qdev.ro>
Do not contact contributors directly about support or help with technical issues.
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/l10n-romania project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-l10n-ro-config 20.0.1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_l10n_ro_config-20.0.1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_l10n_ro_config-20.0.1.1.0-py3-none-any.whl
| Download URL | odoo_addon_l10n_ro_config-20.0.1.1.0-py3-none-any.whl |
|---|---|
| Size | 92.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0b3e164829b0c8d7d1e1bf7957f7531dac9807405f90cf77e525ff30456ee6a1
|
|
BLAKE2b-256 checksum How to use checksums |
c822f9740f8d53875b848329f1c5b27a6d0d142f060701e4e6f7266dff80cca2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-l10n-ro-config 20.0.1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
