mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 22:54:03 -05:00
[GH-ISSUE #6618] [Feature] Suggestion for Reconciliation Adjustment Logic #9741
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#9741
Reference in New Issue
Block 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 @vi000246 on GitHub (Jan 11, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6618
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
Dear Actual Budget Team,
I would like to suggest an improvement regarding the reconciliation process.
Currently, when an adjustment entry is created during reconciliation, the system flags it as "uncategorized."
However, these entries are meant to sync account balances, not to track discretionary spending.
If a category is assigned to these adjustments, it impacts the budget allocations directly.
This can lead to accounting imbalances and makes it difficult to keep the budget and bank balances in sync.
I suggest exempting reconciliation adjustments from the "uncategorized" warning to maintain budget integrity.
Thank you for your great work!
Describe your ideal solution to this problem
No response
Teaching and learning
No response
@github-actions[bot] commented on GitHub (Jan 11, 2026):
✨ Thanks for sharing your idea! ✨
This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 👍!
@jfdoming commented on GitHub (Jan 11, 2026):
In an on-budget account, a reconciliation adjustment is money you spent. So in order for the budget to be balanced it must have a category—you just need to determine how you want to assign the category. For example, a common pattern would be to assign it to your emergency fund. An even better pattern is to ensure you don't have missing transactions in the first place. You can also auto-categorize the reconciliation transactions, if you like, by writing a rule that applies to them.
@vi000246 commented on GitHub (Jan 11, 2026):
Since I migrated my records from another app, allocating the budget has been quite difficult.
Thanks for your reply! I've decided to start a fresh budget year and archive the old data so it won't affect this year's budget.
@jfdoming commented on GitHub (Jan 11, 2026):
That is a good idea! It's also okay to be less specific about categorization when you're starting out.
@db-src commented on GitHub (Jan 11, 2026):
In such a case, I would probably just make a category like Misc or Unknown to avoid it being uncategorised. Like saying 'this does not really have a real category, but I have deliberately chosen to "categorise" it as such' 🤣