Almost the same comment with this one.  It's going to hit the API once for each budget a user has, so this could get expensive fast.

In Graham's branch, he added in an API method that fetches all of the budgets and all of the entries, so we can just call that once when the user logs in and it will set up all of the data.

So I'd say delete this for now since it isn't doing anything, and then we'll just use Graham's method to set up the data.