Before You Sign Up for Any NDIS Software, Five Questions That Expose What You Are Actually Getting

As of March 2026, the NDIS supports over 630,000 participants across Australia. The Commission’s audit activity has increased sharply. Manual compliance tracking is unsustainable for most providers. And the software market is crowded with platforms that look similar in a demo but operate very differently in practice. These five questions will tell you more about a platform than a 30-minute product tour ever will.

Every NDIS software demo looks good.

The presenter knows the platform. The data is clean. The billing run in the demo takes four minutes. The incident gets logged in thirty seconds. Everything works smoothly because it was designed to work smoothly in that specific controlled context.

Then you go live. And you find out what the demo did not show you.

The session note that takes fourteen minutes because the mobile interface is clunky. The billing error that cannot be traced because the session log and the financial record are in different systems. The audit request that takes three days to respond to because nobody indexed the records properly.

The gap between demo quality and operational quality is where most software purchasing mistakes live. The five questions below are designed to close that gap before you sign anything.

Question 1: Show me what happens when a billing claim is rejected

Not describe it. Show you.

Ask the presenter to demonstrate, in the live system, what happens when the NDIA portal returns a rejection on a specific claim. Where does the rejection appear? How does the billing administrator find out? What are the exact steps to identify the error, correct it, and resubmit?

This matters because manual compliance tracking has become unsustainable for most providers and payment rejection rates for manual NDIS billing averaged 14 percent in 2025. A platform that handles rejections smoothly is a different operational experience from one that sends an email notification and leaves the rest to the billing admin.

A good answer looks like: the rejected claim surfaces in the billing dashboard with the specific error identified, the correction can be made without rebuilding the entire submission, and the corrected claim can be resubmitted in under five minutes.

A red flag answer looks like: “we send you a notification and you can then re-enter the claim.” That is the process you already have. You are not buying a process. You are buying something better than the process you already have.

Your NDIS client management software should make the rejection-to-resubmission cycle a 5-minute task. Not a 45-minute one.

Question 2: Show me a worker note submitted at 9 pmon a phone with two bars of mobile signal

This is the real-world test that most demos never run.

Ask the presenter to open the platform on a mobile phone in the demo room, not on a desktop with a full keyboard. Ask them to log a progress note as a support worker would at the end of a shift. On the phone. In the session note template. With goal selection and submission both included.

Watch how many steps it takes. Watch whether the worker needs to navigate away from the note to find the participant’s goals. Watch whether the note template is optimised for mobile or whether it is a desktop form squeezed into a small screen.

This matters because incident management and rostering are the two features that have the most impact on daily operations, followed by participant management and NDIS claiming. Workers who cannot submit quality notes from their phone at the end of a shift will not submit quality notes. They will write something brief from memory later. That brief note becomes your plan review evidence. That plan review evidence determines your participant’s next budget.

If the mobile experience is genuinely good, the presenter will not hesitate to demonstrate it. If they redirect to the desktop, you have your answer.

NDIS compliance software built mobile-first means the session note a worker submits at 9pm from a regional property is as structured and complete as one submitted from a desktop at 9am.

**Try CTARS free at ctars.com.au.** Test the mobile note experience yourself on real sample data. No credit card required.

Question 3: Show me the billing for a Saturday SIL sleepover with travel

This is the technical depth test.

SIL billing involves multiple shift types at different rates. A Saturday sleepover is a specific billing scenario with its own line item, its own rate, and its own rules. If the platform cannot handle this correctly automatically, it cannot handle SIL correctly.

Ask the presenter to walk through how the platform bills a Saturday sleepover shift for a SIL participant, including any travel component. Ask which item codes it generates automatically and which require manual selection. Ask what happens when the shift crosses midnight into Sunday.

General rostering software does not understand SCHADS Award rates and generic invoicing tools cannot validate NDIS line items against the current Price Guide. A platform built specifically for NDIS has this mapped. A platform adapted from a generic tool will require manual selection at billing time.

NDIS billing that maps shift types to item codes automatically from session scheduling means the SIL Saturday sleepover generates the correct claim without a billing admin making decisions that should be made by the system. CTARS integrates directly with Xero and MYOB so the financial records update automatically once the claim is processed.

Question 4: Show me where participant data is stored and what the security certification is

Every NDIS software platform says it is secure. Not every platform can prove it with a verifiable certification.

Ask directly: where is participant data physically stored and what is the security certification? Is the data stored in Australia? Can you show me the certification on a publicly verifiable register?

The Australian Privacy Act requires that personal information transferred overseas is protected to an equivalent standard. The NDIA’s own guidelines expect participant data to be stored and managed to an appropriate standard. A platform that cannot confirm Australian data storage or cannot point to a verifiable certification is a compliance risk you are taking on.

CTARS holds ISO 27001 certification which is the international information security management standard and is verifiable on the public JAS-ANZ register. All participant data is stored on Australian servers. The answer takes thirty seconds and points to a public register, not a marketing claim.

If the answer to this question is “our data is secure” without a verifiable certification or a specific server location, that is a gap worth noting.

Question 5: What happens on 1 July when the NDIS pricing changes?

This is the operational continuity test.

Ask the presenter what happens to your billing codes and rates on the day the new NDIS Pricing Arrangements and Price Limits come into effect each July. Do rates update automatically across all service types and worker qualification levels? Or does someone in your organisation need to update them manually?

The NDIS Pricing Arrangements are updated annually. Sometimes they change in July and again mid-year. Every time they change, every billing code that references an updated rate needs to be current before the first session of the new period is billed.

A platform where rates update automatically on the first day of the new pricing period means your billing admin does not need to manually update hundreds of rate configurations on 1 July. A platform where rates require manual updates means your billing admin is spending the first week of every financial year doing nothing but rate maintenance, and any session billed before the update is complete is billed at the wrong rate.

The answer to this question tells you a lot about whether the platform was built by people who understand how NDIS billing works in practice.

The question you do not need to ask, but should think about

Every platform on the market right now has a response to the 2026 reform environment. Mandatory registration expanding. Digital payment system rolling out. 90-day claims window from December.

Some platforms are genuinely built for what the NDIS requires in 2026. The NDIS regulatory environment in 2026 is going through its biggest transformation since the Commission was established in 2018. Some platforms are playing catch-up.

The question you should ask yourself after any demo is: did this platform feel like it was built for the sector it serves, or did it feel like a generic tool that has been adapted for NDIS? The difference shows up in the five questions above. It also shows up in the terminology the presenter uses, the specific compliance scenarios they can answer without looking anything up, and the speed with which they can demonstrate operations your team will run every week.

Read more about NDIS reporting requirements and how connected systems produce the continuous compliance evidence the 2026 environment demands.

CTARS has supported NDIS and out-of-home care providers across Australia since 2010. ISO 27001 certified. Australian data storage. Built by clinicians who understood NDIS operations before they wrote a line of code.

See every one of these five questions answered on the product tour. Check the pricing page for what fits your service.

The demo is not the product. These five questions are.

**Start your free trial at ctars.com.au.** Test every one of these five scenarios on real sample data. No credit card required.

**Book a 30-minute demo.** Ask us all five questions directly. See the answers in the live system. Bring your hardest scenario.