Skip to content
English
BrioHR Website
  • There are no suggestions because the search field is empty.

Time Attendance Settings to Agree with Your IM

Part of the Time Attendance data migration series for new brioHR clients. This article covers: Settings to agree with your IM.

Audience & Scope

Audience: HR and admin teams setting up brioHR for the first time

Module: Time Attendance

Country: Malaysia, Singapore

Pre-requisites: Implementation kick-off meeting with your Implementation Manager (IM) completed; the Time Attendance migration template from your IM; Employee List loaded and verified (Profile & Dashboards)

 

This article is part of the Time Attendance data migration series. It follows the Time Attendance Data Migration Guide (PDF).

Settings to agree with your IM

Some Time Attendance settings aren't in the template, but your IM needs them to finish your setup. Decide each one below, and send your answers to your IM with your template, for example in an email or a note in the template.

Who follows what

DecideWhy it matters
Which schedule each office follows.Everyone in the office follows it unless they are given their own. The Company Data Template's working days are a good starting point.
Which employees follow a different schedule from their office, and which one.Each one needs to be assigned.
Which employees belong in each policy other than the Default.A list by department or office is usually enough, plus any individual exceptions. A policy change applies from the date the employee is reassigned.

Overtime

DecideOptions
Is overtime calculated? (per policy)On: overtime is recorded in the timesheet and the supervisor is asked to approve it. Off: no overtime is recorded at all.
How is overtime approved? (per policy; only one option)
  • Approved after it is worked (automated): brioHR sends the overtime to the supervisor after clock-out. If no one acts, it is approved automatically.
  • Pre-approved by the supervisor: the supervisor assigns overtime before it is worked. Only the lesser of the pre-approved hours and the hours actually worked is paid, and overtime that wasn't pre-approved is rejected.
  • Requested by the employee, then pre-approved: the employee requests overtime in advance, and the supervisor approves it. Needs supervisor pre-approval switched on too.
  • Submitted by the employee after it is worked: the employee submits their overtime for approval. If they don't, it is rejected when the timesheet is approved.
Overtime buffer? (per policy)Overtime only counts once it is longer than the buffer. For example, with a 30-minute buffer, 20 minutes extra is not overtime, but 40 minutes extra is 40 minutes of overtime.
Overtime email notifications? (per policy)On: supervisors get an email when overtime needs approval. Off: no emails, but approvals still appear in their Pending Actions.

Payroll (if you pay through brioHR Payroll)

DecideWhy it matters
Which pay items overtime is paid under.brioHR links each type of overtime to a default pay item for each payroll center. Your IM can show you the default mapping. Where it can be changed, only pay items marked as overtime can be chosen.
Any shift premiums or deductions: a name, the shift tag(s), whether it counts per shift or per hour, what makes an employee eligible (for example, no lateness in the month), and the pay item for each payroll center.Only work with shift-based schedules. The pay item needs to be a custom pay item with a unit of Shift or Hours, created in Payroll first.
The overtime calculation and rates in your payroll settings.These decide the amount paid for each hour of overtime. They come from your Payroll templates.

Shifts, clocking in and devices

DecideWhy it matters
Break settings for each shift: whether going over the break counts as lateness, whether unused break time counts as work, and whether breaks can only start within a set period.Change how hours worked and lateness are calculated.
How half-day leave splits each shift.New shifts split equally between the two halves unless set otherwise.
The addresses of any clock-in locations.Needed for location checks by shift location or custom location.
Any attendance device or integration: a Timetec device, API or SFTP from another system, and whether employees can mix methods (hybrid attendance).Devices and integrations need setting up with brioHR Support. Integrations can only process clock-ins up to 45 days old, and switch off facial recognition and geolocation for that policy.

🔗 Related articles

← Previous: How to Fill In the TA Policies Tab

Next: Common Time Attendance Migration Mistakes, and Sending Your Template →

Back to Time Attendance Data Migration and Verification: Start Here

 

Ownership

By: Aqilah