openerp-dutch team mailing list archive

[The Loeki <the.loeki@xxxxxxxxx>]

The assumption that only move.lines from the year to be closed would
need to be closed seems a right one.

However, as specified in the initial report, that's not what this patch
or bug is about, and your patch would not /seem/ to prevent the bug from
happening.

The first bug relates to the fact that an invoice could be made in a previous year, and/or be paid in the/a next year. Neither will reconcile correctly.
The second bug relates to invoices that are made in the current (or, after my patch, previous years) and be paid in several parts in the next year(s).

The current code would generate a move.line for each payment, resulting
in a horrible mess.

-- 
[PATCH] account module quite severe issues with closing fiscal years
https://bugs.launchpad.net/bugs/531507
You received this bug notification because you are a member of OpenERP
Dutch Team - Nederland, which is the registrant for OpenERP Dutch
Lokalisatie Project - Nederland.

Status in OpenERP-Dutch-localisation: Fix Committed
Status in OpenObject Addons Modules: In Progress

Bug description:
We have identified two major issues with the wizard_fiscalyear_close in the account module in any 5+ version of OpenERP:

1) As noted in the wizard_fiscalyear_close.py (~line 145):
                #TODO: this query could be improved in order to work if there is more than 2 open FY
                # a.period_id IN ('+fy2_period_set+') is the problematic clause
2) When a reconcile crosses years AND the reconciliation in the new years contains N entries, each reconciled entry in the old year will get reported N times instead of once.

These bugs will quite possibly crap up closing a year, and we consider them therefore to be quite important.