Defect Introduced on Overspending Calculation?
Since the last two updates today, I am seeing on my Visa an overspending amount exactly equal to a single transaction. I checked that category, and it is funded with a positive amount. As a paranoia measure, I overfunded the category to cover that amount, and the Visa account still shows the overspending. I am running the YNAB Toolkit, and all credit card balances are not reporting an error. The balances further tie to the budgeted amounts for the credit cards. Was something introduced in the last set of updates? Only the web shows this issue. In both the iPad and iPhone apps, everything looks normal.
Hey, Saish Dawg !
I bet this is a known bug related to credit card returns. Are you seeing the amount of that transaction showing up in a different Credit Card Payment category as excess money above your current balance (if you pay in full)? If so, that's the bug.
If you'd like to me to take a look at your budget and confirm, I'd be happy to. Just enable Support Access and let me know. But the workaround is to just move money between Credit Card Payment categories and wait until the month rolls over for the overspending warning to clear. :(
I've previously been able to use the Toolkit's "rectify difference" to correct that (and then a browser refresh). However, now, it's persisting. Toolkit not reporting any discrepancy. And balances match the amounts budgeted for the credit card payments. There have been refunds (my first thought to check). But the amount matches an exact debit transaction on that credit card.
Well I think it is definitively a bug. It was a single transaction in "stuff I didn't budget for" (that category remained overfunded throughout). I simply recategorized it as "exceptional" and then moved the money over, and the overspending disappeared. If I move the amount back to the original category (even though it has plenty budgeted), the Visa account erroneously shows overspending.
It is not the YNAB Toolkit causing it either. Disabling and refreshing the page and repeating the above results in the same behavior.