Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Ability to ignore uncleared transactions #4138

Closed
1 of 2 tasks
mbrijun opened this issue Jan 12, 2025 · 1 comment · May be fixed by #4253
Closed
1 of 2 tasks

[Feature] Ability to ignore uncleared transactions #4138

mbrijun opened this issue Jan 12, 2025 · 1 comment · May be fixed by #4253
Labels
bank sync Related to automatic bank syncing feature This issue is a feature request needs votes Please upvote this feature request if you would like to see it implemented!

Comments

@mbrijun
Copy link

mbrijun commented Jan 12, 2025

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

@mbrijun mbrijun added the feature This issue is a feature request label Jan 12, 2025
@github-actions github-actions bot added the needs votes Please upvote this feature request if you would like to see it implemented! label Jan 12, 2025
Copy link
Contributor

✨ 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 👍!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bank sync Related to automatic bank syncing feature This issue is a feature request needs votes Please upvote this feature request if you would like to see it implemented!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants