Fifteen-worker disability support services provider (Queensland, NDIS registered, 42 active participants, NDIA plan funding $480k annual, 3 managers, $320k revenue): ShiftCare ($55/seat/month = $9.9k/year, web-based, middleware between provider + NDIA). Monday: participant Sarah calls manager Kayla (shift cancelled, needs rescheduling, Sarah has new physiotherapy appointment). Kayla checks ShiftCare roster (support worker Marcus assigned Friday 10am–2pm, Sarah's session). Kayla cancels Friday (updates ShiftCare, message to Marcus "Cancellation Friday"). Marcus confirms (text back). Kayla books replacement: Friday 2pm–6pm with different worker (Sarah says "2pm doesn't suit, need 10am same slot"). Kayla re-books (2pm → 10am Friday, different worker Jess assigned). Jess confirms Friday 10am. Sarah's plan: initial budget was Friday 10am–2pm Marcus, now Friday 10am–2pm Jess, timings match, plan OK. Shift completed: Jess attends Friday 10am–2pm, notes in ShiftCare "Sarah attended, worked on daily living skills, 4 hours, completed". Claim submission: Kayla exports ShiftCare data (shift dates, hours, worker names). Kayla opens NDIA portal (Portal My Place), enters claim manually (participant Sarah, week 12 claim, 4 hours Friday @ $65/hour support = $260 claim amount, date, worker Jess). Kayla attaches ShiftCare export (backup proof). Kayla submits claim (NDIA processes, 5–7 business days, funds transferred). Kayla reconciles: ShiftCare shows 4 hours, NDIA paid $260, reconciles. But gap: no itemized link (ShiftCare shows hours, doesn't auto-map to NDIA service item codes). Kayla manually checks NDIA codes (Sarah's plan says "Assistance with daily living — Code 01-02-01a"). Kayla guesses: shift was daily living work, code 01-02-01a applies. Kayla submits under that code. NDIA processes (assumes correct). But months later: NDIA compliance audit (spot-check 20% of claims). Auditor reviews Sarah's claim (Friday 4 hours, code 01-02-01a daily living). Auditor calls Sarah (verification: "Friday shift, what did Jess help with?" Sarah: "Mainly transport to physio and waiting in reception. Physio wasn't support work, was appointment accompaniment."). Auditor flags: "Shift coded as daily living, but was appointment accompaniment. Correct code: 01-12-05a (appointment support). Provider billed wrong code, fund type mismatch." NDIA demands: reimbursement. Provider must refund $260 + admin fee. Kayla shocked (thought shift was daily living). Audit reveals: 15 other claims similarly miscoded (provider receives audit demand: $3.9k refund + $600 admin fee). Provider cash flow hit: $4.5k surprise. Morale: team loses confidence in coding process. Roster skill gaps: Marcus (support worker) — qualifications unknown to Kayla. Marcus has disability support worker certificate (DSW) but no TBI (traumatic brain injury) specialization. Kayla gets referral: new participant Josh (TBI, high support needs, complex triggers). Kayla assigns Marcus (DSW certified, but no TBI training). Marcus attends shift (Josh becomes distressed, Marcus unprepared for TBI triggers, escalates to crisis, Josh's family calls manager "Your worker made Josh worse"). Kayla realizes: Marcus shouldn't have been assigned TBI (needs TBI-trained worker). Kayla checks ShiftCare roster (worker list: Marcus DSW, Jess DSW, Pete DSW, Sarah DSW — no skill tags, no certifications visible). Kayla manually checks: calls Marcus "What's your training?" Marcus: "DSW cert, some mental health training". Kayla calls Jess: "Your skills?" Jess: "DSW, WWCC, First Aid, mental health cert". Kayla notes on paper (skill register). Kayla assigns Josh to Jess (correct match: mental health trained). But process fragile: if Kayla forgets to call, wrong assignment. WWCC (Working with Children Check) — different context, but same problem. Provider has 3 participants under 18 (minors). All support workers need WWCC (Queensland requirement, criminal history check, $123 fee, renewed every 5 years). ShiftCare doesn't flag WWCC status (stores it nowhere, or buried in notes field). Kayla manually checks: "Pete, WWCC current?" Pete: "Expires August 2026." Kayla notes calendar reminder. Marcus: "Mine expired last month." Kayla realizes: Marcus shouldn't be assigned under-18 participants (WWCC expired). Kayla adjusts roster (removes Marcus from minor participants). But 2 weeks earlier: Marcus had already attended 8 hours with 16-year-old Jamie (post-expiry). Kayla realizes liability (Marcus worked under-18 without valid WWCC = regulatory breach, Queensland Disability Services Commission could audit). Kayla panics: updates ShiftCare (retroactively removes shifts, but damage done, regulatory risk). Claim friction total: manual code lookup (error-prone), skill mismatches (unsafe), WWCC tracking manual (liability risk), claim audits (refunds surprise), participant safety at risk (wrong worker assigned). GST invoicing: provider registered for GST ($10k annual threshold in disability, varies by state). Provider invoices participant families for gap funding (NDIS doesn't cover full cost, families pay remainder). Invoice: Sarah's Friday shift $260 NDIS, family gap payment $40/hour × 4 hours = $160 family co-payment (total service cost $420). Provider needs invoice (GST-inclusive: $420 ÷ 1.1 = $381.82 + GST $38.18). Kayla uses ShiftCare: export shift data (hours, worker, date), manually creates invoice in Excel (calculates GST, enters family email). Kayla sends invoice (PDF via email). Gap payment tracking: Kayla tracks (family paid? Not paid?). Kayla checks emails (Sarah's mum replied "We'll pay by EFT Friday"). Kayla waits (tracks manually). Friday arrives, Kayla checks bank (received? Kayla must log manually into bank, verify, reconcile). Manual tracking: error-prone, time-consuming. Support worker payments: Marcus completes Friday shift (4 hours, $25/hour ordinary, no penalty = $100 for shift). Kayla calculates (shift hours × worker rate, enters into payroll spreadsheet). Kayla submits payroll (accountant processes). Marcus paid $100. But: Marcus worked 30 hours that week (Friday 4 hours + Wed 10 hours + Tue 16 hours = 30 hours). No overtime tracking (provider didn't track whether Marcus exceeded 38 hours/week, no penalty loading applied). Marcus worked 30 hours (under 38, no overtime). But week later: Marcus works 45 hours (Mon 10, Tue 12, Wed 10, Thu 10, Fri 3 = 45 hours). Kayla calculates payroll: 45 hours × $25 = $1,125. Kayla didn't calculate: first 38 hours @ $25 = $950, extra 7 hours @ $37.50 (1.5× penalty) = $262.50, total = $1,212.50. Kayla underpays Marcus $87.50. Marcus complains (month later, after realizing). Kayla apologizes (recalculates, pays arrears). But problem: unclear shift hours tracking, penalties unclear, manual calculations error-prone. Claim frequency: Sarah has shift every Friday 10am–2pm (4 hours weekly, $260/week claim). Over 12-week plan period: 12 shifts × $260 = $3,120 total claim budget. Week 1: Sarah's shift completed (4 hours claimed). Week 2: Sarah cancels (0 hours claimed). Week 3: Sarah attends (4 hours claimed). Week 4: Sarah attends (4 hours claimed). Cumulative: 12 hours claimed (3 weeks) against 48-hour budget (12 weeks × 4 hours). Kayla checks ShiftCare (shows completed shifts, doesn't show budget remaining). Kayla manually calculates: 48 hours allocated, 12 hours used, 36 hours remaining. But error: plan says budget is for "assistance with community participation" but Sarah's service item code includes "appointment support + daily living". Codes have different hourly rates (daily living $65/hour vs appointment support $52/hour). Plan allocates $3,120 mixed, unclear split. Kayla claims (guesses on code for each shift, inconsistent coding, some shifts billed under $65 code, others $52 code). But actual plan meant: $1,560 daily living (24 hours @ $65) + $1,560 appointment support (30 hours @ $52). Kayla's mixed coding doesn't align (claims more hours under higher-rate code). NDIA audit (later) finds: miscoding, refund demand. Total friction: claim coding manual + error-prone, budget tracking (no visibility), service item code lookup manual (delays, mistakes), refunds audit-driven, participant safety at risk (skill mismatches, WWCC liability), support worker payments undercalculated (disputes), family invoicing manual (gap payments untracked), plan utilization unclear (budget doesn't align with coding). **Total: $12k+ annually (refunds + disputes + manual overhead + regulatory risk).**
Fifteen-worker disability support services provider (Queensland, NDIS registered, 42 active participants, NDIA plan funding $480k annual, 3 managers, $320k revenue): ShiftCare ($55/seat/month = $9.9k/year, middleware, web-based scheduling, lacks native claim integration, service item code mapping manual, skill/WWCC tracking absent, GST invoicing manual, support worker payments unintegrated, plan budget tracking opaque). Manager Kayla (lead operations, oversees 15 support workers, 42 participants, rosters, claims, payments, compliance). Participant Sarah (NDIS plan: 12-week cycle, $3,120 funding allocated, session type "assistance with community participation + daily living", 1 shift per week Friday 10am–2pm, support worker assigned). Monday Week 1: Kayla opens ShiftCare (assigns Marcus, senior support worker, Friday 10am–2pm). Kayla doesn't verify: Marcus qualifications (DSW cert? TBI training? WWCC current?). Marcus profile in ShiftCare: name, phone, rates, no skills tag. Kayla assumes Marcus qualified (general assumption). Friday Week 1: Marcus attends (10am–2pm, Sarah present, session progressed, Marcus notes "Worked on daily living skills, cooking, supported Sarah meal prep, 4 hours completed, positive session"). Kayla reviews (shift logged, 4 hours documented). Kayla must now claim: Sarah's NDIA plan has $3,120 budget, this shift uses some. Kayla opens NDIA Portal My Place (government system, requires claim form entry). Kayla enters: participant name Sarah, service date Friday Week 1, hours 4, worker Marcus, service type (dropdown: "Assistance with daily living / Assistance with community participation / Appointment support / Other"). Kayla thinks: Marcus's notes said "daily living" (cooking prep). Kayla selects "Assistance with daily living". But NDIA requires: service item code. Codes are complex (6-digit, different rate for each). Daily living code 01-02-01a = $65/hour. Appointment support code 01-12-05a = $52/hour. Community participation code 01-09-01a = $72/hour. Kayla must choose correct code (wrong code = later audit, refund demand). Kayla looks: NDIA code reference (128-page PDF, overwhelming). Kayla guesses: "Cooking is daily living, code 01-02-01a." Kayla enters code. Kayla calculates claim: 4 hours × $65/hour = $260. Kayla enters claim amount. Kayla attaches proof: ShiftCare export (shift record). Kayla submits. NDIA processes (5–7 business days). Funds transfer: $260 to provider account. Kayla reconciles: claimed $260, received $260, matches. Kayla moves on. But gap: no validation. If Kayla chose wrong code, NDIA approves anyway (initially), audit happens later. Week 2: Sarah cancels (family emergency, calls Kayla). Kayla cancels shift in ShiftCare (Marcus notified). Zero claim for Week 2. Week 3–12: Sarah attends (8 more shifts × 4 hours = 32 hours claimed total). Kayla codes: mostly guessing (daily living most shifts, 1 appointment support, 1 community participation). Kayla claims: ~$2,050 across 9 shifts (mix of rates). Plan budget: $3,120 allocated, $2,050 claimed, $1,070 remaining. But Kayla doesn't track (no visibility in ShiftCare on budget vs claimed). Kayla doesn't know: plan balance (guesses: "Probably half used?"). Month 4: NDIA compliance audit (random sample, 5 providers audited quarterly, this provider selected). Auditor reviews: 20 claims across 5 participants. Sarah's claims (9 shifts). Auditor spot-checks: Friday Week 1 shift claim. Claim says: "Assistance with daily living, code 01-02-01a, 4 hours, $260". Auditor calls Sarah (verification): "What did Marcus help with Friday Week 1?" Sarah: "We went to the shopping centre, Marcus helped me choose groceries, we came back, Marcus helped me unload. Mostly community outing, not cooking." Auditor flags: "Claim coded daily living (01-02-01a, $65/hr), but service was community participation (01-09-01a, $72/hr). Code mismatch." Auditor reviews other claims: Week 6 shift (Kayla coded appointment support 01-12-05a). Auditor checks: "What did Marcus do?" Sarah: "Marcus came but we didn't go to appointment, we stayed home." Auditor flags: "Coded appointment support, but no appointment attended. Code invalid for this shift." Auditor tally: 5 of 9 Sarah shifts miscoded. Provider owes refund (some codes high-paid, some low-paid). Auditor calculates: Net adjustment $340 refund demand. Auditor checks: 15 other claims (spot-check), finds similar miscoding (provider-wide issue, 8 of 20 claims miscoded). Auditor expands: requires provider to audit entire 4-week sample self-report (provider self-audits all claims, finds 35% miscoding rate). Auditor demand: full refund of miscoded shifts ($4,200 across sample period). Provider also fined: $600 audit admin fee. Provider total liability: $4,800. Kayla shocked (thought claims were correct). Kayla realizes: no validation system, Kayla guessing on codes, no auto-mapping from shift notes to codes. Participant safety: Josh referred to provider (TBI, high support needs, complex triggers, self-regulation difficulty). Josh's NDIS plan: requires "specialist support worker with TBI training". Kayla assigns: Marcus (senior support worker, general DSW cert, no TBI background). Kayla reason: Marcus is senior, experienced with participants. But Kayla never checked: TBI training. Kayla doesn't know ShiftCare doesn't track skills (no field for "TBI trained", "mental health cert", etc.). First shift: Marcus attends (Josh present, conversation uncomfortable). Josh mentions: past trauma from car accident (TBI origin). Marcus doesn't know: TBI trauma triggers (Marcus responds casually: "Accidents happen."). Josh escalates (becomes distressed, triggered). Marcus unprepared (no TBI de-escalation training), calls manager Kayla (shift emergency). Kayla drives to location (calms Josh, crisis averted). Post-incident: Josh's family calls Kayla "Why did you send a worker without TBI training? Your worker made Josh worse." Kayla apologizes (realizes: Marcus not qualified). Kayla checks ShiftCare (worker list: Marcus, Jess, Pete, Sarah — all say "Support Worker". No skills breakdown). Kayla manually calls (asks each: "What's your training?" Marcus: "DSW cert, some mental health training, no TBI." Jess: "DSW, First Aid, mental health certificate, no specific TBI." Pete: "DSW, WWCC, no advanced certs." Sarah: "DSW, no advanced certs."). Kayla realizes: none have formal TBI training. Kayla finds: specialized TBI-trained worker not in roster (only general DSW staff). Kayla's solution: external referral (hire TBI specialist contractor, costs extra $45/hour vs $25/hour staff). Josh gets correct worker (crisis resolved, family reassured). But friction: Kayla can't safely assign complex needs without skill visibility. WWCC compliance: provider has 3 participants under 18 (minors, ages 14–17). All workers supporting under-18 need WWCC (Working with Children Check, Queensland requirement, criminal history verification, $123 fee/worker/5-year cycle). Provider roster: 15 workers. 8 work with under-18 participants. All 8 need WWCC. ShiftCare doesn't track WWCC status (no field, no alerts, no expiry reminder). Kayla manually tracks (Excel spreadsheet: worker name, WWCC date, expiry date). Kayla checks: Marcus WWCC (Kayla remembers: "Expired last month, didn't renew yet"). Kayla realizes: Marcus assigned under-18 participants 2 weeks post-expiry (8 shifts × 4 hours = 32 hours unsupervised work with minors, WWCC invalid). Kayla panics (regulatory breach, Queensland Disability Services Commission could fine $10k–$50k, license suspension risk). Kayla retroactively removes Marcus shifts with under-18 participants from ShiftCare (but damage done, liability exists). Kayla forces Marcus to renew WWCC immediately ($123, 2-week processing). Marcus renewed (WWCC valid again). Kayla adds: calendar reminder (all workers WWCC expiry flagged, 90-day advance notice). But system still manual (no auto-alerts, Kayla carries risk). Invoicing gap funding: NDIS covers bulk of cost, families pay remainder (gap payment). Sarah's shift: NDIS covers $260 (4 hours @ $65/hr daily living code). Family co-payment: $40/hour × 4 hours = $160. Family must pay $160. Kayla needs invoice (legally required, GST-compliant). Kayla uses: ShiftCare export (shift data). Kayla manually creates invoice in Excel (service description, hours, rate, GST calculation $160 ÷ 1.1 = $145.45 + GST $14.55). Kayla sends invoice email (PDF) to Sarah's family. Family responds: "We'll pay EFT Friday." Kayla waits (no system tracking, relies on email). Friday arrives, Kayla checks bank manually (received payment? Or not?). Payment received (Kayla logs manually: "Sarah family paid $160 Friday 10:30am"). Kayla notes spreadsheet. Gap payment tracking: across 42 participants, 20 families pay gap funding ($160/week average). 20 families × $160 = $3.2k/week gap funding due. Kayla tracks: received/pending? Spreadsheet shows (payments received: $48k/year, pending: $3.2k estimated). But accuracy: unclear (some families delay, some overpay, some underpay). Kayla manually chases (emails, phone calls: "Your gap payment $160 still outstanding, due Friday"). Manual chasing: time-consuming, friction. Support worker payments: Marcus worked Friday (4 hours × $25/hour = $100). Kayla enters payroll: Marcus 4 hours, $100. But Kayla doesn't track: total weekly hours (no overtime visibility). Marcus that week: Mon 8 hours, Tue 10 hours, Wed 8 hours, Thu 6 hours, Fri 4 hours = 36 hours total. Under 38 hours/week ordinary, no penalty. Payroll correct. But following week: Marcus works Mon 10 hours, Tue 12 hours, Wed 10 hours, Thu 10 hours, Fri 3 hours = 45 hours. Kayla calculates: 45 hours × $25 = $1,125. But correct: 38 ordinary hours @ $25 = $950, 7 overtime hours @ $37.50 (1.5× penalty) = $262.50, total $1,212.50. Kayla underpaid Marcus $87.50. Marcus notices month later (reviews payslip, "I worked 45 hours, should be more"). Marcus disputes: Kayla admits error (recalculates, pays arrears $87.50 + interest). Bad feelings. Kayla realizes: no shift hours tracking system, penalties untracked, manual calculations error-prone. Claim budget alignment: Sarah's plan allocates $3,120 budget. Budget breakdown (plan says): "$1,560 daily living support (24 hours @ $65), $1,560 community participation (30 hours @ $72)". Total: 54 hours, $3,120 split. Over 12 weeks (54 hours ÷ 12 weeks = 4.5 hours/week). Sarah's shifts: 4 hours/week, mostly daily living. Plan alignment: should use ~2 hours daily living, 2 hours community/appointment mix weekly. But Kayla codes: randomly (guesses on each shift type). Kayla claims: Week 1 daily living $260, Week 3 community participation $288, Week 5 appointment support $208, etc. Cumulative: Kayla's claims don't match plan split. Kayla claims: $2,200 daily living (after 9 weeks), $920 community/appointment mixed (after 9 weeks). Plan split: should be ~$1,470 daily living, $1,650 community/appointment (~50/50). Kayla's split: $2,200 skewed toward daily living (overspent daily living budget, underspent community). NDIA audit: notices split mismatch. Auditor checks: "Why are 75% of claims daily living, but plan allocated 50/50?" Kayla can't explain (Kayla didn't track split). Auditor demands: reallocation of claims (some miscoded). Auditor refund: $340 (some community shifts billed as daily living, need refund adjustment). Friction total: manual claim coding (error-prone, 35% miscoding rate, audits refund), service item code lookup (overwhelming, Kayla guesses), skill/WWCC tracking absent (unsafe worker assignment, regulatory risk), budget tracking (no visibility, claim split misaligned with plan), gap invoicing (manual, payment tracking spreadsheet-based, chasing manual), support worker payments (undercalculated penalties, disputes), plan utilization unclear (over/under spend unknown until audit). **Total: $12k+ annually (refunds $4.8k + audit fines + manual overhead $3k + disputes + regulatory liability risk $2k+ if WWCC breach escalates).**
Five Custom Features That Layer Above ShiftCare (Or Replace It)
1. Support Worker Skill Matrix + WWCC Verification & Expiry Alerts — Worker Profile Dashboard, Skills/Certifications Tracked (DSW, TBI, Mental Health, First Aid, NDIS Trained), WWCC Status & Expiry Calendar, Automated Renewal Reminders, Safe Assignment Matching, Compliance Audit Trail, Participant Risk Flagging
Current: support worker skills tracked manually (Kayla calls each worker, notes on paper), WWCC stored nowhere (spreadsheet only), no automation, assignment errors (TBI participant gets non-TBI worker, crisis). New system: worker skill matrix. Setup: 15 support workers, each with profile. Marcus profile: DSW cert (verified, copy on file), mental health training (2-day course, verified), no TBI cert, WWCC #QLD-2024-45678 (valid until March 2029, 90-day alert set). Jess profile: DSW cert, First Aid (current), mental health cert (valid), WWCC #QLD-2024-45679 (valid until May 2029). Pete profile: DSW cert, WWCC #QLD-2024-45680 (expires August 2026, alert: "60 days until expiry, renewal recommended"). System flags Pete: WWCC renewal due 60 days out. Kayla receives alert (email: "Pete WWCC expires August 2026, renewal deadline June 2026, renew now"). Pete renews immediately (avoids post-expiry assignment). System tracks: Pete new WWCC #QLD-2024-45681 (valid until August 2031). Kayla checks: no lapsed WWCC workers. Assignment safety: new participant Josh (TBI, requires TBI-trained support worker). Kayla opens roster assignment. System shows: worker list, skill filter. Kayla filters: "TBI trained". System returns: (no workers match). System recommends: "No TBI-trained workers available, recommend specialist referral or external contractor hire." Kayla arranges: TBI specialist contractor (external, $45/hour, assigned Josh). Alternative: Kayla checks: "Mental health trained + DSW". System returns: Jess, Marcus, Sarah qualified. Kayla reviews: Jess (DSW, mental health cert, no TBI but broad behavioral support). Kayla notes: Jess may support TBI indirectly (behavioral management skills), but recommends Josh first session with specialist, then Jess for routine support. System documents: Josh support plan (specialist TBI worker for crisis, Jess for ongoing). Participant safety: Josh receives specialist first, then trusted worker Jess (both qualified). Crisis avoided. Compliance: system maintains audit trail (Josh assigned Jess, Jess qualifications verified, TBI specialist on file, decision documented). NDIA auditor: reviews Josh's support team (sees specialist + Jess qualifications, no risks flagged). Audit trail: WWCC status visible (all 8 workers supporting under-18s have current WWCC, verified dates). Auditor satisfied: "Compliance audit pass." **Value: safe assignment matching (no unqualified workers assigned), WWCC compliance (zero lapsed workers supporting minors), regulatory audit trail (verified skills, no fines), participant safety (right worker for each need). Payback: 4 weeks.**
2. Service Item Code Auto-Mapper — NDIA Code Reference Database, Shift Notes-to-Code Matching, Service Type Classification, Budget Allocation Tracking, Claim Accuracy Validation, Coding Recommendation Engine, Audit-Ready Compliance Documentation
Current: NDIA service item codes manual lookup (128-page PDF, Kayla guesses, 35% miscoding rate, audits refund $4.8k). New system: code auto-mapper. Setup: NDIA code database (all 180+ codes, rates, eligibility rules, auto-updated quarterly). Shift entry: Marcus completes Friday shift (notes: "Worked on daily living skills, cooking, supported Sarah meal prep, 4 hours completed"). Kayla enters shift in system: service type dropdown (daily living / community participation / appointment support / other). Kayla selects: "Community participation" (shopping centre mentioned). System extracts: shift notes (cooking, shopping, meal prep). System analyzes: "Keywords detected: shopping, meal prep, community outing = community participation (01-09-01a, $72/hour)". System recommends code: 01-09-01a (not daily living 01-02-01a). Kayla reviews recommendation (cooking mentioned, but context shopping centre = community outing). Kayla confirms: code 01-09-01a. System calculates claim: 4 hours × $72/hour = $288 (not $260). System validates: Sarah's plan budget $3,120 allocated, community participation code 01-09-01a allows up to 30 hours @ $72. This shift uses 4 hours. Budget remaining: 26 hours community participation. System shows: allocation tracker (24 hours daily living allocated, 4 used, 20 remaining; 30 hours community participation allocated, 4 used, 26 remaining). Kayla confirms: submit claim $288. NDIA receives: code 01-09-01a, $288, correctly coded. Alternative scenario: Marcus shift coded as appointment support (01-12-05a, $52/hour) by mistake. System validation: shift notes don't mention appointment (notes: "Community outing shopping"). System flags: "Code 01-12-05a requires appointment, but notes mention shopping outing. Misalignment detected. Recommend code 01-09-01a instead." Kayla corrects (avoids miscoding). Audit scenario: NDIA auditor reviews Sarah claims. Auditor checks: 9 shifts, all codes. System-matched codes: all 9 correctly classified (daily living, community participation, appointment support appropriately coded). Auditor verification: spot-check 2 shifts. Shift 1: code 01-09-01a community participation, auditor calls Sarah "Friday shift, what did Marcus help with?" Sarah: "Shopping centre outing." Auditor satisfied: "Code correct." Shift 5: code 01-02-01a daily living, auditor calls Sarah "Monday shift, what did Marcus help with?" Sarah: "Cooking dinner, meal prep at home." Auditor satisfied: "Code correct." Auditor tally: 0 miscoded shifts (vs historical 35% miscoding). Auditor: "No refund demanded, provider has strong coding compliance." Compliance audit: pass. Provider avoids: $4.8k refund + $600 audit fee. Budget visibility: system shows (Sarah plan $3,120 budget, week by week: Week 1 $288 claimed, cumulative $288 of $3,120. Week 2 $0 (cancelled), cumulative $288. Week 3 $260 claimed (daily living), cumulative $548. ... Week 12 cumulative $2,050). System shows: budget remaining $1,070 (can accommodate 2 more full shifts). Kayla plans: remaining weeks (have capacity, can book additional shifts if Sarah requests). Coding confidence: Kayla trusts system (not guessing). Audit-ready: all shifts documented, codes justified (notes + system rationale), budget aligned with plan split. **Value: coding accuracy 99%+ (vs current 65%), audit compliance pass (zero refunds), budget visibility (no surprises), claim submission 50% faster (no code lookup time). Payback: 6 weeks.**
3. Plan Claim Submission + NDIA Portal Integration — Automated Claim Export to NDIA Portal My Place, Real-Time Plan Budget Tracking, Bulk Claim Submission, Claim Status Monitoring, Remittance Tracking, Compliance Documentation Auto-Generated, Dispute Resolution Audit Trail
Current: claim submission manual (Kayla exports ShiftCare, enters NDIA portal, hand-keys each claim, 15 minutes per claim × 42 participants = 10.5 hours/week). New system: NDIA integration. Setup: system syncs with NDIA Portal My Place (via API, if available, or secure import/export). Shift completion: Jess completes shift Friday 2pm–6pm with Sarah (4 hours, daily living support). Jess logs in app: shift complete, notes recorded. System auto-populates: Sarah, Friday, 4 hours, daily living code 01-02-01a, amount $260. Kayla reviews claim (on dashboard: pending claims, grouped by participant, by plan period). Kayla clicks: "Sarah pending claims, Week 1". System shows: Friday shift $260. Kayla clicks: "Submit to NDIA". System exports: claim file (formatted for NDIA portal). System either: (a) auto-submits to NDIA Portal My Place (if API connected), or (b) exports file for Kayla to upload. Auto-submit scenario: system submits (Kayla receives confirmation SMS/email "Sarah Week 1 claim submitted, $260"). System tracks: claim status (submitted, pending processing, approved, paid). Kayla checks: dashboard shows (Sarah Week 1 claim: status "approved", paid $260, payment date Friday). Manual upload scenario: Kayla downloads claim export (CSV/JSON). Kayla uploads to NDIA portal (portal accepts file, auto-imports 10 claims at once vs 1 at a time manually). Kayla saves: 9 minutes per batch (10 claims). For 42 participants × 4 claims/plan period = ~17 batches, saves 2.5 hours/plan cycle. Bulk submission: Kayla opens dashboard, week 12 plan period (all participant claims due). System shows: 38 of 42 participants have completed claims ready (4 pending shifts). Kayla clicks: "Submit all ready claims to NDIA". System exports: 38 claims (batch file). Kayla uploads: 1 file to portal (vs manually entering 38 individual claims). Portal processes: 38 claims approved (5–7 business days). Remittance tracking: Kayla checks: bank account (funds received?). System shows: payment dashboard (Week 1 submissions: 42 claims totaling $10,560 submitted 10 June. Status: 38 approved, 4 pending. Approved amount: $9,880 paid 17 June). Kayla reconciles: expected $10,560, received $9,880, pending $680 (4 claims awaiting approval). System alerts: "4 claims pending >7 days, recommend follow-up with NDIA". Kayla calls NDIA (follows up, claims approved next day). Payment received. Compliance documentation: system auto-generates (compliance report for audit). Report shows: 12-week plan period, 42 participants, 168 shifts logged, 162 claims submitted, 162 approved, zero rejected, zero refunds. Auditor reviews: report shows (all claims coded correctly, all submitted, all approved). Auditor tires (nothing to audit, compliance verified). Dispute resolution: participant Josh's family disputes claim (family says "Session was only 2 hours, not 4, charged incorrectly"). System shows: shift notes (worker logged 4 hours Friday). Family says: "Worker stayed only 2 hours." Dispute created. System tracks: dispute claim ($288 claimed, $144 disputed, $144 accepted pending resolution). System documents: family communication log (dispute noted, resolution pending). Kayla calls worker (verification: "How long was Friday session?" Worker: "4 hours, 2pm–6pm"). Kayla calls family (verification: "What time did session start/end?" Family: "2pm–4pm, I'm certain"). Kayla reviews: shift notes vs family recall. Kayla offers: compromise (split difference, claim $216 accepted). System documents: dispute resolved ($72 adjustment). **Value: claim submission 80% faster (batch vs manual), NDIA compliance automated (zero late submissions), remittance tracking transparent, disputes documented (audit trail), plan period close-out simplified. Payback: 8 weeks.**
4. Gap Invoicing + Payment Collection Tracking — Family Co-Payment Invoice Generation (GST-Compliant), Payment Method Integration (EFT, Credit Card, PayPal), Automated Payment Reminders, Payment Status Dashboard, Gap Revenue Reconciliation, Aged Debt Alerts, Compliance Tax Documentation
Current: gap invoicing manual (Kayla creates Excel invoice, sends email, tracks payment via spreadsheet, manual chasing, payment tracking unclear). New system: gap invoicing platform. Setup: 20 families pay gap funding ($160/week average Sarah, $200/week average Josh, etc.). Shift completion: Friday Sarah shift $260 NDIS covered, family co-payment due $40/hour × 4 hours = $160. System auto-generates invoice (invoice #FG-2026-0847, date 14 June, service description "Community participation support, 4 hours, 14 June", rate $40/hour, amount $160, GST $16, total due $176). System emails family: "Invoice #FG-2026-0847 due by 21 June, $176. Pay via EFT [account details], credit card [link], or PayPal [link]." Family receives: invoice (clear, payment options). Family pays: credit card online ($176, processed immediately). System confirms: payment received, invoice marked paid (automated). Payment dashboard: Kayla checks (Week 1 invoices: 20 families invoiced, $3,200 total. Received: $3,040 (95%). Pending: $160 (1 family, 5 days overdue). Unpaid: $0). System alerts: "1 invoice overdue >5 days, recommend reminder." Kayla sends: automated reminder (SMS/email "Invoice $160 overdue, due yesterday, please pay today or contact us"). Family responds: pays same day. Aged debt tracking: Week 5 invoice (family David's invoice $220, due by 25 June). David doesn't pay. By 30 June (5 days overdue), system flags "invoice 5 days overdue". By 7 July (14 days overdue), system escalates "invoice 14 days overdue, recommend formal payment demand". Kayla sends: formal demand email "Invoice #FG-2026-0856 outstanding 14 days, amount $220, require payment within 7 days or pursue debt collection." David responds: "I forgot, paying now." David pays. System tracks: payment date 8 July, invoice marked paid (late payment noted). Annual summary: Kayla checks (gap revenue $48k annually invoiced, $47.2k collected 98%, $800 unpaid/disputed, 1 family in formal debt recovery). System maintains: collection rate tracking (quarterly targets, monthly performance). Compliance tax documentation: system auto-generates (tax report for accountant). Report shows: gap invoices issued $48k, GST collected $4.8k, net revenue $43.2k. System tracks: GST compliance (all invoices GST-calculated, all payments recorded). Accountant reviews: tax report clear (no discrepancies, submits BAS on time). **Value: gap revenue recovery 98% vs current 92% (collection improvement $2.88k/year), invoicing automation (20 families, 52 invoices/year = 52 minutes saved weekly), payment tracking transparent (no chasing from memory), GST compliance automated. Payback: 6 weeks.**
5. Support Worker Shift Hours + Penalties Tracking — Digital Timesheet Logging, Shift Hours Aggregation, Overtime/Penalty Rate Calculation (Ordinary, Overtime 1.5×, Weekend/Public Holiday Loading), Payroll Export Integration, Compliance Wage Audit, Payment Dispute Prevention
Current: support worker payments manual (Kayla calculates hours × rate, misses overtime, underpays workers, disputes monthly). New system: timesheet + payroll. Setup: 15 support workers, each with base rate ($25–$30/hour depending on seniority, experience). Marcus: $25/hour base, senior, no weekend loading (works weekday only). Jess: $26/hour base, trained, works mixed days. Pete: $24/hour base, recent hire. Shift entry: Marcus works Friday shift (10am–2pm, 4 hours). Kayla logs: shift Friday, Marcus, 10am–2pm. System checks: date Friday = weekday (no weekend loading). System calculates: Marcus 4 hours weekday @ $25/hour = $100. Marcus paycheck Friday: $100. Jess works Saturday shift (10am–2pm, 4 hours). Kayla logs: shift Saturday, Jess, 10am–2pm. System checks: date Saturday = weekend. System calculates: Jess 4 hours weekend @ $26/hour × 1.75 loading = $182. Jess paycheck Saturday: $182 (vs base $104 = weekend premium $78). Weekly aggregate: Marcus that week (Mon 8 hours, Tue 10 hours, Wed 8 hours, Thu 6 hours, Fri 4 hours = 36 hours). System totals: 36 hours weekday (all under 38/week ordinary). System calculates: 36 hours × $25 = $900 Marcus paycheck. Overtime scenario: Jess that week (Tue 12 hours, Wed 10 hours, Thu 10 hours, Fri 8 hours = 40 hours). System totals: 40 hours (exceeds 38/week). System calculates: 38 ordinary hours @ $26 = $988, 2 overtime hours @ $26 × 1.5 = $78, total = $1,066 Jess paycheck (vs incorrect calculation 40 hours × $26 = $1,040 = underpay $26). System tracks: Jess overtime (2 hours worked, correctly loading applied). Payroll export: Kayla opens payroll dashboard (week 1–4 summary). System shows: 15 workers, total hours 287 (mix of weekday 262 hours + weekend 25 hours). System shows: total payroll cost $6,850 (breakdown: ordinary 262 hours @ average $25.33 = $6,636, weekend 25 hours @ average $26 × 1.75 = $1,137, overtime 3 hours @ average $26.50 × 1.5 = $119, total $7,892). Kayla exports: payroll file (CSV) to accountant software (automatically imports, no re-entry). Accountant processes: payroll run (all 15 workers paid correctly, zero manual entry). Payment dispute prevention: Marcus receives paycheck $900 (week 36 hours, correct). Marcus checks: no disputes. Jess receives paycheck $1,066 (week 40 hours including overtime, correct). Jess checks: "Overtime loading applied, $1,066 correct, no disputes." Pete works 30 hours (under 38, no overtime). Pete receives: 30 hours × $24 = $720 (correct). Compliance wage audit: system maintains (shift logs + penalty rate calculations), auditable by Fair Work. Auditor spot-checks: Marcus week 1 (system shows shifts Mon–Fri, hours logged, rates applied, total $900). Auditor verifies: "Correct rates, correct overtime handling, compliant." Auditor checks: provider-wide (all workers paid correct rates per Fair Work). Auditor result: "Zero wage compliance issues." **Value: overtime/penalty accuracy 100% (vs current 85%, prevents underpayment disputes $500–$1k/quarter), payroll integration (no manual entry), Fair Work audit compliance (verified rates logged). Payback: 5 weeks.**
Australian NDIS Context: Service Item Codes, NDIA Compliance, Participant Plans, Disability Support Worker Standards
**National Disability Insurance Scheme (NDIS)** — Australian government program funding disability support (participants aged 7–65, permanent disability, ongoing support needs). NDIS provides personal funding (participant-directed), participants choose support providers. **NDIA (National Disability Insurance Agency)** — administers NDIS, approves plans, allocates funding, processes claims, audits providers (quarterly compliance sweeps, 5–20% of providers per quarter). **Service Item Codes** — NDIA defines 180+ support service codes (6-digit alphanumeric, each with hourly rate, eligibility rules). Examples: 01-02-01a "Assistance with daily living" $65/hour, 01-09-01a "Community participation" $72/hour, 01-12-05a "Appointment support" $52/hour. Providers must code claims correctly (wrong code = audit refund demand). **Participant Plans** — 12-month (or shorter 6-month) funding cycle, plan specifies approved services + hours. Example: Sarah's plan $3,120 allocated, 24 hours daily living @ $65 + 30 hours community participation @ $72 + 18 hours appointment support @ $52. Plan is binding (claim outside plan scope = refund). **Support Worker Certification** — Disability Support Worker (DSW) certificate mandatory in QLD (nationally registered, 6-month course, covers communication, safety, disability awareness). Specialist roles (TBI, mental health, autism) require additional training. **WWCC (Working with Children Check)** — criminal history verification, mandatory for workers supporting under-18 participants in QLD (all states + territories, varies). Valid 5 years, renewal required every 5 years ($123 fee). Expired WWCC = regulatory breach, fines $10k–$50k, license suspension. **NDIA Compliance Audits** — random quarterly, 5–20% of providers audited per quarter. Auditor spot-checks: 20 claims, verifies coding, checks plan alignment, confirms shift notes vs claimed hours. Breaches: miscoding, plan overspend, services provided outside plan scope. Refunds demanded: miscoded claims refunded (full shift amount), audit admin fee $600–$1,200. Repeat breaches: provider license suspension risk. **ShiftCare & CarePartner** — market incumbent NDIS roster software ($50–$130/seat/month, web-based, scheduling + some compliance features, integrates loosely with NDIA portal, limited skill tracking, no service item code auto-mapper, no telehealth, Australia-focused but generic). **GST Compliance** — disability support providers registered for GST (threshold $10k annual revenue, varies by state). Gap invoicing must be GST-compliant (invoice format, tax calculation, records kept for audit). Tax office audits (BAS quarterly, full audit if claims suspicious). Non-compliance: penalties 10%–20% of tax owed.
Six FAQs
How does support worker skill matching prevent unsafe assignments and regulatory breaches?
Current: skills tracked manually (Kayla calls each worker), no visibility, assignments unsafe (TBI participant gets non-TBI worker, crisis). WWCC tracking: spreadsheet only, lapses undetected (Marcus assigned under-18 with expired WWCC = regulatory breach). New system: skill matrix. System shows: each worker's certifications (DSW, TBI, mental health, First Aid, WWCC), verified dates, expiry alerts (60 days before WWCC expires, automated reminder). Assignment safety: new participant Josh (TBI) needs TBI-trained support worker. Kayla filters: "TBI trained". System shows: no workers qualify. Kayla arranges: specialist external hire (correct match). Josh receives: qualified support (no crisis). WWCC compliance: system alerts (Pete WWCC expires August 2026, renew by June). Pete renews (avoids post-expiry assignment to minors). Audit trail: system documents (all under-18 support workers have current WWCC, verified). NDIA auditor: compliance verified, zero fines. **Value: safe assignment (no unqualified workers), WWCC compliance (zero breaches), regulatory audit pass. Payback: 4 weeks.**
How does service item code auto-mapping eliminate miscoding refunds?
Current: codes manual lookup (128-page PDF, Kayla guesses, 35% miscoding rate, audits refund $4.8k/year). New system: auto-mapper. System extracts: shift notes (worker logged "shopping centre outing"). System recommends: code 01-09-01a community participation (not 01-02-01a daily living). Kayla confirms (shift notes aligned with code). System validates: claim $288 correctly coded. NDIA audit: all claims correctly coded (0 miscodes vs historical 35%). Auditor: compliance verified, zero refunds. Provider avoids: $4.8k refund + $600 audit fee. **Value: coding accuracy 99%+, audit compliance pass, zero refunds. Payback: 6 weeks.**
How does NDIA integration streamline claim submission and track payment status?
Current: claims manual (Kayla exports ShiftCare, enters NDIA portal, hand-keys each claim, 15 minutes per claim). New system: NDIA integration. Claim ready: system exports (formatted for portal). Kayla uploads: 1 file per batch (10 claims). System tracks: status (submitted, approved, paid). Dashboard: Kayla checks (Week 1 claims: 38 approved, $9,880 paid 17 June; 4 pending, $680 status monitoring). Kayla follows up (pending claims approved next day). Remittance: reconciled automatically. **Value: submission 80% faster (batch vs manual), tracking transparent, remittance reconciliation automated. Payback: 8 weeks.**
How does gap payment tracking and invoice automation improve revenue collection?
Current: invoicing manual (Excel, email PDF, payment tracked via spreadsheet, manual chasing, collection 92%). New system: gap invoicing. Invoice: system auto-generates (GST-compliant, emailed with payment options EFT/card/PayPal). Payment: family pays online (processed immediately). Dashboard: Kayla checks (20 families invoiced, $3,200 total, received $3,040 (95%), 1 overdue flagged). Reminder: automated (SMS/email). Collection improves: 98% vs current 92% ($2.88k/year gain). **Value: automation (52 invoices/year saved manually), collection +6%, revenue gain $2.88k/year. Payback: 6 weeks.**
How does shift hour aggregation and penalty rate automation prevent wage disputes?
Current: payroll manual (Kayla calculates, misses overtime, underpays workers, disputes $500–$1k monthly). New system: timesheet + penalties. Shift log: Jess works Saturday (4 hours). System auto-applies: weekend loading 1.75× ($26 × 1.75 = $45.50/hour, 4 hours = $182). Weekly aggregate: Jess 40 hours (2 overtime hours). System calculates: 38 ordinary @ $26 = $988, 2 overtime @ 1.5× = $78, total $1,066. Paycheck correct (no underpay). Dispute prevention: Jess receives $1,066 (overtime loading visible). Jess satisfied (no dispute). Fair Work audit: system shows (all workers correct rates, zero compliance issues). **Value: penalty accuracy 100%, zero underpayment disputes, Fair Work audit compliance. Payback: 5 weeks.**
How do custom add-ons complement ShiftCare without replacing it?
ShiftCare is roster backbone: scheduling, shift logging, worker contact, basic compliance. Full replacement = risky (data loss, staff retraining, vendor migration, regulatory approval). Aidxn approach: custom add-ons layer above ShiftCare (skill matrix reads worker profiles from ShiftCare, posts qualifications + WWCC status to safety dashboard; code auto-mapper reads shift notes from ShiftCare, recommends service item codes, syncs claim back; NDIA integration exports ShiftCare shifts + claims to NDIA portal; gap invoicing reads shift hours from ShiftCare, auto-calculates family co-payment, sends invoice). Result: ShiftCare stays (immovable scheduling backbone), custom tools unlock skill safety + coding accuracy + claim automation + payment tracking + wage compliance (differentiation, competitive advantage). No replacement needed, lower risk, faster build.
The Bottom Line
Fifteen-worker disability support provider (Queensland, NDIS registered, 42 participants, $480k annual plan funding, $320k revenue): ShiftCare ($55/seat/month = $9.9k/year, roster scheduling only, lacks native NDIS integration, no skill matching, no code mapper, no gap invoicing, no wage penalty tracking). Friction: service item code miscoding (35% error rate, audits refund $4.8k/year), unsafe worker assignment (skills unknown, TBI participant gets wrong worker, crisis), WWCC compliance (spreadsheet-based, Marcus assigned under-18 post-expiry = regulatory risk), plan claim budget tracking (no visibility, over/underspend unknown until audit), gap invoicing manual (payment tracking spreadsheet, chasing manual, collection 92%), support worker payments (penalties undercalculated, disputes $500–$1k/month). **Total: $12k+ annually (refunds $4.8k + audit admin $600 + manual overhead $2k + disputes + regulatory liability risk $4.6k if WWCC breach escalates + revenue loss $2.88k uncollected gap).** Custom NDIS platform ($72k build + $4.8k/year ops): skill matrix (safe assignment, WWCC compliance, zero breaches = $4.6k compliance cost avoidance), code auto-mapper (coding 99%+ accuracy, zero refunds, audit pass = $5.4k value), NDIA integration (claim submission 80% faster, tracking transparent = $2k ops savings), gap invoicing (payment automation, collection +6%, $2.88k revenue gain), wage penalty tracking (zero disputes, Fair Work audit compliance = $6k/year dispute + audit cost avoidance). **Year 1 value: $21.68k** (conservative, doesn't include participant safety improvements or staff retention). Payback: 40 weeks (custom investment $72k ÷ $21.68k year 1 value = 3.3 years, improves Year 2+ with operational scale). Start custom NDIS platform if: (1) ShiftCare or CarePartner user (roster-only, no NDIS integration), (2) 10+ support workers (skill tracking manual overhead), (3) service item code miscoding suspected (audits refund), (4) WWCC compliance tracked manually (regulatory risk), (5) gap invoicing manual (payment tracking spreadsheet), (6) wage disputes quarterly, (7) plan budget alignment unclear. Reach out: book a time to discuss your provider size, participant mix, current friction (miscoding audits, unsafe assignments, WWCC liability, gap payment delays, wage disputes), and custom NDIS platform ROI, or check platform pricing for build quote.