Onscreen warnings:
'The proposed package will exceed available budget in period(s) starting: [date_start] - [date_end]'
'The cost of this support package exceeds the available budget'
Understanding when it’s intended behavior
When two lines on the costing tab are a few days apart, that may be intended behavior.
If the element types are costed as regular payments, that’s exactly how they should display. To show continuous costs, they’d need weekly pro rata elements. This works as expected.
For example, if your element types use a cost unit of “Regular payment (not pro rata)”, the payment’s due on the last day of the week (e.g., Sunday 7th April). Even though the rates start on 1st April, the first payment date is 7th April, that’s why the costs begin then. It may look like the previous costs miss a week, but what’s really happening is the system finishes one rate on a Sunday and starts the next one the following Sunday.
You’ll only see contiguous dates if the element type has a cost unit of “Weekly pro rata cost” or is “Costed and scheduled.”
Make sure staff know that the dates appear this way because of how the costs are set up.
Understanding when it’s unintended behaviour
We’re aware of an issue where the screens don’t always update to reflect the action you’ve taken, or you may see on-screen warnings like the ones above. This usually happens because the views don’t display as they should, not because there’s a problem with the care package data itself.
You’ll typically see this after actions like a rate uplift or a roll cost forward. In these cases, some front-end care package screens such as the Costing tab on an element provision screen don’t keep up with the change.
You might also notice issues when you drill into a weekly cost entry, where the quantity or rate values don’t look correct. Sometimes, you’ll even see a warning that the provisions you’re purchasing will exceed the package budget.
If the Costing tab is completely empty, that’s a separate issue, please see our article: Cost tab for the Service Element Summary is blank
Where any of the above are the case, the support team will be able to correct this with a script which takes data from the main source tables, and rebuilds the data for the auxiliary tables which rely on the source tables, and have the main job of supporting the views the worker sees and improving user experience.
Where any of the above happens, our support team can correct it with a script. The script rebuilds the auxiliary tables (which support what workers see on screen) using data from the main source tables, so the views display properly, and the user experience improves.
Please raise a new case online and reference the title of this article.