c2c-oerpscenario team mailing list archive

["Sharoon Thomas http://openlabs.co.in" <sharoonthomas@xxxxxxxxxxxx>]

Hmmm... This discussion/debate of use of float never seems to end ???

If you need more references:

Why the Tryton (http://tryton.org a fork of OpenERP) decided to use
decimals: https://lists.launchpad.net/openerp-expert-
accounting/msg00070.html

Why Fabien/OpenERP SA considers Float as the solution:
https://lists.launchpad.net/openerp-expert-accounting/msg00067.html

The solution IMHO is to use Decimals which avoids all the nonsense of
rounding (of course at the cost of performance, which could be improved
12x by use of cDecimal http://www.mail-archive.com/tryton-
dev@xxxxxxxxxxxxxxxx/msg01347.html).

Quoting one of my friends in the OpenERP community "We have uml
designer, view designer, report desinger, fancy dashboards but can't do
a single sum(debit) :)"

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/707923

Title:
  [6.0 and 5] invoice tax - rounding issue

Status in OpenERP Modules (addons):
  Won't Fix

Bug description:
  see attachment

  due to rounding of the calculated tax for each position we get totals
  which are wrong.

  In Austria we usually group the basis per tax rate and calculate the
  tax from this basis to avoid such errors.

  in account/invoice.py
  class account_invoice_tax  - 
  def compute must be modified 

  actually only some lines of code to group the invoice lines before
  calculating the tax

  probably this has been discussed (but not solved) already