openerp-expert-accounting team mailing list archive

[Raphael Valyi <rvalyi@xxxxxxxxx>]

Hello,

I fully agree with what Eric said. I recently had a conversation with Joel
from CampToCamp about this and he told me CampToCamp tried to get this
changed the same way Eric said too (but ended patching their customer to
get the job done). May be CampToCamp can confirm here.
We have a customer with this issue (hopefully he will soon purchase an OPW
and we will throw yet an other OPW on that bug).

IMHO, it's quite likely to encounter this kind of issue. If for example you
deal with employees expenses and buy some gas for a travel, it's very
likely that gas unit price will need more than 2 digit precision to match
the invoice you get from the gas station when buying many units. And of
course, accounting will still have to be only 2 digits (BTW, it seems that
in some countries accounting precision could be different than 2 digits,
but it's unrelated to price unit and very rare).
Sorry, but I find it incredible when OpenERP SA tells partners about
selling OpenERP "out of the box", when such issues are running unfix and
even unacknowledged for years and years.

So +1 for Eric's comment from Akretion's point of view.


On Wed, Jul 4, 2012 at 9:59 AM, Eric Caudal <eric.caudal@xxxxxxxxxxxxxx>wrote:

>  As far as I have experienced due to business constraints, you can have
> different precisions for sales prices, purchases prices and accounting.
>
> I have a customer who is selling small pieces at for example 0,123 RMB
> each (in RMB) and buy it at 0,1234 (in euro). You dont want your accounting
> to be impacted because usually these are total numbers (you keep it at 2
> digits).
>
> The factor between euro and RMB is small (x10) but some other currency
> have larger proportion (I am thinking for example in Vietnam dong)
>
> It will depend a lot on business conditions, which is very difficult to
> foresee. This is why I tend to advocate for a common sales price precision
> for SO and CI, a common purchase price precision for PO and SI and a
> separate accounting precision.
>
> To be noted that this is not what this module is doing: it creates only a
> accounting line precision: to achieve sales price precision different to
> purchase price precision, we should create in the invoice line 2 different
> prices (one for sales and one for purchase) and change all internal
> calculations. For simplicity (and because I didnot need it) I kept it as a
> separate precision.
>
>
>   [image: openerp]
>
> *Eric CAUDAL*, Elico Corp, Shanghai.eric.caudal@xxxxxxxxxxxxxx
> Cell: + 86 186 2136 1670. Skype: elico.corp*Premium Certified Training Partner - OpenERP Ready Partner.*
>
>
> [image: Premium CTP]
> http://www.openerp.net.cn
> On 07/04/2012 08:35 PM, Numérigraphe wrote:
>
> Thanks for you input Eric.
> I agree that the precision must be the same in invoices and orders.
> If I understand, you propose to "push" the order's precision to the invoices and accounting entries.
> Isn't it simpler to just set the order lines' precision to that of the accounting?
> Lionel.
>
> ** Summary changed:
>
> - Wrong precision for tax  in sale/purchase order lines
> + Wrong precision for subtotals  in sale/purchase order lines
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-accounting
> Post to     : openerp-expert-accounting@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-expert-accounting
> More help   : https://help.launchpad.net/ListHelp
>
>