Rapid Rostering should honour the service-level "Is Sleepover / Fixed Fee" setting
M
Misha Ahuja
Description:
When a shift is created via Rapid Rostering, the service-level Is Sleepover / Fixed Fee flag is not carried through to the roster item — it's currently hardcoded to 0 regardless of the selected service's configuration. This causes the downstream timesheet calculation to bill based on actual shift duration (e.g. 0.5 hrs × rate) instead of the correct fixed 1 unit × rate for Fixed Fee/Sleepover services.
Standard rostering already reads and passes this value correctly from the selected service — Rapid Rostering is the only entry point affected.
Impact:
Over 200 incorrectly billed line items identified for St Louis Community Care so far, and any other client using Fixed Fee/Sleepover services with Rapid Rostering is potentially affected.
Requires manual identification and correction of historical timesheets until this is addressed.
Requested fix:
Update Rapid Rostering to read the selected service's Is Sleepover / Fixed Fee value (the same way standard rostering does) and pass it through when creating the roster item, so FixedFee is set correctly at creation time. No changes needed to the underlying timesheet/pricing calculation logic — it already handles FixedFee = 1 correctly.