One record.Plan to pay.

NDIS operations on one accountable record, from the plan to the claim and pay.

Sample record. No participant data.

One service record as a chain of six stage cards, from the plan to a cyan approval gate, on a dark field.

Plan

The plan sets the limits.

Every support starts from the participant’s plan: its budgets, supports and dates.

Funding

Funding is matched first.

Each support draws on a known funding line, and money is kept in integer cents.

$1,234.56is stored as123456

Roster

Roster checked.

A shift that would overrun the budget is flagged before it is published.

Service

Support started.

The worker clocks in with a location check, and actual time joins the record.

Evidence

Evidence complete.

Case notes, tasks and travel are checked before review, not after billing.

Review queue Sample

  • Tue 08:00–14:00Self-careReady
  • Wed 09:00–12:00Community accessNo Clock-OutClock-out added
  • Wed 13:00–15:30Community accessKM Missing
  • Thu 10:00–16:00Self-careReady

Caught on Friday, not at audit.

Sample review queue: four shifts. One is blocked by a missing clock-out until it is fixed; one has a missing travel distance, a warning that does not block; two are ready.

Fri 4:42 pm

One thing needs you.

No money moves without a person pressing approve.

Sample. In Nexis365 only an authorised reviewer can approve.

The record halted at the cyan gate under a stone 4:42, waiting for a person.

Claim and pay are held.

Nothing leaves the record until a person approves it.

Four views of the same record.

Explore the modules
  1. 01 / 04

    Operations

    Live shifts, staffing gaps and exceptions in one operational view.

    • Shifts move from draft to published, offered, accepted, in progress, completed and approved.
    • Participant double-bookings are detected before a shift is saved.
    • Clock-in is location-checked, and end-of-day notes stay with the shift.
    Operations in detail
  2. 02 / 04

    Participants

    Plans, funding and support history connected around each participant.

    • Plans with Core, Capacity Building and Capital budgets.
    • Funding lines mapped to NDIS support items.
    • Support coordinators, plan managers and accounting contacts on the participant record.
    Participants in detail
  3. 03 / 04

    Finance

    Invoice drafts, PRODA bulk payment file exports and budget movement tied back to the service record.

    • Invoice drafts built from approved shifts, with a full audit trail.
    • Lines missing data are flagged before anything is exported.
    • NDIS-format invoice PDFs, exports of PRODA bulk payment files, and an MYOB export.
    Finance in detail
  4. 04 / 04

    People

    Actual time, pay categories, credentials, leave and worker evidence in context.

    • SCHADS award pay calculation, with organisation-level overrides.
    • Weekday, Saturday, Sunday and public holiday rates, casual loading and sleepover allowances.
    • Pay categories mapped for your accounting export.
    People in detail

The risk lives between systems.

Nexis365 keeps one record across every handoff, so nothing falls between.

The mechanism is the proof.

Four rules the platform is built on.

Trust and security
Money
Stored and calculated in integer cents, so no rounding drift hides across a pay run.
Access
Every customer’s data is separated by organisation in the data layer, and automated checks flag any query that isn’t.
History
Every change to a billable record leaves an audit trail.
Time
Clock-ins, clock-outs and audit events are timestamped by the server, not the phone.

Built after living the problems it solves.

Nexis365 began on the operations floor of an Australian provider: wrong overnight pay, rejected claims, unsupported shifts and compliance registers scattered across laptops.

About Nexis365

The people behind the record.

Founded in 2024 by Hasan M. H. with a small group of NDIS providers, after about three years in NDIS operations.

Run NDIS on one record.

Book a walkthrough

Every claim traces back to a person’s approval.