My Blog

Despite my contention that MyNetWorth for Windows would not be getting the context menus that are a feature of MyNetWorth, because “adding a context menu to a wpf datagrid in XAML/C# is far more tortuous that adding one to a tableview in SwiftUI)”, I have added context menus to the transaction datagrids in the Accounts, Payees and Schedule Views in MyNetWorth for Windows version 3.6.99, which was published on 26/06/2026.

For a long time I 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 was persuaded that those of you, who batch process your transactions and reconcile them infrequently, e.g. monthly, would 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 in MyNetworth and MyNetWorth for Windows.

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.

MyNetWorth, MyNetWorth for Windows and iNetWorth (together with their Preview and Trial versions) have been updated to improve their usability and reduce the number of interactions needed to enter and edit transactions. The promise to do this appeared in this blog post on some tips and tricks for users of these apps.

One of the fundamental design choices that I made in the development of MyNetWorth, MyNetWorth for Windows and iNetWorth was to exclude any capability for importing transactions from users’ bank accounts automatically. As stated on my Home Page, if you have your banking app set up to import transactions from your bank automatically, it can be difficult to spot any transactions that you didn’t make or didn’t intend to authorise. If you enter your purchases into your banking app manually and reconcile your transactions regularly, you can spot suspicious withdrawals and subscriptions that you no longer need promptly and so protect yourself against losses. The impact of this design choice on my development of MyNetWorth, MyNetWorth for Windows and iNetWorth has been for me to make the manual entry of transactions as easy and as rapid as possible by striving to avoid the need to always add transactions from scratch and thereby reducing the occasions when you must complete each and every field in the Edit Transaction dialogue box.

New versions of MyNetWorth, iNetWorth and MyNetWorth for Windows have been published on the Mac App Store, the App Store and the Microsoft Store. The main new feature is the capability to generate Scheduled Transactions from normal transactions in the Accounts and Payees Views, which could save you both time and effort.

I have been working on one new feature and a number of bug fixes and improvements to MyNetWorth, iNetWorth and MyNetWorth for Windows over the Christmas and New Year break. The new feature is the capability to generate Scheduled Transactions from normal transactions in the Accounts and Payees Views, which simplifies the creation of Scheduled Transactions and could save you a fair amount of time and effort. For example, if you need to set up a years worth of monthly insurance premium payments, where the first payment often differs from the remaining 11, you can enter the first payment as you make it (in the Accounts or Payees View) and then create the remaining payments as a Scheduled Transaction. One simple selection will open a prepopulated dialogue box for editing (and adding) the new Scheduled Transaction; you need only set the Period and the Amount and click/tap on the Save/OK button to create it. You can create Scheduled Transactions in this way for Split, Transfer and Normal Transactions.

Following requests received from users, I have implemented two Home Accountz capabilities that were missing from MyNetWorth, iNetWorth and MyNetWorth for Windows.

Versions 3.2 of both MyNetWorth and iNetWorth (and their Preview equivalents) have been published on the Mac App Store and the App Store. These latest versions are fully compatible with iOS 26 and macOS 26 (Tahoe). They remain compatible with macOS 12 to 15 and with iOS 18 and I have published Mac Catalyst versions of both iNetWorth and iNetWorthPrview.

macOS Tahoe and iOS 26 were published on September 15th. Please do not upgrade your iPhone to iOS 26 immediately. iOS 26 has altered the format of some elements within Toolbars. I use the Toolbars in iNetWorth to display account names and balances in the Accounts View and payee names and balances in the Payees View, primarily to make best use of the iPhone’s limited screen area. The new format can result in balances being truncated in both of these Views in Portrait Mode on an iPhone. My work on a fix is well under way but I will have to carry out some testing before I can submit a new, fully iOS 26 compatible, version of iNetWorth for review and publishing on the App Store; this will take a couple of days or so.

I have made some changes to Schedule View to support the entry of one-off future transactions in MyNetWorth, MyNetWorth for Windows and iNetWorth. Until now users, who want to add one-off future transactions into their accounts have had to do so by entering them in the Accounts or Payees Views, which can make the Current Balance displayed above the list of transactions differ from the actual, real life, current balance. The actual, real life, current balance can be still seen from checking the Running Balance column entry against the current date but this is less than ideal.

MyNetWorth, MyNetWorth for Windows and iNetWorth have all been updated to Version 3.0 recently. Amongst other improvements (such as introducing “stickiness” into the dialogue boxes of MyNetWorth and iNetWorth for editing transactions in the Accounts, Payees and Schedule Views, where switching between normal and split transactions now restores any entries that have been made thus far)1 some important changes have been made to the Schedule View.

