Bug 417167 - Add ability to review and edit ofx when importing
Summary: Add ability to review and edit ofx when importing
Status: REPORTED
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: 5.0.6
Platform: Microsoft Windows Microsoft Windows
: NOR wishlist
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-04 22:18 UTC by Nathen
Modified: 2020-02-06 23:30 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nathen 2020-02-04 22:18:22 UTC
SUMMARY
It would be really helpful to be able to review and edit each transaction when importing an OFX
Currently when importing you have no control, and Kmymoney creates unnecessary payees and transactions that have to be matched and edited and deleted.
The early version (99) Of MSMoney handled it very well and would be nice if it was replicated. 

potential procedure would be
1. Import file
2.Kymoney checks for matching transactions already in account 
2a.Dialog if Kmymoney finds a matching transaction (based on amount and date     range)
3.review each transaction (Kmymoney may suggest a payee if similar transaction found) 
4.Make changes If required
5.Accept changes
6.Dialog box is matching transaction found (Yes it is,No it is not)
7.Transaction added to account.(or not if a match is found and accepted)
Back to step 2

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Jack 2020-02-04 23:46:06 UTC
I would think it would have to be a conditional review, as I certainly would not want to have to approve dozens of transactions (not infrequent with some of my investment accounts) if I know they will be imported OK.  Being able to flag only certain transactions for manual review might be better.

I may also file a separate bug just to add a setting to prevent the creation of new Payees on import, since that one of my greatest costs in editing imported transactions.

Also -  might this apply to any import, such as QIF, and not just OFX?
Comment 2 Nathen 2020-02-05 21:46:12 UTC
Yes A setting to either review or just enter without review may work. I find I have to make some sort of change to almost all the imported transaction anyway.
You are right about the payees. I end up having to remove dozens of payees each time because the bank adds unique identifiers to all transfers.
They (the government) have just introduced new anti laundering laws and its got even worse.
Comment 3 Thomas Baumgart 2020-02-06 06:33:42 UTC
Do you know, that you can get rid of those unique parts by using the regexp matching method? I have the same issue but meanwhile have all payees setup so that I rarely have to modify the matched transactions.
Comment 4 Nathen 2020-02-06 22:35:53 UTC
Are you talking about the "matching" function in Payees. And one of the things I like which has appeared in 5 is the partial match function.
If so Yes,
 But for example on of the things one bank does is put TFSxxxxxx for all inter-bank transfers. eg when I pay my CC. and but also for other payments. This is not a issue with Kymoney, it is just laziness on the part of my Bank. So I have to download the statement, correct the payees,and category information ect and then delete the added Payee ect.
If not can you provide a link to some information.
Comment 5 Jack 2020-02-06 23:30:35 UTC
Why not create a payee "TFXxxx" (literal three x's, not any digits) and match on "TFS" so at least all such transactions get gathered to one payee, and don't create a new one for each transaction.