openerp-expert-accounting team mailing list archive

[Graeme Gellatly <gdgellatly@xxxxxxxxx>]

I think the idea is good, but would like to see it configurable at a Global
and Journal/View/Account/Account type level (which ever is appropriate) by
a new security group.  Just a screen of checkboxes basically.  Different
countries and different companies have different requirements.  OpenERP's
flexibility in structuring charts and restructuring them is an important
feature to us.

I don't see any issue with changing account codes for example.  Certainly
in our jursidiction there is nothing to forbid it.  In fact this creates an
ugly situation when you have legitimate reasons to rename, and surely if
you enforce that you cannot change account code, then you must do the same
for name, account type and internal type.  Code is more meaningless than
the others.
Equally in Bank Journals there are lots of cases for manual entry - mostly
because if you use account_voucher and reconcile bank statements you cannot
also use the bank statement entry screen, so some things must be manually
entered.
Having a date different to the period - personally I don't see a use case,
but clearly OpenERP had a rationale for allowing it, I would like to
understand what that is.
account_cancel allows cancelling invoices which deletes journal entries -
I'm not saying it is a good idea, but sometimes mistakes are made and it is
good to be able to change them without credit and reinvoice.

But other validation I would like to see.
Validation that the invoice total is the same as the journal payable entry
- often they differ by 1 cent after anglo_saxon calculations on the
payables side.

Also I have to disagree with James.  Lack of confidence as a reliable
accounting system is IMHO more related to consistent bugs/unexpected
entries/poor calculations/lack of consistency in relation to automated
entries, not validation, and not manual entries.  It is precisely this
reason that until those issues are well and truly dealt with in a robust
manner I wouldn't want to lose the ability to correct things (and lets face
it, OpenERP SA seems uninterested in core functionality improvements -
Fabien in February - "We will plan a project to review the whole logic some
day" - in relation to persistent average cost errors).  I guess some day is
not here yet.

Creating manual invoices from sales order lines does not apply taxes. - why
even it should be an entirely different function than the other ones I do
not understand - we amended just to call existing invoice logic and it
works fine.
Shipping goods directly from Supplier to customer creates no entries, but
corresponding invoice creates the wrong ones.
Manual invoices apply default taxes, sales orders do not even when they are
identical.
Average cost entries are all wrong unless you use a decimal precision the
same as the currency - sorry fixed now in 6.1.
Average cost is recalculated using stock move prices even when you don't
receive any goods.
Decimal precision as a whole is fairly well broken.

There are so many options and choices in creating automated entries, that
all follow different paths, that IMO it is almost easier to get them wrong
there than in the accounting part.

On Tue, Sep 11, 2012 at 9:46 PM, 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
>
> * 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
>
> *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.
>
> 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
>
>