I am playing around with different parameters, also setting a different date in the query param, but the result is still the same (current_balance: 0)

Strange. In my test runs on the demo site (and locally) it works as expected. I'll see what I can find.

Thanks!
I have no idea why it happened. In the past it was working fine. I'm also browsing through code to find the possible reasons why it happens and all I got is either the cache or the balance in the DB. When I run cache clear command from the console, I see no difference. When I try to do the same from admin, I'm getting the request timeout, because the operations take very long to execute.

Ok, I spent a while on learning Laravel and analyzing the code to investigate the issue ;) I'm sharing my thoughts requesting for a second pair of eyes, maybe I missed something.

• First of all, I noticed that in version 6.2.0 method that calculates the current balance has changed since the last version 6.1.x. Specifically, Steam::finalAccountBalance. For the reference, here's the link with current version in main branch
• What I didn't mentioned in the ticket, the accounts that are affected are of expense type. In that case the $accountCurrency will be null. Hence, the $hasCurrency will be false as well
• The next var, $convertToNative will be false as well, as this preference is disabled for me, so the condition line 316 is not met, so it won't be executed
• In line 355 there are additional calculations, and when I ran the query directly on the DB, it returns valid results, however...
• The condition in line 364 won't be executed as $hasCurrency is false
• Next condition in line 375 won't be met, because the $return variable hasn't been filled with any data yet so the array_key_exists function will return false
• And finally we are coming to the end of this method and no balance has been found, so it always return 0 in the AccountTransformer for expense accounts.
• I noticed that this function works well for assets accounts so some breaking change (and a bug) had to be introduced with converting to native currency feature.

@JC5 Please take a look at the investigation results and confirm whether they make sense. Unfortunately I haven't found any solution to that yet as I don't know the code good enough, but maybe you'll figure it out :)

Good work, this makes sense. I see some other issues with this method as well, so I will pick this up asap. Thanks!