When macOS 15 (Sequoia) was released in September 2024, the Mac Catalyst versions of iNetWorth and iNetWorthPreview stopped functioning correctly and rebuilding them with Xcode 16 cured some problems but caused others; I therefore suspended the support of Mac Catalyst versions of iNetWorth and iNetWorthPreview and froze them at Version 2.11.1. However, I recently upgraded my Mac Mini M1 to macOS 15.4.1 and its installed version of Xcode to 16.3. As a result I was able to recompile Mac Catalyst versions of iNetWorth and iNetWorthPreview and got them to run correctly. I have implemented all of the changes introduced into iNetWorth and iNetWorthPreview, since Mac Catalyst version 2.11.1 was released, and I have now published Mac Catalyst version 2.17 of both apps.

As you may have read from my About page, I am the Treasurer of All Saints’ Church, Mattersey, Parochial Church Council (PCC). You may also have seen this post about using MyNetWorth for managing PCC accounts. Up until now, users of MyNetWorth have had to design and build their own Accounts Trees, which is not a trivial undertaking. I run my own PCC’s accounts, using MyNetWorth, and I have recently rebuilt my Accounts Tree to align it closely with the Church of England Financial Return.

If you are a new MyNetWorth or MyNetWorth Preview user, who intends using MyNetWorth to run your Home accounts, you can save some time and effort by importing a set of accounts designed to match my concept of the typical household:

MyNetWorth was inspired by my (happy) experience as a user of Home Accountz for nearly a decade. MyNetWorth is therefore primarily aimed at individual users, who want to manage their personal financial affairs. However, as many of you may already know, I am the Treasurer of a Parochial Church Council (PCC) and I run my PCC’s accounts with MyNetWorth (and iNetWorth when I am away from my Mac Mini). My PCC Accounts have to be inspected each year by an independent examiner before I can submit them to my Annual Parochial Church Meeting (APCM) for approval and then use them to complete and submit my PCC’s Annual Financial Return to our Diocese.

MyNetWorth and its iOS cousin, iNetWorth were inspired by my (happy) experience as a user of Home Accountz for nearly a decade. They are therefore primarily aimed at individual users, who want to manage their personal financial affairs. However, as many of you may already know, I am the Treasurer of a Parochial Church Council (PCC) and I run my PCC’s accounts with MyNetWorth (and iNetWorth on occasions). My PCC’s accounts share much in common with a small business and the reports that I have to produce are very similar to the reports that I used to produce, when I (with the invaluable assistance of my “better half”) ran a Defence Consultancy SME business (for which we used Business Accountz).

Please note that iCloud synching from iOS to macOS devices is occasionally delayed. If you are not prompted to upload an updated file when you run MyNetworth, but you know that you have edited your file in iNetWorth, please check whether your iCloud drive has been synchronised since you edited your file in iNetWorth. Just click on the symbol that appears, when you hover your mouse over the iCloud Drive entry in the Finder app’s Sidebar. A bubble will appear, showing when your iCloud drive was last synchronised.

There is a bug in macOS Sequoia 15.0 and 15.0.1 that (intermittently) affects the setting of the bookmarks that allow MyNetWorth (and MyNetWorth Preview) to gain secure access to its user’s Transactions Files. More details about the bug can be found at this link. The bug has been fixed in macOS 15.1, which has yet to be released. Version 2.17 of MyNetWorth and MyNetWorth Preview, which was published on 20 October, contains a number of minor improvements, including a User Alert, shown below, that appears, if the macOS 15.0 / 15.0.1 bug has impacted your instance of MyNetWorth or MyNetWorth Preview.

I have upgraded my Mac Mini M1 to macOS 15 (Sequoia) and my iPhone and iPad to iOS 18. The upgrade to macOS 15 (Sequoia) appears not to have had an impact on MyNetWorth beyond very occasionally preventing it opening a Transaction File with the alert: “Unable to access selected Transactions File (Sandbox)”. There is no reason for this in the code and it cannot be cleared by changing the code and recompiling; MyNetWorth appears to simply get stuck. Logging out and back in again on my Mac Mini M1 always clears the issue. However, macOS 15 (Sequoia) has stopped the Mac Catalyst version of iNetWorth from functioning correctly and rebuilding it with Xcode 16 cures some problems but causes others. So, I have decided not to publish Mac Catalyst versions of my iOS apps any longer. Unfortunately, I cannot remove Mac Catalyst versions from the Mac App Store; however, I have stopped listing them on my Apps page. If you do run the Mac Catalyst version of iNetWorth and upgrade to macOS 15 (Sequoia), I suggest you buy the NetWorth Bundle and get MyNetWorth at a bargain price.

Are you using a single entry bookkeeping-based accounting app, such as Quicken, Checkbook, MyMoney or Microsoft Money, where you have a number of Bank and/or Credit Card accounts with a range of Income and Expense categories and you manage all of your transactions by adding, editing or deleting single entries against a Bank or Credit card account? Should you consider moving to a double entry bookkeeping-based accounting app, where you have a range of Asset, Liability, Income, Expense and Equity accounts and all of your transactions involve funds moving from one account to another and can be added, edited or deleted in any of your accounts?1

