21/05/2026; 642 words; 3 minutes to read.
I have long resisted adding a facility to import transactions from online banking websites in MyNetWorth in the belief that, if you enter your purchases into MyNetWorth manually and reconcile your transactions regularly, you will spot suspicious withdrawals promptly and be able to protect yourself against losses. However, I have been persuaded that those of you, who batch process your transactions and reconcile them infrequently, e.g. monthly, could benefit significantly from being able to import transactions from your bank and, as the import process does require you to review and edit each transaction to add missing information, which is not included in bank exports, the ability to spot suspicious withdrawals as you do this still remains. So, I added the capability to import transactions from online banking websites to Version 3.10 of MyNetWorth and I published it at the end of April. You can read about the new capability in the MyNetWorth user guide at this page.
I completed implementing much the same import capability in MyNetWorth for Windows and submitted Version 3.5.98 to Microsoft for certification on 20 May1. As I was writing the associated C# and XAML code, I added buttons for Removing and Editing/Entering imported transactions; in MyNetWorth Version 3.10, I used a context menu, rather than buttons, to allow the user to Remove and Edit/Enter imported transactions. Being as MyNetWorth uses Transaction Editing buttons in the Accounts, Payees and Schedule Views, it seemed to me that the use of a context menu for Removing and Editing/Entering imported transactions was inconsistent with the user interface design philosophy of MyNetWorth as a whole. But, on the other hand, having the option to use context menus does provide a useful (and slightly quicker) alternative to having to use buttons all of the time. So, Version 3.11 of MyNetWorth features Transaction Editing Context Menus and Buttons in the Accounts, Payees and Schedule Views, as well as in the import transactions function.
MyNetWorth Version 3.11 was published on the Mac App Store on 20 May, as was MyNetWorth Preview Version 3.11. This latest version of both apps also fixes a couple of bugs in generating scheduled split transactions from existing split transactions in the Accounts and Payees Views and in exporting MyNetWorth data to MyNetWorth for Windows data files. MyNetworth for Windows Version 3.5.98 will have the same import transactions capability as MyNetworth and will also include the fix to a bug that was causing scheduled split transactions, which have been processed automatically on launch, to lack their subtransactions; MyNetworth for Windows Version 3.5.98 will, however, lack the context menus of MyNetWorth (for now at least, as adding a context menu to a wpf datagrid in XAML/C# is far more tortuous that adding one to a tableview in SwiftUI).
1MyNetWorth for Windows Version 3.5.98 has completed certification and was published on the Microsoft Store on 21 May. You can read about the new import capability in the MyNetWorth for Windows user guide on this page.
Created with Ignite
© 2022 - 2026 Christopher Hull. All rights reserved.