Carer Payroll Software for UK Home Care Agencies: A Complete Guide

Most payroll software was built for people who work the same hours in the same place every week. Home care is the opposite of that. A carer's week is a chain of short visits at different rates for different funders, joined by travel and punctuated by mileage, night shifts and the occasional bank holiday. Generic payroll tools see none of it. They see a number of hours typed into a box, and they trust whoever typed it. Carer payroll software exists to close the gap between what actually happened out in the community and what lands in each carer's bank account. This guide covers what that takes. If you're weighing up platforms more broadly, our guide to how to choose domiciliary care software in the UK is the companion piece.

Why care payroll is uniquely hard

Every sector thinks its payroll is complicated. Home care can actually prove it. Five features of domiciliary work combine to make pay calculation harder here than almost anywhere else:

• Variable visits. A planned 30-minute call becomes 50 minutes because a service user had a fall, or 15 because they were out. Multiply that by hundreds of visits a week and the rota is a forecast, not a record. Paying from the plan means paying wrongly, in both directions.
• Travel time. For National Minimum Wage purposes, time spent travelling between appointments generally counts as working time for domiciliary care workers. An agency that ignores travel when checking average hourly pay can drop below the legal floor without ever intending to, and NMW enforcement in the care sector has a long history of catching exactly this.
• Mileage. Carers drive their own cars between calls, and mileage claims usually live in a spreadsheet or on paper, arriving late, unverified and re-keyed by hand into payroll. It is the single most common source of payday disputes.
• Night work and fixed-price shifts. Sleeping nights, waking nights and live-in placements don't fit an hourly model at all. Since the Supreme Court's 2021 Mencap judgment, sleep-in shifts are typically paid as a flat rate rather than hourly, so your pay engine needs fixed shift rates alongside hourly ones, not instead of them.
• Bank holidays and enhancements. Christmas Day at time and a half, an emergency callout at an agreed premium, a senior carer covering a complex package. Each is an exception to the carer's normal rate, and each has to land on the right visit, not smeared across the week.

Underneath all of that sits a structural quirk of care finance: what you charge and what you pay have nothing to do with each other. A council might commission a visit at a banded rate while the carer delivering it is paid hourly at their grade. Software that forces billing and pay into one model, or derives one from the other, will be wrong about at least one of them every week.

What to look for in carer payroll software

Whether you're evaluating a payroll specialist or the finance module of a wider care platform, the same checklist applies:

• Timesheets derived from actual times. Pay should be built from real clock-in and clock-out data captured on the carer's phone at the door, not from the planned rota and not from a manually completed timesheet. If a human has to transcribe hours, errors are guaranteed at scale.
• Pay separated from billing. The rate you charge a payer and the rate you pay a carer must be independently configurable. In homecareOS, what you charge flows from payer to service to rate, and what you pay flows from pay grade to base rate, with no forced relationship between the two.
• A rate hierarchy, not a rate field. One hourly rate per carer cannot represent grades, bank holidays or one-off premiums. You need a waterfall where the most specific rate wins (more on this below).
• Fixed shift rates. Sleeping nights, waking nights and live-in care need flat shift pricing alongside hourly and banded models.
• Mileage inside the pipeline. Claims submitted from the carer app, approved by a manager, verified against the actual route, and pulled into the pay run automatically. If mileage is a separate process, it will always be the late, disputed part.
• Holiday pay accrual and bank holiday overrides. Calculated by the system as hours are worked, not reconstructed at year end.
• Payroll-ready exports. Clean, itemised pay run data your accountant, bureau or payroll package can consume without re-keying, plus financial reporting so you can see cost per carer, per service user and per payer.
• Pay transparency for carers. Carers should be able to see their projected pay, hours, rates and mileage as the period builds, so payday holds no surprises. Disputes are far cheaper to prevent than to resolve, and pay opacity is a genuine driver of the turnover problem we cover in our Bradford Factor guide.

How the pay waterfall works

The pay waterfall is the piece most generic payroll tools are missing, and it's simple to state: for every visit, the most specific rate wins. In homecareOS the hierarchy has three levels:

1. Visit override. A manual rate set on one specific visit. This is how you handle a bank holiday enhancement, an emergency callout premium or any other one-off agreement. It beats everything below it, and it applies only to that visit.
2. Pay grade. The carer's role-based rate, such as Healthcare Assistant or Senior Carer. If there's no override on the visit, the grade rate applies.
3. Base hourly rate. Every carer has one. If neither of the levels above applies, this is the floor the calculation lands on.

The engine works down the list per visit and stops at the first rate it finds. The practical effect is that exceptions stop being spreadsheet work. A coordinator sets an override on the Boxing Day visits once, and every affected carer's pay comes out right without anyone adjusting a timesheet. Promotion to senior carer is a single grade change, not a find-and-replace across rate cards.

The waterfall answers "at what rate?". The other half of the question, "for how many minutes?", is answered by the four-value time model. Each visit in homecareOS carries planned time, actual time, paid time and charged time as independently configurable values. You might pay the carer for the 50 minutes they actually stayed while charging the council the commissioned 45, or pay a guaranteed minimum on a visit that ran short. Because the four values are independent, neither side of that decision corrupts the other, and both sides stay auditable back to the clock times captured at the door.

Common payroll errors home care agencies make

The same failure modes come up in agency after agency:

• Paying from the rota. The planned week is treated as the worked week. Overruns go unpaid, shortfalls go overpaid, and carers learn that staying the extra 20 minutes with a distressed service user costs them money.
• Losing travel time. Travel between calls never enters the calculation, and nobody checks whether average hourly pay still clears National Minimum Wage once it's included. This is the error with regulatory teeth.
• Mileage as an afterthought. Claims are chased on payroll day, approved without verification, and keyed in by hand. Late claims roll into next month and the dispute rolls in with them.
• One rate per carer. Bank holidays and premiums are handled by editing hours ("add two hours to cover the enhancement"), which destroys the audit trail and makes NMW evidence impossible to reconstruct.
• Deriving pay from billing, or billing from pay. If the system only stores one duration per visit, someone is being short-changed: either the funder is billed for the carer's actual minutes regardless of the contract, or the carer is paid the commissioned minutes regardless of reality.
• Reconciliation by heroics. The office spends two or three days a month assembling pay from visit logs, spreadsheets and memory. The cost isn't just the hours; it's that every manual step is a fresh chance to be wrong, and payroll errors are the kind carers remember.

Where homecareOS fits, and where it stops

homecareOS handles the part of payroll that generic tools can't: getting the numbers right. Timesheets are derived from carers' actual clock-in and clock-out times. The pay waterfall applies visit overrides, pay grades and base rates automatically, with bank holiday rate overrides and holiday pay accrual calculated as the period builds. Mileage claims come in from the carer's mobile app, are approved with route verification via Mapbox, and flow straight into the pay run. Carers see their projected gross pay, hours, rates and mileage in the app as they work. At the end of the period you generate a pay run and export payroll-ready data, alongside visit-based invoicing that runs off the same schedule on the billing side. The full picture is on our finance and billing features page.

And here is where we're straight with you: homecareOS prepares payroll, it doesn't file it. It is not payroll bureau software and it does not submit RTI to HMRC, issue payslips or manage tax codes. Those jobs belong to whoever operates PAYE for you, whether that's your accountant, a bureau or a payroll package, and homecareOS hands them clean, itemised, payroll-ready exports instead of a shoebox of timesheets. In practice that division of labour is exactly what most agencies want: the hard, care-specific part (which minutes, at which rate, with which mileage) solved at source, and the statutory processing left with the professionals already doing it. Payroll exports are included on every plan, free while you have up to 5 carers and then £10 per carer per month on Pro, with the office team unmetered; details are on the pricing page, and our piece on per-carer pricing explains why we meter it that way.

Frequently asked questions

What does carer payroll software actually do?

It turns what happened during the week into what each carer should be paid. That means deriving timesheets from real clock-in and clock-out times rather than the planned rota, applying the correct rate to each visit through a rate hierarchy, adding approved mileage claims, applying bank holiday overrides and holiday pay accrual, and producing a payroll-ready pay run with supporting detail. The output is a set of figures and exports your accountant, bureau or payroll package can process, with every number traceable back to a specific visit.

Does homecareOS run payroll and file RTI with HMRC?

No, and it doesn't pretend to. homecareOS prepares payroll rather than filing it: it derives timesheets from actual visit times, applies the pay waterfall, folds in approved mileage claims and generates pay runs with full financial reporting and exports. You then hand that payroll-ready data to whoever operates PAYE for you, whether that's your accountant, a payroll bureau or payroll software. RTI submissions, tax codes and payslips remain with your payroll provider. The value is upstream: the hours and rates going into payroll are right first time.

How should travel time be paid in home care?

For National Minimum Wage purposes, time a domiciliary care worker spends travelling between appointments generally counts as working time, so it must be included when checking that average hourly pay clears the legal floor. Agencies handle this in different ways: some pay a travel allowance per visit, some pay actual travel minutes, and some build travel into an enhanced hourly rate. Whichever model you use, your payroll process needs visit-level time data to prove NMW compliance, which is why deriving pay from actual clock-in and clock-out times matters so much.

What is a pay waterfall in care payroll?

A pay waterfall is a rate hierarchy where the most specific rate wins. In homecareOS it has three levels: a manual visit override sits at the top, for one-off situations like a bank holiday or an emergency callout; below that sits the carer's pay grade rate, such as Senior Carer; and at the bottom sits the carer's base hourly rate, which every carer has. For each visit the system works down the waterfall and applies the first rate it finds, so exceptional pay is handled per visit without anyone editing a spreadsheet.

How do mileage claims fit into a pay run?

Badly, in most agencies: mileage usually lives in a separate spreadsheet or paper form, gets approved late and is keyed into payroll by hand. The better pattern is to make mileage part of the same pipeline as pay. In homecareOS, carers submit mileage claims directly from the mobile app, managers approve them with route verification via Mapbox, and approved claims flow automatically into the pay run alongside visit pay. One approval step, one export, no re-keying, and mileage stops being the last thing chased on payroll day.