Release Notes: 8 Jul 2026

Our first July release is now live with fixes for several issues affecting the Support at Home Organisation Dashboard, Budgets, and Reconciliation and a fix for location rostering.

Support at Home Organisation Dashboard

Fixed an issue where the Planned Spend and Claimed Funds figures shown on the Organisation Dashboard did not match the figures produced when exporting the same view to CSV. The dashboard, drilldowns, and exports now draw from the same data and will show consistent figures.
Fixed an issue where the drilldown list under each funding type card was including items from all funding types rather than only the selected one, meaning the drilldown could not be reconciled against the card above it. Drilldowns will now show only items for the selected funding type.
Fixed an issue where organisation-level totals could exclude some participants' claimed and committed amounts, understating figures and allowing them to change between page loads. Totals are now calculated consistently across all participants.
Fixed an issue that could cause the Planned Spend drilldown to fail to load with an error for some organisations.

Support at Home Budgets

Fixed an issue where new quarterly ongoing budgets received from the government API were not linked to the participant's existing funding agreement. This required agreements to be manually re-linked every quarter and could cause statements to fail to generate. New quarterly ongoing budgets will now automatically link to the same agreement as the previous quarter's budget, and a warning will be shown if the agreement's date range does not cover the new quarter.

Support at Home Reconciliation

Fixed an issue where uploading a payment file would fail with "Unable to parse payment file" when a free-text field in the file, such as a multi-line address in a transport line item, contained a line break. These files will now process successfully without needing to be manually edited.

Rostering

Fixed an issue where unassigning a worker from an assigned location roster invitation removed the invitation and created a duplicate location client shift that could not be reassigned to another worker. Unassigning a worker will now behave as expected.