Home care and disability support automation

On this page

A provider of Support at Home, NDIS or private home care that coordinates services delivered by other businesses does much of its admin between a supplier’s bill and a client’s claim. Brokerage suppliers, labour-hire agencies, equipment and home modification suppliers, and clients claiming reimbursements all send paperwork, and it arrives as PDFs and photos in more than one inbox. A care partner approves each bill, accounts payable enters it as a draft bill in Xero, and a weekly or fortnightly claim run takes it through exports, spreadsheets and a checklist before it reaches your care-management platform and then Services Australia or the NDIA. Monthly statements then go out against each client’s budget. Care partners decide what a client receives and approve what is billed, and finance decides what is claimed. The matching, pricing, holding and checking around those decisions are predictable, so they run as fixed, tested software. AI is used only where something has to be read, such as a supplier’s invoice or a photo of a receipt, and its output is checked before anything is billed or claimed. Care notes, staff clearances, complaints and privacy records are covered on the health and care page.

These are patterns we see in home care and disability providers, not client case studies. Your process gets its own map in the assessment.

Supplier bills, reimbursements and purchases

Brokerage suppliers send bills, clients send receipts for reimbursement, and equipment and home modification suppliers send invoices. They arrive as PDFs and phone photos in more than one inbox, and some land in the wrong one and have to be found and moved by hand. Each has to be tied to a client, a service and a funding stream, from an invoice that rarely carries your client number. A refund on returned equipment or a cancelled modification can be keyed as a charge, which bills the client instead of crediting them. In the automated version, AI reads each document, and rules route it by what it is rather than which inbox it reached. Rules then match it to the client and the service that was delivered, and credits are recorded as credits. A care partner still approves each bill, and anything that doesn’t match a client and a delivered service goes to accounts payable.

Pricing brokerage services

A brokerage line is priced from the supplier’s cost plus your margin, and sometimes a weekend or public holiday rate, or a client’s special rate, applies on top. When the margin is looked up by the supplier’s name, a supplier that is renamed or spelt differently on its invoice finds no match, and the line goes through at cost. Nobody sees an error, because nothing failed, and it repeats every run. Pricing like this has no judgement in it, so there is no AI in it. Each supplier is matched by its ID in your accounting system, not its name, and the rates and margins in force on the service date are applied to each line, rounded to the cent. A supplier with no rate on file is held for finance rather than passed through at cost, and finance approves each new rate or margin before it is used.

Labour-hire workers on your roster

When an agency worker fills a shift on your roster, the hours are claimed from the roster’s timesheet like any other shift. The agency also sends a bill for the same hours. If that bill reaches the claim, the client is charged twice for one shift, and the client is often the one who finds it, on their statement or invoice. The list that says which bills are labour hire is often kept by hand, one spreadsheet tab per period, and it falls behind. The same agency can be labour hire for one client and a brokerage supplier for another, so the decision belongs to each client and agency pair, not to the supplier. Fixed rules hold every bill that matches a labour-hire arrangement before the claim is built, and flag the list when it hasn’t been updated for the current period. Finance reviews the held bills before the run. A bill that fits both a labour-hire and a brokerage arrangement goes to finance to decide.

The weekly claim run

A weekly or fortnightly claim run moves through exports, a spreadsheet or a macro, tidy-ups at several stages, an import into your care-management platform, another export, and then the upload. The checks are done afterwards, from a checklist, and nothing records what each one found. A duplicate can be flagged and still go through. Lines taken out of a run to be fixed aren’t counted anywhere, so some services are paid to the supplier but never claimed. Automated, the run is fixed software from end to end. Every check runs before the claim is built, every line is accounted for so that none is missing and none is counted twice, and the result of each check is recorded with the run. A person in finance approves each batch before anything is imported or claimed, and the provider keeps responsibility for every claim it makes. The claim and statement steps that follow are covered on the health and care page, under Support at Home claiming and claiming from NDIS, Medicare and health funds.

Rates, rejections and the rules behind the run

Client special rates, discounts and, for Support at Home, contribution arrangements are often kept in notes, a free-text field or someone’s memory. When a rate changes without a date, the old price keeps running, or a client loses a discount they were promised, and it surfaces as a statement query. Rates, discounts and contributions move into one dated table that the claim reads directly, with no AI involved. A line with no matching arrangement for that client is held for finance instead of being priced by default.

Rejected lines come back one at a time, and someone works out the cause, fixes the line and resubmits it. The hard ones wait, and some are never cleared, which leaves services delivered, and often paid to a supplier, that you haven’t been paid for. Rejections are sorted by cause, routine corrections are queued, and each line is tracked until it clears. Delivered, claimed and paid are matched line by line, so a service that was never claimed shows up on a short exception list. The claims officer decides what to do with each one.

Supplier descriptions rarely use the funder’s terms, so someone reads each bill line and chooses the service type or support item by hand, and two people can code the same line differently. The service type is suggested from lines your team has already confirmed for that supplier and service. Where the same description has been confirmed before, the suggestion applies. Where it hasn’t, the line goes to a person to confirm, and that confirmation is used for the next suggestion.

The rules that make a claim run work often live in a macro, a spreadsheet formula or the claims officer’s head. When that person is on leave, the run slows down, stops, or goes ahead without the checks only they knew. The rules move into tables that finance owns and signs off, every change is logged with who made it and when, and the run has a written guide. The checks then run the same way whoever starts the run.

Brokerage suppliers and labour-hire agencies each carry insurance, screening for their workers and an agreement with you, each with its own expiry date. Tracked in a spreadsheet, a lapse tends to surface after the next booking. A register records each supplier’s and agency’s insurance, screening and agreement dates, sends reminders to the supplier and your compliance officer ahead of expiry, and holds new bookings with that supplier when something lapses. AI reads each certificate for the insurer, the cover and the expiry date, and your compliance officer confirms the reading before the record updates. The provider keeps responsibility for the suppliers and workers it uses, and none of this is legal advice.

If one of these costs you real money every month, describe it in four answers.

Thinking about what a process actually costs you?

The assessment is small, fixed-price, and tells you the real number, whether or not you ever build. Claiming for Support at Home or NDIS? Take the claiming health check first. It takes about 3 minutes.

Describe the process

Worth a 30-minute conversation.