'account.invoice.tax' should have a many2one relation to corresponding 'account.tax'

Hello,

You can take account.tax which is a many2many relation in account invoice line, from invoice line you can access tax type and tax rate easily.

Thanks.

I disagree with this solution...picture this...

there are 2 taxes:
tax A -> base code X, tax code Y, account Z
tax B -> base code X, tax code Y, account Z
(yes, in India we need to have 2 different taxes with same base code, same tax code and same account but need to show them as different on invoices)

now on an invoice suppose following are invoice lines:
product M -> tax A
product N -> tax A
product O -> tax B
product P -> tax B
product Q -> tax A, tax B

Now the invoice tax (account.invoice.tax) lines would be:
tax A
tax B

Now if I need to print the above two taxes on invoices and i try to get the rates from invoice lines then u can understand how much overhead that involves. Rather it is much more sensible and logical to have tax lines related to 'account.tax' and each tax line to have unique identity on basis of 'account.tax' rather than on (base code, tax code, account) combination as is now.

What say?

Hello Akshay Jain,

In current situation if you want to show both the taxes will show in separate then for that you need to assign base code or tax code uniquely not same then and then only you will able to see both separately in "account.invoice.tax", Other wise you need to done some customization from your side.
If you want this in tiny then for that please create blue-prints.

thanks.

i did it myself...just had to modify a little code in account.invoice.tax class in invoice.py file in account module.

But yes i am greatly impressed with the open erp's maturity as an enterprise class software...great job guys..keep doing the great stuff!!

Working on blueprints.