On 31/05/13 07:59, Albert Cervera Areny wrote:


El dimarts 28 de maig de 2013 14:21:59 UTC+2, Cédric Krier va escriure:

> For me, including sale or purchase order (not yet invoiced) looks like a
> kind of forecast. Why not just include them within a report (SQL view)?
> Or create the invoice earlier in the purchase/sale process and have the
> invoice create draft move (like when validate a supplier invoice) on
> which you will have your "draft" analytic move.

Creating the invoice earlier is not appropriate because invoice moves should be create at the right time in accounting. We cannot say in the official accounting that we owe money to somebody when it is not true.

> > Another demand, from another company, has been the creation of
> > analytic lines when stocks are moved from certain locations and
> > explicitly without moves on accounting. In this case they treat
> > several locations (farms and animal feed factories) as independent and
> > each move from one location to another is considered as an internal
> > sale in analytic accounting at cost price. As said, in this case,
> > there's never a related accounting move.
>
> Still possible to just create a null move for that a little bit like
> account_stock_continental.

This is what I proposed to the accountant but he simply does not want to. The reason is that he does not want to mix their analytic needs with official accounting which is subject to inspection by tax authorities. This sounds like "I'm going to cheat" but it really is not the case, at least for this customer. It is more a need for a separating two things that simply do not always need to go together.


I also agree that the creation of analytic moves must be unlinked from accounting. Albert has explained two scenarios where it is necessary. Another common scenario is in companies that work with projects and timesheets but they don't want to invoice from timesheets. They want to track the cost of the timesheet lines of their employees using analytic with no relation to accounting.

And also I agree to make the required move_line field in analytic_account.line with validate() instead of an SQL constraint.

--
Jordi Esteve
Consultor Zikzakmedia SL
[email protected]
Mòbil 679 170 693

Zikzakmedia SL
Dr. Fleming, 28, baixos
08720 Vilafranca del Penedès
Tel 93 890 2108

Reply via email to