NDIS Plan Manager Service Agreements in Australia

Alex Solo
byAlex Solo13 min read

An NDIS plan manager has to keep money moving without losing control of authority, consent and communication.

The risks usually come from small gaps: invoices approved over the phone with no record, support coordinators giving directions they are not authorised to give, or a participant expecting the plan manager to check whether every support is good value or clinically appropriate.

A well drafted NDIS plan manager service agreement sets out exactly what the plan manager will do, how fees are charged, who can approve invoices, how information is shared and how the arrangement can end. It should match your actual workflow, not just copy a generic NDIS service agreement template.

For plan managers, clear terms reduce payment disputes, protect participant choice and control, and help your team respond consistently when a nominee, support coordinator, provider or family member wants something done urgently.

What a Plan Management Service Agreement Should Do

A plan management service agreement should define the plan manager's role as a financial administration service, not as a support coordination, clinical advice or advocacy service.

In the NDIS, plan management generally involves helping a participant manage the funding in their NDIS plan. In practice, this can include receiving invoices, checking whether they relate to the participant's plan-managed supports, processing payment requests, keeping budget records, and providing statements or reports. Those tasks are highly administrative, but they sit inside a regulated disability services environment where expectations can be sensitive and urgent.

Your NDIS participant service agreement should make three boundaries very clear. First, it should explain what you do. Secondly, it should explain what you do not do. Thirdly, it should set out who can tell you to take action on the participant's account.

For example, your agreement might state that the plan manager can:

  • process invoices for supports and services that appear to align with the participant's NDIS plan and plan management arrangements;
  • communicate with the participant, their nominee, guardian or authorised representative;
  • give the participant budget tracking information and reports;
  • seek clarification from providers if an invoice is missing required details;
  • claim plan management fees from the participant's NDIS plan where permitted;
  • keep records needed for compliance, audit and participant support.

It should also state that the plan manager does not usually:

  • choose providers for the participant unless separately agreed;
  • decide whether a support is clinically appropriate;
  • provide support coordination unless your business is also engaged for that service under a separate disability support service agreement;
  • guarantee that the NDIA will approve or reimburse every claimed item;
  • give tax, financial, medical, therapeutic or personal legal advice;
  • represent the participant in disputes with providers or the NDIA unless you have separately agreed to help with a specific administrative issue.

This distinction matters because many plan management disputes are not really about the wording of an invoice. They are about expectations. A participant may think the plan manager is responsible for telling them whether a service is reasonable and necessary. A support coordinator may assume they can direct payments without participant authority. A provider may expect immediate payment even if the invoice lacks details. A good agreement gives your staff a practical answer for each situation.

The agreement should also use language that participants can understand. Plain English is especially useful where participants have nominees, carers or family members involved. The document should avoid burying key rights and responsibilities in dense legal wording. If your team relies on a process daily, such as invoice approval cut-offs or budget alerts, that process deserves clear wording in the main agreement or a referenced schedule.

Because plan management is part of the NDIS framework, registered providers need to be mindful of their obligations under the NDIS Quality and Safeguards Commission, the NDIS Code of Conduct and any applicable NDIS Practice Standards. Your agreement should not promise processes that your business cannot consistently follow. If your participant communications, privacy notices and internal procedures do not match the contract, that gap can create compliance and client service problems.

Set Fees, Budgets and Invoice Authority Clearly

The agreement should state exactly what fees may be charged, when they are claimed and what authority the plan manager has to process invoices from the participant's plan.

For a plan manager, the commercial terms are not just about getting paid. They are about giving the participant confidence that their NDIS funds will be handled carefully and consistently. Your NDIS plan management service agreement should identify the types of plan management fees you may claim, how those fees relate to the participant's plan, and what happens if funding is insufficient or plan details change.

Most plan managers will not set their fees in the same way as an ordinary service business. NDIS pricing arrangements, plan categories and the participant's available funding will affect what can be claimed. Your agreement should therefore avoid broad promises such as unlimited administration support or payment of all invoices. Instead, your service agreement should link your services to the participant's approved plan, the plan management budget and applicable NDIS rules.

A practical fee clause should cover:

  • whether an initial setup fee applies, where permitted under NDIS rules;
  • ongoing plan management fees and how they are claimed;
  • whether statements, reports or other standard communications are included;
  • any extra services that are outside standard plan management, if your business offers them;
  • what happens if the participant's plan ends, is suspended or no longer includes plan management funding;
  • how errors, rejected claims or payment reversals will be handled.

Invoice authority is often the more sensitive issue. Your agreement should answer a simple question: who can authorise payment of an invoice? The answer may include the participant, a plan nominee, a guardian, or another representative whose authority has been verified. It might also include a support coordinator for certain administrative tasks, but only if the participant has given clear written authority for that role.

