Community mailing list archives


Re: AW: Chart of Account structure & amp; Financial year closing in Odoo 9

Ahmed Shaaban
- 01/27/2016 01:34:13

+1 wolfgang

Ahmed Elsaka

On 27 Jan 2016 08:26, "Wolfgang Taferner" <> wrote:

HI Fabien,

I am pretty sure you have valid arguments and I am sure Nhomar and Graeme have valid arguments too and in my opinion it was ok from a technical point of view, but the point is…Odoo removed the existing possibility of hierarchy in v9 w/o having a proper generic replacement concept and many people warned and asked for a solution right from the start when you presented and worked on the roadmap and you just IGNORED it.


And even your approach introduced in v10 enterprise is the most ridiculous implementation ( I would think of to have a proper and awesome concept for the framework and its localizations besides it is enterprise which is at least understandable but probably will not change the decisions of companies to subscribe from my PoV as I recommend and ask all my customers anyway to have enterprise contracts for their own advantage and future-proof approach (even without using the enterprise branch) as Odoo SA is the main publisher and has a lot of bundled man-power behind and needs to be supported.


I suggested once that the hierarchy should be moved and made available on a tag level as tags are somehow independent and not critical as objects and generically applicable itself (and could be used in reports only and will not harm performance in case a proper algorithm is developed). Of course someone could mess up, but honestly I prefer that someone is messing up than to rely on semi-generic solutions / non-solutions and most likely companies will just put their work on top of a localization which might be prepared depending on what is provided by the community.


So, I am disappointed about what you have put on the shoulders of your partners and customers and even the community concerning this topic for v9 (besides a lot of awesomeness was provided in v9) and even more when you now try to sell your quick and dirty solution as a new feature or the solution for SaaS or the new and shiny v10.


Please put all your smart heads together and rethink in which way you bring back the hierarchy concept which is fully configurable and not just a narrow implementation of this report or the other and arguments why you removed it which is simply your point of view which is not the view of all possibilities out there in this mostly beautiful world of societies and people.


Best regards,



Mag. Wolfgang Taferner
CEO, Founder, Odoo Consultant/Developer



We Trust in Open IT

Mooslackengasse 17

1190 Wien


Telefon: +43 (1) 23060 - 4095

Fax: +43 (1) 23060 - 4096



FN:  427075b (Handelsgericht Wien)



Von: Fabien Pinckaers []
Gesendet: Mittwoch, 27. Jänner 2016 00:17
An: Community <>
Betreff: Re: Chart of Account structure &amp; amp; Financial year closing in Odoo 9


1.- It was OK on community since Version 4.x

2.- You argument and remove it unilaterally for V9.0 making the highest quantity of extrange arguments about a basic accounting feature.

3.- Now you "Release" as an Enterprise feature, without a correct supported data model (which you damaged actually) removing the parent left parent right.

4.- Now IF no pay no Feature....


Ok, I will explain once again :)


We removed the account hierarchy in version 9 because, from an accounting point of view, a trial balance should be flat and have only one debit or credit per account. (and not both) Have a look at some references from wikipedia or other accounting software in Google Images if you are not convinced:

- Trial Balance Examples:


It's important for Odoo to produce reports the way an accountant expect. And a trial balance / chart of account is NOT a hierarchy.


In addition to that, the parent hierarchy implied a lot of problems / difficulties for accountants: 

- complexity to import a chart of account

- error prone at account configuration, leading to wrong legal statements

- bad usability with strange tricks, like a 'View' account that is a concept which does not exist in accounting

So, we were happy to remove it to avoid these issues and delegate the hierarchy computation to the report engine.


In terms of reporting (the only usefulness of hierarchies), reports can still be in a tree structure, as we moved the hierarchy structure at the report engine level. This is more powerful as, instead of having one hierarchy only, we can have as much as we want: P&L, Balance Sheet, Trial Balance, Cashflow Statement, ... all have their own hierarchy. All of that out-of-the-box, without configuration requirements for the accountant.


I pay all my enterprises (you know) I am not saying you closed a feature... but now , What will we do with aaaaallll the AGPL code that is based on such hierarchy?


The report engine changed in v9. For nearly all countries, it will hugely simplify localizations (probably divide code by 4). The drawback is that these l10n_* modules should be redeveloped on the new accounting structure, instead of trying to forward port old v8 reports.


should not you simply put free the feature in an extra module?.....


We rewrote the report engine in version 9 from scratch. It's a huge effort and we made all accounting reports in Odoo Enterprise. You may like it or not, but we need to put some features in Odoo Enterprise to create value for it. I think we do a good trade-off: some features go to Odoo Community, others to Odoo Enterprise. The list is here and will probably not change that much, and accounting reports are part of Odoo Enterprise:


I do not understand, Thanks for rectify (I mean it seriously), but, NO thanks for making it too late and in the incorrect version, and with the incorrect approach.


Actually, I think the trial balance hierarchy is NOT useful for accountants, and certainly not a requirement of an accounting software. Accountants used to read P&L and BS as a hierarchy, but not trial balances / chart of accounts. However, we did it to help you do the transition: even if the v8 behavior was not good, our users are already used to it.


As a project manager point of view, I think it's better to manage the change with your customer and train them on the new way of working with accounting reports (the CoA is not the main report anymore, now they have dynamic P&L, BS...) However, if you really want to stick to the v8 way of working, you can do it with the provided patch.




Post to:

Post to: