KB Type: Research Theme
Domain Area: Technical/Practice
Confidence: Researched (Andrew via NbLM, RS-05a / RS-05b)
Depth Hint: Standard
Version: 1.0 — 2026-04-25
Status: Active

The National Disability Insurance Agency (NDIA) has transitioned from the Legacy CRM system to the new PACE system, fundamentally altering how claim validations occur. In the Legacy system, claims are rigidly validated against specific line items and exhausted dollar amounts visible in the MyPlace portal. In the new PACE system, validation logic operates primarily at the broader support category level. PACE plans feature a "Support Detail" section within the MyNDIS portal that explicitly labels what supports are stated versus flexible, replacing the need for providers to deduce plan flexibility using financial heuristics. However, because PACE plans include both cleanly migrated Legacy plans and newly built native plans, providers are advised to empirically test claims to verify the exact validation rules.

The NDIA is progressively migrating participants from its older Legacy Customer Relationship Management (CRM) system to the modernised PACE platform. Providers interface with Legacy plans via the MyPlace portal, whereas PACE plans are exclusively accessed and managed through the MyNDIS Provider Portal. This system upgrade fundamentally alters the technological interface for providers, moving claim administration from older infrastructure to a new portal environment. During the transition, a pattern emerged suggesting that simpler PACE plans were often directly migrated Legacy plans that retained less granular data structures, while highly detailed plans were constructed natively within the new PACE system.

In the Legacy system, understanding plan flexibility required providers to decode implicit "digital locks" on a participant's funding. Legacy claims for agency-managed plans are strictly validated against the specific line items and exact dollar amounts visible in the MyPlace portal. If a specific item code is stated alongside a designated dollar amount, the system automatically rejects claims against that code once the funds are exhausted. Furthermore, the Legacy system typically rejects claims for item codes that are not explicitly stated in the plan unless the broader support category inherently permits flexibility.

To navigate this, providers developed an "exact multiple" heuristic to deduce if Category 07 funding was digitally locked to a specific support item, such as Level 3 Specialist Support Coordination. By calculating if the total funding was a clean multiple of the Level 3 hourly rate, providers inferred whether the funds were locked. However, this method is fundamentally fragile because planners frequently include buffer amounts, round figures, or factor in expected non-labour travel costs, which disrupts the clean multiple and leads to false negative assessments of the plan's flexibility.

In the PACE system, this "exact multiple" heuristic is rendered entirely unnecessary. The new system introduces a "Support Detail" section that explicitly describes the types of support a participant can access and labels what is stated versus what is flexible. PACE validation logic appears to shift from line-item rigidity to broader support category validation. Despite this added visibility, the exact claim validation behaviour at the moment of submission can remain ambiguous.

The transition to PACE is not a clean binary switch; the reality involves a complex spectrum of migration scenarios, including "light touch" reassessments that create varying levels of detail within the new system. Because PACE validates claims at the point of submission based on these varying structural scenarios, providers are advised against relying purely on hypotheses or portal inferences to determine billing boundaries. For example, determining whether PACE will validate a claim for Psychosocial Recovery Coaching against a plan that only explicitly mentions "Coordination of Supports" requires direct verification. The most reliable method to navigate PACE claim validation is to empirically verify the system's rules by executing test claims or consulting directly with the NDIA Provider Support team. Consequently, provider billing systems must be designed to accommodate both legacy display formats and new PACE structures without assuming a standardised data format.

Entities referenced: NDIA, NDIS Support Catalogue, NDIS Pricing Arrangements