Entries Encoding by Move allows to use dates in other periods
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In Entries Encoding by Move, it is allowed to use dates out of the period selected, this could result in inconsistencies when requesting for example a General Ledger for the accounts involved in the Move affected, because if a Ledger is asked filtered by dates within the period it will not show this move, either way if a ledger is asked filtered by date and in between the date of this move is within then this move will be shown,
I think a good solution to this issue is to make the period field sensible to the change on the date field, suggesting the period depending on the date, another one could be validate that both field are meaningful or send an alert.
Thanks in advance for your attention.
Hbto.
Changed in openobject-addons: | |
milestone: | none → 6.0 |
status: | Confirmed → Fix Released |
Hi,
We notice this problem too and develop a module called hasa_account_ security that :
-Add two wizards to check and display the incorrect account move lines / account move where the date is not included in the period
-Add two constraints that check in all new account move lines / account moves if the date is included in the period to avoid accounting errors
You can found it on launchpad :
http:// bazaar. launchpad. net/~openerp- community/ openobject- addons/ andre-kurz_ hasa-addons/ files bazaar. launchpad. net/~openerp- community/ openobject- addons/ trunk-addons- community/ files
http://
Hope that it can help you and maybe these constraints could be added to the server addons...
Regards,
Andrek