Bug 310751

Summary:	Please provide a way to match QIF imported transactions
Product:	[Applications] kmymoney	Reporter:	Dmitry Nezhevenko <dion>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	agander93, pub-yannick
Priority:	NOR
Version:	4.6.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	sample patch

Description Dmitry Nezhevenko 2012-11-27 11:33:08 UTC

Hi,
Currently there is no way to match two imported transactions. In case if they are from two different sources (for example another app and bank statement) this is serious limitation. Typical use case for me is when expenses are recorded sometimes directly via kmymoney (for example from receipts) or sometimes from another mobile app and later imported to kmymoney as QIF.

Later when importing bank statement transactions I want to be able to assume that manually entered and imported from mobile transactions will be merged with bank statement.

I've found that kmymoney generates 'bankID' for imported transactions if such ID's are not provided in QIF itself using KMM-specific "#" token. And later matcher will never try to match transactions with different bankID.

Is it possible to provide way to import QIF file without generating bankID? We can still use same KMM-sepcific "#" token. Provided patch is possible implementation 

Reproducible: Always

Comment 1 Dmitry Nezhevenko 2012-11-27 11:34:43 UTC

Created attachment 75501 [details]
sample patch

Comment 2 Thomas Baumgart 2012-11-27 12:48:07 UTC

KMyMoney only supports matching of manually entered transactions against imported transactions. Transactions created by a schedule are also seen as manually entered in this context. One cannot match two imported transactions.

afaics, the cause to your problem is the mobile app. It should not create a line with a hash that is taken as the bank-id. How does the line '#-' gets created so that it can be skipped during QIF import?

Comment 3 Dmitry Nezhevenko 2012-11-27 13:03:56 UTC

Well, I'm creating QIF file from mobile app myself so it's no problem to get rid of '#' line. But this is not the problem.

Basically I have two QIF files: one from mobile app and one from bank. Both of them have no '#' line. And if I import both of them, KMyMoney will NOT match transactions from one QIF file with transactions from another. I know that this is expected for now.. But for me first QIF file (from mobile) symanticaly is not actually bank statement. It's instead short way of reenter manually transactions from stupid mobile app (that stores only date, amount, and description) to KMyMoney. So after such import I still want to merge such transactions with transactions from bank statement.

Comment 4 pub-yannick 2014-04-07 20:40:46 UTC

Hi!
Is the request have a solution in the last KMymoney Version?
Thanks
Yannick

Comment 5 allan 2014-04-28 22:48:30 UTC

This is being investigated at the moment.

*** This bug has been marked as a duplicate of bug 334037 ***