github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 12:28:57 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #3230] [Bug]: Upcoming transfer transactions show incorrect payment/debit direction in one account in PWA #50442

New Issue
Closed
opened 2026-04-30 15:06:33 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-30 15:06:33 -05:00
Owner
Copy Link

Originally created by @ToniCipriani on GitHub (Aug 10, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/3230

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

To reproduce, create 2 scheduled transactions that are functionally the same (e.g. Savings -> Chequing), but with Payee/Account and +/- swapped. These two transactions are doing the same thing:

image

On Desktop, both transactions show up correctly in both accounts as depositing to Chequing as well as payment from Savings:

image
image

However on PWA they show the the payment amount as-is entered in the Scheduled rule without considering direction.

image

In the above, both scheduled transactions should show as a deposit/green in Chequing and payment/red in Savings.

Test budget attached.
2024-08-10-Test Budget.zip

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Other

Operating System

Mobile Device

Originally created by @ToniCipriani on GitHub (Aug 10, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/3230 ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? To reproduce, create 2 scheduled transactions that are functionally the same (e.g. Savings -> Chequing), but with Payee/Account and +/- swapped. These two transactions are doing the same thing: ![image](https://github.com/user-attachments/assets/00de5224-a860-4f70-89cf-287c4460b752) On Desktop, both transactions show up correctly in both accounts as depositing to Chequing as well as payment from Savings: ![image](https://github.com/user-attachments/assets/0310975e-ad5d-46ef-ac8a-9a7c919adc15) ![image](https://github.com/user-attachments/assets/09b78a0a-686a-4f41-9fd4-ac5f08ac425d) However on PWA they show the the payment amount as-is entered in the Scheduled rule without considering direction. ![image](https://github.com/user-attachments/assets/605f3a3f-e841-4ce9-a0c7-2b5a7107dfe0) In the above, both scheduled transactions should show as a deposit/green in Chequing and payment/red in Savings. Test budget attached. [2024-08-10-Test Budget.zip](https://github.com/user-attachments/files/16570038/2024-08-10-Test.Budget.zip) ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Other ### Operating System Mobile Device
GiteaMirror added the bug label 2026-04-30 15:06:33 -05:00
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
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#50442
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?