When a service user has an end-dated budget and a worker tries to add a new budget with a new indicative amount for a new period, they might see the following validation error when attempting to update the Budget Properties specifically when changing the Purchasing Team and Budget Codes, followed by the Change Date:
‘The change date must not be after the budget end date.’
For example, when a service user’s already had a budget and provisions purchased up to a certain end date, the Budget Properties screens rigidly hold those start dates (01/01/2025) and planned end dates (30/03/2025) for that original budget period, and you can’t flex them afterward via Change Date when you try to change the purchasing team (Purchaser and Budget Code tabs).
When the worker creates a new budget period through additional worksteps in the workflow, then tries to amend the Budget Properties (Pencil > Budget Properties button) by changing the purchasing team and setting a new Change Date, the system shows an error validation.
We’ve raised this with our Product and Engineering teams. However, since Mosaic Finance has entered its end-of-life phase, we won’t be making further code changes in this area. As a result, Mosaic Finance will continue to operate as it currently does until it’s decommissioned.
If you're affected by this issue, you'll need to work with Mosaic's current functionality. We're actively working on a replacement finance solution and will make every effort to ensure it doesn't replicate this problem.
In light of this, we advise you to continue new budgets from old ones using the original purchase team and budget codes they were first procured with, since changing them won’t work and won’t be developed further.