Community mailing list archives

community@mail.odoo.com

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

by
Janeesh
- 01/27/2016 02:03:53
Dear Fabien,

From your answers it seems in community version you are never going to include the parent-child relation as in previous versions. 

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

I am also talking in accountants points of view. I have worked with many customers using openerp/odoo as business softwares. I know very well how accountants expect accounting reports.


- 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 
In addition to that, the parent hierarchy implied a lot of problems / difficulties for accountants: 

For all the customers i have worked with, the initial importing of chart of account will be by the odoo experts not by the accountants. For addition of new accounts only, accountants needs to create new accounts. Even if they selected wrong parents, we were able to identify easily from CoA hierarchy view. "View" account was never a strange tricks for accountants. Only the name "View" is from odoo, accountants using the terminology "Control Account".

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: http://bit.ly/1K9eUhI
- Wikipedia: https://en.wikipedia.org/wiki/Trial_balance

​From google I can also get this docs. But this is not the real case happening with customers. For every customers we are making customized accounting reports as per their requirements. In all that reports the hierarchy had a significant​
 
​meaning. 

Anyway I am not making any more arguments as I understood that it is not going to be changed. So we have already planned to customize to make that 
hierarchy
​ structure..​


Regards
Janeesh

On Wed, Jan 27, 2016 at 2:17 AM, Fabien Pinckaers <fp@odoo.com> wrote:
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: http://bit.ly/1K9eUhI

​​
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: https://www.odoo.com/editions

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.

-- 
Fabien

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe