openerp-expert-accounting team mailing list archive

[Ovnicraft <ovnicraft@xxxxxxxxx>]

You can add:

On Tue, Sep 11, 2012 at 4:46 AM, Frédéric Clementi <
frederic.clementi@xxxxxxxxxxxxxx> wrote:

> Dear All,
>
> Our experience with accounting on OpenERP shown us that the system is,
> today, not trustable enough since it allows user to do many mistakes.
>
> So, at Camptocamp, we plan to create a module for (v5 and v6.1)
> adding constraints to Openerp accounting in the core source code ;  we
> want, at the same time, to stick as much as possible to the standard so
> anyone will be able to install it on top of a standard configuration.
>
> In other word, our goal is to press on very few buttons...but, if
> possible, the right ones :)
>
> Here are the first set of ideas we have gathered :
>
> * Account :
> - For Openerp v5 only, forbid to modify the type to 'view' if journal
> entries have been already posted on this account.
> - Forbid to modify the code of an account if journal entries have been
> already posted on this account.
>
> * Reconcile
> - Forbid the reconciliation between move lines if partner is not the same.
> - Forbid partner name duplication -> can generate errors on reconcile
> - Force account with type 'recevable' or 'payable' to have a partner on
> journal entry
>
   - Fix _residual function in invoice object, it change the invoice
residual when from config mistake we get >1 payable|receivable account in
move.

>
> * Date/Period
> - Forbid the possibility to post a journal entry on the wrong fiscal year
> in the core of the source code.
> - Forbid the possibility to get date outside the periode : this
> flexibility given generates too many problems (ie: filters or journal entry
> posted on the wrong month or worst  wrong year). This features already
> exists (checkbox in journal) -> we want to hide this option.
>
> * Fiscal year
> - Forbid the possibility to have more than 1 special period (=opening
> period)
> - This special period must be one day only
> - This special period must be on the very first day of the fy
>
   - can has just 2, opening and closing ?

>
> *Closing fiscal year wizard
> - Forbid to close a fy if : 1 - total debit <> total credit  2 -
> All previous fy are not closed 3 - All period in the fy must be closed 4 -
> All journal entries must be validated (already check in v6 when closing
> period but not in v5)
>
> * Journal entries
> - Forbid the modification / deletion on a automatic journal entries (ie:
> generated by an invoice, bank statement, voucher, cash,... ?)
> - Forbid to post any entries except on journals with type 'general' in
> order to force users to good practices (create invoices and use banks
> statement for ex.)
>
> Of course, it has to be challenged and completed with new ideas so we
> count on your help.
>

Will you fix analytic too ? there is many cases with that too.

* move line from invoice, delete/modify allowed
* product deletion allowed in analytic_default
* model deletion allowed with analytic_plans
* analytic deletion code allowed with account_budget (we use c2c_budget
instead)

I am agree with you in many cases, so we are starting an sprint to improve
and fix Payment area (vouchers, statements, etc).

Best regards,

>
> Thank you all,
>
> Frédéric CLEMENTI
> Business Solutions
> Camptocamp SA
> Tel : + 41 (0)21 619 1041
> http://www.camptocamp.com
>
>
>  <frederic.clementi@xxxxxxxxxxxxxx>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-expert-accounting
> Post to     : openerp-expert-accounting@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-expert-accounting
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Cristian Salamea
@ovnicraft