Odoo Addons (MOVED TO GITHUB)

Bug #659540
Comment #6

Comment 6 for bug 659540

Revision history for this message

Ferdinand (office-chricar) wrote on 2010-11-06: Re: [Bug 659540] [NEW] [trunk] account_cancel - naming issue

On Saturday 06 November 2010 P. Christeas wrote:
> On Wednesday 13 October 2010, you wrote:
> > Public bug reported:
> >
> > IMHO a serious accounting issue
> >...that posted entries
> > may not be altered in a way that the original posting can't be reproduced.
> >
> > violating this principle ... will not be accepted by the fiscal
authorities.
>
> Definitely agree.
>
> On a production system, where OpenERP is used for /official/ [1] accounting,
a
> hard rule[4] must be imposed that accounting moves [2] should not be altered
> or deleted.
>
> That said, this rule might be useful for other models, too [3].
>
>
> [1] Some installations chose to install OpenERP and then send the accounting
> data to their chartered accountants, which do the official bookkeeping. In
that
> case, the "first-level" accounting is not bound by the law. For them, the
hard
> rule /need/ to be relaxed, because they would use OpenERP as a sandbox.
>
> [2] Perhaps this could be per account (depending on country and book-keeping
> "mode"). If they are "tax" or "invoice" or "expense/income" accounts, they
> would be locked. If they are "petty-cash" ones, they could be relax. I
repeat,
> this is country-dependant (or better, chart-of-account-dependant).
>
> [3] I can thing, at least, of the case for hospitals or medical entries,
that
> everything must be recorded and be able to audit. I think we have a rule
also
> for Hotel reservations, too, here.
>
> [4] If implemented, it should be really *hard* to circumvent, because such a
> loss would be violating the law. I was thinking of Pg. triggers or rules;
yes,
> that much. This way, it would ensure that the data is preserved, even if
> somebody tries to mess with SQL.
I have implemented such a trigger system already

IMHO you forgot to mention the role of implementing partners

If these have no chance to trace changes they are "lost", because nobody can
answer questions of clients if delteing and altering of data is arbitrary.
>
>
--
regards
Ferdinand Gassauer
ChriCar Beteiligungs- und Beratungs- GmbH
Official OpenERP Partner

On Saturday 06 November 2010 P. Christeas wrote:
> On Wednesday 13 October 2010, you wrote:
> > Public bug reported:
> > 
> > IMHO a serious accounting issue
> >...that posted entries
> > may not be altered in a way that the original posting can't be reproduced.
> > 
> > violating this principle  ... will not be accepted by the fiscal 
authorities.
> 
> Definitely agree.
> 
> On a production system, where OpenERP is used for /official/ [1] accounting, 
a 
> hard rule[4] must be imposed that accounting moves [2] should not be altered 
> or deleted.
> 
> That said, this rule might be useful for other models, too [3].
> 
> 
> [1] Some installations chose to install OpenERP and then send the accounting 
> data to their chartered accountants, which do the official bookkeeping. In 
that 
> case, the "first-level" accounting is not bound by the law. For them, the 
hard 
> rule /need/ to be relaxed, because they would use OpenERP as a sandbox.
> 
> [2] Perhaps this could be per account (depending on country and book-keeping 
> "mode"). If they are "tax" or "invoice" or "expense/income" accounts, they 
> would be locked. If they are "petty-cash" ones, they could be relax. I 
repeat, 
> this is country-dependant (or better, chart-of-account-dependant).
> 
> [3] I can thing, at least, of the case for hospitals or medical entries, 
that 
> everything must be recorded and be able to audit. I think we have a rule 
also 
> for Hotel reservations, too, here.
> 
> [4] If implemented, it should be really *hard* to circumvent, because such a 
> loss would be violating the law. I was thinking of Pg. triggers or rules; 
yes, 
> that much. This way, it would ensure that the data is preserved, even if 
> somebody tries to mess with SQL.
I have implemented such a trigger system already

IMHO you forgot to mention the role of implementing partners

If these have no chance to trace changes they are  "lost", because nobody can 
answer questions of clients if delteing and altering of data is arbitrary.
> 
> 
-- 
regards
Ferdinand Gassauer
ChriCar Beteiligungs- und Beratungs- GmbH
Official OpenERP Partner