One of the main reasons I stick with Gnucash is the monolithic file format. If one day I need an accountant to review my finances, or if I suffer an audit by the tax man, I can send on the single .gnucash file with all my data. While Gnucash's UI is not the greatest, an accountant/auditor can easily install Gnucash and generate reports with only basic knowledge.
Another nice feature is the file linkage features, where I can directly link my payslip pdf files to the gnucash entries. I have folder structure on my GDrive with all of my stored bills, payslips etc. If required, I can zip up my Gnucash file and corresponding documents folder and the reviewer can instantly access important financial documentation from within the Gnucash application. Gnucash uses relative file paths for sourcing linked documents - all a reviewer has to do is specify the head directory and all the linked documents will open as usual. Correct me if I'm wrong, but I dont think this is a feature in the text-only approaches.
Roughly 100 transactions per month I would say. On average 2 card based transactions per day --> 60 transactions per month. Then bills, incidentals and direct debits make up the remaining 40.
I never did any personal bookkeeping before I used GnuCash. I was however self-learning basic accounting for my startup at the time where we use the cloud-based software package Sage Accounting. After a few months of using Sage I was interested in applying similar methods to my personal finances and discovered Gnucash along the way.
Cash is a tricky one. Generally I keep cash spends to a minimum. Any small cash withdrawls from my account are generally expense straight into Expenses:Cash Misc. and I don't bother tracking the inidividal cash payments.
However if it is a large cash amount (e.g. rent payment) then I will transfer from Asset:Bank to Asset:Cash before entering into Expenses:Rent.
I gave up early on with importing bank statements. Instead I just manually create each gnucash entry for each transaction on my online bank statement. If the final gnucash account balance matches my actual bank balance then I know I did it correctly. If it does not balance, I persist in finding the mistyped entry.
This method relies on balancing to the cent each time, since I use my actual bank balance as the target.
It is indeed tedious at first, however I find that 1) manually entering transactions helps me spot problem payments quickly (comprimised credit card, overcharges on direct debits etc.) and 2) the predictive auto-complete feature speeds entries up over time, as most entries are assigned to either a a)groceries, b)eating-out or c)bills expense account. You just press 'Tab' when the correct suggestion pops-up after entring the first few letter, and the line entry gets auto-filled. I still usually need to change the numerical value, but the correct expense account and transaction detail are prepopulated correctly most of the time.
Overall I would recommend giving it another chance.
I've been using Gnucash since 2020 to manage personal expenses and income, and it has made the world of a difference. In particular, I find the income statement feature very powerful when I'm doing an end-of-year review of my spending.
In terms of time commitment, about 20 mins every two weeks seems to be enough for logging all my transactions into Gnucash - I have 3 bank accounts, 1 investment account and 1 retirement account.
One of the main reasons I stick with Gnucash is the monolithic file format. If one day I need an accountant to review my finances, or if I suffer an audit by the tax man, I can send on the single .gnucash file with all my data. While Gnucash's UI is not the greatest, an accountant/auditor can easily install Gnucash and generate reports with only basic knowledge.
Another nice feature is the file linkage features, where I can directly link my payslip pdf files to the gnucash entries. I have folder structure on my GDrive with all of my stored bills, payslips etc. If required, I can zip up my Gnucash file and corresponding documents folder and the reviewer can instantly access important financial documentation from within the Gnucash application. Gnucash uses relative file paths for sourcing linked documents - all a reviewer has to do is specify the head directory and all the linked documents will open as usual. Correct me if I'm wrong, but I dont think this is a feature in the text-only approaches.