Follow-up Comment #3, task #13888 (project health):
Thanks for the feedback !
For me, that does is not optimal in terms of scalability. I see now that
Tryton has the similar code in Purchase and Sales. So, for every document
involving invoices (including health services model) we would have to enter
all those attributes and methods related to tax rules computation. That does
not scale well.
I propose that the tax rules should be calculated at invoice validation, in a
similar fashion as the computation of Tax lines total.
So, at the invoice model, we have the party (and its tax rules), we have the
product (and its associated taxes). So it should be feasible to compute the
tax substitution rules, and will make the code much leaner and scalable.
Is it possible ?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?13888>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
