Free tool · NDIS claiming

NDIS bulk payment request builder & checker.

Build a bulk claim CSV in the portal's exact format, or drop in the file you already have and see every error before the myplace provider portal does — bad dates, wrong item numbers, prices over the limit and missing cancellation codes.

Item numbers and price limits from the NDIS pricing schedule 2026–27 (effective 24 September 2026). Column format matches the CSV Suppora exports for the myplace provider portal. A pre-check, not a guarantee of payment — the portal also checks plans, budgets and service bookings. Look up an item in the NDIS price guide. Your data stays in this browser.

Guide

The NDIS bulk payment request file, column by column

A bulk payment request is one CSV file that claims many supports at once through the myplace provider portal. The portal processes it row by row, and a single bad date, item number or price can reject a row and hold up payment. This guide covers each of the 15 columns, the codes the portal accepts, and the mistakes that cause rejections.

Key facts

columns in the template, in a fixed order

dd/mm/yyyy

date format for SupportsDeliveredFrom and To

43…

every NDIS number: 9 digits starting with 43

GST code for most NDIS supports (GST free)

Who uses bulk payment requests

Registered providers claim payment for NDIA-managed (agency-managed) supports through the myplace provider portal. You can make a single payment request on screen, or upload many at once as a bulk payment request CSV. Plan managers also make payment requests through the portal for the plans they manage.

Self-managed and plan-managed supports work differently: you send an invoice to the participant or their plan manager rather than claim from the NDIA. For those, use the NDIS invoice generator or the plan-managed invoice generator.

The 15 columns

The header row has to match the template exactly. The template is a little odd: three headings — UnitPrice, AuthorisedBy and ParticipantApproved— carry a leading and trailing space. The builder writes them that way so the file matches what the portal and accountants' import scripts expect.

Bulk payment request columns, in order
Column	Required	What goes in it
`RegistrationNumber`	Yes	Your NDIS provider registration number (10 digits, starts with 405).
`NDISNumber`	Yes	The participant's NDIS number: 9 digits starting with 43.
`SupportsDeliveredFrom`	Yes	First date of the support, dd/mm/yyyy.
`SupportsDeliveredTo`	Yes	Last date of the support, dd/mm/yyyy. Same as From for a single day.
`SupportNumber`	Yes	Support item number from the 2026–27 schedule, e.g. 01_011_0107_1_1.
`ClaimReference`	No	Your own reference — an invoice or shift number — so you can match payments back.
`Quantity`	Yes*	Units delivered. For hourly items, hours as a decimal (45 minutes = 0.75).
`Hours`	Yes*	Hours for hourly items. *Quantity or Hours must be above zero.
`UnitPrice`	Yes	Price per unit, 2 decimal places, at or below the price limit.
`GSTCode`	Yes	P2 GST free (most supports), P1 tax claimable 10%, P5 out of scope.
`AuthorisedBy`	No	Usually blank.
`ParticipantApproved`	No	Usually blank.
`InKindFundingProgram`	No	Only for in-kind arrangements. Usually blank.
`ClaimType`	Depends	Blank for a direct service; otherwise CANC, REPW, TRAN, NF2F or IRSS.
`CancellationReason`	If CANC	NSDH, NSDF, NSDT or NSDO. Blank on every other row.

One row is one claim for one participant, one item and one date range. Don't merge different items, or weekday and weekend supports, into one row — the price limit depends on the item, and each time-of-day item has its own number.

GST, claim type and cancellation codes

GSTCode

P2 — GST free (most NDIS supports)
P1 — Tax claimable (10%)
P5 — GST out of scope

Most disability supports delivered under a participant's plan are GST-free, so P2 is the usual code. Where GST does apply, the price limit already includes it.

ClaimType

Direct service (leave blank)
CANC — Cancellation
REPW — NDIA-requested report
TRAN — Provider travel / transport
NF2F — Non-face-to-face
IRSS — Irregular SIL supports

CancellationReason (CANC rows only)

NSDH — No show due to health reason
NSDF — No show due to family issues
NSDT — No show due to unavailability of transport
NSDO — Other

Price limits and zones

The pricing schedule sets three maximum prices for most items: national (Modified Monash Model 1–5), remote (MMM 6) and very remote (MMM 7). Since 24 September 2026 these maximums are set by a ministerial determination, and for NDIA-managed supports the NDIA can't pay more than the maximum for the participant's location.

The file doesn't say where the participant lives, so the checker grades each price:

At or below the national limit — fine anywhere.
Above national but within the remote limit — a warning: only valid for remote or very remote participants.
Above remote but within very remote — a warning: only valid for very remote participants.
Above the very remote limit — an error: the portal won't pay it anywhere.

Items that aren't in the price-limited schedule — quotable supports, assistive technology, consumables and some travel costs — are flagged as a warning rather than an error, because they can still be valid claims.

Uploading and checking results

