Community mailing list archives
Re: Accounting Roadmap V9by
Chart of Accounts will created once in a company and this will be done after proper consultation not like other masters like partner or product.
CoA normally finalized by finance manager or auditor. So parent can be optional and no need to make mandatory because by mistake it will not skip if company really required moreover any time parent can be changed. So there is enough space for corrections.
+ 971 55 66 77 001
Sent from Note III
On 2014-10-10 20:17, Fakrudeen Abbaz wrote:<blockquote cite="mid:email@example.com" type="cite">
parent accounts must be either optional or mandatory - except root account for a compayn.
if a company decides to use parent account structure it must be complete, you can not leave this to users / managers, they will forget if not enforced.
Agree with Fabien
Parents (view) are optional for accounts.
PL and BS are normally preparing year end some companies monthly.
But Accountants & Auditors need Trial Balance with drilling facility.
For this purpose CoA tree view can be used with some modification, drill down to root level can be achieved.
Please see the sample chart of accounts hierarchy
Thanks & Regards
Fakrudeen Abbaz (ACMA)
Management & ERP Consultant
Mob. : 00971 55 66 77 001
India : 0091 9 44 777 0001
<img border=0 width=166 height=98 id="Picture_x0020_4" src="cid:image002.png@01CFE4D7.6E5A0A90" alt=800377.png>
From: Fabien Pinckaers [mailto:firstname.lastname@example.org]
Sent: Friday, October 10, 2014 8:54 PM
Subject: Re: Accounting Roadmap V9
> I think in accounting (pure accouting) a partent account IS a parent> account that's it.
In pure accounting, accountants used to work in views like this:
Not in tree views of the CoA.
IMHO the default way to check your financial status should be throughthe P&L or BS, not the CoA. Currently in Odoo, everyone uses the CoAbecause it's the only way to have balances on the screen. But this isnot the habit of "non odoo" accountants.
> In some countries you have even a close relation between the code and> the parent child relation, you actual datamodel achieve such need> __perfect__.>> Why do you need remove it from the account itself and move to reports?>> If you are so sure of this is the correct path... without develop it> yet, can you explain how will be the new approach?>> As I understand from SQL pov you will change:
No, we can use the Type field on accounts to create hierarchies ordefine reports.
> Please dont try to convince us that the "usability " needs change the> data model, with actual data model you can achieve perfect views and> improve a lot the usabilitiy.
Usability is about what the accountant expect to see. An accountantusually work in P&L or BS or other reports. Not in a tree view of accounts.
> Today: 1 method compute all the balance in the CoA.> Tomorrow?.
Today: the balance grouped according to parents:- Class 1, Class 2, Account 12___, 13___, ...
Tomorrow, the balance grouped according to accountant expectations:- Income,- Expenses,- Gross Profit,- Net Profit, ...
Note that I am note against hierarchies. It's ok for me to keep a parentrelationship
I just think that accountant will work in the P&L or the BS instead ofthe Chart of Accounts. So, the CoA is not useful anymore (and we stillhave the Type field for the general ledger)
The default way to check your income and navigate through accountsshould be through the P&L, not the CoA.
It's ok for me to keep hierarchies but I am against having *mandatory*hierarchies. I find these constraints not good:- having a root node to define a chart of account (not logic foreveryone)- using hierarchies to structure reports (should be defined by typefield)- I have seen so much time an accountant on Odoo creating an account atthe root level because they did not understood the Parent/Childrenconcept. (which is an Odoo concept, not an accounting one) It has towork even without hierarchies.
--Fabien PinckaersOdoo Founder
Phone: +188.8.131.52.00Web: https://www.odoo.comTwitter: @fpodoo
Instant Demo: https://odoo.com/start