mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
Closed
opened 2026-05-16 07:51:32 -05:00 by GiteaMirror
·
19 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
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#70120
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 @Jeremy-Pichon on GitHub (Apr 30, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/975
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
Month budgets are not always tight to actual month (1st to 31th), but more to payday.
In my country salary is on 25th (or last working day before this day)m therefore my actual month budget is from 25th of previous month to 24th of current month.
Describe your ideal solution to this problem
I would add a section in settings to pick first day of month.
Maybe in the same section as
NumbersandDates.Implementation could be a global setting or a budget related setting.
Teaching and learning
Probably same as Dates and Numbers it would have a default value (eg:
1st day of month).Here is an example of the same feature on Money Wizz.

@github-actions[bot] commented on GitHub (May 1, 2023):
✨ Thanks for sharing your idea! ✨
This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).
The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=is%3Aissue+label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc
Don’t forget to upvote the top comment with 👍!
@fillwe commented on GitHub (Jan 3, 2024):
Yes this is so needed! Have tried the recommended way in the docs and hold the money for the 1st of the month but you become so out of sync with the rest of society. In Sweden it’s set in stone that you count your budget from the 25’th - 24’th, and all the bills for the next month is due before 1st usually.
@frbrigagao commented on GitHub (Jan 29, 2024):
Same! In Brazil there isn't a standard. Some receive their salaries in the 1st, 5th, 10th, 20th or some other day. Having a monthly budget with a fixed 1st day of the month doesn't make sense in this scenario.
@napoleonjumprope commented on GitHub (Mar 16, 2024):
I could not agree more. Actual holds so much promise that I tried moving to a calendar month way of budgeting but it just does not work* when the payday cycle starts on the 25th.
@TheBlueCircle commented on GitHub (May 12, 2024):
Excellent idea, but we probably want to disaggregate two concepts here: budget month and payroll period. In particular:
Perhaps a simple fix would be to create a new budget period based on rules? So if I receive > $€¥£x from y then it's recognised as my salary and a new budget period starts automatically?
The question about pay periods could then be a separate question which might be needed for future period projection, but which would be more complex.
@fillwe commented on GitHub (May 28, 2024):
Thanks for the reply, you might be right about this. But it isn't possible to set a rule to start a new budget period in the current release, right? If it is i can't seem to be able to find it.
@rare-magma commented on GitHub (Oct 15, 2024):
Is this a matter of making the
startDateof thecreateSpendingSpreadsheet()function customizable (link)? Is there any change required in the backend / database? I couldn't find any other references to this in the codebase. If the maintainers are willing to accept this change and provide some pointers I could work on a PR to implement this feature.@napoleonjumprope commented on GitHub (Nov 5, 2024):
This would be AMAZING. :)
@ElDubsNZ commented on GitHub (Dec 30, 2024):
I also support being able to create non-month based budget periods. I'm paid fortnightly on a Tuesday, so fortnightly budgets would make so much more sense for me.
@Th3K1ngP1n commented on GitHub (Jan 15, 2025):
Upvoting this !!
@garyabrahams commented on GitHub (Jun 8, 2025):
Agree this is a must and is the only reason why I can't use this product as I need a budget from 14th to 13th. Calender month does not work for me
@Haasie commented on GitHub (Jun 10, 2025):
+1
@Th3K1ngP1n commented on GitHub (Jun 10, 2025):
I stopped using this app due to the missing feature that probably most of Europe requires. Almost 6 months...
@Mansarde commented on GitHub (Jun 10, 2025):
I live in Europe and I've never needed to change the first of the month to my payday.
Just curious for why you deem this to be an essential feature for your budgeting?
@Th3K1ngP1n commented on GitHub (Jun 10, 2025):
Well that's my point. I don't need to change to the 1st of the month. The app starts the payroll from the 1st which is no good if you get paid on the 16th for example.
@Mansarde commented on GitHub (Jun 11, 2025):
But why is that no good? What problem does that create for you?
For example, I also get paid pretty late, in the last week of the month.
Sometimes I need some of that money for the current month, so I distribute a portion to where it's needed.
But most of it I don't need in the current month, so I simply forward it for use next month.
That's what Actual's
Hold for next monthoption is for when you click on the "To Budget" number at the top of the budget screen.@TateWalker commented on GitHub (Jul 11, 2025):
When I get paid midway through the month (once a month), I fund everything I'll need until my next paycheck. This includes expenses tracked per month (groceries for August). So if my water bill is due the last day of the month, I want my budget templates to fund that for the current month when I get paid. There will be another paycheck before the next month's water bill, so I don't need to fund it now.
I get the idea of "hold enough money for all expenses in the next month", but I personally like to run my bank account lean and invest any extra money. By running budget templates on the first of the month, I'm forced to hold money to cover the entire next month's bills.
I'd rather change my "month" to my pay date. Or have an income template that says "Run budget templates when income received from this payer"
@youngcw commented on GitHub (Jul 11, 2025):
@TateWalker You can use template priorites to do what you are asking. Also, there is no reason you cant be aggressive with investing and still be a month ahead. The budget doesn't care what account the funds are in, so you can be budgeting funds that are in savings accounts or a CMA/brokerage if they are on budget.
@darkporpoise commented on GitHub (Jul 28, 2025):
I found this a point of friction when trying to adopt AB as my first budgeting app. If AB is locked to a calendar month then it doesn't really support true envelope budgeting. AB is implicitly expecting me to budget money that I don't yet have.
I have played with a few workarounds for this:
I'm loving AB and it's really helping me to get a handle on my finances but I'm still having to manually calculate and track things that AB would do for me if I happened to be lucky enough to be paid on the 1st of each month.