Back to blog
Pricing7 min read

SDA location factors: A pricing register checklist for providers

Location factors are easy to underestimate because they sit behind the headline SDA price tables. The current 2026-27 SDA pricing arrangements, released on 30 July 2026 and valid from 1 July 2026, include separate location factor appendices for new builds and for existing and legacy stock. The NDIS pricing page also links to an SDA price calculator to estimate expected annual income for an enrolled home. For SDA providers, this is not only a modelling issue. A wrong location, dwelling stock type, building type, resident configuration or source version can flow into claim assumptions, owner reports, vacancy projections and investor conversations.

Why location factors need a register

Many providers hold SDA pricing logic in spreadsheets, owner pro formas, accountant workbooks or individual finance notes. That can work for one dwelling, but it becomes risky across a portfolio with multiple states, build years, apartments, group homes, OOA rooms, sprinkler states and changing resident mixes.

The pricing arrangements set out the maximum prices the NDIA considers appropriate for SDA supports. They do not guarantee occupancy, participant funding, payment approval or owner income. The NDIA's investor guidance is also clear that SDA investment carries risk, that income is not guaranteed and that demand varies by location. A provider pricing register should therefore show the controlled basis for a price assumption, not present the assumption as a promise.

A practical register gives finance, intake, vacancy management and owner reporting the same answer to one question: what official pricing basis are we using for this enrolled dwelling and why?

Start from the enrolled dwelling

Do not start the record from a marketing brochure or development model. Start from the dwelling as enrolled or currently being enrolled. The NDIS enrolment guidance says providers need to apply through the my NDIS provider portal, upload mandatory documents, and the NDIA decides whether the home meets enrolment requirements. The guide to providing SDA also reminds providers that design stage certification does not itself mean the home will be enrolled as SDA.

That distinction matters for location factor controls because the pricing pathway depends on facts that should be anchored to the official dwelling record: address, postcode, enrolled building type, design category, stock type, resident capacity, OOA status, sprinkler status, GST treatment where relevant, enrolment status and claimable participant occupancy.

If a provider lets an owner model, assessor document or pipeline register override the enrolled dwelling record, pricing drift can enter before the first claim run. The operating record should preserve the source of each field and the date it was verified.

Build the pricing register fields

A good SDA location factor register should be boring, structured and easy to audit. The aim is to stop manual reinterpretation each month, especially when finance is reconciling claims while operations is managing vacancies and owners are asking for income updates.

Version the official source

Record the pricing year, version number, release date, document URL, calculator URL and date checked. The 2026-27 arrangements are version 1.0, and the NDIS page should remain the source for the latest version.

Lock the location basis

Store address, postcode, state, region label used in the pricing appendix, and who verified it. Avoid free-text region guesses where the claim and owner model depend on a specific location factor row.

Separate stock type

Keep new build, pre-2023 new build, existing stock and legacy stock as explicit fields because the arrangements use different base price and location factor tables for different stock categories.

Capture the dwelling configuration

Record building type, design category, bedroom and resident configuration, OOA, sprinkler state, breakout-room state where relevant, and resident mix. These fields determine which base table and location factor column applies.

Tie price to participant dates

Connect the pricing assumption to occupancy dates, service agreement dates, funding management type, my provider status and claim period. A correct annual price is still not claim-ready if the participant or portal pathway is not ready.

Store owner-reporting limits

Keep expected annual income, submitted claims, paid claims, vacancy assumptions and owner distributions in separate states. Do not expose participant NDIS numbers, plan screenshots or private support records in owner reports.

Reconcile before each claim run

The NDIS guide to getting paid says providers need participant details, support dates, support item reference number and support item price for payment requests. It also says claims must be accurate and in line with approved funding and pricing rules. For SDA, that means pricing verification should happen before export, not after a payment is rejected or questioned.

Use a monthly pricing control that compares the claim line against the register: support item, participant, dwelling, claim dates, annual price source, daily or period calculation, vacancy state, MRRC separation and payment pathway. If any field has changed since the previous month, require a reason code such as new pricing version, resident mix change, plan reassessment, enrolment amendment, OOA change, vacancy, correction or owner agreement update.

Keep rejected, capped or manually reviewed claims linked back to the pricing register. Without that connection, the same location or configuration error can recur across multiple participants and only appear as a cashflow problem.

Use market data carefully

Location factors should not be confused with demand. A higher factor may affect the pricing model, but it does not prove that a participant will choose that dwelling or that the home will remain occupied. The NDIS demand data guidance says demand data helps providers understand potential need across regions and is updated 4 times a year. It also measures different participant states, including people living in SDA and people with SDA funding who are looking for suitable SDA.

Use demand data, SDA Finder activity, referral pipeline and support-coordinator feedback beside the pricing register, not inside the price itself. That keeps the provider from blending official price limits with market-confidence claims.

This is especially important for owner reporting. Owners may need to understand why two similar homes have different price assumptions or vacancy risks, but the report should make clear whether the number is an official price limit, a submitted claim, a paid amount, an expected distribution or an unproven pipeline forecast.

How StepFree fits the workflow

StepFree SDA can help providers keep pricing inputs connected to enrolled dwellings, participant occupancy, claim readiness, payment outcomes, vacancy states and owner reporting. The point is not to replace the NDIS pricing arrangements, the calculator or the provider portals. It is to stop official pricing facts from being copied into disconnected spreadsheets where source version, location factor, participant dates and owner assumptions drift apart.

For SDA teams managing multiple dwellings, a controlled location factor register turns pricing from a one-off modelling exercise into an operating control that finance, intake, compliance and owners can rely on.

Conclusion

SDA location factors should be treated as part of the claim and reporting control environment. Anchor the price to the enrolled dwelling, use the latest official pricing source, verify the location factor and stock category, reconcile participant claim dates, and keep owner reporting separate from participant evidence. That discipline reduces preventable pricing drift without turning owner forecasts into unsupported income promises.

StepFree SDA can help providers manage location-sensitive pricing records, claim controls, vacancy assumptions, reconciliation and owner-safe reporting in one operational workflow.