openerp-india team mailing list archive
-
openerp-india team
-
Mailing list archive
-
Message #10304
[Bug 814128] Re: regression: wrong logic in numbering invoices
Hello,
I'd like to add a note that I've confirmed Normunds opinion -- this is not the proper way to handle supplier invoice numbering, from an Accounting standard, from a programming standard, or a user-expectation standard.
In my opinion, this is a Bug and not an Opinion.
Kind regards,
Ken
--
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/814128
Title:
regression: wrong logic in numbering invoices
Status in OpenERP Addons (modules):
Opinion
Bug description:
Accounting module: ver.6.0.2
There are read-only field "Number" in account.invoice object, what is only generated when invoice is validated and is equal with account.move number.
There are no problems as far as this approach is used for Customer Invoices.
For supplier invoices situation is quite different.
When we enter a supplier invoice we need to manually set an invoice number form received invoice, what is not possible to do, cause "Number" field is read-only.
It is possible to encode invoice number in "Free Reference" field, but
this lead to inconsistence and misunderstandings- as:
- "Number" field for Customer Invoice is used as it means, while for Supplier invoices this field is rather internal accounting move number than invoice number,
- "Number" field is not as it is really, as it is account/move number for both Incoming/Outgoing.
- even if we assume the right field for entering Supplier Invoice number is "Free reference", then even according to workflow this number is for other purposes, like link Invoice to purchase order. (Try to make Purchase Order and Invoice from it, the field "Free Reference" is automatically filled with Purchase Order Nr.).
To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/814128/+subscriptions