mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
Closed
opened 2026-04-14 17:33:13 -05:00 by GiteaMirror
·
10 comments
No Branch/Tag Specified
master
dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a
api-browser-custom-data-dir
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
v26.7.0
v26.6.0
v26.5.2
v26.5.1
v26.5.0
v26.4.0
v26.3.0
v26.2.1
v26.2.0
v26.1.0
v25.12.0
v25.11.0
v25.10.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.1
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.1
v25.2.0
v25.1.0
v24.12.0
v24.11.0
v24.10.1
v24.10.0
v24.9.0
v24.8.0
v24.7.0
v24.6.0
v24.5.0
v24.4.0
v24.3.0
v24.2.0
v24.1.0
v23.12.0
v23.11.0
v23.10.0
v23.9.0
v23.8.1
v23.8.0
v23.7.2
v23.7.1
v23.7.0
v23.6.0
v23.5.0
v23.4.2
v23.4.1
v23.4.0
v23.3.2
v23.3.0
v23.2.9
v23.2.5
v23.1.12
v22.12.9
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
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
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#14758
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @faspina on GitHub (Jul 21, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1381
I get paid on the last day of the month , sometimes it hits on the 28ht or 29th. I want to designate this money to be utilized int he next month budget rather than the current month.
I would like to see a INCOME: NEXT MONTH category that push a July 28 paycheck to income for August
YNAB was able to do this and it works very well
@kyrias commented on GitHub (Jul 21, 2023):
What would the advantage be over using the "hold for next month" functionality?
@faspina commented on GitHub (Jul 21, 2023):
If my paycheck clears on Jun 29th or Jun 30th , I won't use that money in June. It will be budgeted for July expenses. As a result July budget show actual income allocated for July
@kyrias commented on GitHub (Jul 21, 2023):
If you use the "hold for next month" feature then while it'll show up in the income category in June, because that's when you actually received it, it won't be available for budget purposes until July.
@Kidglove57 commented on GitHub (Jul 21, 2023):
@faspina
Here is screenshot showing you the button, illustrative only I had no more income to send to next month!
@Kidglove57 commented on GitHub (Jul 21, 2023):
And here is the current documentation that included this feature (scroll down a bit):
https://actualbudget.org/docs/budgeting/
Very similar to YNAB 4 but more flexible
@faspina commented on GitHub (Jul 21, 2023):
I got it working, thanks
@darthlite commented on GitHub (Dec 8, 2023):
Related question I guess: Aside from manually inputting a new date, is there a way to get this month's income to show up as next month's income in reports and such?
If I receive income towards the end of November, but use it to budget for December, I would like to compare it to December's expenses.
Problem with changing the date is it messes up the transactions and account syncing.
@faspina commented on GitHub (Dec 8, 2023):
I don't like the HOLD for next month option because I do have etra money after budget that I want to alocate to envelops but this amount is a paycheck. I like the idea of doing this at the transaction level , a tag that says use this next month maybe. With a stead y pay check every 30 of the month it would just be easier to do it this way
@shawalli commented on GitHub (Aug 15, 2024):
I really like the way YNAB does it, where you can either assign a transaction to "Income: this month" or "Income: next month". The reason I like this approach better than the "hold" method is I don't need to do any math or special tricks to figure out how much money it available in the current or next month to budget. Additionally, when looking backward, you can easily see which income transactions are siloed into which months, rather than a floating level of money.
Having used AB for about 6 months now, it is one of the two features I still long for, because it makes the income management process dead-simple (at least as a user; I make no claims as to how it would be implemented behind the scenes).
@arwandar commented on GitHub (Oct 28, 2024):
What about a 2 incomes household? I'm get paid on the 29th, but my husband is paid the 2nd. So I can't use hold for next month as it won't solve the problem. I would like as @faspina to have the setting at a transaction level.