Our second July release is now live with updated Support at Home quoting rates, fixes for the SAGE invoice export and Support at Home statements.

Updated the Support at Home quote tool with the government's Schedule of Subsidies and Supplements effective 1 July 2026. Quotes dated on or after 1 July 2026 will automatically use the new classification and supplement rates, while quotes dated earlier will keep the previous rates so existing quotes are unchanged.

Fixed issues where the SAGE invoice export could apply GST to GST-free lines, pull through incorrect accounting codes for some line items, and export unit amounts lower than those recorded in Visualcare. Exported invoices will now reflect the rates, accounting codes, and tax settings configured in Visualcare, so exports no longer need to be corrected manually before loading into SAGE.

Fixed an issue where a participant's Home Modifications budget was not shown on their statement, either as a budget graph or in the Budget Information section, even though the budget existed on the participant's record. Home Modifications budgets will now appear on statements alongside other budget types.

The updated NDIS Support Catalogue is now available in Visualcare. It reflects the 2026-27 NDIS pricing schedule released on 3 July 2026.

If you already updated your pricing before 14 July 2026, please follow the steps again. The NDIS has added new Support Items that were not included in the initial release.

Your existing pricing will not change automatically. When you are ready, update your NDIS pricing by following the steps in our guide: Update NDIS Pricing.

You will also need to update your Supported Independent Living (SIL) agreements to the new NDIS line items. Follow the steps in our guide: Update your SIL agreements to the new NDIS line items.

Questions? Contact our support team through the helpdesk.

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.

This release introduces Pay Cat Connect, an integration that brings automated SCHADS Award interpretation into your rostering and payroll. Pay Cat handles the award interpretation, and Visualcare gives your rostering and payroll teams the cost visibility to act on it.

Pay Cat Connect adds two capabilities, depending on your plan.

See the real-time SCHADS cost of a shift while you are still on the client roster. When you assign a worker and interpret the shift, Pay Cat looks across the whole pay period, so if that worker has already picked up hours elsewhere, you see the overtime, broken shift or minimum engagement impact before you finalise the roster, not after payroll has run.

Send approved timesheets to Pay Cat, review the interpreted costing grouped by worker, then export the costed payroll to Xero or MYOB.

Pay Cat's SCHADS Award interpretation has been independently audited by Effective HR and legally certified by SLF Lawyers, so your teams are working from award logic that has been verified by HR and legal specialists.

Pay Cat Connect replaces the legacy vAir interpretation and covers the full SCHADS Award, a significant upgrade on what vAir could do.

Want it switched on? Reach out to your customer success manager.

We have updated the NDIS Support Catalogue in Visualcare ahead of the annual NDIS support price changes that apply from 1 July 2026.

The updated NDIS Support Catalogue is now available in Visualcare. It reflects the 2026-27 NDIS pricing schedule released on 22 June 2026.

Your existing pricing will not change automatically. Once you are ready, you can update your NDIS pricing by following the steps in our guide:

We recommend applying the update so your pricing is ready to go from 1 July 2026.

If you have any questions or need help with the update, please reach out to our support team. We are happy to help.

Our second June release is now live with fixes for several issues affecting the Support at Home Dashboard, Statements, Invoicing, Worker Timeline, and Documents.

Our first June release is now live with fixes for two issues that have been affecting statements and the Support at Home Dashboard.

Fixed an issue where participant statements showed incorrect figures for clients with Home Care Package (HCP) or Commonwealth Unspent Funds (CUF) utilisation. In the Ongoing summary, the utilised amount was being incorrectly deducted from the available budget rather than added to it, causing the remaining balance to appear lower than it should be. Statements will now calculate and display the correct figures.

Fixed an issue where March statements (and later months) were not appearing in the Support at Home Dashboard for some providers, even when the statements had been successfully generated. These are now visible as expected.

Our latest release is now live. This one is heavily focused on Support at Home statement reliability and invoicing workflow improvements, along with a handful of platform usability fixes that have been on the list for a while.

We've resolved several statement issues that have been causing pain across a number of customers.

May 19, 2026

09:10 - 16:30 AEST

Visualcare web application (app.visualcare.com.au)

At approximately 09:10 AEST, customers began reporting that the Visualcare web application had become slow and unresponsive. Investigation identified that the primary web application server had entered a degraded state after running under sustained high CPU load for approximately two weeks.

During the incident, a series of unhandled application errors caused PHP-FPM worker threads to hang, resulting in elevated CPU utilisation on the primary server. The degradation became severe enough that AWS was unable to successfully reboot the instance remotely.

Engineering worked to restore service by reintroducing a previous web server and later deploying a new replacement server behind the load balancer. While these actions partially restored access for many customers, additional routing inconsistencies were identified where some customer domains bypassed the load balancer entirely and pointed directly to the failed server. This caused continued intermittent failures for affected customers until those paths were identified and corrected.

The incident was fully stabilised after the temporary replacement environment was removed and routing behaviour was normalised.

Elevated utilisation. See the healthier utilisation following remediation actions outlined in red.

Administrators across multiple providers experienced significant slowness, intermittent failures, and periods where the Visualcare web application was unavailable during the incident window.

Worker and Participant access through the Visualcare mobile applications was unaffected.

No data loss or compromise occurred during the incident.

On May 19, a series of unhandled application errors triggered a condition where PHP-FPM worker threads became stuck and did not recover correctly. As the number of hung workers increased, CPU utilisation escalated, resulting in the server becoming unresponsive to both application traffic and infrastructure management operations.

Because some customer domains were configured to bypass the load balancer and point directly to the affected server, those customers continued experiencing failures even after alternate infrastructure was introduced.

Attempts to restore service using both a previous server and a newly provisioned server improved availability for many customers but introduced secondary issues, including SSL/SNI mismatches and login instability, which prolonged the incident duration.

Engineering restored partial service by temporarily reintroducing a previous web application server into the load balancer, followed by deployment of a newly provisioned replacement server.

During investigation, it was discovered that some customer domain configurations bypassed the load balancer entirely. These configurations were corrected so traffic could route through the intended infrastructure path.

The affected server was ultimately isolated from production traffic while further remediation and stability work continued.

13 May 2026

16:30 – 17:10 AEST

Visualcare web application (app.visualcare.com.au)

Following a scheduled deployment at approximately 16:30 on 13 May 2026, users began experiencing login failures on the Visualcare web application (app.visualcare.com.au). During the deployment process, a file intended for the API component was inadvertently deployed to the web application, overwriting an existing file of the same name (functions.php) that serves a different purpose within the web app. This caused the login authentication step to fail, preventing users from accessing the application.

Engineers responded immediately and began investigating the issue by tracing the path of the login error. Through this analysis, they identified that functions.php on the web application had been replaced with an incorrect version during the deployment. Once identified, the correct version of the file was restored from version control and redeployed to the web application, resolving the issue at 17:10.

During the incident window (16:30–17:10 on 13 May 2026), users were unable to log in to the Visualcare web application (app.visualcare.com.au). No other systems were impacted, for example vWorker remained fully operationally during the outage.

During the 13 May 2026 deployment, the wrong source folder was selected, resulting in the API version of functions.php being uploaded to the web application server instead of the correct web application version. Both components contain a file with the same name; this was not immediately apparent during transfer and led to the web application’s authentication failing.

The issue was resolved by restoring the correct version of functions.php from version control and uploading it to the web application server. Following the fix, the deployment was re-executed using the correct source folder to ensure all intended updates were applied to the appropriate servers.