KB Type: Concept
Domain Area: Billing / Operational
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.

Cross-category claiming refers to the practice of billing certain support costs, such as provider travel non-labour expenses, to a flexible NDIS budget category instead of the primary support's designated category. Specifically, support coordinators can bill non-labour travel costs to the Core budget (Category 01) using codes like 01_799_0106_1_1 rather than depleting Capacity Building funds (Category 07). This strategy is crucial for NDIS support coordinators because it allows them to bypass "digital locks" where a planner has rigidly allocated all Category 07 funding to a specific stated item, which would otherwise cause travel claims to be rejected by the portal.

When an NDIS planner applies a "digital lock" or "stated" designation to Category 07 funding, the entire budget becomes ring-fenced to that specific 15-digit item code. For example, if 100% of Category 07 is allocated exclusively to Level 2 Coordination (07_002_0106_8_3), the NDIS payment portal will reject claims against other codes within that category, including the standard non-labour travel code (07_799_0106_6_3). The system registers a $0 flexible budget for the travel line item, resulting in "Insufficient Funds" or "Support Not in Plan" errors.

The NDIA has intentionally designed item codes that enable this workaround. For Support Coordination under Registration Group 0106, the item code 01_799_0106_1_1 is categorised under Support Category 01 (Assistance with Daily Life) rather than Category 07. When a provider submits a claim using this code, the portal bypasses the locked Category 07 budget and instead draws from the participant's Core budget.

The 2025-26 NDIS Pricing Arrangements and Price Limits explicitly validates cross-category claiming on pages 73-74, stating that providers of Level 1 Support Connection and Level 2 Coordination of Supports can claim non-labour travel costs using 01_799_0106_1_1. This regulatory validation makes cross-category claiming a compliant billing strategy rather than a workaround.

RS-09 research (T6) reframes cross-category claiming as a participant value-maximisation strategy, not merely a workaround for a technical portal constraint.

The conventional framing treats 01_799_0106_1_1 as a bypass when Category 07 is locked. RS-09 extends this: even when Category 07 is not fully locked, a provider may strategically elect to draw non-labour travel from Core rather than Capacity Building. The reasoning is that Category 07 budgets are finite and tightly scoped to specialist support — every dollar spent on travel is a dollar unavailable for direct face-to-face coordination or coaching.

By routing non-labour travel through Core:

This framing has direct implications for how the strategy is disclosed in Service Agreements. The rationale to present to participants is not "our billing system rejected the travel claim" but "we are protecting your specialist support budget so it goes further." Participant understanding and consent should be sought on that basis.

RS-09 also pairs this strategy with Activity Based Transport (ABT) for PRCs: in scenarios where the coordinator provides both coaching and transport to an appointment, the ABT code (07_501_0106_6_3) covers the support time, while 01_799_0106_1_1 covers non-labour travel expenses — both working together to maximise the value the participant receives from their plan.

RS-10 research (T3, T5) documents how the cross-category choice is operationalised at EYC's iinsight rebuild. The activity standard list implements a three-variant design for every non-labour travel event:

The key design principle is that the coordinator must actively choose cb or cr at the point of billing — the system does not default. This architecture eliminates the passive mistake of always drawing from Category 07 (which may be locked or scarce), makes the participant value-maximisation decision auditable at each entry, and prevents double-counting via the ms placeholder.

This is the most operationally concrete implementation of cross-category claiming documented in the wiki — a live software rebuild rather than a theoretical billing discussion.

For cross-category claiming to be compliant, providers should:

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