github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #4684] [Bug]: Incorrect payee on scheduled transactions #43642

New Issue
Closed
opened 2026-04-26 04:16:02 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-26 04:16:02 -05:00
Owner
Copy Link

Originally created by @newtoat on GitHub (Mar 24, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4684

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

For the past few months I've seen an issue where scheduled transactions map to the wrong payee. I think it started this year (i.e. 2025.1 onwards) but as my Schedules are monthly I didn't notice it straight away, and I don't think an update introduced the issue, I think I've just mangled the data somehow.

When looking at a Schedule, it shows the correct Payee / Account for the scheduled transaction.
When looking at the transactions list, the upcoming transactions show the schedule with the wrong Payee / Account.
When Posting the transaction, it then maps the transaction to the wrong Payee / Account.

What's interesting is that the incorrect payees used is one of my accounts and so the transactions end up as transfers when Posting the transaction:

Image Image Image

Note that while these aren't fully sanitised, I've done this intentionally to demonstrate they are the same transactions easier.

How can we reproduce the issue?

I don't know for sure how to recreate it - I was cleaning up some Schedules and ended up deleting the existing ones and re-using the find tool to re-create them.
Appreciate that doesn't do much to help, I've tried exporting and re-importing the database, resetting the cache, resetting the sync, deleting the Schedule and recreating, updating the Schedule to a different payee and back again.

Happy to delete the transactions in my budget and upload a slimmed down copy of it if required.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox, Chrome, Safari, Microsoft Edge, Desktop App (Electron)

Operating System

Linux

Originally created by @newtoat on GitHub (Mar 24, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4684 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? For the past few months I've seen an issue where scheduled transactions map to the wrong payee. I think it started this year (i.e. 2025.1 onwards) but as my Schedules are monthly I didn't notice it straight away, and I don't think an update introduced the issue, I think I've just mangled the data somehow. When looking at a Schedule, it shows the correct Payee / Account for the scheduled transaction. When looking at the transactions list, the upcoming transactions show the schedule with the wrong Payee / Account. When Posting the transaction, it then maps the transaction to the wrong Payee / Account. What's interesting is that the incorrect payees used is one of my accounts and so the transactions end up as transfers when Posting the transaction: <img width="253" alt="Image" src="https://github.com/user-attachments/assets/3c124efe-3e36-4753-948d-62eb8ac97d8d" /> <img width="1307" alt="Image" src="https://github.com/user-attachments/assets/62b50e0b-ded9-42cc-b104-d87e65aa970f" /> <img width="700" alt="Image" src="https://github.com/user-attachments/assets/98e38d32-173a-4875-9a86-b6365bcd1fb2" /> Note that while these aren't fully sanitised, I've done this intentionally to demonstrate they are the same transactions easier. ### How can we reproduce the issue? I don't know for sure how to recreate it - I was cleaning up some Schedules and ended up deleting the existing ones and re-using the find tool to re-create them. Appreciate that doesn't do much to help, I've tried exporting and re-importing the database, resetting the cache, resetting the sync, deleting the Schedule and recreating, updating the Schedule to a different payee and back again. Happy to delete the transactions in my budget and upload a slimmed down copy of it if required. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox, Chrome, Safari, Microsoft Edge, Desktop App (Electron) ### Operating System Linux
GiteaMirror added the bug label 2026-04-26 04:16:02 -05:00
GiteaMirror commented 2026-04-26 04:16:03 -05:00
Author
Owner
Copy Link

@alecbakholdin commented on GitHub (Mar 24, 2025):

Make sure you check your rules. One of them may be renaming Natwest Bills to a transfer.

<!-- gh-comment-id:2748874780 --> @alecbakholdin commented on GitHub (Mar 24, 2025): Make sure you check your rules. One of them may be renaming Natwest Bills to a transfer.
GiteaMirror commented 2026-04-26 04:16:05 -05:00
Author
Owner
Copy Link

@newtoat commented on GitHub (Mar 24, 2025):

Yep, it was a rule 🤦‍♂️

I had somehow ended up with an 'imported payee = nothing' rule. Didn't realise that it would also apply to non-imported transactions / transactions created directly in the applications.

Image

Appreciate the steer, thanks!

<!-- gh-comment-id:2749245898 --> @newtoat commented on GitHub (Mar 24, 2025): Yep, it was a rule 🤦‍♂️ I had somehow ended up with an 'imported payee = nothing' rule. Didn't realise that it would also apply to non-imported transactions / transactions created directly in the applications. <img width="917" alt="Image" src="https://github.com/user-attachments/assets/c0963371-205c-4020-bfd2-ff3153c05620" /> Appreciate the steer, thanks!
GiteaMirror commented 2026-04-26 04:16:05 -05:00
Author
Owner
Copy Link

@alecbakholdin commented on GitHub (Mar 24, 2025):

Glad I could help!

<!-- gh-comment-id:2749247539 --> @alecbakholdin commented on GitHub (Mar 24, 2025): Glad I could help!
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#43642
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?