Unit rounded invoice by Currency
account_invoice_rounding_by_currency · OCA/account-invoicing
Health
32/100
poor
-
Security22/251 minor finding
-
Activity0/25Last human commit 109 months ago
-
Required by5/250 modules depend on it
-
Maturity5/25In 1 Odoo series since 8.0
Heuristic over the facts below, not an audit · How it's computed
Required by
0
Modules depending on it
External deps
0 pip · 0 bin
Python packages / system binaries
License
AGPL-3
No conflicts with its dependencies
Folder size
0.03 MB
Module directory on disk
Code analysis
6 migration notes
4 models
1 view
0 HTTP endpoints
Migration considerations
- Migrating to 19.0: only `__manifest__.py` is recognized: a module with `__openerp__.py` is not detected at all. migration-openerp-manifest · source
RoundingByCurrency— Migrating to 19.0: `_sql_constraints` is ignored and its constraints are silently not created: declare `models.Constraint` attributes instead. migration-sql-constraints · sourceview_account_config_settings_currency— Migrating to 17.0: `attrs=`/`states=` are rejected in views: convert them to Python expressions in `invisible`/`readonly`/`required`, keeping the original AND/OR logic. migration-view-attrs-states · source- Migrating to 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp`) migration-openerp-import · source
- Migrating to 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp`) migration-openerp-import · source
- Migrating to 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp`) migration-openerp-import · source
Migration review checklist, not a compatibility verdict. "Migrating to X.0" applies once you upgrade to that version; "Since X.0" means this version already ignores or rejects that code. Methodology
Description
Dependencies
Code analysis
Extracted from the source by best-effort static analysis (no code is executed); details may be incomplete.
Views touched 1
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
view_account_config_settings_currency |
account settings.add.rounding.currency | account.config.settings | Inherits account_invoice_rounding.view_account_config_settings |
HTTP endpoints 0
No HTTP endpoints found for this module.
Models touched 4
New fields (2)
-
company_idMany2one → res.companydefault=_default_companyrequired=True args: 'res.company', 'Company' -
currency_rounding_rulesOne2manyrelated='company_id.currency_rounding_rules'string='Rounding Rule'
-
onchange_company_id(self, cr, uid, ids, company_id, context=None)
New fields (0)
No new fields.
Public methods (0)No public methods.
New fields (5)
-
company_idMany2one → res.companyrequired=True args: 'res.company', 'Company' -
currency_idMany2one → res.currencyrequired=True args: 'res.currency', 'Currency' -
tax_calculation_roundingFloatargs: 'Tax Rounding Precision' -
tax_calculation_rounding_account_idMany2one → account.accountdomain=[('type', '<>', 'view')] args: 'account.account', 'Tax Rounding Account' -
tax_calculation_rounding_methodSelectionhelp="If you select 'Round per line' : for each tax, the tax amount will first be computed and rounded for each PO/SO/invoice line and then these rounded amounts will be summed up, leading to the total amount for that tax. If you select 'Round globally': for each tax, the tax amount will be computed for each PO/SO/invoice line, then these amounts will be summed up and eventually this total tax amount will be rounded. If you sell with tax included, you should choose 'Round per line' because you certainly want the sum of your tax-included line subtotals to be equal to the total amount with taxes."string='Tax Calculation Rounding Method' args: [('swedish_round_globally', 'Swedish Round globally'), ('swedish_add_invoice_line', 'Swedish Round by adding a line')]
No public methods.
New fields (1)
-
currency_rounding_rulesOne2many → company.roundingargs: 'company.rounding', 'company_id', 'Rounding Rule'
No public methods.