AndréRookie
Leider habe ich dasselbe Problem. Ausgaben werde in Insights teilweise gar nicht angezeigt, obwohl sie einer Kategorie zugewiesen wurden.
Leider habe ich dasselbe Problem. Ausgaben werde in Insights teilweise gar nicht angezeigt, obwohl sie einer Kategorie zugewiesen wurden.
@New-Pink-Anteater-3344903371#235944 Manchmal kann es ein paar Stunden dauern, bis sich die Insights vollständig aktualisiert haben. Besteht das Problem auch nach 24 Stunden noch, nachdem du die Kategorie vergeben hast für die Zahlung?
Mittlerweile werden die Kategorien in den Insights angezeigt. Allerdings ist die Verzögerung schon enorm. Gibt es evtl eine Möglichkeit diese Funktion in Echtzeit abzubilden in zukünftigen Updates?
Ja ik geraak er niet meer in
1 year later. Insight still suffers from wrong categories calculations. Terrible!!!
I have the same problem. At the moment it is so bad i think half of the transactions are calculated under the wrong spending group. This makes the budget tool useless. I hope they will fix this soon
Ik wilde het vandaag ook proberen. Leek mij logisch dat als ik bij een betaling de categorie wissel, die betaling ook bij die categorie wordt ingedeeld. In de uitleg moet het anders: dan moet je eerst naar een bepaald budget toe, en daar dan een betaling opzoeken (wat frustrerend genoeg niet meer werkt als ik de categorie al gecorrigeerd heb, want dan wordt hij doorzichtig/onklikbaar maar nog altijd niet meegeteld). Dit kan bv niet als je in die maand nog niets op een bepaalde categorie hebt. En als het wel kan, werkt het ook niet (tenzij met vertraging zoals sommigen hierboven beweren; morgen nog maar eens kijken…).
Es funktioniert leider immer noch nicht.
Insights is a core feature of the app, it’s also well built and it’s great that we can choose sub accounts. However… not showing corrected expenses under the right category makes the whole feature useless.
I have already mentioned the bug to support, let’s hope that the devs have some time for this, now that the new update is out of the way
By the way, I’d like to suggest 2 features:
Continues to be a problem for me as well. Insights is important to get solved imo.
I have the same problem. One of the main reasons I use Bunq is due to this feature. But it is becoming Bunq useless for me.
Vielen Dank für das Upgrade 20. Es ist wieder einiges besser geworden. Leider funktioniert die Budgetierung immer noch nicht.
I have the same issue and it is really annoying. Bunq, when will this be fixed?
I also have this issue, it's true that it is annoying. What worries me is that this was initially reported 19 months ago, it's an obvious bug that super shallow QA should catch. Makes you wonder how well tested and maintained the app actually is beneath the layer of constant new bells and whistles.
I also have the issue that changing the category doesn’t refresh the overview. This has been happening for a very long time and it also worries me that bunq isn’t able to solve this properly in a year’s time…
Nouveau sur bunq, j’ai rencontré le problème aujourd’hui et je suis très étonné de lire que c’est un problème connu de longue date.
I'm also experiencing this issue and echo others on how important this feature is. If this doesn't get fixed soon, it's a real reason for me to look for other solutions elsewhere as it's critical part of my use of Bunq.
If anyone is a fan of zero-sum/envelope budgeting (which is a bit different to the budgets offered by the bunq app) that also works reliably, then my personal recommendation is YNAB. I've used it for many years with bunq and it's possible to set up an automatic synchronization between the two on your own server. Currently I'm also looking into self-hosting Actual which seems to be another great solution but I haven't found the time to write an integration with their API.
I am having this problem as well. I found that it happens with all transactions, where I had to adjust the category after the transaction was registered. One transaction from last month was displayed correctly after the last update to version 20, yet all others were not.