Hi,

Before I raise a bug report!

In previous versions of KMyMoney when I import a bank statement transaction matching happens automatically, but in 4.7.0. I have to match transactions manually. Is this expected?

Thanks

Nick

The transaction matching code was rewritten in 4.7 so there might be some issues but first let's check if everything is OK on your side. Transactions match if the following conditions are met:

• accounts match
• bank ids match or the existing transaction does not have a bank id
• amounts match
• payees match or at least one payee is empty
• existing transaction is not already matched

Are you sure that the above conditions are met in your case?

There is already this report where the changed matching in 4.7.0 is discussed so if you could provide more information please join that discussion.

I'll take a look at the discussion and join if I have anything to add.

Just to go through the points you raised:

• my bank doesn't provide account information in the QIF file, but the KMyMoney import wizard prompts me to select an account so I can only assume that it passes this to the matching process
• confirmed - no bank ID
• confirmed - the amounts match
• payees match, but not exactly, my bank usually adds some text on the end (a date, or transaction ID etc.) which obviously I can't predict when I set-up scheduled transactions
• confirmed - the existing transaction is not already matched

Could you try to setup payee matching for that particular payee that gets some string appended to it's name?

I'll do that - will let you know how I get on in a few weeks when I next import my bank statement!

Thanks for your help.

Setting up payee matching does seem to have improved things - at least SOME of my transactions are now being matched compared with none last month.

Was there a problem with transaction matching in 4.6 that I wasn't aware of? I can only speak from my own experience but the matching process "just worked" without any intervention on my part, but in 4.7 it "sometimes works" and that's after I've had to edit matching criteria for individual payees.

I hate to sound picky, because KMyMoney is fantastic, but this feels like a backward step.

I'm still having issues with Transaction Matching - as I mentioned before it JUST WORKED in 4.6.

Here's just one example:

I have a scheduled transaction set-up for a payee called Direct Debit - Yorkshire Water.

As suggested, I amended the matching criteria for the above payee:
- match on a name listed below
- yorkshire water
- ignore case

The imported bank statement has an entry for YORKSHIRE WATER with the same date and quantity exactly as the scheduled trasaction entry in the ledger yet KMyMoney fails to match the two.

Am I doing something wrong?

Suggestions please as this minor frustration is becoming a major time-wasting annoyance!

From your description I could not figure out if payee matching actually works. I mean you said that you have set it up as it's expected but did the imported transaction (which did not get matched to the scheduled transaction entry in the ledger) end up having Direct Debit - Yorkshire Water as payee?
If not that's the reason why the transactions did not match. If it does have the correct payee we must investigate the existing transaction.