Community mailing list archives

Re: Accounting Roadmap V9

FACTOR LIBRE SL, Carlos Liébana Anero
- 10/10/2014 06:13:14

Following Ana's comments, I see in the document "Phase 2: Localisation of key countries - 3 months" and a lot of questions came to my mind: 
- Can you elaborate what "key countries" are included? 
- Do we suppose that there will be only a team for the whole work or one team for each country? 
- How is the community of each country involved? Who is going to be in charge of future evolutions an changes?
- What's the specific scope of the localisation for each country?

With all the changes planned, I bet one of my kidneys that even a dedicated team for Spain's localization having in mind to reach the current features would't get nothing in that time.

Best regards.

2014-10-10 11:49 GMT+02:00 Ana Juaristi <>:
Fabien... sorry but I disagree. As much simple you do is better. We agree on that, but... as much simple you do, more custom modules we need to feet our customers needs and that's not good at all.
I think a kind of balance should be found between simplicity, usability and functionality. Otherwise it will not work. 

I'm totally worried about erasing accounts hierarchy and also about the movement with taxes on journal.items because we need it just like it is know. I don't think it's complicated, just it feets our legal requirements  ... my concern is.. why to change or erase if it works? Another concern is... how much work it would supose for us in R&D trying to adapt again our localization to V9 trying to include missing functionality that was available on previous versions?   (I don't understand. will we never have an stable Odoo version be whatever it will be?)  

IMHO Odoo should not erase a functionality just because it's too complex as it has been done in past but just make it simplier and more usable, technically more eficent if needed but it's needed to improve, not to erase 
Erasing parent_id on accounts, will cause collateral efects for sure and it will supose hundreds of hours trying to fix problems that were solved on previous aproach. Just filling fear due to experiences coming from other big movements like this one.  :(

If we could help ... please, just let us know. 

Thank you:

2014-10-10 0:46 GMT+02:00 Fabien Pinckaers <>:


Please read my mails and the doc carefully. We are not killing any features; just defining priorities. The CoA does not disappear, not even a hierarchical way to display it.

It's important to read the doc carefully. Otherwise we may waste time discussing on everyone's fears.

My apologies if the doc is not clear. We ran out of time, so we focused on describing the technical solution, not the "why". --> it was initially an internal document to launch developments quickly.

It's also largely incomplete. We will complete it during our workshop of next week.



On Oct 10, 2014 1:12 AM, "Pawel Kostrzewa" <> wrote:


My 2 cents. Please don't kill Odoo accounting. We devleop cash flow forecast management now, its complicated, and you will kill ERP accounting features? Increase functionalities and maybe split features - micro companies accounting and full erp features, then you have two products - for "small business" like xero and full featured ERP system.
Luck of payment order? Thats creazy! COA? Its a must in SME. I disagree. Sorry thats for small business. There are many apps for small business, localized to local fiscal requirements. I mean people from camp2camp, elico disagree and others from OCA too 

2014-10-09 22:52 GMT+02:00 <>:

Odoo need to decide if they are building a simple small business accounting package (which is what Xero is) or an ERP accounting package foe small-medium sized businesses with complex requirements.

If it is the former, then why would someone choose Odoo when they can just have Xero?

Issues that worry me:

1. Loss of the COA hierarchy. We keep the heirarchy but have also built a tree view for GL transactions with all the grouping/filtering that users required - that way we have the best of both worlds.
2. Payment orders - in any business of any size, payment of supplier invoices is NOT done by opening an invoice and marking for payment.  
3. Banking flow - hourly integration is not required. In practice, the accounts person comes in in the morning, downloads the bank statement and processes. What is important is that the bank statement process is efficient, so
   - integration with payment orders created for payments
   - auto-population of GL coding for such things as direct debits/automatic payments
   - ability to allocate customer receipts to outstanding transactions.
   - write-off of small differences
   - full multi-currency

We have already extended the standard functionality to meet business requirements and it is looking like if this goes ahead as is we will just run our own accounting system and not use standard functionality.

Kevin McMenamin
ERP Capability Manager

Mobile  +64 22 651 3753
Phone  +64 9 977 5805

Solnet Solutions Limited
Level 7, Brookfields House
19 Victoria Street, Auckland 1010
PO Box 6619, Auckland 1141

From:        Graeme Gellatly <>
To:        "Community" <>,
Date:        10/10/2014 08:14 a.m.
Subject:        Re: Accounting Roadmap V9


I am sure once they realize that analytics are a major popular feature of xero even at the microsmb level it will get changed. I guess they aren't that far through the manual yet because it makes no sense to say only xero features are priority, then 2 lines earlier say, major popular feature is not.

Best xero accounting feature is $49/month unlimited users.

On 10/10/2014 4:06 AM, "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 :
<blockquote 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.

Post to:

Post to:

Attention: This email may contain information intended for the sole use of the original recipient. Please respect this when sharing or disclosing this email's contents with any third party. If you believe you have received this email in error, please delete it and notify the sender or as soon as possible. The content of this email does not necessarily reflect the views of Solnet Solutions Ltd.

Post to:

Post to:

Post to:

CEO Avanzosc, S.L : Office phone / Tfono oficina: (+34) 943 02 69 02
Ana Juaristi Olalde : Personal phone: 677 93 42 59. User/usuario skype: Avanzosc

El contenido de esta comunicación y de toda su documentación anexa es confidencial y se dirige exclusivamente a su destinatario. El uso no autorizado de esta información está prohibido por la legislación vigente. Si usted no es el destinatario le rogamos nos lo indique, no comunique su contenido a terceros y proceda a su destrucción. Disculpe las molestias que le haya ocasionado la recepción indebida de este e-mail. Sus datos figuran en un fichero cuyo titular es Avanzosc, S.L., a quien usted puede dirigirse para ejercer sus derechos de acceso, rectificación, cancelación y oposición en Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), Tef. 943 02 69 02 -

Komunikazio honen edukia eta dokumentazio erantsia konfidentziala da eta hartzaileak bakarrik jaso beharko luke. Indarrean dagoen legeriak debekatu egiten du bertan eskainitako informazioa baimenik gabe erabiltzea. Komunikazioa zuri iritsi bazaizu, baina zu ez bazara hartzailea, mesedez, guri jakinarazi, eta jasotako informazioa ez inori jakinarazi eta suntsitu. Barkatu okerreko email hau jasotzeak eragindako eragozpenak. Zure datuak Avanzosc, S.L. enpresaren fitxategietan sartuta daude. Zure datuak atzitzea eska dezakezu, bai eta, datuak zuzentzea, ezereztea eta tratamenduari aurka egitea ere. Horretarako, enpresara jo dezakezu, helbide honetan: Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), telefonoa: 943 02 69 02 -

This message and all documents attached to it are confidential and intended only for the person or entity to which it is addressed. Any use of this information by unauthorised persons is prohibited under current legislation. If you received this message by error, please advise us, destroy it and refrain from communicating its contents to third parties. We apologise for any inconvenience receiving this email improperly may cause to you. Your personal data are included in a file owned by Avanzosc, S.L. If you want to exercise your rights of access, correction, erasure and objection you can contact the Controller at Julio Urkijo, 32, 20720, Azkoitia (Gipuzkoa), T: 943 02 69 02 –

Post to:


Director |
+34 635 86 67 92