You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Not a problem but a enhancement
Describe the solution you'd like*
Under expenses tab we got a category Investment which is a kind of saving. So if some input with the category Investment is entered then it should be entered under savings table not under expense table. Assume I withdraw 1000 from ATM where do i store that value. If I store it under expenses then it will cause duplication of data.
The text was updated successfully, but these errors were encountered:
Savings page is designed in a different way here - Say you have to buy a Laptop of 70k but you do not have that bulk money right now, so you keep aside a certain amount of money each month until you save 70k, this page is designed to log those savings - ( You are saving to buy something after certain amount of time )
Investment is something you actually get returns after a long amount of time. although there are short term and long term investments , This actually depends. I added this keeping long term investments in mind . but i know this is'nt a exact place to keep track of investment and returns , but i have something to keep track. need to think of this .
In the case of withdrawal of money from ATM - this is just a withdrawal, but what actually you are spending that 1000 RS For are your expenses , so recommend not logging the withdrawals , and just logging the expenses.
Is your feature request related to a problem? Please describe.
Not a problem but a enhancement
Under expenses tab we got a category Investment which is a kind of saving. So if some input with the category Investment is entered then it should be entered under savings table not under expense table. Assume I withdraw 1000 from ATM where do i store that value. If I store it under expenses then it will cause duplication of data.
The text was updated successfully, but these errors were encountered: