Community mailing list archives
Re: Accounting Roadmap V9by
Hello.2014-10-13 2:37 GMT-04:30 Christophe Hanon <email@example.com>:Quentin,thanks for the roadmap.I put below a few comments about the roadmap - thanks to all for commenting.Again, thanks for sharing and see you tomorrow,ChristopheChristophe Hanon - Adins
1 Analytic accounting
I have seen analytic accounting as a second priority. Anyway, I think it would be simpler to integrate multi-dimension into the base. It is quite exceptional to have analytic accounting and no distribution (a single dimension). Having multi-dimension in the base would remove inconsistencies in modules supporting one account instead of distribution.
è - Integrate multi-axis in base
è - Re-qualify the word plans
è - Improve the user interface for distribution encoding
è - Because plan is linked to journal and drives the display – add the journal to sales and purchases (something accountants ask for long)
è - In my opinion analytic journal is a non required concept. Globally I always create one analytic journal per journal...
Absolutly Agreed I will remove exactly this statement from my own analysis, IMHO it is the perfect approach.
2. Review Reconciliation (full & partial)
“We propose to simplify partial reconciliation. Instead of using the same concept than full reconcile (link several lines together), a partial reconciliation is a direct link from one journal item to another: you can link the journal item of a payment to one and only one receivable journal item (from an invoice).”
Very strange to me, partial reconciliation is typically related to the ‘complex’ cases multiple payment vs multiple invoices / credit notes.
Note I mention payment, invoice and credit notes because it is the most common scenario. But other exists including payment to payment, invoice to credit note, invoice to invoice etcIMHO: We should lit in some place all the user cases we have because the fact of don't have 1 reconciliation way (simplest of more difficult) bring a lot of issues in accounting, the exactly as Odoo did with WMS which comply with almost 100% of proffesianal use of warehouses this topic should be covered case by case with even the unit testing from a technical PoV per case.I think there are something like 20 scenarios not too much and it is feasible,a +1 for this topic as relevant other poit to remove from my list.
3. Taxes“And the following tax statement lines (linked to the journal entry, not the journal items)”
This is an over simplification of the structure.This simplification will change a lot of import interfaces and custom reports.
Also in my opinion it will loose the trail of audit between taxes and the accounting move. Example in Belgium is the need to individualize VAT amounts for cars.You can achieve better, simpler by using your idea and linking to account.move.line (journal items).I am agreed on the fact that it it over simplify the concept, but maybe it is not clear enought in the document, @qdp what is you opinion here?a list with user cases can help also.
4. ExpensesBut most business work with the concept of sheets (for linking receipt and managing approval), so the proposed approach does not match business.For us expenses in Latinamerica never works Out of the box due to the fact that in Latinamerica the employee comes with an Invoice to be pid to him but loaded in the system from a third party.Then the original hr_expense module was huge improved by us (may be not technically correct) but it works from almost all cases you can find our approach here:
5. Reporting EngineGreat idea – very important is to have a great xls (or other spreadsheet) export.Here I must give you a 0 (but not a -1) In our customers we avoid as much as we can allow use excel (but not 100%) because enable the use of excel is tell Accountants:"Load in the system garbage that at the end of the day you will work manually".In our best implementations we even don't show how export the aml, we improve a little the navigation and teach how to use correctly the system.We developed a powerful report engine to allow customer even build reports using ifrs concepts "but" without excel.It is funny (just as an experience) we implemente Odoo in an Oil company where there were 7 SAP accountant expert and they say "SAP do this, SAP do that" but all of them finish the reports in SAP with Excel... then... "Why SAP?".My point is that the "Accounting report engine" must be so flexible and using correct accounting terminology and methodoloy, that was our approach on that module done by our accountant expert (hbto AT vauxoo.com).Concepts like "Initial Balance" -clearly defined- must be considered, sum rows and columns and other yerbs, you can see the concept here:Again, may be not technically perfect, but the concept in great, all our accountants loves it.
6. Periods managementProblem is that monthly and quarterly periods are legal concept e.g for VAT declaration. Also suppressing opening period may be cool, but an opening date is not better.Having a separate period simplify some reporting (current exercice vs complete history)
Last but not least all financial reports we are currently using will be broken.A big +1.Periods is necesary on accounting and on Invoicing, (invoices are loaded by period too!) purchase and sale invoces can be loaded outofdate for several reasons.
7. Menu items
“The number of menu items will drastically be reduced thanks to the dashboard. (kanban view of journals) Secondary features will be available from the dashboard.”
Just a remark, most accountant are searching for journals in the system, not to see the list of journals but just seeing the entries in it.Thanks for bring these points alive.--On Thu, Oct 9, 2014 at 3:03 PM, De Paoli Quentin <firstname.lastname@example.org> wrote:
Here's the roadmap we have so far for the accounting in v9: https://docs.google.com/document/d/1MahXh0TdfjI0ohdTSz_c8cML7HqxvcAtvSAY63N20Tc/edit?usp=sharing. The work is still in progress but it's a good basis of work.
You'll also find, below this email, a webex invitation to virtually attend the presentation that will be held on the 14th of October (next week) on this document, for those who couldn't attend the 2-days session in Brussels. (Please don't forget to confirm me your presence if you can be physically there).
See you there,
have a great end of week,
-------- Original Message --------
Subject: Meeting invitation: Accounting Roadmap V9 Date: Wed, 8 Oct 2014 13:24:49 +0000 (GMT) From: Odoo Webinar <email@example.com> Reply-To: firstname.lastname@example.org To: email@example.com
Odoo Webinar invites you to attend this online meeting.
Topic: Accounting Roadmap V9
Date: Tuesday 14 October 2014
Time: 10:00, Europe Summer Time (Brussels, GMT+02:00)
Meeting Number: 700 691 141
Meeting Password: roadmap
To join the online meeting (Now from mobile devices!)
1. Go to https://odoo.webex.com/odoo/j.php?MTID=m41de38739b0f408bb2890b970e94c392
2. If requested, enter your name and email address.
3. If a password is required, enter the meeting password: roadmap
4. Click "Join".
To view in other time zones or languages, please click the link:
1. Go to https://odoo.webex.com/odoo/mc
2. On the left navigation bar, click "Support".
You can contact me at:
To add this meeting to your calendar program (for example Microsoft Outlook), click this link:
The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://odoo.webex.com/odoo/systemdiagnosis.php.
IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.