OpenERP do not prevent reconciliation of move lines with different accounts

Bug #1215897 reported by Frederic Clementi - Camptocamp on 2013-08-23
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
OpenERP Publisher's Warranty Team
OpenERP Community Backports (Addons)
Status tracked in 7.0
OpenERP Community Backports

Bug Description


OpenERP do not prevent reconciliation of move lines with different accounts which is a nonsense from a accounting perspective.

To reproduce :
- Go to Runbot Stable version 7.0 (but it is true in all version also)
- Go to Accounting / Journal Entries / Journal Items
- Select 2 move lines with a different account (but important : with a same partner or no partner at all -> there is an other constraint on this field)
- Gp to 'More' Button and select reconcile.
- Do a partial reconcile for exemple

See also : the attached printscreen.

Many thanks


Related branches

tags: added: maintenance
Amit Parik (amit-parik) wrote :

Hello Frederic,

Its working fine, I have attached the video for you with latest v7. You can check and notify us.

Thank you!

Amit Parik (amit-parik) wrote :
Changed in openobject-addons:
status: New → Incomplete
Changed in openobject-addons:
status: Incomplete → New
Amit Parik (amit-parik) on 2013-09-26
Changed in openobject-addons:
assignee: nobody → OpenERP Publisher's Warranty Team (openerp-opw)


This verification was disabled by mistake in 6.1 at revision 6529
revid:<email address hidden>, while correcting the FY closing system.

The check has been re-enabled in 6.1 and 7.0 at the following revisions:
- addons 7.0 rev 9759 rev-id <email address hidden>
- addons 6.1 rev 7295 rev-id <email address hidden>

Thanks for reporting,

PS: the fix in OPW and OCB branches seems quite redundant with this (restored) implementation, it should probably be removed

Changed in openobject-addons:
importance: Undecided → Medium
milestone: none → 7.0
status: New → Confirmed
Changed in openobject-addons:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers