Comment 10 for bug 868839

Amit,

With all due respect, I couldn't disagree more with your assessment that this is not a "blocking point".

If I change Account Precision to accommodate a higher precision tax rate then my transaction amounts don't calculate correctly due to accumulated rounding differences (as in sub-point 1 under comment #5 above).

If I leave the Account Precision alone then tax amounts are not calculated correctly (as in sub-point 2 under comment #5 above).

Account Precision and Tax Rate Precision are two separate things. It makes no sense for them to share the same precision setting. The only way to calculate correct tax amounts and correct transaction amounts is to have two different precision settings (as in sub-point 3 under comment #5 above). Without the modification I made to the code (in the original summary to this bug), OpenERP would be completely UNUSABLE in places such as California where high precision tax rates are common and lower precision transaction amounts are necessary.

That's my two cents at least.