The New Tax Engine and How to Use it in Localizations - Olivier Colson, Developer, Odoo

1. The New Tax Engine
and How to Use it in Localizations
Olivier COLSON • Developper
“The past holds the key to the present”
2019
EXPERIENCE

2. Fiscality War
A functional look at v131

3. A Brand New Look

4. ● Localized layout
New Reporting

5. ● Switch to generic report dynamically
New Reporting

6. ● Generic tax report is still there
New Reporting

7. The Past
What did we forget?2

8. What if...
Let us play a little bit with v12

15. Assembling
the Taxvengers
What were the models in v12?
3

16. Models in v12

17. Gathering
the Fiscality Stones
Finding a solution in the distant past
4

18. Remember this?

19. Tax Codes
● account.tax.code
● Directly define a line of the tax report each
● Directly linked to move lines

20. Though, tax codes
were not so great

21. ● Way too many fields on taxes ; unclear
○ base_code_id
○ ref_base_code_id
○ tax_code_id
○ ref_tax_code_id
○ tax_sign
○ ref_tax_sign
Tax codes were not so great

23. ● tax_amount field
● Both credit and debit = 0 on some lines
○ For base lines, when multiple taxes need to apply
Tax codes were not so great

24. Reshaping the Future
Introducing the new models5

25. Goals
● Should we only fix this use case?
● Can we do more?

26. ● Avoid retroactive effect when modifying a tax
Goals

27. ● Improve tax form usability
Goals

28. The Big Picture
● New model: account.tax.repartition.line
● tag_ids directly on account.move.line
● Generalize account.generic.tax.report
● New model: account.tax.report.line

29. Model Interaction

30. Taxes Today
● Declare repartition lines in XML

31. Taxes Today
● Tags are signed
● Tax templates reference tax report lines through dedicated
fields, depending on the tag (+ or -) to be used

32. Taxes Today
● No more need to declare groups of taxes for complex taxes

33. Taxes Today
● No more need to declare tax groups for complex taxes

34. The New Tax Report
● Make tax report XML declaration more explicit

35. The New Tax Report
● One tag per line, no more domain
● Tags are now automatically created by report lines

36. The New Tax Report
● No more sum.balance / -sum.balance
● Signs are directly on tags

37. The New Tax Report
● No need to have the resulting move lines in mind anymore
○ Example: 1 refund + 1 invoice with base 100$

38. The New Tax Report
● No need to have the resulting move lines in mind anymore
○ Example: 1 refund + 1 invoice with base 100$

39. The New Tax Report
● No need to have the resulting move lines in mind anymore
○ Example: 1 refund + 1 invoice with base 100$

40. The New Tax Report
● No need to have the resulting move lines in mind anymore
○ Example: 1 refund + 1 invoice with base 100$
■ To do the same in v12, 3 financial report lines:
● An invisible subline with
● Another invisible subline with
● The actual line, summing both sublines with

41. The New Tax Report
● It is still possible to combine lines in a formula

42. The New Tax Report
● No additional menu items anymore
● The generic report now manages everything

43. Living
in this New World
How to use the new models the best way
6

44. Community ?
● Taxes : yes
● Tax report lines : yes
● Tags : yes
● Tax report engine : no (like before)

45. Can we still use
the old way ?
● Financial and SQL-based reports are still possible
○ With a few minor changes
● But you should always ask yourself if it should be done so ;)

46. The Old Way, The New Way
● You can still define the tags directly in XML

47. The Old Way, The New Way
● A dedicated field in tax templates allows referencing XML tags
● No question of sign here, just like in v12

48. The Old Way, The New Way
● The tags are then assigned to move lines, as usual
● Referencing them can be done from financial reports using
their tag_ids field

49. What about
migration ?

50. Endgame?
What more can we expect in the future?7

51. The Taxvengers will return.
#odooexperience
2019
EXPERIENCE
Feedback is welcome!
V13 Taxes (dev): oco@odoo.com
Accounting (functional): avw@odoo.com
Localizations (dev): jco@odoo.com
Localizations (functional): jcr@odoo.com