github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 19:52:56 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: Handling of negative Transactions for income/funds #2511

New Issue
Closed
opened 2026-02-28 20:16:35 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 20:16:35 -06:00
Owner
Copy Link

Originally created by @Kyrodan on GitHub (Oct 2, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I have a account with two transaction:

  • +100, Category "Income"
  • -10, Category "Income"

Now the amount of "to be budget" is "100". I expect it to be 90 because I don't have 100 bucks available to spend (=> to be budget)

My expectation is, either of these two possibilities:

  1. Lower the "to be budget" amount to "90"
  2. Don't allow negative Transactions for Income-Categories

I prefer option 1.

I can circumvent this behavior if I add the negative transaction to any (budgatable) other category and budget this amount.

My use cases:

  1. I sell something which I have to send my mail. I receive the money on my bank account and pay postage from my cash account. So I add the incoming (positive) transaction to my "selled" income/funds categroy and have postage costs as new (negative) transaction to the same "sell" category added.
  2. Sometimes I have to pay tax, sometimes I get overpaid tax back. I have only one income category "taxes".

If this is not seen as a bug (which would be okay for me because there is a workaround), then this should maybe mentioned in documentation more precisely (e.g on https://actualbudget.org/docs/budgeting/returns-and-reimbursements).

How can we reproduce the issue?

  1. Have a new file with one account and no transactions.
  2. Add 2 transactions as mentioned abobe => balance total is 90
  3. In "Budget" view see "To be budget" => is 100

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Windows 11

Originally created by @Kyrodan on GitHub (Oct 2, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I have a account with two transaction: * +100, Category "Income" * -10, Category "Income" Now the amount of "to be budget" is "100". I expect it to be 90 because I don't have 100 bucks available to spend (=> to be budget) My expectation is, either of these two possibilities: 1. Lower the "to be budget" amount to "90" 2. Don't allow negative Transactions for Income-Categories I prefer option 1. I can circumvent this behavior if I add the negative transaction to any (budgatable) **other** category and budget this amount. My use cases: 1. I sell something which I have to send my mail. I receive the money on my bank account and pay postage from my cash account. So I add the incoming (positive) transaction to my "selled" income/funds categroy and have postage costs as new (negative) transaction to the same "sell" category added. 2. Sometimes I have to pay tax, sometimes I get overpaid tax back. I have only one income category "taxes". If this is not seen as a bug (which would be okay for me because there is a workaround), then this should maybe mentioned in documentation more precisely (e.g on https://actualbudget.org/docs/budgeting/returns-and-reimbursements). ### How can we reproduce the issue? 1. Have a new file with one account and no transactions. 2. Add 2 transactions as mentioned abobe => balance total is 90 3. In "Budget" view see "To be budget" => is 100 ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Windows 11
GiteaMirror added the needs infobug labels 2026-02-28 20:16:35 -06:00
GiteaMirror commented 2026-02-28 20:16:36 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Oct 2, 2025):

Im not able to recreate this. I get 90 as expected in the to budget number. Can you give the details on how to create this problem, or submit a demo file to test with?

@youngcw commented on GitHub (Oct 2, 2025): Im not able to recreate this. I get 90 as expected in the to budget number. Can you give the details on how to create this problem, or submit a demo file to test with?
GiteaMirror commented 2026-02-28 20:16:37 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 10, 2025):

This issue has been automatically closed because there have been no comments for 7 days after the "needs info" label was added. If you still need help, please feel free to reopen the issue with the requested information.

@github-actions[bot] commented on GitHub (Oct 10, 2025): This issue has been automatically closed because there have been no comments for 7 days after the "needs info" label was added. If you still need help, please feel free to reopen the issue with the requested information.
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 bug needs info
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#2511
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?