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

[GH-ISSUE #4005] [Bug]: Reports do not consider future dated transactions when claiming to use the range 'All time' #27483

New Issue
Closed
opened 2026-04-18 03:58:02 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-18 03:58:02 -05:00
Owner
Copy Link

Originally created by @mullermn on GitHub (Dec 18, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4005

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

The reports feature has several date filtering options, once of which is 'Live'/'All time'.

From its name this should show all transactions that Actual is aware of, but as currently implemented it only shows historical transactions, not future dated ones that may be there for planning.

How can we reproduce the issue?

Create some future dated transactions and experiment in the report builder.

As a side note, though this is potentially more of an enhancement, the date selectors for static dates should enable the selection of the most future dated transaction in Actual (for the same reason that I've raised this bug), but currently they're capped at the current date

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Mac OSX

Originally created by @mullermn on GitHub (Dec 18, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/4005 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? The reports feature has several date filtering options, once of which is 'Live'/'All time'. From its name this should show all transactions that Actual is aware of, but as currently implemented it only shows historical transactions, not future dated ones that may be there for planning. ### How can we reproduce the issue? Create some future dated transactions and experiment in the report builder. As a side note, though this is potentially more of an enhancement, the date selectors for static dates should enable the selection of the most future dated transaction in Actual (for the same reason that I've raised this bug), but currently they're capped at the current date ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Mac OSX
GiteaMirror added the reportsbug labels 2026-04-18 03:58:03 -05:00
GiteaMirror commented 2026-04-18 03:58:07 -05:00
Author
Owner
Copy Link

@pwinnski commented on GitHub (Dec 19, 2024):

This seems to be a philosophical issue. Actual is budgeting software, not planning software. Transactions with future dates aren't valid because they haven't happened. They're not Actual!

These assumptions, this philosophy, is very deeply embedded into the software, and I suspect that the date picker and "All time" are just the tip of the iceberg.

<!-- gh-comment-id:2552709940 --> @pwinnski commented on GitHub (Dec 19, 2024): This seems to be a philosophical issue. Actual is budgeting software, not planning software. Transactions with future dates aren't valid because they haven't happened. They're not Actual! These assumptions, this philosophy, is very deeply embedded into the software, and I suspect that the date picker and "All time" are just the tip of the iceberg.
GiteaMirror commented 2026-04-18 03:58:07 -05:00
Author
Owner
Copy Link

@mullermn commented on GitHub (Dec 19, 2024):

Discussion on philosophy should probably happen elsewhere, but as far as relevance to this bug report goes, I'll just point out that if that IS the philosophy then there are numerous places where it's not being applied already:

  • You can enter future dated transactions
  • You can have uncleared transactions imported from banks (until they clear they haven't happened)
  • The whole concept of scheduled transactions relates to things that haven't happened yet, and Actual supports those
  • You can set budgets for the future
  • The whole concept of budgeting relates to future planning - dealing purely with things that have happened already would just be accounting. Removing future dated transactions from this planning just creates a voluntary blind spot in that planning.

but smallest in scope and most tangible for this bug report:

  • If that is the case then the label for this drop down is wrong - it's not 'All time' it's 'To date', or perhaps 'Cleared'.
<!-- gh-comment-id:2553170753 --> @mullermn commented on GitHub (Dec 19, 2024): Discussion on philosophy should probably happen elsewhere, but as far as relevance to this bug report goes, I'll just point out that if that IS the philosophy then there are numerous places where it's not being applied already: - You can enter future dated transactions - You can have uncleared transactions imported from banks (until they clear they haven't happened) - The whole concept of scheduled transactions relates to things that haven't happened yet, and Actual supports those - You can set budgets for the future - The whole concept of budgeting relates to future planning - dealing purely with things that have happened already would just be accounting. Removing future dated transactions from this planning just creates a voluntary blind spot in that planning. but smallest in scope and most tangible for this bug report: - If that is the case then the label for this drop down is wrong - it's not 'All time' it's 'To date', or perhaps 'Cleared'.
GiteaMirror commented 2026-04-18 03:58:08 -05:00
Author
Owner
Copy Link

@pwinnski commented on GitHub (Dec 19, 2024):

👍 on the label being unclear.

👎 on your other points. Uncleared transactions are still Actual transactions, and not future-dated. Scheduled transactions are not Actual transactions until posted. Budgeting, or assigning income to categories, is categorizing Actual income received in a transaction, not a transaction itself.

IMO, AB stands in a line of software that has historically eschewed the kind of planning you're talking about, focusing on Actual expenses (or "True Expenses"). You're welcome to view things however you wish, but you might end up hitting limitations more often than not with entering transactions that haven't actually happened yet. 🤷

<!-- gh-comment-id:2554553767 --> @pwinnski commented on GitHub (Dec 19, 2024): 👍 on the label being unclear. 👎 on your other points. Uncleared transactions are still Actual transactions, and not future-dated. Scheduled transactions are not Actual transactions until posted. Budgeting, or assigning income to categories, is categorizing Actual income received in a transaction, not a transaction itself. IMO, AB stands in a line of software that has historically eschewed the kind of planning you're talking about, focusing on Actual expenses (or "True Expenses"). You're welcome to view things however you wish, but you might end up hitting limitations more often than not with entering transactions that haven't actually happened yet. 🤷
GiteaMirror commented 2026-04-18 03:58:09 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Nov 4, 2025):

I think this has been fixed in https://github.com/actualbudget/actual/pull/5753

<!-- gh-comment-id:3483171109 --> @matt-fidd commented on GitHub (Nov 4, 2025): I think this has been fixed in https://github.com/actualbudget/actual/pull/5753
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 bug reports
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#27483
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?