[Feature] Actual Budget currently uses only the booking/clearing date for GoCardless synced transactions. #2740

New Issue

GiteaMirror · 2026-02-28T20:26:22-06:00

GiteaMirror commented

2026-02-28 20:26:22 -06:00

Originally created by @horvathgergo on GitHub (Dec 23, 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?

For my bank (Erste but maybe many), the booking date of pending transactions is set in the future, whereas the transaction date reflects the actual moment the spending occurred. Using only the booking date can therefore misrepresent daily/weekly spending and reporting, causing transactions to appear on incorrect dates.

In GoCardless data, transaction date information is often available, sometimes embedded in remittanceInformationUnstructured for pending payments or simply stored as transaction date for already booked transactions.

Currently, Actual ignores this field.

Describe your ideal solution to this problem

Store transaction date as an optional secondary field when available.

Keep booking date as the default to maintain balance accuracy.

Allow users to choose which date (transaction or booking) is used for reports, filters, and daily/weekly analysis.

Teaching and learning

This would improve the accuracy of reports for users who care about the actual timing of transactions, especially for pending or recently authorized payments, end of month payments without affecting the default behavior for balance tracking.

Originally created by @horvathgergo on GitHub (Dec 23, 2025). ### 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? For my bank (Erste but maybe many), the booking date of pending transactions is set in the future, whereas the transaction date reflects the actual moment the spending occurred. Using only the booking date can therefore misrepresent daily/weekly spending and reporting, causing transactions to appear on incorrect dates. In GoCardless data, transaction date information is often available, sometimes embedded in remittanceInformationUnstructured for pending payments or simply stored as transaction date for already booked transactions. Currently, Actual ignores this field. ### Describe your ideal solution to this problem Store transaction date as an optional secondary field when available. Keep booking date as the default to maintain balance accuracy. Allow users to choose which date (transaction or booking) is used for reports, filters, and daily/weekly analysis. ### Teaching and learning This would improve the accuracy of reports for users who care about the actual timing of transactions, especially for pending or recently authorized payments, end of month payments without affecting the default behavior for balance tracking.

GiteaMirror added the needs votes feature labels 2026-02-28 20:26:22 -06:00

GiteaMirror closed this issue

2026-02-28 20:26:22 -06:00

GiteaMirror commented

2026-02-28 20:26:23 -06:00

@github-actions[bot] commented on GitHub (Dec 23, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 👍!

@github-actions[bot] commented on GitHub (Dec 23, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 👍!