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

[Bug]: Auto-generated schedules don't seem to work with new transactions #1465

New Issue
Closed
opened 2026-02-28 19:44:15 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 19:44:15 -06:00
Owner
Copy Link

Originally created by @mullermn on GitHub (Oct 4, 2024).

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?

I have recently moved to Actual from YNAB4 and done an import of that budget. I used the autodiscovery of schedules feature and set up a load of rules. I've then set up GoCardless and started receiving live transactions, but they never seem to match automatically.

I have been through these very carefully (and it's many rules, not a single rule) and I've checked every single field, and also messed around with the fields to try and make them more tolerant to get a match, but I cannot get it to work. It's like there's some hidden attribute in the auto generated schedule that is being compared and preventing a match.

Rule description

And here's the new transaction that should have matched:

Should have matched

When I create a new schedule based on the current transaction, it doesn't match the pre-Actual ones either. I backedated the one in this screenshot to August and it hasn't matched August or September.

image

These Tesla payments happen to be almost perfectly consistent in date/amount etc so there is no (logical) reason why they wouldn't all match, unless the rule is incorporating baggage that it imported from YNAB in its matching logic behind the scenes?

At least one other user thinks they are experiencing this:
https://discord.com/channels/937901803608096828/1291668861233659904

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Safari, Desktop App (Electron)

Operating System

Mac OSX

Originally created by @mullermn on GitHub (Oct 4, 2024). ### 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? I have recently moved to Actual from YNAB4 and done an import of that budget. I used the autodiscovery of schedules feature and set up a load of rules. I've then set up GoCardless and started receiving live transactions, but they never seem to match automatically. I have been through these very carefully (and it's many rules, not a single rule) and I've checked every single field, and also messed around with the fields to try and make them more tolerant to get a match, but I cannot get it to work. It's like there's some hidden attribute in the auto generated schedule that is being compared and preventing a match. ![Rule description](https://github.com/user-attachments/assets/0d764229-a6fc-4164-954e-aadf215b41e2) And here's the new transaction that should have matched: ![Should have matched](https://github.com/user-attachments/assets/f3ae651d-284a-4d1e-9959-9bc65dfae8a0) When I create a new schedule based on the current transaction, it doesn't match the pre-Actual ones either. I backedated the one in this screenshot to August and it hasn't matched August or September. ![image](https://github.com/user-attachments/assets/6d4c6402-b99a-4af5-a422-8e87f2a1a549) These Tesla payments happen to be almost perfectly consistent in date/amount etc so there is no (logical) reason why they wouldn't all match, unless the rule is incorporating baggage that it imported from YNAB in its matching logic behind the scenes? At least one other user thinks they are experiencing this: https://discord.com/channels/937901803608096828/1291668861233659904 ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Safari, Desktop App (Electron) ### Operating System Mac OSX
GiteaMirror added the bank syncneeds infobugschedules labels 2026-02-28 19:44:15 -06:00
GiteaMirror commented 2026-02-28 19:44:16 -06:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Aug 16, 2025):

Hey 👋

Can you confirm that you're still seeing this issue on a more recent version?

@MikesGlitch commented on GitHub (Aug 16, 2025): Hey 👋 Can you confirm that you're still seeing this issue on a more recent version?
GiteaMirror commented 2026-02-28 19:44:17 -06:00
Author
Owner
Copy Link

@mullermn commented on GitHub (Aug 18, 2025):

I'm afraid I don't have time to reconstruct the test scenario for the YNAB4 import to retest, and speaking selfishly it's no longer relevant for me (having migrated to Actual nearly a year ago), so if nobody else is complaining I think it could be closed.

@mullermn commented on GitHub (Aug 18, 2025): I'm afraid I don't have time to reconstruct the test scenario for the YNAB4 import to retest, and speaking selfishly it's no longer relevant for me (having migrated to Actual nearly a year ago), so if nobody else is complaining I think it could be closed.
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 bank sync bug needs info schedules
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#1465
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?