[Bug]: Bank Imports before budget start date #609

Closed
opened 2026-02-28 19:11:16 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @kennylarsen on GitHub (Aug 31, 2023).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Using the GoCardless transaction import I am sometimes getting transactions imported prior to the budget start date. This seems a little hit and miss, sometimes they appear sometimes they don't. Do we need some kind of filter which drops everything before the starting balance date?

What error did you receive?

No response

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

Microsoft Edge

Operating System

Windows 11

Originally created by @kennylarsen on GitHub (Aug 31, 2023). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? Using the GoCardless transaction import I am sometimes getting transactions imported prior to the budget start date. This seems a little hit and miss, sometimes they appear sometimes they don't. Do we need some kind of filter which drops everything before the starting balance date? ### What error did you receive? _No response_ ### Where are you hosting Actual? Fly.io ### What browsers are you seeing the problem on? Microsoft Edge ### Operating System Windows 11
GiteaMirror added the transaction importbug labels 2026-02-28 19:11:16 -06:00
Author
Owner

@youngcw commented on GitHub (Feb 4, 2024):

Has this been seen recently? The bank sync logic should check for the first transaction in an account and never pull from further back then that.

@youngcw commented on GitHub (Feb 4, 2024): Has this been seen recently? The bank sync logic should check for the first transaction in an account and never pull from further back then that.
Author
Owner

@mosbror commented on GitHub (May 8, 2024):

I've recently started moving over from YNAB.
In the past I've just not added all account activity. So I have a similar issue.
If there would be some "sync settings" where you could set a "Ignore account activity before: 2024-03-03".
As an alternative, the system could "remember" which transaction you've deleted in the past and just not import them again with the next sync.

@mosbror commented on GitHub (May 8, 2024): I've recently started moving over from YNAB. In the past I've just not added all account activity. So I have a similar issue. If there would be some "sync settings" where you could set a "Ignore account activity before: 2024-03-03". As an alternative, the system could "remember" which transaction you've deleted in the past and just not import them again with the next sync.
Author
Owner

@youngcw commented on GitHub (Jun 28, 2024):

Closing this as old. To put a start date on bank syncing add a starting transaction to the account to set the account balance. Sync will then not pull from before that.

@youngcw commented on GitHub (Jun 28, 2024): Closing this as old. To put a start date on bank syncing add a starting transaction to the account to set the account balance. Sync will then not pull from before that.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#609