NDIS Support Provider Payroll Across the Mornington Peninsula

The short answer: the Mornington Peninsula's spread-out geography, Mornington, Mount Eliza, Rosebud, Hastings and everywhere between, means NDIS support workers often travel further between clients than in a dense suburb. That makes travel time, vehicle allowances and genuine broken shifts a bigger, more frequent part of payroll here than the SCHADS Award basics alone cover, and getting the distinction between travel time and a broken shift right matters more on the peninsula than almost anywhere else in Victoria.

Geography Changes How Often Payroll Complexity Shows Up

In a compact inner-suburban area, a support worker might see three clients within a few streets of each other. On the Mornington Peninsula, the same three visits can mean driving between Mornington and Rosebud, or out towards Hastings, with genuine travel time in between rather than a short walk. That distance turns what would be a straightforward shift elsewhere into something that more often qualifies as a broken shift, or that needs travel time and a vehicle allowance factored in correctly. For how SCHADS classification, allowances and penalty rates work in full, see our complete national guide to NDIS payroll under the SCHADS Award. This article focuses on what the peninsula's own geography specifically means for payroll.

Understanding the Peninsula's NDIS Service Area

The Mornington Peninsula isn't one compact service area, it's a string of townships, Mornington, Mount Eliza, Mount Martha, Rosebud, Dromana, Hastings, Somerville and further out toward Sorrento and Portsea, each with its own client base, connected by roads that can take twenty to forty minutes to travel depending on the route and time of day. A provider taking on clients across several of these townships is, in effect, running a genuinely regional service, not a suburban one, even though the whole area sits within a single local government region. This shapes everything from how shifts get rostered to how realistic a single worker's daily schedule actually is once real driving time is accounted for.

Where Peninsula Rostering Trips Up Payroll

The providers we see get this wrong on the peninsula usually aren't getting the SCHADS classification levels wrong, they're getting the travel and gap-time side wrong, because it comes up so much more often here than it would for a provider working a tight metro radius. A gap between two visits that's genuinely travel time, not a true unpaid break, needs to be recorded and paid differently to a broken shift with a real gap in the middle. Getting that distinction backwards, in either direction, either underpays a worker who genuinely drove 40 minutes between clients, or overpays a gap that should have been a broken shift allowance instead.

Rostering across the peninsula and not sure travel time is being handled correctly? Book a free call and we'll take a look. No obligation, no lock-in contracts.

Travel Time vs Broken Shift: Getting the Distinction Right

The core distinction comes down to why the gap exists. If a worker is actively travelling from one client to the next, driving from Rosebud to Hastings, for instance, that's travel time within the shift, and is generally treated and paid differently to an unpaid break. A broken shift, by contrast, is a genuine gap in the working day, a morning visit and an evening visit with several hours of the worker's own time in between, not spent travelling. On the peninsula, both situations happen regularly, sometimes on the same day for the same worker, and a roster that doesn't clearly distinguish between the two makes it effectively impossible for payroll to apply the right treatment without manual investigation every single fortnight.

Vehicle and Travel Allowances Explained

Where a support worker uses their own vehicle to travel between client visits, a vehicle allowance can apply on top of any travel time payment, intended to cover the real cost of running a car for work purposes, fuel, wear and distance. For a peninsula-based provider, this isn't a minor edge case, it's close to a standard feature of the role for any worker covering more than one township in a day. Getting vehicle allowance calculations right depends on accurate distance data from the roster, which is exactly why rostering software that only records start and finish times, without capturing actual travel between locations, consistently under-serves peninsula-based providers.

Getting Rostering Data Feeding Payroll Properly

The fix isn't complicated, but it does require the roster to actually capture real travel time and distance between visits, not just start and finish times for each appointment, so that the correct treatment, travel time, vehicle allowance, or broken shift allowance, gets applied automatically rather than guessed at every fortnight. For a peninsula-based provider, this one piece of setup usually has more payroll impact than anything else, simply because the geography means it comes up on nearly every roster.

There's a practical upside to getting this right beyond compliance too. A provider that can genuinely price and schedule visits around real travel time, rather than treating every visit as if it were around the corner, ends up with rosters that hold together better on the day, fewer late arrivals, fewer workers stretched too thin between towns, and fewer last-minute reshuffles when a shift runs long because the drive was never properly accounted for in the first place.

Example: A Peninsula Provider

A support provider covering clients from Mornington through to Hastings had eleven support workers on a roster built purely around appointment times, with no travel data captured between visits. A payroll review found that genuine travel time was routinely being logged as unpaid gaps, meaning several workers were owed travel payments going back months, while a handful of shorter gaps that should have been paid as broken shift allowances were instead being treated as full travel time, an overpayment in the other direction. After rebuilding the roster to capture actual travel distance and time between each visit, and configuring Xero to apply the correct allowance automatically based on that data, the provider corrected both errors and cut the time spent manually reviewing each fortnight's roster by more than half.

Watch: NDIS Payroll Across the Peninsula