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

[GH-ISSUE #377] Option to Ignore/skip rows #7071

New Issue
Closed
opened 2026-04-10 16:44:24 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-10 16:44:24 -05:00
Owner
Copy Link

Originally created by @seeni-dev on GitHub (Sep 3, 2022).
Original GitHub issue: https://github.com/actualbudget/actual/issues/377

While importing the data, it would be nice to skip/ignore rows since Banks always garbage filler lines above and below the actual data that we care.

Originally created by @seeni-dev on GitHub (Sep 3, 2022). Original GitHub issue: https://github.com/actualbudget/actual/issues/377 While importing the data, it would be nice to skip/ignore rows since Banks always garbage filler lines above and below the actual data that we care.
GiteaMirror added the featureimporters labels 2026-04-10 16:44:24 -05:00
GiteaMirror commented 2026-04-10 16:44:26 -05:00
Author
Owner
Copy Link

@TomAFrench commented on GitHub (Sep 3, 2022):

Can you provide an example file?

<!-- gh-comment-id:1295749723 --> @TomAFrench commented on GitHub (Sep 3, 2022): Can you provide an example file?
GiteaMirror commented 2026-04-10 16:44:27 -05:00
Author
Owner
Copy Link

@bverkron commented on GitHub (Oct 18, 2022):

I have never seen any "garbage filler" lines in my imports but a mechanism for this may have some relationship with https://github.com/actualbudget/actual/issues/357 if it's also implemented with a date based "filter" to ignore previous transactions before a certain date. For example if transactions in the import file were dated before the last reconciled transaction in the account they would be automatically ignored (but you could choose to import them anyway if you wanted).

This could also apply to account start dates (in Actual), not just last reconciled date.

This is useful in two scenarios that I've come across:

  1. When first setting up accounts in Actual and importing data from a bank you cannot always (or forget to) filter the transactions down to just new transactions before exporting from the bank. This means actual will import transactions before the start date of the account (in actual. For example if I started using Actual on June 1st but the data being imported from the back goes back to May 20th (either because I could not filter it enough on the bank side or forgot to) it will import data from May that I don't want and will mess up the balance until I manually delete those transactions.

  2. When some transactions are missing (missed during import, accidently deleted, etc) I will purposely export data quite a ways back (sometimes months or an entire year) in order to fix the problem. This can basically lead to the problem described in point 1. i.e. importing transaction before the start date of the account in Actual.

Both 1 & 2 could arguably be handled by more tight management of the imports but requires extra manual work and is prone to human error sometimes. Would be a much nicer experience if Actual helped filter out those "before account start" or "before last reconcile date" transactions automatically.

<!-- gh-comment-id:1295749725 --> @bverkron commented on GitHub (Oct 18, 2022): I have never seen any "garbage filler" lines in my imports but a mechanism for this may have some relationship with https://github.com/actualbudget/actual/issues/357 if it's also implemented with a date based "filter" to ignore previous transactions before a certain date. For example if transactions in the import file were dated before the last reconciled transaction in the account they would be automatically ignored (but you could choose to import them anyway if you wanted). This could also apply to account start dates (in Actual), not just last reconciled date. This is useful in two scenarios that I've come across: 1. When first setting up accounts in Actual and importing data from a bank you cannot always (or forget to) filter the transactions down to just new transactions before exporting from the bank. This means actual will import transactions before the start date of the account (in actual. For example if I started using Actual on June 1st but the data being imported from the back goes back to May 20th (either because I could not filter it enough on the bank side or forgot to) it will import data from May that I don't want and will mess up the balance until I manually delete those transactions. 2. When some transactions are missing (missed during import, accidently deleted, etc) I will purposely export data quite a ways back (sometimes months or an entire year) in order to fix the problem. This can basically lead to the problem described in point 1. i.e. importing transaction before the start date of the account in Actual. Both 1 & 2 could arguably be handled by more tight management of the imports but requires extra manual work and is prone to human error sometimes. Would be a much nicer experience if Actual helped filter out those "before account start" or "before last reconcile date" transactions automatically.
GiteaMirror commented 2026-04-10 16:44:28 -05:00
Author
Owner
Copy Link

@naftalibeder commented on GitHub (Nov 13, 2022):

I'd love this too - here's an example of the first four lines from a Schwab brokerage export:

"Transactions  for account XXXXXXXXXXXXXX ...XXX as of XXXXXXXXXXXX PM ET"
"Date","Action","Symbol","Description","Quantity","Price","Fees & Comm","Amount"
[actual transactions]

and checking:

"Transactions  for Checking account ...XXX as of 11/12/2022 11:07:21 PM ET"
"Date","Type","Check #","Description","Withdrawal (-)","Deposit (+)","RunningBalance"
"Pending Transactions are not reflected within this sort criterion."
"Posted Transactions"
[actual transactions]
<!-- gh-comment-id:1312633827 --> @naftalibeder commented on GitHub (Nov 13, 2022): I'd love this too - here's an example of the first four lines from a Schwab brokerage export: ``` "Transactions for account XXXXXXXXXXXXXX ...XXX as of XXXXXXXXXXXX PM ET" "Date","Action","Symbol","Description","Quantity","Price","Fees & Comm","Amount" [actual transactions] ``` and checking: ``` "Transactions for Checking account ...XXX as of 11/12/2022 11:07:21 PM ET" "Date","Type","Check #","Description","Withdrawal (-)","Deposit (+)","RunningBalance" "Pending Transactions are not reflected within this sort criterion." "Posted Transactions" [actual transactions] ```
GiteaMirror commented 2026-04-10 16:44:29 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 2, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:1531911820 --> @github-actions[bot] commented on GitHub (May 2, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍!
GiteaMirror commented 2026-04-10 16:44:29 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 14, 2024):

🎉 This feature has been implemented in #3234 and will be released in the next version. Thanks for sharing your idea! 🎉

<!-- gh-comment-id:2289920397 --> @github-actions[bot] commented on GitHub (Aug 14, 2024): :tada: This feature has been implemented in #3234 and will be released in the next version. Thanks for sharing your idea! :tada: <!-- feature-implemented-comment -->
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 feature importers
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#7071
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?