1. Mailing Lists
  2. Accounting
  3. Re: Feedback Accounting Blog

Accounting mailing list archives

accounting@odoo-community.org

Browse archives

Re: Feedback Accounting Blog

Re: Feedback Accounting Blog

Avatar

Re: Feedback Accounting Blog

by
Camptocamp SA, Frédéric Clementi
- 13/11/2015 15:09:29 
Hello,

Please see my answers inlines below.

Thanks for your answers.

Frederic

2015-11-13 11:23 GMT+01:00 Fabien Pinckaers <fp@odoo.com>:
Feedback on this blog: https://odoo-community.org/blog/oca-news-1/post/odoo-9-accounting-oca-28

1/ Removal of fiscal year

Removal of fiscal years has a lot of advantages: no more painful opening of fiscal years (I would say that 30% of our customers call us in the beginning of a fiscal year because they could not invoice), easier comparison mechanism, performance improvement, better lock-in system, efficient multi-company settings. 

There is only one little drawback (*) in the current implementation: the user has to select date ranges when doing a report for complex fiscal year (>12 months). It's a rare use case and it takes just 30 seconds to set custom dates on a report.

Trying to put back fiscal year would be a HUGE mistake. It may complexify the code and the user experience.

If you want to solve the drawback, the small improvement I would suggest it to just save the current report date selection so that if you launch the report again, it uses the same selection.

(*) or is there other drawbacks?

You can remove period as you did (personnaly I like it) but there is no way you can remove the fiscal years because this is legal, because a fiscal year is not always 12 months, because it is easier to filter, because everybody want to work this way in the accounting business in the world and it can be a issue to sell Odoo because of this.

But I am curious, why would it be a mistake if we simply log somewhere that a specific fiscal year has a start date and a end date just to allows that filter on reports ? It is no question of putting back the opening entry or a closing wizard.



2/ Limited access to journal items

We will not add this as we think it's too technical for the majority of the users who should use Journal Entries which is cleaner as you can work in it, and they reflect a real accounting document. Journal items view can only be readonly, which makes them useful.

But we understand that some "advanced" users may want to have it. 

Note that we have added (not sure it's merged yet, but it will be soon) the link from the general ledger report to open journal items related to the account. (currently the link is showed if there are more than 80 records, but we will make it appears even on low number of entries)

I am sorry this is not enough for me.

Hide the Journal item menu if you like but :
- Add a filter on account on the GL report
- Add a clickable reconcile code on the GL with the reconcile/unreconcile action
- Give possibility to increase the 80 lines limit

(This comment of course will not help in the Community version)

 
3/ Removal of hierarchy

That's just a technical point of view. If you have a look at the accountant needs: they need hierarchy in P&L, Balance Sheet, Chart of Accounts...

All reports in Odoo have a hierarchy (P&L, BS, Chart of Accounts), but this way of managing the hierarchy is cleaner than a simple parent_id approach. In v8, we only had a hierarchy for Chart of Accounts --> how do you manage the hierarchy of P&L, ...? In v9, every report can have its own hierarchy.

I agree Fabien but after I read community feeback I realized that I probably underestimate this aspect as well.
First, It is not only a reporting matter and secondly, the problem is even bigger regarding analytic accounts because of strong existing relation with other modules like budget and projects. 
ie:  Budget item could be linked to a view account, project are ofter organized by hierarchy... tags are not appropriate tool for this. 

Remember you said analytic is not in the scope of Odoo 9 accounting reenginerring. You where right, analytic is too big to be changed this way.


4/ Basic reports

Yes, some reports can be improved.

Well, this is a huge euphemism in my view. You cannot print or visualise a summary of an account or a partner !

Fabien, reports are just amazing and beautiful in the enterprise version but not comprehensive.
As an accountant, I want to be able to audit a specific account : on the screen, on pdf... with all transactions, initial balance, end balance, currency balance and I want to find errors easily.

 

5/ What's the use case?

Since v9, you don't need to use the reconciliation mechanism anymore (réconciliation comptable). The system is designed around the bank reconciliation. (rapprochement banquaire). Or, only for very specific use case. 99% of the reconciliation will be on the bank statement or the invoice directly, and this is a good thing, just a different way to work. (BTW the reconciliation wizard is still there)

For visualization, I do agree we should add some information on the journal entry to zoom to reconciled documents (invoices, other payments, ...)

But reconciliation are mainly invoice - payment relations but not only ! 
What about internal transfer account ? Or Social cotisations (booked through payslip vs effective payement), ... 
And what about the unreconciliation ? The wizard is there I know but again in the debug mode.
How can you see accounting lines reconciled ? 

 
6/ Payments

What is the nightmare with payments in currencies?
My uses cases was to try paying several invoices with different currencies and invoices already partially paid.


But I do agree that we should add a multi-suppliers payment feature. (If I am not wrong, technically, the feature is there but not activated as I have seen it working before the release; but it does not seems to work anymore)
good
 



Thanks for the feedback and effort to improve Odoo,

-- 
Fabien

_______________________________________________
Mailing-List: http://odoo-community.org/groups/accounting-28
Post to: mailto:accounting@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


Reference