my-ndis-portal

Status Page

My NDIS Portal

KB Type: Concept
Domain Area: Operational / Planning
Confidence: Provisional — requires Andrew's research to verify
Depth Hint: Standard
Version: 1.0 — 2026-04-26
Status: Provisional

Provisional article — seeded from NbLM. Requires Andrew's research to verify and expand.

Grounding Summary

The myNDIS portal (also referred to as the PACE portal) is the modern NDIS system that replaces the legacy myPlace portal for managing participant plans and provider payments. Under the new PACE framework, the myNDIS portal structures and tracks budgets differently, notably pooling funds at the broader support category level rather than separating them by specific item codes. This topic is critical for NDIS support coordinators because they must actively navigate these new structures, manually track sub-budgets, and interpret "specific planner instructions" hidden in the portal's "Support Details" to determine whether a participant's funding is flexible or restricted by a "digital lock."

Detail

Transition from Legacy myPlace

The myNDIS portal represents a fundamental shift from the legacy myPlace system. Key differences include:

Feature Legacy myPlace myNDIS (PACE)
Budget structure Item-code level tracking Category-level pooling
Digital lock visibility Mathematical heuristics Explicit "Allocated Items" table
Stated support warnings Implicit (claim rejection) Explicit portal warnings
Sub-budget tracking Manual estimation Portal-managed (emerging)
Plan architecture visibility Limited Enhanced with Support Details

Category-Level Budget Pooling

Under the PACE framework, budgets are pooled at the support category level. For example, Category 07 (Capacity Building - Support Coordination) may contain funds for Level 1, Level 2, Level 3, and PRC all within a single pooled amount. The portal does not automatically track sub-budgets for each item code within the category.

This pooling creates operational challenges:

  • Manual tracking required: Coordinators must maintain separate records of how much has been claimed against each item code
  • Risk of overspending: Without careful tracking, participants may inadvertently deplete funds allocated for specific purposes
  • Planner instructions matter: "Specific planner instructions" in Support Details may indicate intended allocations that the portal doesn't enforce

The "Allocated Items" Table

The myNDIS portal features a prominent "Allocated Items" table that defines budget restrictions:

  • Stated designation: If an item is marked as "Stated", the portal applies a definitive digital lock
  • Explicit warnings: The system displays warnings such as "Stated supports are intended solely for the purpose of that support"
  • No allocated items: If the category shows no stated allocated items, flexibility remains intact

Support Details and Specific Planner Instructions

Within the Support Details section, planners may include specific instructions about:

  • Intended use of funds within a category
  • Which item codes should be prioritised
  • Whether funds should be treated as stated or flexible
  • Special conditions or requirements

Coordinators must interpret these instructions to understand the intended budget architecture, even when the portal itself doesn't enforce these distinctions.

Relationship to Participant Statement Toolkit

The Participant Statement Toolkit is specifically designed to bridge the participant's voice with the technical architecture of the PACE system:

  1. "PACE Budget Architecture Recommendations" section (Block 3): Allows coordinators to proactively advise NDIA planners on myNDIS portal configurations
  2. Recommending funding periods: Suggesting fortnightly, quarterly, or annual releases based on risk assessment
  3. Designating flexible or stated: Recommending whether categories should be locked or remain flexible
  4. Applying digital locks: Formally recommending locks to mitigate risk

Mastering the Portal

Support coordinators must master the myNDIS portal to:

  • Build compliant service agreements
  • Advocate for correct plan architecture
  • Prevent billing failures
  • Navigate the transition from legacy to PACE plans
  • Distinguish between "migrated" legacy plans and natively-built PACE plans

The Category-Level Tracking Limitation — An Acknowledged NDIA System Flaw

RS-09 research (T2) documents a significant and explicitly acknowledged limitation of the current PACE portal: budgets are tracked at the support category level, not at the item-code level. For Category 07, the portal shows a single aggregated "Released / Spent / Available" balance regardless of how the planner has structured the funding internally.

This limitation becomes critical in dual-budget (Configuration C) scenarios — where a plan's Specific Planner Instructions allocate separate amounts to Level 2 Coordination and Level 3 Specialist Support Coordination from the same Category 07 pool. The portal merges these into one wallet. It cannot prevent a provider from inadvertently drawing Level 3 funds against Level 2 billing codes. The entire sub-budget tracking burden falls on the provider.

Operational implications:

  • Providers must maintain internal records that mirror the planner's intended sub-budget split
  • Service agreements must document the sub-budget structure explicitly
  • Billing systems (such as iinsight) require custom logic to enforce plan-level restrictions the portal cannot enforce itself

The NDIA has acknowledged this as a system limitation and a portal upgrade to enable item-code-level tracking is reportedly planned — but no rollout date has been confirmed as of RS-09 (2026-05-01).

Legislative Basis

Reference Provision Relevance to this article
NDIS Act 2013 s33(2A) Budget categorisation and periods Legislative basis for PACE portal architecture
NDIS Amendment Act 2024 PACE framework introduction Enables new portal system

Confidence is Provisional because this article is NbLM-generated and requires Andrew's research verification.

Open Questions

  • Q-KB-113 — How will the myNDIS portal handle upcoming upgrades to track individual item-code-level budgets (e.g., separating Level 2 and Level 3 Support Coordination)? — 2026-04-26
  • Q-KB-114 — What are the best methods for coordinators to definitively distinguish between a legacy plan that was "migrated" into PACE versus a plan built natively in PACE? — 2026-04-26
  • Q-KB-115 — Should the current toolkit be adapted to explicitly accommodate old framework plans, or should it remain exclusively PACE-oriented? — 2026-04-26

Entity Tags

  • entity: my-ndis-portal
  • type: Concept
  • domain: Operational / Planning
  • confidence: Provisional
  • links: [[concepts/pace-framework]] via implements, [[concepts/legacy-crm]] via replaces

Change History

Date Change Source
2026-04-26 Initial article created from NbLM primer RS-06 ingest
2026-05-01 E-M5: Backlinks added — topics/budget-tracking-limitations-pace, topics/legacy-pace-plan-flexibility, topics/digital-lock-mechanism (RS-09 T2, T1, T3) Sonnet E-M5
2026-05-01 E-M6 enrichment — Category-level tracking limitation section added: dual-budget burden, acknowledged NDIA flaw, planned upgrade, from RS-09 T2 Sonnet E-M6