On 2015-09-02 11:30, Jordi Esteve wrote:
> El 01/09/15 a les 17:17, Cédric Krier ha escrit:
> >Hi,
> >
> >I'm looking for a way to put expenses (purchases) into the cost of a
> >project.
> >The usual way I have seen in similar software is to use analytic account
> >but I think it is not the correct way for 2 reasons:
> >
> > - analytic accounting almost always misses the employee cost
> > (because it is too much work)
> >
> > - analytic accounting is a normally tool design to allow users to
> > create its own/custom accounting view (not for developers)
> >
> >So for now, the project_revenue module computes a theoretical revenue
> >(list price * effort) and a cost (timesheet * employee cost).
> >It is only missing the expenses to get the complete picture of the
> >profitability of a project/task. If we use the project_invoice module to
> >know the real/invoiced revenue.
> >
> >So my proposal is to add on project_revenue an extra_depends on purchase
> >which will add a many2one field on purchase line to a project (with
> >possibility to add line to project later via a one2many on it).
> >With this link we could include the invoiced amount of those purchase
> >line to the cost of the project.
> >
> >Of course some could say that sometimes a purchase line is linked to 2
> >projects. I think it is a very rare case that could be solved by
> >splitting the line in two.
> >
> >So what do you think?
>
> It sounds good.
>
> A remark: In my experience, a lot of projects like technical ones have
> travel expenses like transport, hotel, restaurant, ... They usually are
> introduced in the ERP like supplier invoices, it is not worth create
> purchases for this kind of expenses because they don't create shipments.
> Your proposal will force to introduce them like purchases. So, maybe is
> better create a relation between supplier invoice lines to projects?
I don't want to introduce such field at the invoice level for 2 reasons:
- normally it is not the accountant job to set such information
- customer and supplier invoices share the same Model, I don't want
to have this field filled for customer invoice at all (as it will
break the computation)
Also of course you can manage expenses with a purchase order (shipping
or not is not the problem) and having this project field on it will
enforce to use purchase instead of creating direct invoice which is for
me a good practice.
But indeed, it will be much better to have a specific Model for employee
expenses and once this Model exists we will have to included to
project_revenue like we do for purchase.
--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric.kr...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/