Avoid vague wording that allows invoices to be processed whenever they are received from a provider. Some plan managers do use pre-authorised payment processes for recurring supports, but those processes need guardrails. For example, your agreement can distinguish between:

  • pre-approved recurring invoices, such as weekly therapy or support work within an agreed budget and provider arrangement;
  • participant-approved invoices, where the participant or authorised person must approve each invoice before payment;
  • invoices needing clarification, where details such as dates, support category, ABN, provider information or participant details are missing;
  • invoices that may be declined or paused, such as invoices outside the plan dates, outside available budgets or inconsistent with the information held by the plan manager.

Budget monitoring should also be framed carefully. Participants often value plan managers because they can see what has been spent and what remains. However, a plan manager usually should not promise that a participant will never overspend or that funds will always be available for future supports. Budgets can be affected by late invoices, provider errors, plan reassessments, duplicate claims, or the participant choosing to use supports more quickly than expected.

Your agreement can say that you will use reasonable systems to track claims and provide budget information, while making clear that the participant remains involved in decisions about how supports are used. It can also explain whether you send alerts when a budget appears low and whether those alerts are automatic, periodic or upon request.

One useful workflow example is a new participant who tells their therapist to send invoices directly to you. The therapist sends three months of backdated invoices in one batch. Without clear terms, your team may be pressured to pay quickly even if the participant disputes some sessions or funding has changed. With clear terms, your staff can pause the invoices, request participant approval, check plan dates and explain why payment cannot be automatic.

Manage Communication With Participants, Nominees and Support Coordinators

The agreement should identify authorised contacts and set communication rules before a support coordinator, family member or provider asks your team to act.

Plan managers often sit in the middle of a busy network. A participant may communicate directly. A parent may help with emails. A plan nominee may have formal authority. A support coordinator may organise providers. A provider may chase payment. Each person may think they are helping, but not everyone has authority to give instructions about NDIS funds or personal information.

Your participant service agreement should require the participant to nominate authorised contacts at the start of the relationship. It should also explain how authority can be added, limited or removed. This is particularly useful when a participant changes support coordinators, a family member is no longer involved, or a provider tries to obtain information about remaining budgets.

A clear communication clause can deal with:

  • the main contact person for day-to-day communications;
  • whether instructions can be given by email, phone, portal, text message or another method;
  • which instructions must be in writing;
  • how your business verifies a new authorised representative;
  • whether you can communicate with support coordinators and providers;
  • what information you will and will not share with third parties;
  • expected response times for routine enquiries and urgent payment issues.

The agreement should also recognise that a participant's legal authority arrangements may differ from their informal support network. A plan nominee appointed for NDIS purposes may have authority in relation to the participant's NDIS plan. A guardian or administrator may have authority under state or territory laws. A support coordinator, on the other hand, usually does not automatically have authority to direct a plan manager just because they are engaged by the participant.

Conflicts with support coordinators are common enough that they deserve express wording. For example, a support coordinator might ask for invoices to be paid from a category that the participant has not approved, or ask for budget information to be sent to a new provider. Your agreement can state that support coordinators may assist with administration and coordination, but the plan manager may require participant or nominee confirmation before processing payments or sharing sensitive information.

Provider communication also needs boundaries. A provider may contact your team to ask whether the participant has enough funding before delivering a service. A plan manager can provide certain information if authorised, but should avoid creating the impression that payment is guaranteed. Your terms can say that any budget information is current only at the time it is provided and may change as other invoices are processed.

From a privacy perspective, the Privacy Act 1988 may apply to your business depending on your circumstances, and disability service businesses commonly handle sensitive health and personal information. Even where a business is not required to comply with every part of the Privacy Act, clear privacy practices are still commercially sensible. The agreement should work alongside your privacy policy and consent processes so participants know how their information will be collected, used and disclosed.

Communication terms should also be accessible. If your business mainly uses email but the participant needs phone contact or another communication support, the agreement should explain how reasonable communication preferences are recorded. This can reduce misunderstandings and support participant choice and control.

Approval Workflows, Privacy and Ending the Agreement

Your agreement should turn everyday operational steps into clear rules for approvals, records, privacy, complaints and termination.

A generic NDIS service agreement template may cover names, services and signatures. A plan manager needs more than that. The document should reflect how invoices actually move through your business from receipt to payment, and what happens when something does not match the participant's plan or authority.

A strong approval workflow usually covers these stages:

  1. Invoice receipt: the provider sends an invoice through the approved channel with the participant's details, dates of support, support description, amount, ABN and payment details.
  2. Initial check: the plan manager checks whether the invoice appears to relate to the participant, falls within the relevant plan period and contains enough information to process.
  3. Authority check: the plan manager confirms whether the invoice is pre-approved, participant-approved or requires further consent.
  4. Budget check: the plan manager checks available budget information, noting that budgets can change as other invoices are received or processed.
  5. Claim and payment: the plan manager processes the claim and pays the provider according to its standard timeframes, subject to NDIS systems and any issues with the invoice.
  6. Record keeping: the plan manager records the payment, updates budget information and makes statements available to the participant.

The agreement should give your team permission to pause or reject an invoice in defined circumstances. This might include suspected duplication, missing information, lack of authority, insufficient funds, a service date outside the plan period, or a concern under the service terms that the invoice does not match the participant's instructions. The wording should be firm but fair, so participants understand the pause is a control measure, not an attempt to withhold support.

