mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 22:54:03 -05:00
Closed
opened 2026-05-18 22:20:45 -05:00 by GiteaMirror
·
8 comments
No Branch/Tag Specified
master
dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a
enforce-append-only-migrations-ci
claude/error-codes-worker-boundary-26i5uu
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#77851
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 @IAmParadox27 on GitHub (May 30, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1080
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
People get paid on different days of the month.
To help people better budget instead of forcing to budget strictly to the month, it would be better if people could budget for payday to payday.
Allow the user to specify when their months should run from and to.
Describe your ideal solution to this problem
I would recommend having a setting where the user can specify when they would like their month to start.
Options:
A setting should exist to say what happens on weekends (bring forward)
The last day of the monthly cycle should either be the day before the next month is due to start and shouldn't have a setting to specify its rule OR a fixed duration of time after month start (eg for people that get paid weekly or every X weeks).
Teaching and learning
No response
@github-actions[bot] commented on GitHub (May 30, 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=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+
Don’t forget to upvote the top comment with 👍!
@jpdsc commented on GitHub (Jun 15, 2023):
As someone who gets paid on the 24th, this feature is actually needed for me and probably others to start using this software.
I've tried and setting up the budget flow from 1st till last day of month but it will not match current finances and needs too much manual intervention to make it work.
+1 for this feature.
@gitchap commented on GitHub (Feb 22, 2025):
I can see how this feature would make things LOOK tidier... but how does it actually change anything? How are you paying your bills before the 24th? I'm assuming you use funds from your last paycheck. (Unless all your bills are due between the 24th and the 1st of next month, in that case, just wait till the 24th to budget.)
I get that not everyone is in a position to budget this month's income as next month's budget.
I guess my point is that this is more of a "nice to have" feature, and not a "need." Most people don't get paid on the 1st of the month. Many people are paid weekly or bi-weekly. Most bills are monthly. In the end all that matters is do you have enough money to pay the bill when it is due.
I don't see how being able to pick the day of the month that the software splits the budget into changes anything other than aesthetics.
I'm curious what kind of "manual intervention" is needed to make the budget "work"? I'm not paid monthly, so maybe I don't get it.
@jpdsc commented on GitHub (Feb 23, 2025):
I've been using Actual for a while now. After doing quite some research on "best way to budget" and you're right, you should budget for next month with the income of this month.
I re-arranged my finances, got some recurring transactions changed to be booked from the 1st onwards and kept anything between 24 and 1 as low as possible.
I feel, budgetting 1st till last day of the month is a lot easier than doing pay > pay (what is was doing previously). It's one time bridging the expenses from 24 till end of the month. But if you contact the recurring payment provider/company, often you can change the recurring date and set it to beginning of the month (if not enough funds to initiate this faster).
@IAmParadox27 commented on GitHub (Mar 17, 2025):
My issue with it is mostly aesthetic. But there's a frustration when being paid on the last working day of the month. Mostly because that pay is for the following month, but appears in the month prior. So things like budgeting looks proper wonky.
Lets say I start now, putting in a budget for April onwards. I put in my pay that I'll receive on 31st March, that appears in the March tab as "To Budget" but there's no spending or budgeting because I'm going from 1st April. So then we head to April and put all the budget in, track the spending etc etc, then we get to the end of the month and we put the pay in for 30th April and the April tab is then updated with "To Budget" of my salary again.
By adding a pay cycle into the software, what ends up happening is there is only ever 1 pay per month to budget.
Mostly this is useful for those that currently live paycheck to paycheck and are wanting to get a grip on finances to be free from the pay to pay lifestyle. But that's difficult to do and making that as easy as possible to manage is only ever a good thing. My view here is its a feature that's opted for rather than a feature forced upon a user, and anything that can help an individual (like myself) get a grip on their finances to shift mindsets and budget better should be something worth supporting.
I'd do it myself, but I'm not massively familiar with the stack that's used to write it and I'd probably get lost and "do it wrong" :D
@sidvishnoi commented on GitHub (Dec 14, 2025):
Duplicate of https://github.com/actualbudget/actual/issues/975?
@IAmParadox27 commented on GitHub (Dec 14, 2025):
Looks like it yes
@Juulz commented on GitHub (Dec 14, 2025):
You can use auto-hold for next month or change the date on the deposit.