github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 15:14:02 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #4138] [Feature] Ability to ignore uncleared transactions #91395

New Issue
Closed
opened 2026-05-25 23:04:45 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-25 23:04:45 -05:00
Owner
Copy Link

Originally created by @mbrijun on GitHub (Jan 12, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4138

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

I have been using Actual Budget very actively for over 3 months now. In that time I have observed several instances where synchronising uncleared transactions causes issues.

  • One reliable example is a transport authority in London (TFL - Transport for London). They allow paying for journeys by presenting one's payment card to an automated card reader at a platform gate. For any cards that TfL do not know about, they charge a small amount (£0.10) just to verify that the card is operational. The actual sum owed for that day is worked out after the day has ended (for example, £7.00). Depending on when and how often the account sync is taking place, it is entirely possible to capture both the test payment and the actual sum TfL want to charge. As a result, the budget for public transport gets skewed.
  • In the past I encountered many instances with a local train company where a technical problem when collecting a payment online would still (temporarily) reflect on my bank statement. That erroneous amount would eventually disappear, but it would not happen immediately. I can imagine it would be captured by a sync operation and again would skew the budget.

I believe the above instances are a feature, not a bug, of the payment system, where a grace period is given for all parties to agree on the correct amount charged. It does present a very real problem for automated import, as Actual Budget does not remove transactions that are no longer on the bank statement.

Describe your ideal solution to this problem

As a solution to this problem with temporary or erroneous transactions, I propose that end-users are given a choice to filter out uncleared transactions when importing data from specific (or all) accounts.

Please kindly refer to a recent bug report for additional details.

Teaching and learning

No response

Originally created by @mbrijun on GitHub (Jan 12, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4138 ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? I have been using Actual Budget very actively for over 3 months now. In that time I have observed several instances where synchronising uncleared transactions causes issues. * One reliable example is a transport authority in London (TFL - Transport for London). They allow paying for journeys by presenting one's payment card to an automated card reader at a platform gate. For any cards that TfL do not know about, they charge a small amount (£0.10) just to verify that the card is operational. The actual sum owed for that day is worked out after the day has ended (for example, £7.00). Depending on when and how often the account sync is taking place, it is entirely possible to capture both the test payment *and* the actual sum TfL want to charge. As a result, the budget for public transport gets skewed. * In the past I encountered many instances with a local train company where a technical problem when collecting a payment online would still (temporarily) reflect on my bank statement. That erroneous amount would eventually disappear, but it would not happen immediately. I can imagine it would be captured by a sync operation and again would skew the budget. I believe the above instances are a feature, not a bug, of the payment system, where a grace period is given for all parties to agree on the correct amount charged. It does present a very real problem for automated import, as Actual Budget **does not remove transactions that are no longer on the bank statement**. ### Describe your ideal solution to this problem As a solution to this problem with temporary or erroneous transactions, I propose that end-users are given a choice to filter out uncleared transactions when importing data from specific (or all) accounts. Please kindly refer to a recent [bug report](https://github.com/actualbudget/actual-server/issues/529) for additional details. ### Teaching and learning _No response_
GiteaMirror added the featurebank sync labels 2026-05-25 23:04:46 -05:00
GiteaMirror commented 2026-05-25 23:04:52 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 12, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. 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:2585793837 --> @github-actions[bot] commented on GitHub (Jan 12, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. 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 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-05-25 23:04:55 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 14, 2025):

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

<!-- gh-comment-id:2659404592 --> @github-actions[bot] commented on GitHub (Feb 14, 2025): :tada: This feature has been implemented in #4253 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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bank sync feature
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#91395
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?