Description
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
Activity