| Summary: | Matching transaction incomplete on transfers with scheduled transaction. | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | Jonatan Cloutier <cloutier.jo> |
| Component: | importer | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 5.0.8 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Data file containing accounts and schedule
QIF import file containing a single transfer between two accounts init kmy file result kmy file mars qfx file april qfx file |
||
|
Description
Jonatan Cloutier
2020-02-29 17:13:10 UTC
Still present on 5.0.8 Can you provide the following for us to duplicate the problem, please? a) sample .kmy file with two accounts and a scheduled transfer b) sample ofx file with a transaction that causes the problem to show up Attach those to this bug. Please make sure to modify the details in the OFX file so that no personal information is contained but leave the structure as it is when you get it from your institution. In case you cannot download a file but only have a direct connect, you can turn on OFX logging in 'Configure/General/Support'. Many thanks in advance. Created attachment 128270 [details]
Data file containing accounts and schedule
Created attachment 128271 [details]
QIF import file containing a single transfer between two accounts
There are two different ways I tested:
a) open the .kmy file, import the qif file and accepted the match to the schedule and
b) open the .kmy file, enter the overdue schedule, import the qif file.
In both cases, the transaction matches. It could well be that your problem is related to the OFX import and how it reports the data to the KMyMoney statement reader which is used by all importers. So I am waiting for an OFX sample showing the problem, maybe using the .kmy file attached here.
Created attachment 128288 [details]
init kmy file
Created attachment 128289 [details]
result kmy file
Created attachment 128290 [details]
mars qfx file
Created attachment 128291 [details]
april qfx file
Hello, It took a bit of work to reproduce this on a vanilla file. 1. I started with a new data file, created 2 accounts and importing a first ofx file (for March). 2. Both transactions were imported but not matched automatically (I don’t know if I messed up the qfx file or some kmymoney setting or it's another bug, but it doesn't really matter here). So I linked them manually and created a recurring transaction from them ( right click -> create recurring...) 3. I imported another qfx file for the April month result: the transaction was imported and matched in the second account, but I have 2 transactions in the first one. I upload both qfx file, the startup kmy file I produce and the result kmy file to make sure you have all the info. To quickly reproduce you can start with the init kmy file and import April qfx file. Thank you for looking into that. Thanks for the files. That shows me what is going on. The transaction matcher works on payees. The problem here is, that you have two different names for the same payee, so matching cannot work. Solution: add '^VIR WEB CD - 1234$' as matching text to the payee 'Virement' and delete the "VIR WEB CD - 1234" payee. If you do the import with that setting, you get the result you expect. Hope that helps. Thanks, it did solve the issue. |