Negative Assigned on Mobile

Most likely, you're reading this because you saw a negative number in the Assigned column, and you're wondering— "how did that get there?"

The assigned column for a category shows a negative $34 assigned this month

You're in the right place! This typically happens when a category has cash left over from a previous budget month, which gets moved to a different category. Let's walk through an example scenario!

Here I had $50 left over in the Clothing category at the end of August. That rolled into September—and I decided not to budget any  more money, leaving Assigned at $0 in September.

The assigned column for the category shows $0 and the Available column shows the $50 leftover from last month

In fact, I realize I need extra money in my Gifts category for September (Mimi's Birthday is coming! 🎁) and move $34 there, knowing I'll still have $16 left in Clothing. Any time money is moved out of a category, the Assigned value will decrease by that amount. Since $0 was Assigned in Clothing, it will decrease to negative $34, whereas the amount Assigned in the Gifts category will increase from $0 to $34. 

The assigned column shows the $34 removed from the first category and the $34 added to the second category

As long as the Available amount is green or gray, it's all good—there's no reason to worry about that negative number in Assigned - its just letting you know that more money was removed from the category than assigned to it this month. If it turned yellow or red though, you may want to move some money back until the Available amount goes back to zero.

Assigning Money in the Future?

While negative Assigned amounts in the current month are just fine, it should always be avoided in any future months. If the money ends up being spent in the current month, it can cause some unintended overspending at the start of the new month. When assigning or moving money in a future month, be sure that the Assigned column never dips below zero!

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.