Stop chasing invoices. Start approving them.
Every invoice that lands on your desk still needs the same checks: is this participant's plan active, does the item code exist, is the rate under the cap, does the math add up. One at a time, all month, on top of everything else your team does.
We want to build a way to get that checking done before it reaches your team, so a reviewer's day is spent making decisions, not hunting for the numbers to check them against. It's the same time-back idea behind what this looks like for providers, and we're looking for a small group of Plan Managers to build it with, not for.
Got a backlog right now? Send us a batch to check by hand → No software, no waiting on early access.
-
Plan active for the service dateCover confirmed before anything else runs
-
Item codes exist6 of 6 matched to the catalogue
-
Rates under the capChecked against current price limits
-
Line 4 doesn't add upQuantity × rate doesn't match the line total
The part of the job nobody signed up for
Plan Manager back-office work isn't the hard part of the job. It's the volume of small, repetitive checks standing between an invoice arriving and a participant's provider getting paid.
- 01Re-keying the same fields from PDF after PDF
- 02Cross-checking rates against the NDIS Pricing Arrangements by hand
- 03Chasing a provider because a line item doesn't map to anything in the catalogue
- 04Re-doing the same checks a second time because nobody's sure which invoices were reviewed already
- 05The scramble at month-end when the backlog catches up with you
None of it requires judgement. All of it takes time your team could spend on the invoices that do need a human look.
What changes
Same invoices, same obligations. A different order of operations.
| Stage | The way it works now | The way it could work |
|---|---|---|
| An invoice arrives | Sits in a queue until someone has time to open it | Checked against pricing and plan details the moment it lands |
| Routine checks | A person re-types and re-checks every field, every time | Already done: flagged clean or flagged for a reason |
| Your team's time | Spent on every invoice, clean or not | Spent only on the ones that actually need a decision |
| Before anything is paid | Depends on whoever got to it | A person always makes the final call, nothing goes out on autopilot |
| Month-end | A backlog waiting to become a scramble | Nothing waiting, because nothing piled up |
If that left-hand column is your month, you already know what it's costing your team.
Build it with us →Don't take our word for it. Run the checks yourself.
The right-hand column above isn't a promise we're asking you to wait for. A working piece of it is live: check a single line, or upload a CSV of de-identified invoice lines and it runs seven checks over every one of them — price limit, arithmetic, plan dates, item code, duplicates, the 90-day submission window and remaining category budget — marking each line clean or flagged with the reason and the numbers behind it.
No signup, no upload, nothing stored. The checks run entirely in your browser, and the sample batch takes about a minute. Load it, break it, then tell us where it's wrong.
The one thing that doesn't change
However this gets built, one thing stays fixed.
A human approves every payment. The goal is to have the checking already done and the evidence already in front of your reviewer, not to make the call for them. Every approval is still a person's decision, recorded as theirs.
That's a design commitment, not a feature we might cut later: no straight-through processing, no invoice pays itself. If it can't be verified cleanly, it goes to a person, clearly marked, with the reason why. It's the same principle Claim-ready holds on the provider side.
Trust, data, and privacy
Worth being upfront about, especially since some of you might send us real invoices before anything is properly built.
Early, hands-on work, not a certified system
We'll tell you plainly what is and isn't in place at each stage.
Australia by default
Invoice and participant data stays inside Australia, not routed through infrastructure outside that.
De-identify anything you send us
Strip participant names, NDIS numbers, and any other participant-identifying details first. We only need the line items: item codes, descriptions, rates, quantities.
A person reviews it, not an unchecked script
Rio (or whoever's helping on a given batch) personally looks at it, the same care as handing it to a colleague.
Held only as long as it takes to check it
Deleted within 7 days of sending your results back. We're not building a store of invoice data.
Checking, not approving or paying, and the responsibility stays with you
We tell you what would pass and what wouldn't. Your team still makes the call, holds the money, and carries responsibility for the claim's accuracy and compliance, same as today. If we get something wrong in this early, unaudited process, that's ours to own and fix, it doesn't shift onto you, and it doesn't shift the claim itself onto us either.
Compliance context
We check invoices against the pricing rules in the NDIS Pricing Arrangements and Price Limits, and treat provider and participant information as sensitive information under the Privacy Act 1988 (Cth) and the Australian Privacy Principles, the same obligations Plan Managers already carry under the NDIS Practice Standards.
On anything you send us
We're checking arithmetic and item-code mapping, not verifying that an invoice, provider, or claim is genuine. Sending us a batch confirms it's accurate to your knowledge and that you're authorised to share it. Responsibility for anything fraudulent, false, or unauthorised in it sits with whoever sent it. If something looks off, we'll stop and flag it rather than keep working through it.
Want relief before any of this is built?
Got invoices sitting in the backlog? Send a de-identified batch (see Trust, data, and privacy above) and we'll check it by hand, no software involved. We'll tell you which lines are clean and which need a closer look, and why, so your team can approve and pay with the checking already done. It also shows us exactly what your admin looks like before we design anything.
This isn't a service we're scaling up, it's a handful of Plan Managers helping shape what gets built, so we can only take on a few at a time.
- Lines that are clean, ready to approve
- Lines that need a closer look, and why
- No software to set up, nothing to install
Who's building this
I'm Rio, a product designer who's spent close to a decade designing for regulated, high-stakes industries: healthcare, sport, SaaS. I started Nueco after watching how much of NDIS admin work is people doing manual, repetitive checking that a system should be doing for them, on both sides of the provider-participant relationship.
This is that same thinking pointed at the back office (the team that processes what providers submit, rather than the providers themselves), and I'd rather build it with the people doing that work than decide what it should be on my own.
A few things worth asking upfront
Straight answers before you put your name to anything.
Is this live yet?
No. Nothing's built yet, and that's the point. We want a small group of Plan Managers involved from here, not shown a finished product later, so what you tell us directly shapes what gets built.
Will this replace my reviewers?
No. It's built to remove the repetitive checking around a decision, not the decision itself. Every payment still needs a person to approve it.
What about data security?
See Trust, data, and privacy above, Australia by default, with specifics on how it's handled while things are still manual.
Does this replace my existing software?
No, the intent is to sit alongside whatever you already use, not to be a new system of record you have to migrate into.
What will it cost?
Not decided yet. Early access is about hearing what would actually be worth paying for, not locking in a price before we've built anything.
What happens after I sign up?
You'll be one of a small number of Plan Managers we talk to directly and regularly as this gets built, not a name on a list waiting for a launch email. Early conversations, early looks at what we're putting together, and a real say in what it does before it's finished. No cost, no obligation to keep going if it's not for you.
Help us build this right
We'd rather design this with the people who deal with the admin every day than guess at it alone. Put your details in and we'll set up a conversation.
- No cost, no obligation, stop whenever it stops being useful
- Direct conversations with Rio, not a name on a launch list
- Early looks at what we're building, and a real say in it
- A human approves every payment, always
Prefer to just ask a question first? Email us, no form required.