[GH-ISSUE #1253] [Bug]: Budget can't be balanced when "Hide decimal places" in the setting is on. #49590

Closed
opened 2026-04-30 11:10:33 -05:00 by GiteaMirror · 5 comments
Owner

Originally created by @Barkov-F on GitHub (Jul 1, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1253

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When I budget using the whole numbers I sometimes get very annoying red zeros, which @j-f1 and I see as an unintended consequence of getting rid of the decimals. I've raised the issue on the support channel on discord

What error did you receive?

No response

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @Barkov-F on GitHub (Jul 1, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1253 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? When I budget using the whole numbers I sometimes get very annoying red zeros, which @j-f1 and I see as an unintended consequence of getting rid of the decimals. I've raised the issue on the support channel on [discord](https://discord.com/channels/937901803608096828/1121540590425878682) ### What error did you receive? _No response_ ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the bug label 2026-04-30 11:10:33 -05:00
Author
Owner

@aloysb commented on GitHub (Jan 7, 2025):

To reproduce

  1. Go to rules
  2. Tick "Hide decimals place"
  3. Set a budget to 100 to new category "Power"
  4. Add a transaction towards the new category "Power" of 100.01
  5. In budget, the number will appear as -0 in red.

I'll have a look at how to a best address this, but the first thing that comes to mind is to truncate the number when evaluating it when decimals are hidden.

image
<!-- gh-comment-id:2574306745 --> @aloysb commented on GitHub (Jan 7, 2025): # To reproduce 1. Go to rules 2. Tick "Hide decimals place" 3. Set a budget to 100 to new category "Power" 4. Add a transaction towards the new category "Power" of 100.01 5. In budget, the number will appear as -0 in red. I'll have a look at how to a best address this, but the first thing that comes to mind is to truncate the number when evaluating it when decimals are hidden. <img width="785" alt="image" src="https://github.com/user-attachments/assets/e3cab1a6-2638-4f79-a410-17ed55eb4dfc" />
Author
Owner

@CosineP commented on GitHub (Sep 27, 2025):

Bump to this bug. Is there a bug bounty program? I would happily pay $30 to have it fixed, since it is my primary frustration as opposed to other paid services.

My two cents (as it were): I think the behavior is almost correct - cents should be included in all calculations, even when hidden. However, when evaluating if a category is overspent, -0.99 should count as NOT over budget.

<!-- gh-comment-id:3341830427 --> @CosineP commented on GitHub (Sep 27, 2025): Bump to this bug. Is there a bug bounty program? I would happily pay $30 to have it fixed, since it is my primary frustration as opposed to other paid services. My two cents (as it were): I think the behavior is almost correct - cents *should* be included in all calculations, even when hidden. However, when evaluating if a category is overspent, -0.99 should count as NOT over budget.
Author
Owner

@Barkov-F commented on GitHub (Sep 30, 2025):

I see it as an UI issue, not a logic one. When the decimals are off, behind the scene each and every cent should be accounted for, but the view should reflect more lenient approach to balancing, allowing for overspending up to 0,50 and rounding it to -1 otherwise. Similarly, I think that the monthly totals should follow the same route.

<!-- gh-comment-id:3351859068 --> @Barkov-F commented on GitHub (Sep 30, 2025): I see it as an UI issue, not a logic one. When the decimals are off, behind the scene each and every cent should be accounted for, but the view should reflect more lenient approach to balancing, allowing for overspending up to 0,50 and rounding it to -1 otherwise. Similarly, I think that the monthly totals should follow the same route.
Author
Owner

@rcgomezap commented on GitHub (Jan 21, 2026):

Hello @Barkov-F , @MatissJanis

Just a heads up — this issue should already be resolved by PR #6274 , which has been merged.

Unless there’s something I’m missing, I think this issue can be closed. Thanks!

<!-- gh-comment-id:3775986846 --> @rcgomezap commented on GitHub (Jan 21, 2026): Hello @Barkov-F , @MatissJanis Just a heads up — this issue should already be resolved by PR #6274 , which has been merged. Unless there’s something I’m missing, I think this issue can be closed. Thanks!
Author
Owner

@MatissJanis commented on GitHub (Jan 21, 2026):

Thanks @rcgomezap . It does seem your PR has solved this. Will close this off for now, but if anyone objects - please let me know the steps how we can still reproduce an issue here and I will re-open.

<!-- gh-comment-id:3781101085 --> @MatissJanis commented on GitHub (Jan 21, 2026): Thanks @rcgomezap . It does seem your PR has solved this. Will close this off for now, but if anyone objects - please let me know the steps how we can still reproduce an issue here and I will re-open.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#49590