In PL we understand PRO-FORMA invoice the same way. No number and no 
accounting. Then when customer pay the pro-forma invoice we have to issue 
normal invoice in (probably) 7 days.

In our local systems pro-forma invoice is usually printed from Sales order. 
So it is not related to invoice functionality at all.

But it can have some functional drawback (not formal) in such case. Even if 
we issue pro-forma invoice we expect some functionality for checking if this 
invoice is paid or not.

When I red docs I remember that it was: pro-forma - no number but WITH 
accounting move. So I didn't test it thinking that it would be wrong for PL. 
Now you are writing that it is probably good for PL.
GG.

-- 
pro-forma invoices: documentation doesn't match implementation
https://bugs.launchpad.net/bugs/551543
You received this bug notification because you are a member of OpenERP's
Accounting Experts, which is a direct subscriber.

Status in OpenObject Addons Modules: New

Bug description:
I'm not an international accountant, but it seems the term "pro-forma invoice" 
is ambiguous and can describe 2 kind of invoices, and unfortunately there is an 
ambiguity about what pro-forma invoices are supposed to be in OpenERP: with or 
without accounting moves attached.

The manual reads "A Pro Forma invoice doesn’t yet have an invoice number, but 
the accounting entries on the invoice that’s created correspond to the amounts 
that Open ERP will record as the customer’s payables": 
http://doc.openerp.com/book/3/3_7/accounting_workflow.html#open-or-pro-forma-invoices
This is one way of managing pro-forma invoices: an invoice without a number, 
with accounting entries. It seems to be a disputable practice, and it's 
forbidden here in France, but in some places people seem to understand 
"pro-forma invoices" this way however.

But in the implementation of v5.0, pro-forma invoices really are invoices 
without a number and without accounting entries. French people (among others) 
understand "pro-forma invoices" this way.

So, either the doc is wrong or the implementation is wrong - but it has to be 
settled and fixed.
Lionel.



_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-accounting
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~openerp-expert-accounting
More help   : https://help.launchpad.net/ListHelp

Reply via email to