github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #1839] [Feature] Sub-accounts #26490

New Issue
Closed
opened 2026-04-18 02:42:21 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-18 02:42:21 -05:00
Owner
Copy Link

Originally created by @kabo on GitHub (Oct 29, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1839

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

We have a revolving credit account. This means we can withdraw up to -$X from the account, but we only pay interest on the money we have withdrawn. If the account balance is $0 or higher we pay zero interest.

So naturally we want to have as much cash as possible in this account. So we dump all my money, my partner's money, etc. into this one account.

It would be great if accounts could have sub-accounts so we can easily see what money is in there, which account or purpose it belongs to.

By purpose I mean we have some payments that are only paid 3/times year. We could create sub-accounts for those things and transfer a quarter of the upcoming payment each month into that sub-account.

This keeps the grand total for the account correct and easily verifiable, money isn't sent of to expenses that haven't happened yet, and lets us know we're on track for upcoming payments.

Describe your ideal solution to this problem

Accounts should be able to have sub-accounts, accounts that aren't physical accounts, but partitions in a physical account.

This would allow us to save up for future payments or for bigger things, while keeping the money in the same physical account.

Could be nested as well, e.g.

All accounts $90
├── BankA $30
│   └── AccX $30
│       ├── Purpose1 $10
│       └── Purpose2 $20
├── BankB $60
│   └── AccY $50
│       ├── Purpose3 $20
│       └── Purpose4 $30
│   └── AccZ $10
└── BankC $0
    └── AccZZ $0

Teaching and learning

I feel like some sort of tree structure should make it fairly clear.

Originally created by @kabo on GitHub (Oct 29, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1839 ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? We have a revolving credit account. This means we can withdraw up to -$X from the account, but we only pay interest on the money we have withdrawn. If the account balance is $0 or higher we pay zero interest. So naturally we want to have as much cash as possible in this account. So we dump all my money, my partner's money, etc. into this one account. It would be great if accounts could have sub-accounts so we can easily see what money is in there, which account or purpose it belongs to. By purpose I mean we have some payments that are only paid 3/times year. We could create sub-accounts for those things and transfer a quarter of the upcoming payment each month into that sub-account. This keeps the grand total for the account correct and easily verifiable, money isn't sent of to expenses that haven't happened yet, and lets us know we're on track for upcoming payments. ### Describe your ideal solution to this problem Accounts should be able to have sub-accounts, accounts that aren't physical accounts, but partitions in a physical account. This would allow us to save up for future payments or for bigger things, while keeping the money in the same physical account. Could be nested as well, e.g. ``` All accounts $90 ├── BankA $30 │   └── AccX $30 │   ├── Purpose1 $10 │   └── Purpose2 $20 ├── BankB $60 │   └── AccY $50 │   ├── Purpose3 $20 │   └── Purpose4 $30 │ └── AccZ $10 └── BankC $0 └── AccZZ $0 ``` ### Teaching and learning I feel like some sort of tree structure should make it fairly clear.
GiteaMirror added the needs votesfeature labels 2026-04-18 02:42:22 -05:00
GiteaMirror commented 2026-04-18 02:42:24 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 29, 2023):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:1784041187 --> @github-actions[bot] commented on GitHub (Oct 29, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-04-18 02:42:25 -05:00
Author
Owner
Copy Link

@normanu commented on GitHub (Nov 2, 2023):

same as https://github.com/actualbudget/actual/issues/1320 ?

<!-- gh-comment-id:1790955436 --> @normanu commented on GitHub (Nov 2, 2023): same as https://github.com/actualbudget/actual/issues/1320 ?
GiteaMirror commented 2026-04-18 02:42:26 -05:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 2, 2023):

Correct me if I am wrong, but I would say it's different, this would be in Accounts, not Budget. I would like this for my savings account. I would designate different funds within my savings account without having to open a new account with the bank. For example, for a new car, and saving for a vacation. I attached an image, though I do think @kabo's diagram is better. I do see an issue to overcome: If I were to take out more money than is in one of the sub-accounts, how would Actual determine which sub-account to pull from next?
image

<!-- gh-comment-id:1791013358 --> @ghost commented on GitHub (Nov 2, 2023): Correct me if I am wrong, but I would say it's different, this would be in Accounts, not Budget. I would like this for my savings account. I would designate different funds within my savings account without having to open a new account with the bank. For example, for a new car, and saving for a vacation. I attached an image, though I do think @kabo's diagram is better. I do see an issue to overcome: If I were to take out more money than is in one of the sub-accounts, how would Actual determine which sub-account to pull from next? ![image](https://github.com/actualbudget/actual/assets/87683650/81efbdfc-dac0-4b99-aa32-4d26e177fc12)
GiteaMirror commented 2026-04-18 02:42:26 -05:00
Author
Owner
Copy Link

@kabo commented on GitHub (Nov 14, 2023):

In my mind sub-accounts can go negative. So not sure that needs to be a problem.

<!-- gh-comment-id:1809494519 --> @kabo commented on GitHub (Nov 14, 2023): In my mind sub-accounts can go negative. So not sure that needs to be a problem.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#26490
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?