Saving goals with limit cap

Sjeefr

The 25 sub-accounts per account easily allows creating multiple saving goals/sub-accounts for a variety of goals, such as ‘car services’ and ‘medical emergencies’. Instead of having one large pile, it might be smarter to have separate jars, to have a better understanding of how much cash is reserved for each purpose.

Alright, so you are splitting your paycheck into those jars and see your money stack. At one point, those savings might go beyond a baseline and there is no reason to save any further. At this point, the Saving goals with limit caps come into play.

Limiting your saving goals might solve reaching other saving goals (as excess savings is forwarded elsewhere), allow better budgeting or enjoy an even more worry-free life as you are prepared for each occasion. And all those accounts with 100% might bring a smile as well.

Joeri-Silver-Lynx

Great Idea! 😁 Very well written: "Limiting your saving goals might solve reaching other saving goals (as excess savings is forwarded elsewhere), allow better budgeting or enjoy an even more worry-free life as you are prepared for each occasion"

Your idea has (let's call them) domino-day design decisions.

I could answer them for you with what I would want, but maybe it is more fun for you if I ask questions and you provide your thoughts.

Setting the stage for you:
- Using different transactions or splitting paycheck results in filling up various sub-accounts and saving goals.

Let's for the sake or argument say that your idea of saving caps is not limited to Saving accounts because those accounts have other limitations itself (like not being able to connect) and your idea in essence could be bigger than only saving accounts. Let's not limit ourselves just yet.

Imagine having 5 sub-accounts for various purposes. A (€475),B(€495),C(100),D(60%),E(20%)
In line of your proposed idea limits have been set in 100% for a savings sub-account or a number-limit for a normal sub-account. A, B (Cap: 500 euro), C, D, E (100%)
Now, the big transaction is happening.
Sub-account A is reaching 500 euros

Q1: What do you want to happen in this case?

Q2: If the system *{insert desired behaviour here, Q1-answer} accomplishes it successfully, what does the system need to know to accomplish that, besides the previous set caps you proposed in your core idea?

Q3: If the system needs to know {insert Q2-answer} here, how do you want the user to communicate that information to the system/app? Describe superficially what and how is 'communicated'/entered.

Q4: About Q2's answer, is that information always the same, or can it change over time?"

Q5: If Q2's answer can change of time, based on what information* or personal imagined factors would your answer of Q2 change? Why isn't it static? What causes the differences if any?

And now, going full circle:
Q6: If Q5's answer contains various scenario's, would Q3's answer by any chance be depended on Q2's dynamic answer? If so, do you have any idea how to coop with this dynamic behaviour?

Please note that if the dominos are falling in your head, you are always free to answer '42' or say you want an AI-entity to take a best guess on what you want automagically. 🧙‍♂️

* At this point you might think I am messing with you, I am not, I am having fun though with the material though. 🤓😊