[GH-ISSUE #4705] [Bug]: Post Transaction Today option #116372

New Issue

GiteaMirror · 2026-06-11T09:38:06-05:00

GiteaMirror commented

2026-06-11 09:38:06 -05:00

Originally created by @g4m3r7ag on GitHub (Mar 29, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4705

Verified issue does not already exist?

I have searched and found no existing issue

What happened?

When a scheduled transaction for a future date is showing on the ledger, the date is usually approximate. I selected the transaction, selected the drop down that appears for the selected transaction, and choose Post Transaction Today. This takes it out of its pending/future state and posts it to the ledger, however it posts it with whatever the scheduled future date is, rather than "today". I would expect it to automatically adjust the date to "today".

How can we reproduce the issue?

Create a scheduled transaction in the future, select the pending/upcoming transaction in the ledger and choose the "Post Transaction Today" option. The date remains the future date.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @g4m3r7ag on GitHub (Mar 29, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4705 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? When a scheduled transaction for a future date is showing on the ledger, the date is usually approximate. I selected the transaction, selected the drop down that appears for the selected transaction, and choose Post Transaction Today. This takes it out of its pending/future state and posts it to the ledger, however it posts it with whatever the scheduled future date is, rather than "today". I would expect it to automatically adjust the date to "today". ### How can we reproduce the issue? Create a scheduled transaction in the future, select the pending/upcoming transaction in the ledger and choose the "Post Transaction Today" option. The date remains the future date. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11

GiteaMirror added the bug label 2026-06-11 09:38:06 -05:00

GiteaMirror closed this issue

2026-06-11 09:38:07 -05:00

GiteaMirror commented

2026-06-11 09:38:08 -05:00

@TimPasquini commented on GitHub (Apr 4, 2025):

I'm having a similar but slightly different issue with the same feature.

I have a scheduled transaction showing April 3rd as the scheduled date (it's set up to automatically create the transactions but I suspect a separate bug/issue related to weekly schedules). Today is the 4th, so I hit the button expecting to get a transaction posted for today and instead it adds one for March 27th (which already was posted and connected to the schedule).

Overall, Actual seems to know today is the 4th because that is what it is defaulting to for new transactions, not sure why it didn't post the transaction yesterday and why attempts to post it push back a week.

@TimPasquini commented on GitHub (Apr 4, 2025): I'm having a similar but slightly different issue with the same feature. I have a scheduled transaction showing April 3rd as the scheduled date (it's set up to automatically create the transactions but I suspect a separate bug/issue related to weekly schedules). Today is the 4th, so I hit the button expecting to get a transaction posted for today and instead it adds one for March 27th (which already was posted and connected to the schedule). Overall, Actual seems to know today is the 4th because that is what it is defaulting to for new transactions, not sure why it didn't post the transaction yesterday and why attempts to post it push back a week.

GiteaMirror commented

2026-06-11 09:38:08 -05:00

@radtriste commented on GitHub (May 12, 2025):

I think there has been a misunderstanding on the original feature and the title menu displayed.
The original feature was meant to foresee expenses in the future and enter them in advance into the account at the date they are expected (so, for example, I can see how much money I will have left at the end of the month) but indeed the menu Post transaction today was misleading.

I think 2 features have been mixed there:

Enter the transaction as the date of today because it ended up today in my account
Enter the transaction in the future, when it is planned so I can foresee expenses

@Bhautik2902 @youngcw I guess we should have both options.
Also looks like the change introduced an issue with rules on scheduled transactions

@radtriste commented on GitHub (May 12, 2025): I think there has been a misunderstanding on the original feature and the title menu displayed. The original feature was meant to foresee expenses in the future and enter them in advance into the account at the date they are expected (so, for example, I can see how much money I will have left at the end of the month) but indeed the menu `Post transaction today` was misleading. I think 2 features have been mixed there: - Enter the transaction as the date of today because it ended up today in my account - Enter the transaction in the future, when it is planned so I can foresee expenses @Bhautik2902 @youngcw I guess we should have both options. Also looks like the change introduced an issue with rules on scheduled transactions

GiteaMirror commented

2026-06-11 09:38:09 -05:00

@youngcw commented on GitHub (May 12, 2025):

I think there has been a misunderstanding on the original feature and the title menu displayed. The original feature was meant to foresee expenses in the future and enter them in advance into the account at the date they are expected (so, for example, I can see how much money I will have left at the end of the month) but indeed the menu Post transaction today was misleading.

I think 2 features have been mixed there:

Enter the transaction as the date of today because it ended up today in my account

Enter the transaction in the future, when it is planned so I can foresee expenses

@Bhautik2902 @youngcw I guess we should have both options. Also looks like the change introduced an issue with rules on scheduled transactions

what is the benefit of posting the transaction in the future like you originally had? How is posting the transaction in the future, like you originally had, any different than what the schedules already do?

@youngcw commented on GitHub (May 12, 2025): > I think there has been a misunderstanding on the original feature and the title menu displayed. The original feature was meant to foresee expenses in the future and enter them in advance into the account at the date they are expected (so, for example, I can see how much money I will have left at the end of the month) but indeed the menu `Post transaction today` was misleading. > > I think 2 features have been mixed there: > > * Enter the transaction as the date of today because it ended up today in my account > * Enter the transaction in the future, when it is planned so I can foresee expenses > > [@Bhautik2902](https://github.com/Bhautik2902) [@youngcw](https://github.com/youngcw) I guess we should have both options. Also looks like the change introduced an issue with rules on scheduled transactions what is the benefit of posting the transaction in the future like you originally had? How is posting the transaction in the future, like you originally had, any different than what the schedules already do?

GiteaMirror commented

2026-06-11 09:38:10 -05:00

@DavidHeiniluoma commented on GitHub (May 12, 2025):

I think there has been a misunderstanding on the original feature and the title menu displayed. The original feature was meant to foresee expenses in the future and enter them in advance into the account at the date they are expected (so, for example, I can see how much money I will have left at the end of the month) but indeed the menu Post transaction today was misleading.
I think 2 features have been mixed there:

Enter the transaction as the date of today because it ended up today in my account

Enter the transaction in the future, when it is planned so I can foresee expenses

@Bhautik2902 @youngcw I guess we should have both options. Also looks like the change introduced an issue with rules on scheduled transactions

what is the benefit of posting the transaction in the future like you originally had? How is posting the transaction in the future, like you originally had, any different than what the schedules already do?

For one thing, it will update the account's ending balance once it is posted, but not while it is in "upcoming" statue.

My use case: I have AutoPay set up to pay my full credit card balance on the due date (same day each month), with a scheduled recurring transaction. But the amount fluctuates, so I usually post the transaction and update the amount once I know the amount that will be taken out in the next payment. Now when I change the amount of that transaction and post it, it has today's date even though it won't actually be paid for a couple weeks.

@DavidHeiniluoma commented on GitHub (May 12, 2025): > > I think there has been a misunderstanding on the original feature and the title menu displayed. The original feature was meant to foresee expenses in the future and enter them in advance into the account at the date they are expected (so, for example, I can see how much money I will have left at the end of the month) but indeed the menu `Post transaction today` was misleading. > > I think 2 features have been mixed there: > > > > * Enter the transaction as the date of today because it ended up today in my account > > * Enter the transaction in the future, when it is planned so I can foresee expenses > > > > [@Bhautik2902](https://github.com/Bhautik2902) [@youngcw](https://github.com/youngcw) I guess we should have both options. Also looks like the change introduced an issue with rules on scheduled transactions > > what is the benefit of posting the transaction in the future like you originally had? How is posting the transaction in the future, like you originally had, any different than what the schedules already do? For one thing, it will update the account's ending balance once it is posted, but not while it is in "upcoming" statue. My use case: I have AutoPay set up to pay my full credit card balance on the due date (same day each month), with a scheduled recurring transaction. But the amount fluctuates, so I usually post the transaction and update the amount once I know the amount that will be taken out in the next payment. Now when I change the amount of that transaction and post it, it has today's date even though it won't actually be paid for a couple weeks.

GiteaMirror commented

2026-06-11 09:38:10 -05:00

@TimPasquini commented on GitHub (Jun 2, 2025):

I think 2 features have been mixed there:

Enter the transaction as the date of today because it ended up today in my account

Enter the transaction in the future, when it is planned so I can foresee expenses

@Bhautik2902 @youngcw I guess we should have both options. Also looks like the change introduced an issue with rules on scheduled transactions

what is the benefit of posting the transaction in the future like you originally had? How is posting the transaction in the future, like you originally had, any different than what the schedules already do?

I think a simple solution would be to offer two options: "Post" and "Post Today".

"Post" uses the date already on the pending transaction (past or future).

"Post Today" assigns today’s date.

@DavidHeiniluoma gave a valid use case for future-dated posting, but I only reconcile monthly, and I doubt I'm the only one with that workflow. I'm usually dealing with past-dated scheduled transactions that should retain their original dates when posted.

For example, today is June 1st. I have scheduled paychecks in "Upcoming" for May 8, 15, 22, and 29. Those transactions actually occurred on those dates, but I didn’t log in each week to post them. When I manually post all four today, they’re assigned June 1st, which means I have to manually correct their dates and it defeats the purpose of scheduling them.

When importing a CSV or QFX, the dates are handled correctly. But if an account doesn't support some sort of export, I have to manually post and then fix each date.

This would mostly be resolved for me if scheduled transactions had an option to auto-post when the scheduled date hits. I only schedule things that are regular and reliable, so in the rare case something is off, I'd rather fix or delete the one-off afterward than have to confirm all the transactions I already told the software to expect.

@TimPasquini commented on GitHub (Jun 2, 2025): > > I think 2 features have been mixed there: > > > > * Enter the transaction as the date of today because it ended up today in my account > > * Enter the transaction in the future, when it is planned so I can foresee expenses > > > > [@Bhautik2902](https://github.com/Bhautik2902) [@youngcw](https://github.com/youngcw) I guess we should have both options. Also looks like the change introduced an issue with rules on scheduled transactions > > what is the benefit of posting the transaction in the future like you originally had? How is posting the transaction in the future, like you originally had, any different than what the schedules already do? I think a simple solution would be to offer two options: "Post" and "Post Today". "Post" uses the date already on the pending transaction (past or future). "Post Today" assigns today’s date. [@DavidHeiniluoma](https://github.com/DavidHeiniluoma) gave a valid use case for future-dated posting, but I only reconcile monthly, and I doubt I'm the only one with that workflow. I'm usually dealing with past-dated scheduled transactions that should retain their original dates when posted. For example, today is June 1st. I have scheduled paychecks in "Upcoming" for May 8, 15, 22, and 29. Those transactions actually occurred on those dates, but I didn’t log in each week to post them. When I manually post all four today, they’re assigned June 1st, which means I have to manually correct their dates and it defeats the purpose of scheduling them. When importing a CSV or QFX, the dates are handled correctly. But if an account doesn't support some sort of export, I have to manually post and then fix each date. This would mostly be resolved for me if scheduled transactions had an option to auto-post when the scheduled date hits. I only schedule things that are regular and reliable, so in the rare case something is off, I'd rather fix or delete the one-off afterward than have to confirm all the transactions I already told the software to expect.

GiteaMirror commented

2026-06-11 09:38:11 -05:00

@CalebBurton commented on GitHub (Jun 2, 2025):

I'm another person who prefers to set up my monthly transactions in advance and would like the ability to post on the scheduled date rather than today. Having both options would be great.

@CalebBurton commented on GitHub (Jun 2, 2025): I'm another person who prefers to set up my monthly transactions in advance and would like the ability to post on the scheduled date rather than today. Having both options would be great.

GiteaMirror commented

2026-06-11 09:38:11 -05:00

@g4m3r7ag commented on GitHub (Jun 2, 2025):

@TimPasquini On my schedules I check the box for automatically add transaction and it auto-posts them on the date if it arrives and hasn't been posted already. The reason I opened the issue was because some of my scheduled transactions occur around a specific date but not always on the same date. Some of my bills auto pay on different dates because of dates falling on a weekend etc... when that happens I want to post it immediately which would be "today" and not the scheduled date. If the auto pay doesn't happen until after the date on the schedule falls then I have to change the date on the already present transaction when it finally does come out of my account.

@g4m3r7ag commented on GitHub (Jun 2, 2025): @TimPasquini On my schedules I check the box for automatically add transaction and it auto-posts them on the date if it arrives and hasn't been posted already. The reason I opened the issue was because some of my scheduled transactions occur around a specific date but not always on the same date. Some of my bills auto pay on different dates because of dates falling on a weekend etc... when that happens I want to post it immediately which would be "today" and not the scheduled date. If the auto pay doesn't happen until after the date on the schedule falls then I have to change the date on the already present transaction when it finally does come out of my account.

GiteaMirror commented

2026-06-11 09:38:11 -05:00

@TimPasquini commented on GitHub (Jun 2, 2025):

@g4m3r7ag Yea, I had something similar (amongst other issues) when I originally commented, but the thread has spiraled in scope a bit which is why I made sure to quote the comments I was specifically addressing.

Interesting that yours will switch to posted on the actual date, mine haven't done that since these other issues started popping up. I felt like the schedules and postings all used to work pretty perfectly for me and then at some point within the last year the scheduling & posting problems started piling up. I honestly don't even know what is intent vs bugs at this point.

@TimPasquini commented on GitHub (Jun 2, 2025): @g4m3r7ag Yea, I had something similar (amongst other issues) when I originally commented, but the thread has spiraled in scope a bit which is why I made sure to quote the comments I was specifically addressing. Interesting that yours will switch to posted on the actual date, mine haven't done that since these other issues started popping up. I felt like the schedules and postings all used to work pretty perfectly for me and then at some point within the last year the scheduling & posting problems started piling up. I honestly don't even know what is intent vs bugs at this point.

GiteaMirror commented

2026-06-11 09:38:12 -05:00

@radtriste commented on GitHub (Jun 2, 2025):

Sorry I did not get any email notifications about this.

I also like to enter my transactions ahead of time so I can plan my budget for the next months.
I can try to take the time to implement both options: Post now and Post next occurrence like @TimPasquini suggested

@radtriste commented on GitHub (Jun 2, 2025): Sorry I did not get any email notifications about this. I also like to enter my transactions ahead of time so I can plan my budget for the next months. I can try to take the time to implement both options: `Post now` and `Post next occurrence` like @TimPasquini suggested

Sign in to join this conversation.

Branches Tags

master

claude/verify-migration-guardrails-i82c8m

cross-version-sync-stage2

api-browser-custom-data-dir

dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a

tabedzki/feat/replacing-month-picker-with-day-picker

delay-initial-sync-until-loaded

jfdoming/mobile-app-build

cross-version-sync-compat

jfdoming/api-tokens-part-1

jfdoming/api-tokens-part-2

jfdoming/api-tokens-part-3

jfdoming/mobile-app-updates

claude/budget-version-migration-compat-151jlr

claude/worker-error-serialization-9iqtl7

claude/react-table-library-research-afx83z

claude/issue-8401-regression-test-9nw9l3

jfdoming/mobile-app-foundation-part-1

jfdoming/mobile-app-scaffold

release

ai-fix-cleanup-def-8290

claude/relaxed-shannon-jusywa

claude/fervent-keller-s6f2fq

claude/determined-feynman-st1y9z

claude/wizardly-einstein-vi2wce

claude/sweet-albattani-7nseio

feat/bank-sync-per-budget-file

claude/affectionate-cannon-y0kc82

claude/dependabot-findings-m9pgmb

claude/mac-app-ios-publish-zjs1lz

claude/vigilant-tesla-aiiyos

depot-migrate-secrets-1781296330308

claude/quirky-cerf-v5qck7

claude/animation-removal-alternative-2etfh1

claude/netlify-preview-comments-consolidate-9XPYa

osc/7391-error-boundaries-reports

claude/pensive-dijkstra-7DYui

claude/server-app-version-mismatch-HTCGv

claude/pr-8027-review-feedback-mELuO

claude/zealous-wozniak-e5pO0

claude/intelligent-heisenberg-BSHJq

claude/translation-download-refactor-jFRsO

claude/mobile-performance-ideas-G9PAO

claude/github-issue-7988-5A5ly

blacksmith-migration-ff70d2d

claude/great-mayer-KRvOk

claude/react-native-ios-compilation-fcJh5

claude/serene-goldberg-58xv0

claude/kind-euler-LVG3K

release-automation/edge-nightly

7710-bundle-migrations

claude/fix-docker-build-error-WMfed

claude/llm-compatible-release-notes-t20Nr

7710-tests-tdd

cursor/transaction-table-rewrite-f077

claude/plan-ci-secure-context-OtEe1

claude/fix-issue-7667-DPXi3

cursor/resolve-pr-7449-ee11

claude/fix-typescript-build-error-JPtZ5

copilot/add-repository-configs-to-packages

worktree-compressed-drifting-ritchie

claude/api-consumer-verification-kfz1K

pr-7454

claude/fix-issue-7410-LLLQ4

revert-7281-generate-icons

react-query-useSchedules

copilot/sub-pr-6140

package-upgrades

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/actual#116372