Here's the problem with journals. Yes, journals are used to keep transactions in chronological order. However, each transaction represented in the fiscal year periods already belongs to a journal. And if you are proposing that we create the situation where we have lots of transactions and each one belonging to multiple journals, I see lots of chances for chaos.
The problem is mainly one of setting opening balances to the fiscal year and setting closing adjustments to the fiscal year. You cannot make those adjustments within any of the fiscal periods within the fiscal year without corrupting the monthly or quarterly numbers. This is why every other accounting system uses special periods (not journals) for performing these accounting adjustments. And even with the solution I proposed you can really have N adjusting periods if you want. It's just an attribute on a period. The other part of the problem is how to handle the move_ids such that data can be purged, fiscal periods can be closed and yet unpaid invoices can always be carried forward and paid in the current period. This is also dealt with in the solution proposed in the blueprint that I submitted. Regards, Gerry -------------------- m2f -------------------- -- http://www.openerp.com/forum/viewtopic.php?p=28564#28564 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
