openerp-expert-accounting team mailing list archive
-
openerp-expert-accounting team
-
Mailing list archive
-
Message #00020
Re: Trouble with accuracy and currency handling in the invoice process
I do not agree we have 2 possibilities. We have 3 actually. :-)
With respect to the named possibilities, I still believe these are
solving a erroneous visible behavior, not the bug itself.
Like all rounding issues in Open ERP, the problem is that rounding is
done to early and to often (read in every stage of storing into the
database) and using different styles/types of rounding in the whole
application. Result is rounding on a previous rounding, on a
pre-previous rounding, on a .......... where the error is cumulating itself.
When all data is stored in the database without rounding and only, only
then rounding is done in, always in the same manner, at the end of a
workflow e.g. the final invoice, no problem would occur.
Still you can display on the fly rounded values on screen and reports
abstracted from the non-rounded values in database.
So in my opinion the only best solution would be to tackle the
rounding-issue in general by storing non-rounded values in the database
before reaching the end of a workflow.
But i also see this would be a enormous rewrite to do. OpenERP should
have 2 rounding functions defined, one for specific financials and one
for general purpose like logistic and production. Only those 2 rounding
functions should be used everywhere in the application.
In the mean time option 1 in Luc's email is my preferred solution. One
would need a write-off also when the rounding problem is solved, due to
the currency rate changes that will occur.
------------------------------------------------------------------------
Met vriendelijke groet,
*Veritos - Open Source Business Solutions
Jan Verlaan CPIM*
Follow ups
References