openerp-expert-accounting team mailing list archive

[Robin <robinstc@xxxxxxxxxx>]

Hi Luc and others

As a professional accountant (ACA/CMA/CPA) and a 
developer/designer/analyst, I wholeheartedly concur with the plea not to 
limit the ability to post invoices/expenses to prior periods.

In fact, when reviewing software I would deprecate  products that did 
not allow this to happen.

When designing ledger systems from scratch, I always allow for classes 
of transaction, to allow for current periods, prior periods, company 
depreciation, tax depreciation etc., it does simplify life. To create 
proper accounting reports one needs to be able to assign transactions to 
current period / last period / previous period in order to produce 
comparatives for reports involving fund flows.

Regards

Robin St.Clair

On 30/03/2014 11:00, Luc Maurer wrote:
> Hello All,
>
> No, I really recommend to no split this module => this date constraint 
> is for me mandatory. We have more than 8 years experience with finance 
> into OpenERP and I can tell you that before having this constraint it 
> was the nightmare each end of year. People doesn't understand the 
> difference between period and dates....
>
> By default you can choose in the journal if you want to have a control 
> between date and period (into the same FY) it is enough.
>
> If needed in Belgium you should change the localization to avoid this 
> constraint but I really not recommend it !
>
> Regards.
>
>
>
>
> *camptocamp*
> INNOVATIVE SOLUTIONS
> BY OPEN SOURCE EXPERTS
>
> *Luc Maurer*
> Directeur et associé
>
> +41 21 619 10 10 (central)
> +41 79 606 07 73 (mobile)
> +41 21 619 10 12 (direct CH)
> +33 4 79 44 44 95 (direct FR)
> *
> *
> *Camptocamp SA*
> Quartier de l'Innovation EPFL, PSE-A
> 1015 Lausanne
> Suisse
>
> www.camptocamp.com <http://www.camptocamp.com/>
>
>
> On Fri, Mar 28, 2014 at 5:17 PM, Bidoul, Stéphane 
> <stephane.bidoul@xxxxxxxxx <mailto:stephane.bidoul@xxxxxxxxx>> wrote:
>
>     Hi experts!
>
>     In module account_constraints, there is a check that the date of
>     the move is in the same fiscal year as the period.
>
>     Here in Belgium I meet accountants saying that, while exceptional,
>     it is perfectly valid to enter a supplier invoice with a date in
>     previous fiscal year while forcing the period in current fiscal year.
>
>     How would you recommend dealing with this situation? Should
>     account_constraints be split in more granular modules implementing
>     subsets of constraints so we can chose the one that are applicable
>     in our regions?
>
>     Best regards,
>
>     -sbi
>
>     Stéphane Bidoul | @SBidoul <https://twitter.com/SBidoul>
>     Acsone sa/nv | http://acsone.eu/ <http://acsone.eu/> |+32 2 888
>     3120 <tel:%2B32%202%20888%203120>
>
>
>
>
>
>
>     _______________________________________________
>     Mailing list: https://launchpad.net/~openerp-expert-accounting
>     <https://launchpad.net/%7Eopenerp-expert-accounting>
>     Post to     : openerp-expert-accounting@xxxxxxxxxxxxxxxxxxx
>     <mailto:openerp-expert-accounting@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~openerp-expert-accounting
>     <https://launchpad.net/%7Eopenerp-expert-accounting>
>     More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> _______________________________________________
> 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