0024815: Silient failure when matching imported financial account transactions into a closed period

Description

When you import a bank statement into a financial account (either manually or through OFX or CSV files) and try to match the transactions as part of the reconciliation process, if one of the transactions in the statement falls into a closed period, the Match Statement process fails silently.

A silent failure makes it very difficult to diagnose the problem.

Steps To Reproduce

1) In a Financial Account, set the Matching Algorithm to Advanced Matching Algorithm.
2) In the Imported Bank Statements tab, create a manual bank statement
3) Add two lines in the statement one for August and one for September
4) Make sure to specify both the business partner and a G/L item for both lines
5) Make sure August is closed and September is open
6) In the Financial Account window, click Match Statement. The expected behavior is that the Match Statement window opens up with both transaction proposed to be created. Instead, the window is empty.
7) Now, modify the August transaction by removing the G/L Item
8) Press Match Statement again. This time, both transactions are found, the September one with a proposed match and the August one empty.
9) Press + and create a transaction to match the August one. When you do so, you get an error because the period is closed.

Proposed Solution

Match Statement should not fail silently and instead show an error message.

Issue History
Date Modified	Username	Field	Change
2013-09-24 04:56	pjuvara	New Issue
2013-09-24 04:56	pjuvara	Assigned To	=> dmiguelez
2013-09-24 04:56	pjuvara	Modules	=> Core
2013-09-24 04:56	pjuvara	Triggers an Emergency Pack	=> No

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
There are no notes attached to this issue.