regression: wrong logic in numbering invoices

[Normunds (Alistek)]

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.).

[Dhruti Shastri(OpenERP) (dhs-openerp)]

Hello Normunds,

I have checked your issue but we are not considering this as generic way, because this is not generalize issue.

We need to more discussion on this before implementing it.

So currently I am setting this as an Opinion.

@Experts :

Would you please share your views on this.

Thanks and more suggestion are welcomed.

[Normunds (Alistek) (3pm)]

Hello!

Put it as you like.
My only question: where I can read the discussion after everything was messed up in ver. 6.x?

THERE WERE NO ISSUES in ver. 5. neither ver. 4 regarding invoices numbering. But someone changed it without even considering consequences.

What's now? We need discussion to put things back as it should be.
Sorry, but that is not a way to go.
There should be at least discussion, BEFORE changing some substantial workflows or part not AFTER.

Normunds

[Ken Woychesko (bx09m7-ken)]

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

[marcomarkiori (marcomarkiori)]

Invoices are issued by suppliers, so the sequetial number assigned to the supplier invoice has the same archiviation purposes (protocol number) but a different meaning from the sequential number assigned to the customer invoice when issued.
This is a bug: two different fields are required.

[qdp (OpenERP) (qdp)]

Hi there,

that bug was finally fixed in revision 7835 of trunk addons.
Thanks