The first thing you should do is to read this (from 2010). If that doesn't convince you, the read this (from 2014) and this (from 2017). Developers are discovering that SQL, transactions and consistency weren't such old-hat after all!
NoSQL is a tasty soufflé composed of more air than substance. There are some cases for which NoSQL is a good fit, and those are NOT finance management apps!
You abdsolutely want strong consistency for anything to do with monetary activities! NoSQL is one of those industry bandwagons which come along from time to time, like a star which is about to go supernova, briefly shines brightly, only to explode, then withers and dies a lingering and painful death much like a white dwarf!
NoSQL paradigms are good for social media type sites (i.e. the user typically isn't paying anything, or for only a small subset of services) where absolute consistency (through proper transactions) isn't a priority.
Systems such as marketing and/or analysis and/or reporting apps could be NoSQL. However, SQL is also great for slicing and dicing data for marketng, analysis and reporting. See Brian Aker's (former MySQL chief architect) hilarious take on NoSQL here.
From a similar thread about banking, there is a suggestion that NoSQL could be suitable for banking if the system has strong consistency and transactions - which brings us back to the RDBMS anyway. This is sort of the point of the 2014 link above - i.e. that NoSQL systems are all trying to put a strongly consistent SQL layer above their systems - we're back to the classic database: It's like déjà vu all over again :-).
Take a look at what Michael Stonebraker - a man who knows a thing or two about databases calls NoSQL a giant step backwards. He proposes "NewSQL" which "all support the relational data model and use SQL as their primary interface".