Does the system calculate overtime pay?
PeopleMuster records the overtime hours that pay is built from. Working hours per day come from attendance, and logged hours per project come from timesheets, both reviewed and approved. Turning those hours into pay happens in your current payroll process, and payroll is a planned PeopleMuster module. Attendance exports to CSV for the hand-over.
Overtime pay goes wrong in the hours far more often than in the arithmetic. A missed check-out or an unapproved evening block moves the figure before any rate touches it.
So the value sits in getting the hours right. Working hours come from the gap between check-in and check-out. Missing punches are fixed through requests a reviewer approves, and every fix keeps its before and after values.
Timesheets add the second view. Hours logged per project, moving from draft to submitted to approved, show which client work absorbed the extra time.
Leave types carry paid and unpaid flags as well, so the days that affect pay are marked on the type itself.
Questions have a home too. The support desk carries a payroll category, so a query about an overtime figure reaches the right person.
Where a policy separates requested extra hours from volunteered ones, capture that approval at the time. The reason on an evening block's punch request is the natural place to note it.
Export the period's attendance to CSV and hand it to whoever runs pay. Filter by department and date range first, so the file holds exactly the people and days in the run.
Related questions
Which hours count as overtime?
Whatever your policy defines. PeopleMuster gives the accurate daily working hours and project hours to apply it to.
Can hours be handed to a payroll provider?
Yes. Attendance exports to CSV with dates, working hours and late minutes, filtered to the pay period.
Is payroll coming to PeopleMuster?
Payroll is a planned module. Ask us for the current plan on a call.