Community mailing list archives

Re: Accounting Roadmap V9

Onestein, Samer Nefawa
- 10/10/2014 07:39:02
Hallo all,

My approach will be based on the market needs. This means stick to the basic functionalities and make them perfect. Later (as Fabien mentioned) improve other things, eg budget etc. Client will be happy to use reconcile functionality (which doesn't work well) than using  budget functionality in a system that doest reconcile well, this was an example.


Samer Nefawa
General Manager

Onestein B.V.
Tel: +31 (0) 88 6270400
GSM: +31 (0) 6 39 12 32 55

<img src="" name="Afbeelding1" align="left" border="0" height="60" width="468">

De informatie verzonden in dit e-mail bericht is uitsluitend bestemd voor de geadresseerde. Gebruik van deze informatie door anderen dan de geadresseerde is verboden. Indien u dit bericht ten onrechte ontvangt, wordt u verzocht de inhoud niet te gebruiken maar de afzender direct te informeren door het bericht te retourneren en het daarna te verwijderen. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking van de in de e-mail ontvangen informatie aan derden is niet toegestaan. ONESTEiN BV en de afzender staan niet in voor de juiste overbrenging van een verzonden e-mail, noch voor de tijdige ontvangst daarvan.

The information contained in this email message is intended solely for the addressee. Use of this information by anyone other than the intended recipient is prohibited. If you receive this message, you are requested not to use the content but by returning the message and delete it. Then the sender immediately Disclosure, copying, distribution and / or distribution of the information received in the mail to third parties is not allowed. ONESTEiN BV and the sender are not liable for the proper and complete transmission of e-mail, nor for any delay in its receipt.


Fabien Pinckaers schreef op 9-10-2014 om 23:07:
<blockquote cite="" type="cite">

You may have misunderstood the "remove hierarchy" technical spec.
I completed the "Reporting" section to make it more clear on our goal
to improve the 'structured' CoA.


On Thu, Oct 9, 2014 at 10:35 PM, Fabien Pinckaers <> wrote:
> Hello,
> A few notes:
>   - the accounting spec is in draft. A lot of things will probably
> change after the meeting of next week.
>   - we did it quite quickly so it's not complete enough: a lot will
> evolve over the next weeks
>   - My feeling is that it's only 20% of the spec. (especially, all the
> usability stuff have not been analysed yet. More will come later.)
> I changed the access rights on the document so that anyone can add
> comments and/or ideas:
> Please only add constructive comments to keep the document readable:
>   - try to argue with links or examples
>   - avoid subjective arguments (no +1, ...)
> Thanks,
> On Thu, Oct 9, 2014 at 8:16 PM, Ben Olsen <> wrote:
>> I must agree with Lek. Many of the new and redesigned features sound great,
>> but losing account hierarchy would cause serious issues. In our company we
>> must maintain a very complicated and detailed Chard of Accounts, because we
>> face scrutiny from government auditors. We need the account hierarchy to
>> keep everything organized, and trying to throw our 500+ accounts into one
>> giant list would be a disaster. Additionally, we rely on the View types to
>> sum up all totals from child accounts, giving us quick overviews of
>> different sub-sections of the Chart of Accounts.
>> I looked over and can see why Odoo would want to aim for that kind
>> of user-friendly interface. However, in terms of functionality, Odoo needs
>> to remain a full-featured ERP and allow for much more complicated settings,
>> especially with Accounting.
>> Perhaps v9 could offer a simplified accounting system for small businesses,
>> but allow the more complicated features, like account hierarchies, to be
>> enabled if desired?
>> Thanks,
>> Ben Olsen
>> On Thu, Oct 9, 2014 at 11:18 AM, Wipawii <> wrote:
>>> Greeting from Thailand,
>>> Agree with Lionel. Budget is important for an organisation. It is to
>>> control how your business should go. It is a plan of finance.
>>> +1 for Reconciliation, reduce complication of Tax setting, very good for
>>> restart sequence for new FY, tax is workable on Expense, More flexible on
>>> Reporting with pdf and excel are optional and last one menu items is NICE!
>>> However, removing account hierarchy  is incomprehensible. Account
>>> hierarchy is sort of like basic of accounting in part of presentation for
>>> management assertion, unless Odoo will have other friendly feature to
>>> support CFO to create their own financial report template freely. Hopefully,
>>> new account type and reporting in this roadmap will help.
>>> Cheers,
>>> Lek
>>> Sent from my Android
>>> On Oct 9, 2014 9:58 PM, "Lionel Sausin" <> wrote:
>>>> I find the beginning of the document very worrying :
>>>> "(...) Not a priority:
>>>> Budget
>>>> Analytic"
>>>> I'm worried because our company is into manufacturing, and our accounting
>>>> is so simple that we didn't even bother making it in Odoo - EBP compta does
>>>> the job for ~200€.
>>>> BUT analytics and budgets are major features for us, the only ones we'll
>>>> really use in Odoo's accounting.
>>>> So please, by all means do improve whatever you want on accounting, but
>>>> do NOT remove any more existing features.
>>>> Lionel Sausin
>>>> Le 09/10/2014 15:51, Graeme Gellatly a écrit :
>>> cite="" >>>> type="cite"> >>>> >>>> Omg. You are taking your model from a 1-10 user accounting system with no >>>> concept of stock, no concept of anglosaxon, not even a concept of a sales >>>> order really and literally quoting their CEO verbatim while inserting >>>> screenshots of their product. >>>> >>>> Dont get me wrong, i like xero, i use xero, i have written integrations >>>> between xero and openerp, in fact i own shares in xero, but this is either >>>> crazy or odoo is abandoning anybody subject to anything but a small business >>>> reporting standard. >>>> >>>> I feel sorry for partners. I think you just got screwed but at least the >>>> direction is clear early. >>>> >>>> >>>> _______________________________________________ >>>> Mailing-List: >>>> Post to: >>>> Unsubscribe: >>> >>> _______________________________________________ >>> Mailing-List: >>> Post to: >>> Unsubscribe: >> >> >> _______________________________________________ >> Mailing-List: >> Post to: >> Unsubscribe:

Post to: