Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: "To Budget" should take into consideration transactions with no category #2377

Closed
1 of 5 tasks
tavlima opened this issue Feb 19, 2024 · 4 comments
Closed
1 of 5 tasks
Labels
bug Something isn't working

Comments

@tavlima
Copy link

tavlima commented Feb 19, 2024

Verified issue does not already exist?

  • I have searched and found no existing issue

Is this related to GoCardless, Simplefin or another bank-sync provider?

  • I have checked my server logs and could not see any errors there
  • I will be attaching my server logs to this issue
  • I will be attaching my client-side (browser) logs to this issue
  • I understand that this issue will be automatically closed if insufficient information is provided

What happened?

I just imported 6 months worth of transactions and didn't have time to go and classify all of them, but coming from nYNAB, I thought I could rely on the "To Budget" for current/future months, still... Except that I can't.

IMHO, the current behavior is misleading, as I definitely don't have 900 available for March.


The transactions

image

The budget

image

nYNAB transactions

image


nYNAB budget, for reference

image

image

What error did you receive?

No response

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

No response

Operating System

None

@tavlima tavlima added the bug Something isn't working label Feb 19, 2024
@youngcw
Copy link
Member

youngcw commented Feb 19, 2024

There is a feature request for this #1794. Closing the issue since its not really a bug, but its true that it can be confusing.

@youngcw youngcw closed this as completed Feb 19, 2024
@tavlima
Copy link
Author

tavlima commented Feb 19, 2024

I see. IMHO it is not just confusing: it makes the whole budget useless, unless you have all of those transactions categorized. In fact, this is the second bug report about the same thing, so I'm afraid we will have to disagree on how to classify this. If this is not a bug, then I guess it is "by design", which doesn't make much sense to me.

@tavlima
Copy link
Author

tavlima commented Feb 19, 2024

Also, apologies for not search thoroughly before posting this.

@Kidglove57
Copy link

I have four years of records in Actual so of course I can’t fully appreciate your situation. However, leaving aside any rights or wrongs as to the issue you raise, I would have approached it this way:

  1. Set an opening balance on each account at the beginning of the series of imported transactions.
  2. Check that my account balances after import are still correct
  3. Categorise all the imported transactions as either “Pre Actual Expenses” or “Pre Actual income”
  4. Start budgeting in Actual from the beginning of a new month using the account balances available
  5. In due course use the “hide category” facility for the “ Pre Actual” categories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants