Odoo/addons/l10n_do/data/fiscal_position_template.xml, branch 14.0 The current checkout of upstream Odoo [IMP] account, l10n_*: v13 taxes 2019-05-10T11:52:58+00:00 Olivier Colson oco@odoo.com 2019-04-19T10:06:07+00:00 3936d655c4bfd845b6ead724cecdc8e7c62816eb - Add repartition lines on taxes - Link account tags directly to account.move.line; remove the tag_ids field from account.tag - Add a new report engine dedicated to tax reports, directly generating account tags. It is called as an alternate mode of generic tax report, with a dedicated "Use tax grids" toggle. >> The biggest change lies in the way the new tax report computes its values. Everything is now aggregated directly using the tags set on the account move lines. Thanks to that, modifying the configuration of a tax today will not impact the report for the previous periods anymore. This is a big improvement, as it means the report will keep on reflecting the values that were submitted to the state before, whatever the configuration change. - Add an audit char field to account.move.line telling with tax grids are impacted by the line, with the corresponding amount - Modify the behavior of cash basis taxes: the cash basis account is now used as the transition account, while the regular account given in tax declaration is used to store the final entry (it was the opposite before) - Modify every l10n_* module in order to keep them consistent with these changes closes odoo/odoo#32833 Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com> 
- Add repartition lines on taxes

- Link account tags directly to account.move.line; remove the tag_ids field from account.tag

- Add a new report engine dedicated to tax reports, directly generating account tags. It is called as an alternate mode of generic tax report, with a dedicated "Use tax grids" toggle.

>> The biggest change lies in the way the new tax report computes its values.
Everything is now aggregated directly using the tags set on the account move lines. Thanks to that,
modifying the configuration of a tax today will not impact the report for the previous periods anymore.
This is a big improvement, as it means the report will keep on reflecting the values that were submitted
to the state before, whatever the configuration change.

- Add an audit char field to account.move.line telling with tax grids are impacted by the line, with the corresponding amount

- Modify the behavior of cash basis taxes: the cash basis account is now used as the transition account, while the regular account given in tax declaration is used to store the final entry (it was the opposite before)

- Modify every l10n_* module in order to keep them consistent with these changes

closes odoo/odoo#32833

Signed-off-by: Quentin De Paoli (qdp) <qdp@openerp.com>
 [FIX] l10n_do: adapt to Norma 07-2018 2018-04-13T14:03:55+00:00 qdp-odoo qdp@odoo.com 2018-04-13T13:55:37+00:00 080094207888f4514f6a0a8f0263166d7998bbf5 Was PR #24123 and #24124. Courtesy of Gustavo Valverde (Iterativo) 
Was PR #24123 and #24124. Courtesy of Gustavo Valverde (Iterativo)
[IMP] l10n_do: update CoA (for IFRS), taxes, fiscal positions and journals. 2017-03-23T15:49:06+00:00 Gustavo Valverde g.valverde02@gmail.com 2017-03-23T15:41:35+00:00 06c5db50b6212497514fa7e3706efafd872ed10b Courtesy of Gustavo Valverde. PR #13787 Details: ------- - Easier implementation for most of the people - Minor customization to be fully compliant with local regulations - Standardized configuration to help other Odoo consultants and implementers - Use of the account types defined in account instead of creating new ones To comply with local and tax regulations: -The whole Charts of Accounts was changed -Most of the Journals has been preconfigured to comply with tax regulator -All the regulatory taxes were added and configured with group taxes To standardize the Dominican implementations: -An IFRS compatible CoA that does not need major changes for most companies -A well structured CoA with a codification logic. -Use of the Odoo original flow for creating tax compliant invoice sequences 
Courtesy of Gustavo Valverde. PR #13787

Details:
-------
- Easier implementation for most of the people
- Minor customization to be fully compliant with local regulations
- Standardized configuration to help other Odoo consultants and implementers
- Use of the account types defined in account instead of creating new ones

To comply with local and tax regulations:
-The whole Charts of Accounts was changed
-Most of the Journals has been preconfigured to comply with tax regulator
-All the regulatory taxes were added and configured with group taxes

To standardize the Dominican implementations:
-An IFRS compatible CoA that does not need major changes for most companies
-A well structured CoA with a codification logic.
-Use of the Odoo original flow for creating tax compliant invoice sequences