Zerosum
Zerosum
Apr 30

For Next Month Issue

I allocated all my income received during April to the "For next Month" category - say 4000.I have today budgeted this "For Next Month" money in May. This has correctly "zeroed" out  May and May is showing as "All Money Budgeted"However, what is misleading (at least to me) is that April now shows as 4000 "over budgeted"!  Whilst I do understand that the true effect is nothing, as May is showing the correct numbers, I am nonetheless reporting this as the display is misleading and a bit unsettling. I am still running BFB in parallel and that app gives me the correct numbers in both months.Have I inadvertently done something wrong?
CompletedCompleted

Completed
changed status toCompleted·Apr 30, 2026
Apr 30, 2026

Hello! Yeah, you've inadvertently caught a regression I introduced this morning. I shipped a fix for a different RTB issue (over-commitment to future months was being silently hidden), and unfloored the banner so users could see when they were genuinely over-committed. That unflooring exposed a separate bug in the math: FNM money was being subtracted twice — once correctly when it gets deferred from April's RTB, and then again as a "future commitment" when you budget it in May. Net result: April showed −4000 even though nothing was actually over-committed. Got the root cause identified and a fix is out. The new formula nets future-arriving money (FNM rolling forward, future paychecks, etc.) against future-month commitments before subtracting from the current month, so April will correctly show 0 in your scenario. Over-commitment will still surface as a negative number when it's real (e.g. if you budgeted 5000 in May with only 4000 of FNM, April would show −1000). Thanks for the detailed report. Let me know if you see any issues :)

Apr 30, 2026

Thank you for the quick fix! There was a very minor difference that was still there between the two months but this waacvery quickly resolved, so all good now and hopefully ahead of others trying to budget on 1 May!

Apr 30, 2026

Hey Paul! Glad the fix landed before May 1. Quick favor: when you say there was a very minor difference between the two months that resolved itself — could you remember roughly what it was? A specific cents-level mismatch, or which two numbers didn't quite line up? My best guess is the deploy rollover (the old browser bundle running against the new API for ~2 minutes until you next navigated), but I'd like to rule out a real arithmetic edge case before lots more people start budgeting on the 1st. Happy May 1st budgeting!

May 1, 2026

Good Morning! I am as certain as I can be that this was all resolved by your fix. This is where your unlimited undo table came in handy. I was 34.39 over assigned in April after the fix. So I covered this from another category. I then went into May and I had 34.39 available there to budget so I was able to move this back into the category that I had "borrowed" from. On looking back through the Undo table I found 34.39 that I had allocated to a category early last evening during my budgeting, pre fix. So it looks like this was the same issue but manifesting itself in two different ways. So it should only effect anyone else who made an early start on their May budgeting.

May 1, 2026

Nice, good to hear!

Progress
changed status toIn Progress·Apr 30, 2026