Predictive payroll lets you run and finalise payroll before the pay period ends. Florence pays any shift that doesn't have an approved timesheet yet using its rota times. When you approve the real timesheets, your next payroll run adds or takes off any difference.
For example, you pay staff for the whole of October, but your payroll provider needs your figures by 22 October. Your managers approve timesheets up to 21 October as normal. Florence pays the shifts from 22 to 31 October as predicted shifts, using their rota times. Your November payroll run then corrects any October shift that someone worked differently.
Before you start
To create and finalise payroll runs, and to change payroll group settings, you need the Manage Payroll permission.
To confirm payroll for a location, you need the Confirm payroll permission.
You choose predictive payroll for each payroll run, or once for a payroll group that has a payroll cycle.
How it works
You create a payroll run with Include predicted shifts ticked.
Florence pays shifts with an approved timesheet as normal.
Florence pays booked shifts in the pay period that don't have an approved timesheet using their rota times. These are your predicted shifts.
You finalise the run, even though the pay period hasn't ended.
On your next payroll run, Florence checks each predicted shift against its approved timesheet and adds or takes off any difference.
The timesheet cut-off date
If your locations confirm their own payroll before you finalise it, you also choose a Timesheets required up to date.
Every shift on or before this date needs an approved timesheet before the location can confirm payroll.
Florence pays shifts after this date as predicted shifts.
If your locations don't confirm payroll, there's no cut-off date. Florence pays every shift in the pay period without an approved timesheet as a predicted shift.
Running payroll with predicted shifts
Use this if you create your payroll runs yourself.
Go to Payroll.
Choose the Payroll group, and the From and To dates of the pay period.
Tick Include predicted shifts.
If you see Timesheets required up to, choose the cut-off date. It must fall inside the pay period.
Click Run payroll.
You can't change these settings after you create the run. To change them, delete the draft run and run payroll again.
Setting up predicted shifts for a payroll group
Use this if your payroll group has a payroll cycle, so Florence creates each run for you.
Go to Payroll and click Payroll groups.
Click the group to open it.
Tick Include predicted shifts.
In Create the run this many days before the period ends, enter a number of days.
Click Save.
For example, with an End of month cycle and 10 days, Florence creates October's draft run on 22 October. If your locations confirm their own payroll, they need approved timesheets up to 21 October, the day before Florence creates the run.
If When a run is created automatically is set to Don't automatically create runs, the field reads Require timesheets up to this many days before the period ends instead. Florence doesn't create the run for you. Shifts up to that many days before the period ends need an approved timesheet, and Florence can pay the shifts after that as predicted shifts.
Every run for the group then includes predicted shifts, whether Florence creates it automatically or you click Generate draft or Generate now. Your changes apply from the next run Florence creates. To change a draft that already exists, change the group's settings, then delete the draft and create it again.
Checking your predicted shifts
On the payroll run page:
The label Predicted shifts beyond [date] appears under the run's name, next to its status. Hover over it to see how many shifts and hours Florence is paying as predicted shifts. If the run has no cut-off date, the label says Includes predicted shifts.
The Predicted shifts tab lists every predicted shift with its Rota times, Predicted hours and Status. Click a row to open the shift.
Each predicted shift has one of three statuses:
Not yet worked: the shift hasn't happened yet.
No timesheet: the shift has happened, but the staff member hasn't submitted a timesheet.
Timesheet submitted: the staff member has submitted a timesheet, but nobody has approved it yet. Florence uses the rota times until someone approves it.
On a staff member's payroll summary, a predicted day has a clock icon next to its rota times.
To download the list, click Export, choose Export predicted shifts CSV as the format, then click Download CSV. This also works after you finalise the run, when the page may no longer show the tabs.
On the Payroll page, a label shows which runs include predicted shifts. The label stays after you finalise the run.
Confirming and finalising early
A location can confirm payroll once every shift up to the cut-off date has an approved timesheet, and its leave requests and adjustments have a decision as usual. The run page counts shifts on or before the cut-off date that haven't happened yet under Shifts still to come before the cut-off.
When you click Review payroll for a location, two extra tiles can appear next to Hours worked:
Predicted hours: the hours this run pays as predicted shifts for the location. It appears when the run includes predicted shifts.
Correction hours: the hours this run adds or takes off for shifts an earlier run already paid. This can be a minus number. It only appears when the location has corrections.
Florence saves both figures when you confirm. If they change afterwards, the location shows as changed and needs confirming again before you can finalise the run.
When every location has confirmed, you can finalise the run straight away, before the pay period ends. A run without predicted shifts still has to wait until its pay period has ended.
Once you finalise a run, it doesn't change. Florence puts any differences on your next payroll run.
If your payroll group finalises runs automatically, Florence still waits until the pay period has ended.
What happens on your next payroll run
Florence checks every predicted shift from your last run against its approved timesheet.
What happened to the shift | What your next payroll run does |
Worked to its rota times | Nothing |
Worked longer | Pays the extra hours |
Worked shorter | Takes off the hours nobody worked |
You cancelled the shift, or the staff member's booking on it | Takes off all the hours your last run paid |
You gave it to someone else | Takes the hours off the first staff member, and pays the second from their own timesheet |
You moved it to a date in another pay period | Takes the hours off the old pay period and pays the shift in its new one |
You cancelled leave the last run paid | Takes off all the leave hours your last run paid |
Still no approved timesheet | Stops anyone confirming or finalising the next run until you resolve it (see below) |
Florence does this even if your next run doesn't include predicted shifts.
The Corrections tab
Your next run lists every difference on its Corrections tab. There's one row for each pay code a shift or leave request was paid under, in the same units as your payroll export:
Pay code: the pay code, named as it is in your payroll export.
Prediction: what your last run paid.
Actual: what the approved timesheet works out to.
Difference: what this run adds or takes off. Amounts this run takes off show as a minus.
Reason: why it changed, for example Timesheet differs, Shift cancelled, Shift reassigned, Shift date changed or Leave cancelled. Hover over the icon next to Reason to see what each one means.
A shift can have more than one row. For example, if someone worked their rota hours but went into overtime, you'll see 2 hours off Basic and 2 hours on Overtime, with no change to the total.
When a shift didn't happen and Florence takes off all its hours, we call this a take-back. Click a row to open the shift.
To download the corrections, click Export, choose Export corrections CSV as the format, then click Download CSV. The CSV has the same rows, with a Pay code column.
To see one staff member's corrections, click Review payroll, then click their row in the list of staff. Their corrections appear under Prior periods, with the hours before and after the change.
Shifts from last run awaiting a timesheet
If a predicted shift from your last run still doesn't have an approved timesheet, you can't confirm or finalise your next run. The run page shows a Shifts from last run awaiting a timesheet card, and Confirm payroll stays greyed out.
The Unresolved from last run tab lists the shifts.
For each shift, either:
approve its timesheet, or
if it didn't happen, cancel the shift or the staff member's booking on it.
Cancelling leave a run has already paid
With predicted shifts you often finalise a run before the leave in it happens, so plans can change after you've paid it. If a finalised run paid approved leave that isn't going ahead, you can cancel it.
Open the leave request.
Click Cancel leave.
Click Cancel leave again to confirm.
Your next payroll run takes back the hours the earlier run paid. You can't edit leave a run has already paid. If the staff member still needs leave, cancel it and book the right leave.
You can't cancel holiday adjustments or accrued leave payouts this way.
Choosing what you see and export
Use the Period filter at the top of the payroll run page to choose what the page shows and what your exports include:
This period: shifts and leave in this run's pay period.
Corrections: differences for shifts an earlier run already paid.
Historical: anything else from before this pay period that no earlier run included, such as a timesheet someone approved late.
The filter shows All selected until you change it.
Worked example
Sunnybrook Care Home pays staff for the whole calendar month, and its managers approve timesheets up to the 21st before payroll.
The October run includes seven predicted shifts from 22 to 31 October. The home finalises it early and pays staff for the full month.
When the home creates the November run:
Julia worked her 22 October shift to its rota times, so nothing changes.
Mohammed stayed 1.5 hours late on 24 October. November pays the extra 1.5 hours.
Alice left 3 hours early on 26 October. November takes off 3 hours.
The home cancelled Emma's shift on 27 October. November takes back all the hours October paid for it.
Michael's shift on 29 October still has no approved timesheet. The home can't finalise November until a manager approves his timesheet or cancels the shift.
Things to know
Predicted shifts don't build up holiday. Accrued holiday only builds up from approved timesheets. Florence never predicts leave.
Florence ignores submitted times until someone approves them. It pays the rota times until then.
Approved timesheets count first. When working out overtime, Florence counts approved timesheets before predicted shifts. So if a staff member goes into overtime, it usually falls on their predicted shifts. If Florence takes back one of those shifts, its overtime comes off with it.
Hours can move between pay types. A correction can show, for example, 2 hours off Basic and 2 hours on Overtime, with no change to the total. The Corrections tab shows these as separate rows. That's expected.
Corrections use the current pay rate. Every line on a run uses the pay rates in place when that run starts. If a pay rate changes between runs, Florence pays the correction at the new rate.
Minus hours are normal. A staff member whose only line on a run is a take-back shows with minus hours.
Draft runs don't update on their own. If timesheets, shifts or leave change after Florence creates the draft, the run shows Out of date. Click it to see each change in the Changes since this pay run was last processed panel, then click Re-run payroll to bring the run up to date.
Every predicted shift needs a contract. If a staff member has no contract on the date of a predicted shift, Florence can't process the run. This also happens if a contract changes after Florence creates the draft. The run page lists the shifts to fix: fix each contract or cancel the shift, then re-run payroll.
Common questions
Can I switch on predicted shifts for the whole company?
You set it on each payroll run, or once on each payroll group that has a payroll cycle.
Can I change a run's settings after I've created it?
No. Delete the draft run and create it again with the settings you want.
A staff member has submitted their timesheet. Why does the predicted shift still use rota times?
Nobody has approved the timesheet yet. Florence only uses times from approved timesheets.
Why can't I confirm or finalise my payroll run?
Check the cards at the top of the run page. If Shifts from last run awaiting a timesheet shows a number, open the Unresolved from last run tab, then approve each timesheet or cancel the shift.
Why does a staff member have minus hours?
Your last run paid one of their shifts as a predicted shift, and the shift didn't happen or was shorter than its rota times. The Corrections tab shows the details.
Can Florence finalise payroll automatically before the period ends?
No. Automatic finalising still waits until the pay period has ended. To finalise early, finalise the run yourself.
Can I change leave after it's been paid?
You can cancel it, and your next run takes the hours back. You can't edit it. Cancel it and book the right leave instead.
How do I see which runs included predicted shifts?
On the Payroll page, these runs have the label Includes predicted shifts.










