-
-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[16][REF] account_ecotax split #454
base: 16.0
Are you sure you want to change the base?
Conversation
Co-authored-by: Maksym Yankin <[email protected]>
Co-authored-by: Alexandre Fayolle <[email protected]>
Co-authored-by: Alexandre Fayolle <[email protected]>
6af346d
to
e68d793
Compare
e68d793
to
8d6082d
Compare
I think the PR is ready, reviews are very welcome @gurneyalex @mourad-ehm @hparfr @bealdav @yankinmax @epanisset @PaulGoubert I've added basic override of the invoice report in |
8d6082d
to
6d05643
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, I'll make some manual tests
6d05643
to
0659a4f
Compare
This PR has the |
…_tax The goal is to be able to choose between the implementation with and without using the odoo tax mechanism. The advantages of the implementation based on Odoo tax mechanims are : - Possibility to choose if product price include or exclude the ecotax amounts - Isolate the ecotax amounts into a specifc accounting account The disadvantage is that it adds a small layer of complexity and you have to manage the tax configuration and see all those ecotax taxes on your invoices And a major difference which can be good or not depending on your use cases, the ecotax amounts are not in the turnover when using Odoo tax mechanism
…n from tests The dependency does not really ease the present test but forces us to put the test as post-installed which cant work as account_ecotax_tax changes the account_ecotax behavior Instead of isolating the tests of account_ecotax, it seems better to get rid of the AccountTestInvoicingCommon dependency. It also speed up the tests.
0659a4f
to
721647d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gurneyalex The module works fine with 3 main settings :
- The tax created with the field eco tax ticked ,ranked upper the others and included into the price.
- The eco tax classification into accounting / configuration / eco tax classification
- The eco tax classification set into the product into the accounting tab
However, i suggest to remove modules account_ecotax_tax & account_ecotax_sale_tax to keep the untaxed amount not deduced of the ecotax amount :
If not, the tax amount is not so clear to understand.
=> with model account_ecotax_tax & account_ecotax_sale_tax OCA :
=> without model account_ecotax_tax & account_ecotax_sale_tax : ( i unistalled the modules to display like below)
I suggest also to add ecotax amount into the invoice template into line an total level :
721647d
to
0c6d651
Compare
@Abraao-Levasseur With account_ecotax_tax, it is different, since ecotax is considered as a tax, you should create a dedicated tax group named "ecotax" or something and it will be displayed along with the vat |
This PR aims to replace this one : #428 as explained here : #453
Going from the module here : #428
to
account_ecotax_tax
of this PR does not require migration script, just the installation of the newaccount_ecotax_tax
module should be enough.