github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-25 07:42:48 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Ability to "hold" money via the API #767

New Issue
Closed
opened 2026-02-28 19:18:22 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:18:22 -06:00
Owner
Copy Link

Originally created by @jat255 on GitHub (Nov 27, 2023).

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?

When importing from other tools (such as financier.io or nYNAB), their default strategy is that income gets assigned to the "next month", in that it is available to budget in the month after the income is received, in order to encourage people to live one month behind and stop any paycheck to paycheck behavior.

When migrating budgets from a tool like this to Actual, this results in the monthly "available to budget" amounts being off, since all income goes to the month it is received in Actual. At first glance, it looks like something happened with the import to make the values all be off, but this can be corrected by clicking on the 'to budget' amount, then "hold for next month", then pressing enter for every month. For a large budget (mine goes back to 2015), this has to be done many many times.

Describe your ideal solution to this problem

I would suggest a new API function named setBudgetForNextMonth(month, amount: optional). If no amount is given, it will default to whatever the current "To budget" amount is. If an amount is given, it will behave identically to the UI workflow of (1) clicking on to budget, (2) clicking "hold for next month", and (3) entering an amount.

(I checked that I'd be open to implementing this feature, but I am a very novice javascript programmer...)

Teaching and learning

Add documentation of the new API function in the API docs

Originally created by @jat255 on GitHub (Nov 27, 2023). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [X] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? When importing from other tools (such as financier.io or nYNAB), their default strategy is that income gets assigned to the "next month", in that it is available to budget in the month after the income is received, in order to encourage people to live one month behind and stop any paycheck to paycheck behavior. When migrating budgets from a tool like this to Actual, this results in the monthly "available to budget" amounts being off, since all income goes to the month it is received in Actual. At first glance, it looks like something happened with the import to make the values all be off, but this can be corrected by clicking on the 'to budget' amount, then "hold for next month", then pressing enter for every month. For a large budget (mine goes back to 2015), this has to be done many many times. ### Describe your ideal solution to this problem I would suggest a new API function named `setBudgetForNextMonth(month, amount: optional)`. If no `amount` is given, it will default to whatever the current "To budget" amount is. If an amount is given, it will behave identically to the UI workflow of (1) clicking on to budget, (2) clicking "hold for next month", and (3) entering an amount. (I checked that I'd be open to implementing this feature, but I am a _very_ novice javascript programmer...) ### Teaching and learning Add documentation of the new API function in the API docs
GiteaMirror added the feature label 2026-02-28 19:18:22 -06:00
GiteaMirror commented 2026-02-28 19:18:23 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 27, 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 👍!

@github-actions[bot] commented on GitHub (Nov 27, 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 -->
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
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#767
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?