From shifts to payment

1
Gather delivered supports
Only claim supports already delivered. Each needs a shift record or case note behind it.
2
Build or export the CSV
Use the builder above, or your billing system's export, then run it through the checker.
3
Don't re-save in Excel
Opening and saving a CSV in a spreadsheet can turn 05/10/2026 into another format or strip leading zeros.
4
Upload in myplace
Upload the file as a bulk payment request in the myplace provider portal.
5
Check the results
The portal reports which rows were accepted and which were rejected and why. Fix rejected rows and resubmit only those — not the whole file, or you risk a double claim.

Why rows get rejected

Wrong date format — yyyy-mm-dd or d/m/yy instead of dd/mm/yyyy, often after a spreadsheet re-save.
Future dates— supports can only be claimed once they've been delivered.
NDIS number typos — not 9 digits, or not starting with 43.
Old or mistyped item numbers, or a weekday item used for a weekend support.
Price above the limitfor the participant's location.
Text in ClaimType such as STANDARD, or a cancellation row with no reason code.
Duplicate rows — the same participant, item, dates and amount twice. The checker flags these as possible double claims.
No funds or no arrangementin the relevant budget. The checker can't see plans, so check the participant's budget with the budget tracker.

Glossary

Bulk payment request: A CSV file of many payment requests uploaded at once in the myplace provider portal.
myplace provider portal: The NDIA's online portal where registered providers make payment requests.
NDIA-managed: Supports paid directly by the NDIA to a registered provider. Also called agency-managed.
Registration number: The number the NDIS Commission gives a registered provider.
MMM: Modified Monash Model — the remoteness scale that sets which price limit applies.
Direct service: A support delivered as booked. ClaimType is left blank.

References

Sources checked 7 October 2026.

myplace provider portal and resources (including bulk payment request guidance) — National Disability Insurance Agency, checked 7 October 2026
Getting paid — National Disability Insurance Agency
Pricing arrangements (NDIS pricing schedules 2026–27) — National Disability Insurance Agency, checked 7 October 2026
National Disability Insurance Scheme (Pricing Arrangements) Determination 2026 (F2026L01268) — Federal Register of Legislation, registered 23 September 2026
National Disability Insurance Scheme Act 2013 — Federal Register of Legislation
ABN format and check digit — Australian Business Register

Questions

Frequently asked

What is an NDIS bulk payment request?+

A CSV file that lets a registered provider claim many NDIA-managed supports at once through the myplace provider portal, instead of entering each payment request on screen.

What columns does the bulk payment request CSV need?+

Fifteen, in this order: RegistrationNumber, NDISNumber, SupportsDeliveredFrom, SupportsDeliveredTo, SupportNumber, ClaimReference, Quantity, Hours, UnitPrice, GSTCode, AuthorisedBy, ParticipantApproved, InKindFundingProgram, ClaimType and CancellationReason.

Is my file uploaded anywhere when I check it?+

No. The file is read by your browser with JavaScript and checked on your device. Nothing is sent to Suppora or the NDIA.

Does a clean result mean the NDIA will pay every row?+

No. The checker catches format, code and price-limit problems. It can't see the participant's plan, budget, plan dates or your service bookings, which the portal also checks.

What date format does the NDIS bulk payment CSV use?+

dd/mm/yyyy — for example 05/10/2026. Spreadsheet programs often change dates when you open and re-save a CSV, so check the date columns before you upload, or build the file here and upload it without opening it in Excel.

Should ClaimType be blank for a normal support?+

Yes. A direct service — the support was delivered as booked — leaves ClaimType blank. Codes such as CANC (cancellation), TRAN (travel), NF2F (non-face-to-face) and REPW (NDIA-requested report) are only for those claim types. Writing STANDARD or DIRECT in the column gets the row rejected.

Do I fill in Quantity or Hours?+

Suppora's own export fills Quantity for every line and also Hours for hourly items, with the same value. For items priced per Each, Day or Week, use Quantity only. If both are filled and they differ, the checker warns you, because it's unclear which one you meant.

Why did my bulk upload fail for a price above the limit?+

For NDIA-managed supports the NDIA can't pay above the maximum price in the pricing schedule for the participant's location. The checker can't know where the participant lives, so it compares the price to the national limit and warns if it's only valid for remote (MMM 6) or very remote (MMM 7) participants, and flags an error if it's above every limit.

Can plan managers use this?+

Plan managers submit payment requests through the portal too, and some of their files carry the provider's ABN. If your file has an ABN column, the checker validates each ABN against the ATO check-digit rule. The other checks are the same.

In Suppora

Bulk claims straight from completed shifts.

In Suppora, completed shifts become claim lines with the right item numbers and price limits, and NDIA-managed lines export as one bulk payment request file — already in this format, with lines marked processed once you've uploaded.

Start free NDIS billing & bulk claims

More free tools

All tools