github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-11 09:38:37 -05:00
Code Issues 1.6k Packages Projects Releases 57 Wiki Activity

[Feature] Transaction Rounding (Up/Down) in Split Transaction / Rules to Automate This #2097

New Issue
Closed
opened 2026-02-28 20:03:21 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 20:03:21 -06:00
Owner
Copy Link

Originally created by @stephenmoore33 on GitHub (May 5, 2025).

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?

Finding that my wife and I were getting deeper and deeper into a financial problem, about 2 years ago, we adopted the Cash envelope method. Each pay, we pay our bills first, then withdraw physical cash from our bank and fill envelopes for regular spending. This worked very well, and we have built enough discipline to do this virtually. Hence, we are using Actual Budget.

Actual Budget server works great for us (me, as a home-lab dabbler). However, one feature that is not in Actual Budget is the ability to round-up to the next dollar in a category.

When we paid with physical cash, any change that was given back to us was set aside and put in a piggy bank for our son. Over just a few short months, it’s grown quite substantially, and we didn’t notice it financially.

Rounding up/down into different categories within Ac

Image

tual Budget would allow us to continue to build our son's savings account without noticing it.

Describe your ideal solution to this problem

Having the ability to create a rule to perhaps split a transaction and round up the change into another category would be very helpful.

However, this does bring up the potential issue of Actual Budget increasing the amount of the original transaction.

When I split a transaction manually and round up the change into another account, the banner to fund the remaining amount (even though it is negative) is persistent.

This banner is still needed, in the event of over-funding a split transaction, in case the user does this by mistake. However, if the amount is negative in a split, there could be a boolean checkbox within the amount left banner to "Dismiss Negative Amount".

While I am not familiar with the schema of Actual Budget's database, I would assume that a boolean column for split transactions would need to be created for dismiss_negative in order for this to work.

I also previously mentioned having the ability to automate this with rules; if a separate issue is needed for this, I would be happy to create one.

(Assuming) TO-DO Tasks:

  • Database - Create a column for dismiss_negative (or dismiss_variance if rounding down) in a split transaction
  • Front End - Add a boolean checkbox on Accounts > On Budget for the "Amount Left" modal for split transactions, that when checked, "dismiss_variance" is set to true on the database for the split transaction, and the message disappears.

TO-DO Tasks (for rules):

  • When creating/editing a rule with a Split transaction, in the allocate section, add option "Round Up/Down to nearest dollar"
  • Additional database schema modifications would likely be required for this.

Teaching and learning

This would be beneficial for users who want to fund other categories by rounding change. A separate page within the Documentation should be created explaining how to use the rounding feature by rules in Actual Budget.

Image

Originally created by @stephenmoore33 on GitHub (May 5, 2025). ### 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? Finding that my wife and I were getting deeper and deeper into a financial problem, about 2 years ago, we adopted the Cash envelope method. Each pay, we pay our bills first, then withdraw physical cash from our bank and fill envelopes for regular spending. This worked very well, and we have built enough discipline to do this virtually. Hence, we are using Actual Budget. Actual Budget server works great for us (me, as a home-lab dabbler). However, one feature that is not in Actual Budget is the ability to round-up to the next dollar in a category. When we paid with physical cash, any change that was given back to us was set aside and put in a piggy bank for our son. Over just a few short months, it’s grown quite substantially, and we didn’t notice it financially. Rounding up/down into different categories within Ac ![Image](https://github.com/user-attachments/assets/b3f3faed-8223-4a27-ab2f-a5c4a73d0611) tual Budget would allow us to continue to build our son's savings account without noticing it. ### Describe your ideal solution to this problem Having the ability to create a rule to perhaps split a transaction and round up the change into another category would be very helpful. However, this does bring up the potential issue of Actual Budget increasing the amount of the original transaction. When I split a transaction manually and round up the change into another account, the banner to fund the remaining amount (even though it is negative) is persistent. This banner is still needed, in the event of over-funding a split transaction, in case the user does this by mistake. However, if the amount is negative in a split, there could be a boolean checkbox within the amount left banner to "Dismiss Negative Amount". While I am not familiar with the schema of Actual Budget's database, I would assume that a boolean column for split transactions would need to be created for dismiss_negative in order for this to work. I also previously mentioned having the ability to automate this with rules; if a separate issue is needed for this, I would be happy to create one. (Assuming) TO-DO Tasks: - Database - Create a column for dismiss_negative (or dismiss_variance if rounding down) in a split transaction - Front End - Add a boolean checkbox on Accounts > On Budget for the "Amount Left" modal for split transactions, that when checked, "dismiss_variance" is set to true on the database for the split transaction, and the message disappears. TO-DO Tasks (for rules): - When creating/editing a rule with a Split transaction, in the allocate section, add option "Round Up/Down to nearest dollar" - Additional database schema modifications would likely be required for this. ### Teaching and learning This would be beneficial for users who want to fund other categories by rounding change. A separate page within the Documentation should be created explaining how to use the rounding feature by rules in Actual Budget. ![Image](https://github.com/user-attachments/assets/a6357a6e-6713-4c75-91ac-03b80850f929)
GiteaMirror added the needs votesfeature labels 2026-02-28 20:03:22 -06:00
GiteaMirror commented 2026-02-28 20:03:22 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 5, 2025):

✨ 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 (May 5, 2025): :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 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#2097
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?