← Back to team overview

openerp-expert-accounting team mailing list archive

Re: [Bug 919572] [NEW] Invoice line quantity must have "Product UoS" decimal precision

 

Now its seems that there are more problems than to have correct UoS/UoM. I
suggest that clever use of inheritance can be solution, f.e. create
templates for invoice and invoice line which will have 99% of functionality
and inherit them to create  new objects for extending, changing
customer/supplier invoices/invoice line objects. If we choose to put
all differences on one place it can be to complicate in the future
to understand all these complex situations, dividing to smallest parts
gives opportunity for every country to adapt accounting for its own needs.

---
Paulius Sladkevičius
2012/1/22 Eric Caudal <eric.caudal@xxxxxxxxxxxxxx>

>  I agree.
> If not, the sales quotation sent to close the deal with your customer will
> differ from your invoice. This can lead to:
> - some delays in payments: some customers have automated systems or even
> catch the slightest opportunity not to pay on time.
> - some questions: "why your software is not able to send the same?"
> - discrepancies with external softwares (in China for example there is an
> official machine to print the invoices in official paper)
>
> This problem is not only restricted to UoS but more generally to prices.
> Typically, I have a customer, they sale with 4 digits sales prices and the
> accounting decimal precision is 2 digits (used for price in invoices): we
> had to develop a specific module to add a new "account Line" decimal
> precision.
>
> http://apps.openerp.com/addon/6658?filter=%7B%22order_by%22%3A+%22click_counter+desc%22%2C+%22text_search%22%3A+%22decimal%22%7D&page=0
>
> Additionally, because sales and purchased prices are the same object with
> 2 rules, the current used system is not coherent for the same reasons:
> eg:
> - Sales prices accuracy = 3
> - Purchase price accuracy = 4
> - Account accuracy = 2
> How do create a proper sales invoice (dp=2) that matches the quotation
> (dp=3) and the supplier invoice (dp=2) with the PO (dp=4)
>
> In short, we should have a simple rule: "All calculations in invoices and
> sales quotation and PO should be identical"
>
> To solve this I dont think having duplicated the invoice_line objects are
> needed, as 99% of the information is common (only difference in my opinion
> is price).
> Nevertheless, we should separate sales prices and purchases price in the
> invoices and treat them in separate fields in account_incoice_line:
> - supplier invoice: use purchase price dp for a field purchase_price.
> - Sales invoice: use Sales price dp for a field sale_price.
>
> Additionally, we should choose a coherent and consistent calculation
> method for invoices. eg:
> - in customer and supplier invoices, sales order and PO:  use no digits
> constraint in calculation for subtotals and truncate the total after
> according to account dp.
> - consistently use UoM dp between sales quotation/PO/invoices.
> - use same rules for taxes calculations.
>
> There have been an interesting mail some time ago from Graeme Gellatly
> with deeper researches on calculation scheme that could be investigated.
>
> Collateral problem: standard cost dp should be issued as well: currently
> is used "account" dp for standard cost and this is not enough for the same
> reasons stated above (purchase price is 4 digits and accounting is 2)
>
> Best regards
>
>   [image: openerp]
>
> *Eric CAUDAL*, CEOeric.caudal@xxxxxxxxxxxxxx
> Cell: + 86 186 2136 1670. Skype: elico.corp*Elico Corp - OpenERP Ready Partner, Shanghai.*http://www.openerp.net.cn
>
>
>
> _______________________________________________
> 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
>
>

References