[Kmymoney-devel] Re: Matching Transfers
aganderson at ukonline.co.uk
Thu Sep 30 19:53:26 CEST 2010
On 29/09/10 11:19, allan wrote:
> On 29/09/10 00:51, allan wrote:
>> On 28/09/10 23:22, allan wrote:
>>> I remember there was a problem some time back with the 'big bang' QIF
>>> import, where a transfer occurred between two banks - the transactions
>>> became duplicated when the the second bank account is imported, showing
>>> the other end of the transfer.
>>> I still have a bit of an issue with this, and how best to resolve it. A
>>> category can't be assigned because neither an expense nor an income is
>>> involved, and if the 'opposite' account is inserted, this causes the
>>> It would seem to me to be best to match the two transactions, but
>>> presently this is not possible, because they are both imports.
>>> Could someone explain to me, please, why two imports can't be matched?
>>> I've never understood the rationale behind this.
>> I'll have another go at this tomorrow/today. Things may not be as they
> After a night's sleep, and going slowly, there is no problem. These
> matching transactions can be matched, as, after adding the transfer
> account name, the new transaction that appears in the other account is
> not an import, and therefore can be matched.
> Sorry for the noise.
Back again. Sorry for this, but there is an issue here.
It occurs when importing two bank statements, one from Bank A including
a transfer to Bank B, and the other including the opposite end of that
1) Import file A.
2) Check that all is correct and accept the transactions.
3) Import File B.
4) Account B, assign the transaction in question to Account A.
5) In Account A, attempt to match the two associated lines. Matching is
If step 2 is omitted, matching is possible.
If step 2 is kept, but step 4 is reversed, so the item in Account A is
assigned to Account B,then matching is possible.
I think this is why I sometimes have a difficulty, and I suspect it must
relate to the status of the transaction getting changed. In step 2,
accepting the import presumably changes the status from imported.
Attempting matching against that will now fail. However, if that
transaction is matched against the one in Account B, which has not yet
been accepted, then all is well.
I don't know if this is a bug, but if it is not, then the user
instructions have to be very clear about the steps needed to accomplish
what seems a fairly trivial exercise. There are pitfalls.
I'll ask again, my original question.
"Could someone explain to me, please, why two imports can't be matched?
I've never understood the rationale behind this."
In fact, why can't the user be allowed to match any two transactions he needs to ?
More information about the KMyMoney-devel