On Wednesday, September 2, 2015 at 1:20:06 AM UTC+10, Cédric Krier wrote: > > 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? > > Thanks, > -- > Cédric Krier - B2CK SPRL > Email/Jabber: cedric...@b2ck.com <javascript:> > Tel: +32 472 54 46 59 > Website: http://www.b2ck.com/ > Could you explain how the analytic account method is implemented? Or point to a good documentation? I will also need to investigate how Tryton manages projects and costs, but I am familiar with implementations from other accounting software where it is possible to report on specific groups of expenses as well as sale lines. 1. The one I like best is Saasu which allows the user to add and create tags on each line of a purchase or sale. As it is possible to have more than one tag, lines can be associated with more than one "project". These tags can be used in reports such as Profit and Loss to show only values from specified tags. 2. Xero has a similar concept but they call it categories rather than tags. This solution would avoid splitting the line in 2 except when the actual amounts need to be specifically linked to only one project. But there is also the scenario where expenses need to be linked to 2 different "projects" because of requirements from different government departments. It's like having more than one Chart of Accounts. This is relevant in the mining industry here in Australia where companies need to report to the mining departments based on mining licences. Instead of having deep trees where every expense account has sub accounts for each project it is better to have 2 separate chart of accounts. I have seen companies simply manage 2 copies of their accounting files: one for tax office and one for the mining department.
