mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 15:14:02 -05:00
Closed
opened 2026-05-25 17:05:21 -05:00 by GiteaMirror
·
6 comments
No Branch/Tag Specified
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
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#90064
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 @joel-jeremy on GitHub (Jun 16, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1142
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
I'm only getting starting to budgeting and using the zero based budgeting system and I'm currently having trouble wrapping my head around how to handle credit cards in the budget. Maybe it's a silly question but how should we budgets for credit card payments that are due for the month and not for the other cards that are due next month? How do we correctly reflect the credit card payment transaction when the statement arrives?
Currently what I did is:
Credit Cardaccount and categorize them appropriately.Checkingaccount.Checkingaccount to myCredit Cardaccount.CheckingandCredit Cardaccounts now reflect the actual (no pun intended 😅) amounts.Credit Cardcategory still have a balance.Is this the correct way to go about it? Is the balance still supposed be non-zero? Because in my mind I already spent that money (paid credit card) but why is still showing a balance as if I still some remaining money to spend? Am I missing something? Please let me know your thoughts. Thank you!
Describe your ideal solution to this problem
It would be great if the "Managing Credit Cards" documentation can be updated to include different scenarios on how to budget for credit card payments.
Teaching and learning
It would be great if the "Managing Credit Cards" documentation can be updated to include different scenarios on how to budget for credit card payments.
@github-actions[bot] commented on GitHub (Jun 16, 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 👍!
@youngcw commented on GitHub (Jun 16, 2023):
Your main issue is you did one too many steps. You only need to make a credit card category if you are paying off existing debt or are running a balance on your credit card. Since you paid the card in full in your example your transfer covered everything and that's all that is needed.
Your categories represent money that is going to leave your budget, and since you already budgeted for those expenses in your cell, and entertainment categories you are double budgeting by having a dedicated credit card payment category. So for $100 of bills you budgeted $50+$50+$100 so that's why you end up with 100 extra with nowhere to go.
@j-f1 commented on GitHub (Jun 16, 2023):
This is covered by https://actualbudget.org/docs/budgeting/creditcards, is there something we could improve there (or somewhere in the app we should be linking to that page) to help guide new users in the right direction?
@rafacla commented on GitHub (Jul 2, 2023):
Hi guys,
I'm so happy to discover that Actual actually exists 🤣
After a few trials myself on building something like Actual/YNAB, I had gave up and migrated for a local paid Finance website and while it worked great, it wasn't a Zero Based budget tool.
So, I'm still figuring out as this tool works, one thing that I'm feeling it could be improved is the credit card scenario, but I'm not sure if this is just a problem on my side, I mean: here in Brazil (but I think the same applies globally), we have great advantages on using credit cards for basicly everything, as we have cashback using credit cards (like 1% to 1,5% on every transaction).
For budgeting is really ok: when transaction happened is when category should incur the cost, but to conciliate the statements is like a nightmare, once Banks filters transactions by statement due date it's hard to not mess one statement with transactions from another one.
It'd be hard to deploy a view to filter transactions by due date?
Also, one thing I heard that is not common in another countries is the possibility to split the payment of a purchase in no interest installments, for example, a couple months ago I've paid half of a car in 10 installments, so I'd really like to have a option to incur each installment in its budget month, as this make senses for recurring subscriptions and big assets purchases like a car.
I mean, I'd be happy to help on building those features if those features are something devs would like to see in the future.
I'm also available to translate Actual to Brazilian Portuguese.
So, many thanks for this fantastic tool and I'd love to see if you guys have any interest on this.
@piyushpaliwal commented on GitHub (Jul 6, 2023):
I am also in a similar situation. Basically, the guide that's available covers the scenario where you pay off credit card completely on the same month. However, the real use-case is a little different.
For me, I get paid on 1st June and do my budgets the same day; the credit card bills get generated in the middle of the month, say 15th June. This includes transactions from previous month (16th May to 15th June), and at the same time I am making transactions for the current month on credit card (starting 1st june), putting them in actual and tagging appropriate category to it.
So, there is indeed a balance that I am carrying, thus making the credit card category required. Based on the guide, I set it up in such a way that am carrying the overspending on CC category to the next month but the moment I pay/transfer the previous month's CC bill, I end up in exactly the same situation as OP; credit card account shows 0, however, I am left with cc category budged amount.
Am super confused, pretty new to budgeting and actual in general. Any help around this would be really appreciated.
@diraol commented on GitHub (Feb 29, 2024):
100% with @rafacla that would be really an outstanding feature!