Bug: Currency Conversion Issue in Budget Calculation

[rezaplus]

Bug Description:
There is a discrepancy between the transaction currency and the budget calculation currency. Specifically, as seen in the attached screenshot:

Transactions are recorded in TRY (Turkish Lira).
Budgets are calculated using the default currency (USD), without proper currency conversion.

This leads to misleading budget overspending values. For example:

Transaction: 13,000 TRY (correctly recorded).
Budget: 365 USD, leading to an inaccurate overspending calculation of $12,635 USD.

[zachgoll]

@rezaplus thanks for the report! Just to confirm—is your family currency set to USD, and a subset of your accounts have transactions in TRY?

In other words, you're intending for the overall budget to be in USD and specifically commenting on how individual transactions are not properly rolled into the totals?

[rezaplus]

Hi @zachgoll thanks for getting back to me!

Yes, my family currency is set to USD, but I have accounts with transactions in TRY.

I intend for the overall budget to remain in USD, but the issue is that individual transactions in TRY are not being properly converted into USD before being rolled into the totals. This causes the budget calculations to show inaccurate values and overspending warnings.

Let me know if you need more details or testing on my end!

[zachgoll]

@rezaplus got it, thanks for the detail! That's all I need.

[zachgoll]

We may need to implement #1615 prior to being able to fix this because many of the budget calculations are run in fairly verbose queries, which will require joins on the exchange_rates table (and thus, will need those rates pre-loaded).