Pricelists should be used in invoices even without sale orders

[TeMPO]

OpenERP 5.0 (all releases)

When manually defining a stock move "to be invoiced" we can specify the partner but not the price list so that
the invoice takes in account the product price and not the price defined in a price list

There is no problem when the stock move is generated from a sale.

Maurice

There is also a generic need for beeing able to record invoices using pricelists when no sale order is involved (please see duplicate bugs).
Identified workflows include:
- standalone invoice
- invoice from packings
- invoice from membership
Lionel

[Numérigraphe (numerigraphe)]

This of course is the normal behavior for 5.0 and should not be changed.
We wish it could be improved in the next stable.

TeMPO, I'm redirecting several duplicate or very similar reports to this, I hope you don't mind.

Lionel

[Christophe Hanon (www.adins.be) (chanon)]

I don't see how this can be 'normal'. Pricelist assigned to a customer should be applied to the customer. This is a functional bug.

As indicated in Bug #531905 this apply to direct invoice and also to membership module. Price condition granted to a customer should be applied in all circumstance in the same way.

[Numérigraphe (numerigraphe)]

Dear accounting experts, can you give your opinion on this issue please?
Are there other workflows that create invoices and should consider pricelists?

[Numérigraphe (numerigraphe)]

Sorry Christophe Hanon, by "normal" I meant this is the expected behavior and a known limitation of v5.0. There's nothing we can/should do about it in the current stable. It can be done on the trunk.
Lionel

[TeMPO (info-tempo-consulting)]

Dear all,

I fully agree with Christophe, pricelist assigned to a partner should
be taken anyway no matter if there is a sale order or not.

When you say "normal" I think you mean "in accordance of the code" but
for me this is clearly a lack of functionnality

> I don't see how this can be 'normal'. Pricelist assigned to a customer
> should be applied to the customer. This is a functional bug.
>
> As indicated in Bug #531905 this apply to direct invoice and also to
> membership module. Price condition granted to a customer should be
> applied in all circumstance in the same way.
>
>

--
Très cordialement

Maurice MORETTI

_________________________________________________________________________
TeMPO CONSULTING Valparc 9, rue du Parc 67205 Oberhausbergen FRANCE

Web : http://www.tempo-consulting.fr
email : <email address hidden>

Tel : [phone]
Fax : [phone]
Mobile : [phone]

[Grzegorz Grzelak (OpenGLOBE.pl) (grzegorz-og.pl)]

I think every user (and me) would expect that pricelist will be applied
directly into invoice.
GG.

----- Original Message -----
From: "Numérigraphe" <email address hidden>
To: <email address hidden>
Sent: Thursday, April 08, 2010 9:23 AM
Subject: [Openerp-expert-accounting] [Bug 387374] Re: Pricelists should
beused in invoices even without sale orders

> Dear accounting experts, can you give your opinion on this issue please?
> Are there other workflows that create invoices and should consider
> pricelists?
>
> ** Description changed:
>
> OpenERP 5.0 (all releases)
>
> When manually defining a stock move "to be invoiced" we can specify the
> partner but not the price list so that
> the invoice takes in account the product price and not the price defined
> in a price list
>
> There is no problem when the stock move is generated from a sale.
>
> Maurice
>
> There is also a generic need for beeing able to record invoices using
> pricelists when no sale order is involved (please see duplicate bugs).
> + Identified workflows include:
> + - standalone invoice
> + - invoice from packings
> + - invoice from membership
> Lionel
>
> --
> Pricelists should be used in invoices even without sale orders
> https://bugs.launchpad.net/bugs/387374
> 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: Confirmed
> Status in OpenObject Addons trunk series: Confirmed
>
> Bug description:
> OpenERP 5.0 (all releases)
>
> When manually defining a stock move "to be invoiced" we can specify the
> partner but not the price list so that
> the invoice takes in account the product price and not the price defined
> in a price list
>
> There is no problem when the stock move is generated from a sale.
>
> Maurice
>
> There is also a generic need for beeing able to record invoices using
> pricelists when no sale order is involved (please see duplicate bugs).
> Identified workflows include:
> - standalone invoice
> - invoice from packings
> - invoice from membership
> Lionel
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-accounting
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~openerp-expert-accounting
> More help : https://help.launchpad.net/ListHelp

[Ferdinand (office-chricar)]

+1 pricelist assigned to a partner should be taken anyway no matter if there is a sale order or not.

we have to consider less experienced users - how should they now what is "normal" in OpenERP - incontrary to what is "normal" in business life.

[Albert Cervera i Areny - http://www.NaN-tic.com (albert-nan)]

+1.

We may create a module for 5.0 and I think it should be solved in core for 6.0.

[Ana Juaristi Olalde (ajuaristio)]

+1.
I agree with ferdinand and Albert.

2010/4/8 Jay (Open ERP) <email address hidden>

> ** Changed in: openobject-addons/trunk
> Milestone: None => 6.0
>
> ** Changed in: openobject-addons/trunk
> Assignee: (unassigned) => Harry (Open ERP) (hmo-tinyerp)
>
> --
> Pricelists should be used in invoices even without sale orders
> https://bugs.launchpad.net/bugs/387374
> You received this bug notification because you are subscribed to
> OpenObject Addons.
>
> Status in OpenObject Addons Modules: Confirmed
> Status in OpenObject Addons trunk series: Confirmed
>
> Bug description:
> OpenERP 5.0 (all releases)
>
> When manually defining a stock move "to be invoiced" we can specify the
> partner but not the price list so that
> the invoice takes in account the product price and not the price defined
> in a price list
>
> There is no problem when the stock move is generated from a sale.
>
> Maurice
>
> There is also a generic need for beeing able to record invoices using
> pricelists when no sale order is involved (please see duplicate bugs).
> Identified workflows include:
> - standalone invoice
> - invoice from packings
> - invoice from membership
> Lionel
>
>
>
>
>

--
Ana Juaristi Olalde
Consultor Freelance OpenERP
www.anajuaristi.com
www.openerpsite.com
www.avanzosc.com
677 93 42 59 - 943 85 06 25

[Borja López Soilán (NeoPolus) (borjals)]

Grzegorz Grzelak (Cirrus.pl) wrote:
> I think every user (and me) would expect that pricelist will be applied
> directly into invoice.
> GG.
>
+1

Other ERPs I have tested used the same pricelist/discount rules for the
invoices as for the sale orders.

--
Borja López Soilán
<email address hidden>

Pexego Sistemas Informáticos S.L.
Avenida de Magoi 66 - 27002 Lugo (España)
Tel./Fax [phone]
http://www.pexego.es

[Borja López Soilán (NeoPolus) (borjals)]

+1

On other ERPs I've tested, they used the same discount/pricing rules for the invoices as for the sale orders. So if your partner has a 20% discount, and you create an invoice directly (for example a pro-forma invoice), the prices on the invoice get that 20% discount.

After all, that's what the users would do if didn't have software but created their invoices 'by hand'.

[Eduardo Ruiz (readylan)]

+1

I think pricelist must be in invoices too. Its behaviour could be the same as in sale orders: on new records automatically proposes the value predefined in res_partner, allowing you to change it.

[jugglefish (pniederlag)]

This is really unexpected and also happens when using the "create invoice from timesheet data", the pricelist/version for the customer does not get applied. Anyone already working on a patch?

[jugglefish (pniederlag)]

sry, that's not true "create invoice from timesheet data" works as expected, you only have to keep in mind that you need to attach the pricelist on the corresponding analytic account! Then it mostly works as expected.
Still it is very true that when creating an invoice or invoice-line manually the pricelist of the customer should be applied.

[Wyden Silvan (brain-tec) (brain-tec)]

+1

I think pricelist must be in invoices too.

[Nhomar - Vauxoo (nhomar)]

+1

It should be a module as Albert offer make it, and It must be part of the core for version 6.0

IOH, I think the module purchase_discount _must_ be part of the core too, the manipulation of prices on invoice must be so flexible in Invoices directly from sales.

We are improving the module purchase_discount with some functions extra, I will report the bugs generated in the correct place. but is closly related with this one.

[Raphaël Valyi - http://www.akretion.com (rvalyi)]

+1 also for this behavior, I think it's what is expected.

Also notice that, at least in v6 that has cleanest dependencies, the sale
module depends on stock which depends on account.
But of course account doesn't depend on sale.
That mean that sale pricelist code should somewhat move to the account
module instead and both account and sale should use the same factored
pricelist functions.

As a general consideration, I think that OpenERP lacks of such abstractions
that would allow business objects to share methods implementations or
ainterfaces even if they don't inherit one form an other. Yes there are
workarounds to reuse the code, but something cleaner here would have been
welcome (such as Java interface + the required design pattern plumbing, or
say Ruby mixins and I'm pretty sure there would be Python abstractions too,
specially since Python supports multiple inheritance).

Raphaël Valyi
*http://www.akretion.com* <http://www.akretion.com>
[image: logo_only_17 (another copy).png]

On Thu, Jun 17, 2010 at 9:49 PM, Nhomar Hernández -
http://openerp.netquatro.com <email address hidden> wrote:

> +1
>
> It should be a module as Albert offer make it, and It must be part of
> the core for version 6.0
>
> IOH, I think the module purchase_discount _must_ be part of the core
> too, the manipulation of prices on invoice must be so flexible in
> Invoices directly from sales.
>
> We are improving the module purchase_discount with some functions extra,
> I will report the bugs generated in the correct place. but is closly
> related with this one.
>
> --
> Pricelists should be used in invoices even without sale orders
> https://bugs.launchpad.net/bugs/387374
> You received this bug notification because you are subscribed to
> OpenObject Addons.
>
> Status in OpenObject Addons Modules: Confirmed
> Status in OpenObject Addons trunk series: Confirmed
>
> Bug description:
> OpenERP 5.0 (all releases)
>
> When manually defining a stock move "to be invoiced" we can specify the
> partner but not the price list so that
> the invoice takes in account the product price and not the price defined
> in a price list
>
> There is no problem when the stock move is generated from a sale.
>
> Maurice
>
> There is also a generic need for beeing able to record invoices using
> pricelists when no sale order is involved (please see duplicate bugs).
> Identified workflows include:
> - standalone invoice
> - invoice from packings
> - invoice from membership
> Lionel
>
>
>
>
>

[Fabien (Open ERP) (fp-tinyerp)]

I set as "Won't fix" because it's not planned for v6. I agree it's a good feature, and we will probably plan it for v6.1.
Thanks,

[Olivier DOSSMANN (odossmann)]

Hey, v6.1 is coming, isn't it ?
So what about this "good feature" ?

[Matthias Chardon (matthias-chardon)]

Dear all,

In order to complete testing next week and as discussed with Jean-François,
we all need to use the same chart of accounts.
The one used in the roadshow is not 100% satisfying on the balance sheet
side.

Therefore we should be using:
- The attached chart of accounts for classes 1 to 5 (B/S)
- The same expense & revenue accounts as currently used in the roadshow DB

Pls advise if you need more information (account attributes etc) to set up
this new CoA properly.

Thanks for your help!

Matthias

(See attached file: Sprint 1 - CoA for functional tests.xls)