Complaints and error handling should be addressed in plain terms. If an invoice is paid incorrectly, your agreement should explain how the participant can raise the issue and how your business will investigate. If a provider has charged the wrong amount or sent the wrong invoice, the participant should know whether your business will contact the provider, ask the participant to resolve it, or do both depending on the issue.

Plan managers should also think about the Australian Consumer Law. Participants receiving plan management services may have consumer rights, including guarantees that services will be provided with due care and skill, fit for any disclosed purpose, and within a reasonable time where no time is agreed. Your agreement should not attempt to exclude rights that cannot be excluded. Instead, focus on setting a practical service scope, communication process and timeframe expectations.

Privacy and confidentiality clauses are especially important because plan managers often hold NDIS plan details, invoices, contact information, health-related context and support provider records. Your agreement should explain:

  • what participant information you collect to provide plan management services;
  • when information may be shared with providers, nominees, support coordinators, the NDIA, auditors or regulators;
  • how participants can update their contact and authority details;
  • how you handle incorrect information or suspected unauthorised requests;
  • how long records may be kept to meet legal, audit and business obligations.

Termination is another area where plan managers need practical wording. A participant may want to move to another plan manager quickly, especially at the start of a new plan. Your business may also need to end services where there is repeated abusive conduct, no valid authority, funding no longer includes plan management, or the participant repeatedly asks you to process claims you cannot lawfully or properly process.

Your termination clause should cover notice, final invoices, transfer of records, remaining budgets, pending invoices and cooperation with a new plan manager. Avoid wording that traps a participant in the arrangement or creates unreasonable barriers to changing providers. At the same time, your business needs a workable handover process so staff are not expected to process years of records overnight.

For example, your agreement might say that after termination you will process valid invoices received before the end date or within a stated handover period, if authorised and supported by the participant's plan. It can also say that new invoices after the end date should be sent to the new plan manager unless you have agreed otherwise in writing.

If your business uses software portals, automated approvals or offshore administration support, the agreement and privacy documents should describe the practical effect for participants. Participants do not need every technical detail, but they should know how to submit invoices, who may access their information, and what happens if a system outage delays processing.

FAQs

Do NDIS Plan Managers Need a Written Service Agreement?

A written agreement is strongly recommended because it records the participant's authority, your fees, communication rules and invoice workflow. It also helps your team show consistent processes if a participant, provider, nominee, auditor or regulator asks why an invoice was paid, paused or declined.

Can I Use a Generic NDIS Service Agreement Template?

A generic template may be a starting point, but it often misses plan manager-specific issues such as invoice authority, budget reporting, support coordinator instructions, pre-approved recurring invoices and payment holds. Your agreement should match the way your business actually receives, checks and pays invoices.

Can a Support Coordinator Approve Invoices for a Participant?

A support coordinator should only approve invoices or give payment instructions if the participant, nominee or another authorised decision-maker has clearly authorised that role. Your agreement should state when support coordinator instructions are accepted and when participant or nominee confirmation is required.

What Should Happen if an Invoice Looks Wrong?

Your terms should allow your team to pause processing while you seek clarification from the provider, participant or authorised representative. The agreement should also say that missing details, suspected duplicates, budget issues or lack of authority can delay or prevent payment.

How Should a Participant End a Plan Management Arrangement?

The agreement should set a clear notice and handover process. It should explain how final invoices are handled, what records will be provided, who receives budget information, and when providers should start sending invoices to the new plan manager.

Key Takeaways

  • An NDIS plan manager service agreement should define plan management as financial administration and avoid promising support coordination, clinical advice or guaranteed funding outcomes.
  • Invoice authority needs clear rules for participants, nominees, support coordinators, providers and recurring approvals.
  • Fee clauses should reflect NDIS plan management funding, available budgets and applicable NDIS rules rather than ordinary fixed-price service terms alone.
  • Communication and privacy terms should identify authorised contacts, information sharing permissions and how authority can be changed.
  • Termination and handover clauses help participants move providers while giving your team a practical process for final invoices and records.

If you need help drafting or updating your participant service agreement, invoice approval terms, privacy wording or provider communication process, Sprintlaw's online lawyers can help you get the documents right for your plan management business. Contact us on 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.

Make the contract match the deal

What should you test beyond the template?

Scope, payment, dependencies, liability, IP, change and exit clauses should work together for the actual relationship. They should not just read well in isolation.

Alex Solo
Alex SoloCo-Founder

Alex is Sprintlaw’s co-founder and principal lawyer. Alex previously worked at a top-tier firm as a lawyer specialising in technology and media contracts, and founded a digital agency which he sold in 2015.

Make the contract match the deal

Get in touch with our team

Tell us what you need and we'll come back with a fixed-fee quote - no obligation, no surprises.

Need support?

Need help with your business legals?

Speak with Sprintlaw to get practical legal support and fixed-fee options tailored to your business.