Im trying to import a MT940 Swift File and expect the payee to match a word in the "purpose" field. But seemingly, no matter what I input in the custom match filter in the payee details - the transactions imported are not matched to the payee defined in kmymoney. Reproducible: Always Steps to Reproduce: 1. Create payee and assign a match key 2. Import the MT940 File 3. Open Ledger into which the data got imported Actual Results: Transactions are missing category and payee Expected Results: Transactions have the payee assigned and the corresponding category When I import the MT940 file with the Aqbanking CLI tool. It shows this: transaction { char localAccountNumber="123456789" int uniqueId="0" int idForApplication="0" int groupId="0" valutaDate { date { int day="15" int month="10" int year="2014" } #date int inUtc="1" time { int hour="12" int min="0" int sec="0" } #time } #valutaDate date { date { int day="16" int month="10" int year="2014" } #date int inUtc="1" time { int hour="12" int min="0" int sec="0" } #time } #date value { char value="-119%2F10" char currency="CHF" } #value int textKey="0" int textKeyExt="0" char transactionKey="MSC" char customerReference="00425" char bankReference="NONREF" int transactionCode="0" char purpose="Service Description ", " RESTAURANT BILL" char period="unknown" int cycle="0" int executionDay="0" char type="unknown" char subType="unknown" char status="unknown" char charge="unknown" char sequenceType="unknown" } #transaction
KMymoney Version 4.6.4 KDE Platform Version 4.13.3
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!