MyNetWorth for Windows is based on MyNetWorth, which was inspired by my (happy) experience as a user of Home Accountz for nearly a decade. As a result MyNetWorth for Windows shares many features and capabilities with Home Accountz. Now that Home Accountz is no longer commercially available or supported, I am hoping to encourage current users of Home Accountz on Windows based devices to migrate to MyNetWorth for Windows.

I must apologise to users of MyNetWorth for Windows, who are having problems with adding new Payees in the Payees View. I am particularly sorry as adding new Payees in Payees View is the recommended action for doing so in the User Guide. When I was testing MyNetWorth for Windows, which I ported to Windows from MyNetWorth for Mac, I carried out most of my testing on a file that was saved in MyNetWorth for Windows format but generated by MyNetWorth for Mac. As a result, I did not test adding new Payees thoroughly enough, until I noticed that duplicate Payees were appearing in normal use, when I was updating my Parochial Church Council (PCC) accounts in MyNetWorth for Windows.

MyNetWorth and iNetWorth share the same file format (.mnydata) so that you can share your data files between your macOS and iOS devices over iCloud. This means that you can access your financial data on both your iPhone / iPad and on your MacBook / iMac. I have recently returned from a week’s holiday in Verona, where I found iNetWorth to be very useful indeed. I did not take my MacBook with me but I did take my iPhone. I was able to record (and reconcile) all of the purchases that I made for meals out, etc., while I was there, rather than having to trawl through a giant set of receipts after I had got back home, which was brilliant!

As you may recall from my about page, I am the treasurer of a Parochial Church Council (PCC). For several years I used Gnucash to manage my PCC’s accounts. Gnucash is an open source multi-platform application that is sophisticated, capable and has some excellent report generating capabilities. However, it is really designed to support large businesses so I found that I was using only a small proportion of its full functions. I also found Gnucash a little cumbersome, it lacks the capability to record (and monitor) payees and I did not like the way in which it handles split transactions. So, I started using MyNetWorth as my PCC accounts manager at the beginning of 2022 and I have found it to be very suitable indeed.

MyNetWorth and its iOS cousin, iNetWorth were inspired by my (happy) experience as a user of Home Accountz for nearly a decade. As a result MyNetWorth and iNetWorth share many features and capabilities with Home Accountz. Now that Home Accountz is no longer commercially available or supported, I am hoping to encourage current Home Accountz users to migrate to MyNetWorth. Users who ran Home Accountz under MS Windows, who lack access to an iMac, Mac Mini, Mac Studio or MacBook but do have access to an iPhone or iPad, can migrate to iNetWorth and I am hoping to encourage them too.

One of the major benefits of using MyNetWorth is its capability to generate bespoke reports to calaculate much of the financial information needed to complete an annual Self Assessment Income Tax Return for the UK HMRC. This post walks you through some of the processes that I used in 2022 to complete my own Self Assessment Income Tax Return. By the way, you can use the same processes in iNetWorth, although I would not recommend trying to do so on an iPhone; using an iPad is much more practical.

You can now purchase both of the latest versions of iNetWorth and MyNetWorth together - at a substantial discount - on the App Store as a NetWorth Bundle. This option offers an affordable way for MyNetWorth users, who own iOS devices, to have full access to their financial data when on the move and away from their macOS device(s).

I recently retired my iMac (21.5-inch, Late 2013) after Apple had decided it was too old to host macOS 11 Big Sur. This is despite my having replaced its standard mechanical HDD with a Crucial 500 Gb SSD, using an OWC upgrade kit. I can recommend OWC. Their products are first class (I put the iMac’s old HDD into an OWC enclosure and used it as a Time Machine backup disk after the upgrade) and the OWC instructions/video on how to carry out the upgrade were also first class. The performance of my upgraded iMac was very good and certainly good enough to run Big Sur but I really wanted to move beyond Catalina so getting a new desktop machine was unavoidable …

When you decide to buy the Full version of MyNetWorth or iNetWorth after trying out the Preview version, you will most likely have saved a number of accounts, account groups, payees and transactions to file; these will be data you will not want to have to re-enter. Fortunately (and intentionally), the file format used by both versions (.mnydata) is identical, so you can open a file saved with the Preview version in the Full version. However, you do need to take care when upgrading to the Full version of iNetWorth. It is essential that you install iNetWorth and move your data file(s) out of your iNetWorthPreview folder before you remove/delete the iNetWorthPreview app from your _iOS_device. This is due to the way iOS sandboxing works.

There are a whole host of competing account and finance related apps available on the App Store and the Mac App Store. Why do I think should you consider buying MyNetWorth, MyNetWorth for Windows and/or iNetWorth? Well, it’s because: