How Can Singapore Employers Connect Attendance and Overtime to Payroll?
How Can Singapore Employers Connect Attendance and Overtime to Payroll?
Introduction
Connecting attendance and overtime data to payroll is an important step towards improving payroll accuracy and reducing administrative work for Singapore employers. Businesses that manage employees across offices, retail outlets, factories, construction sites, warehouses and field locations often need to consolidate working hours, shift records, overtime approvals and leave information before calculating salaries.
When attendance and payroll systems operate separately, HR and payroll teams may need to transfer information manually, check timesheets, calculate overtime and resolve discrepancies. This can lead to incorrect salary calculations, missed overtime payments, duplicate entries and delays in payroll processing.
Integrating attendance software with payroll allows approved working hours, overtime records, shift details and relevant absence information to flow into the payroll system. Payroll teams can then review the imported data, apply the appropriate salary rules and generate accurate payroll reports and payslips.
However, integration alone does not guarantee compliance. Employers must configure the system according to Singapore's Employment Act, applicable overtime provisions, contractual arrangements and CPF requirements.
This article explains how Singapore employers can connect attendance and overtime to payroll, the features they should evaluate and the checks they should complete before processing salaries.

1. Understand How Attendance Data Affects Payroll
Before integrating attendance software with payroll, employers should identify which attendance records affect employee earnings and deductions.
Attendance information can influence several payroll components, including:
- Regular working hours.
- Overtime hours.
- Late arrivals.
- Early departures.
- Unauthorised absences.
- Approved unpaid leave.
- Shift allowances.
- Rest-day work.
- Public-holiday work.
- Additional working hours for hourly employees.
Not every attendance event should automatically change an employee's salary. For example, a late check-in may require a manager's review before any deduction is considered. Similarly, an employee staying beyond scheduled working hours does not necessarily mean that the additional time should automatically be classified as approved overtime.
Employers should establish clear rules for identifying payable working time and the attendance information that must be transferred to payroll.
Practical example: A retail employee is scheduled to work from 9:00 a.m. to 6:00 p.m. but checks out at 7:00 p.m. The attendance system records an additional hour. Before payroll processes it as overtime, the system should check whether the employee actually performed work, whether the time qualifies under the applicable employment terms and whether the required approval has been obtained.
2. Choose Compatible Attendance and Payroll Systems
The first technical step is to confirm that the attendance and payroll systems can exchange information reliably.
Employers should assess whether the software supports:
- Direct attendance-to-payroll integration.
- API-based data exchange.
- Secure file imports and exports.
- Automated scheduled synchronisation.
- Employee ID matching.
- Multiple salary periods.
- Multiple business locations.
- Different employee categories.
- Error notifications and failed-record reports.
Direct integration can reduce manual work, but it should not be selected solely because a vendor advertises an integration feature. Employers should understand exactly which records are transferred and whether the receiving payroll system can interpret them correctly.
For example, an attendance system may record 9.5 hours of presence, while payroll needs approved working hours after excluding unpaid meal breaks. The integration should transfer the correct payroll-relevant information rather than simply importing the total time between check-in and check-out.
What to test: Ask the vendors to demonstrate a complete attendance-to-payroll data transfer using sample employee records. Check whether employee IDs, work dates, shift information, approved hours and overtime records are mapped correctly.
3. Create Consistent Employee Records Across Both Systems
Accurate employee identification is essential for successful integration.
Attendance and payroll systems must use consistent employee references so that working hours and overtime records are assigned to the correct employee.
Before enabling integration, compare the employee information in both systems.
Important details include:
- Employee ID.
- Full name.
- Employment status.
- Department.
- Job designation.
- Work location.
- Employment commencement date.
- Termination date, where applicable.
- Employment category.
- Basic salary or hourly rate.
- Applicable working schedule.
Where an employee has different identification numbers in the two systems, configure a reliable employee mapping process.
For example, an attendance system may identify an employee using a biometric device number, while payroll uses an internal employee ID. The integration should map both references to the same employee record.
Employers should also ensure that employees who have resigned, transferred or changed employment arrangements are updated in both systems.
Practical tip: Maintain one authoritative employee master record, usually in the HR or payroll system, and establish a controlled process for synchronising employee changes to attendance software.
4. Configure Working Schedules and Shift Rules
Attendance data becomes useful for payroll only when the system understands each employee's expected working schedule.
Singapore businesses may have employees working under different arrangements, including:
- Standard office schedules.
- Five-day working weeks.
- Six-day working weeks.
- Rotating shifts.
- Overnight shifts.
- Split shifts.
- Flexible working arrangements.
- Part-time schedules.
- Weekend and public-holiday schedules.
The attendance system should support these arrangements and compare actual attendance against the employee's assigned schedule.
For example, a factory employee may work from 10:00 p.m. to 6:00 a.m., while an office employee works from 9:00 a.m. to 6:00 p.m. The system must recognise the correct shift dates and working periods.
Overnight shifts require particular attention because a single shift may cross midnight. The system should not incorrectly split working hours, assign them to the wrong payroll period or generate duplicate overtime records.
Employers should also configure meal breaks and other non-working intervals accurately.
What to test: Create sample schedules for day shifts, night shifts, rotating shifts and part-time employees. Confirm that the system calculates working time correctly and assigns each shift to the intended payroll period.
5. Establish Clear Rules for Calculating Working Hours
Employers should define how attendance records are converted into payable working hours.
The system should distinguish between:
- Scheduled working hours.
- Actual attendance time.
- Paid working hours.
- Unpaid break time.
- Approved overtime.
- Unauthorised additional attendance.
- Paid leave.
- Unpaid leave.
For example, an employee may check in at 8:45 a.m. and check out at 6:15 p.m. If the employee has a one-hour unpaid meal break, the system should calculate the relevant working time after applying the configured break rules.
Employers should also decide how to handle:
- Missing check-ins.
- Missing check-outs.
- Duplicate attendance punches.
- Forgotten break records.
- Device or network failures.
- Employees working at different locations.
- Approved manual attendance corrections.
The rules should be consistent and communicated to employees and managers.
Important: Attendance software should not automatically deduct salary for every late arrival or missing punch. Payroll deductions must be reviewed against the applicable employment terms and Singapore's legal requirements.
6. Configure Overtime Rules According to Singapore Employment Requirements
Overtime calculations require particular care because Singapore's statutory overtime provisions do not apply identically to every employee.
Under Part 4 of the Employment Act, overtime provisions generally apply to:
- Workmen earning a monthly basic salary of S$4,500 or less.
- Non-workmen earning a monthly basic salary of S$2,600 or less.
Managers and executives are not covered by Part 4. Employees outside Part 4 may still have overtime or additional-hours entitlements under their employment contracts, collective agreements or company policies.
For employees covered by Part 4, overtime generally refers to work performed beyond normal hours of work, excluding breaks.
For common working arrangements, normal contractual hours are generally limited to:
- Up to 9 hours per day or 44 hours per week for employees working five days or fewer per week.
- Up to 8 hours per day or 44 hours per week for employees working more than five days per week.
Other arrangements, including qualifying shift arrangements, have specific rules.
The attendance and payroll systems should therefore support different overtime configurations rather than applying one universal rule to all employees.
For eligible employees, the statutory overtime rate is at least 1.5 times the hourly basic rate of pay.
The system should be configured to identify:
- Employee eligibility for statutory overtime.
- Normal working hours.
- Approved overtime hours.
- Applicable hourly basic rate.
- Statutory or contractual overtime multiplier.
- Applicable payment period.
- Relevant rest-day or public-holiday arrangements.
What to test: Configure different employee categories and verify that statutory overtime rules are applied only where appropriate. Confirm that contractual overtime arrangements for other employees are handled separately.
7. Automate Overtime Hour Calculations
Once the overtime rules are configured, attendance data can help identify potential overtime hours.
A useful system should compare actual approved working time with the employee's normal working schedule and calculate additional hours according to the employer's configured rules.
Important features include:
- Automatic overtime identification.
- Overtime calculation by day.
- Weekly overtime summaries.
- Monthly overtime totals.
- Different overtime rates.
- Separate rest-day and public-holiday work records.
- Overtime approval status.
- Overtime payment period tracking.
For employees covered by Part 4, employers should also monitor the statutory limits.
The general maximum is 12 hours of work per day, subject to the applicable exceptions and exemption arrangements. Overtime is generally limited to 72 hours per month, with certain exemptions available under MOM rules.
The system should provide alerts when recorded hours approach or exceed applicable limits.
Example: An eligible employee has worked 44 normal hours in a week and completes an additional four approved hours. The system should identify the additional hours and calculate the applicable overtime payment according to the employee's basic hourly rate and statutory requirements.
It should also retain the underlying attendance and approval records supporting the calculation.
8. Create an Overtime Approval Workflow
Automatic overtime detection should not mean automatic overtime payment without appropriate verification.
Employers should establish an approval process that confirms whether the additional time represents actual work and whether it should be paid under the applicable rules.
A practical workflow may include:
- Employee or supervisor records the overtime request.
- Manager reviews the reason for additional working hours.
- Authorised manager approves or records the work performed.
- Attendance software records the approved overtime hours.
- Approved data is transferred to payroll.
- Payroll reviews the calculated amount.
- The payroll manager approves the final payroll.
The system should retain the approval history, including the employee, manager, date, hours and reason.
Employers should avoid workflows that automatically reject payment for work merely because prior approval was not obtained. Internal approval policies must be administered consistently with applicable legal obligations and the actual work performed.
What to test: Submit a sample overtime request, approve it as a manager and verify that the approved hours flow into payroll. Also test rejected, amended and retrospectively recorded overtime entries.
9. Connect Overtime Rates With Employee Salary Information
Overtime calculations depend on the employee's applicable basic rate of pay. Attendance software should therefore receive the necessary salary information from payroll or HR.
For a monthly-rated employee covered by Part 4, the hourly basic rate is calculated using:
Hourly basic rate = (12 × Monthly basic rate of pay) ÷ (52 × 44)
For an eligible employee, statutory overtime pay is calculated using:
Overtime pay = Hourly basic rate × 1.5 × Overtime hours
The statutory overtime calculation uses the basic rate of pay, not the employee's gross salary. Allowances, bonuses and other payments should not automatically be included in the basic rate calculation.
Example:
Assume an eligible monthly-rated employee has a monthly basic salary of S$2,600 and completes 10 hours of approved overtime.
Hourly basic rate:
(12 × S$2,600) ÷ (52 × 44) = S$13.64.
Overtime pay:
S$13.64 × 1.5 × 10 = S$204.60.
The software should use the applicable calculation method and rounding rules when processing the payment.
For other employee categories, the system should apply the relevant contractual or statutory arrangement rather than assuming that this formula applies universally.
What to test: Change an employee's basic salary in the payroll system and verify that the updated rate is reflected in subsequent overtime calculations. Check whether historical payroll records retain the original applicable rate.
10. Handle Rest-Day and Public-Holiday Work Separately
Work performed on rest days and public holidays should not be treated as ordinary overtime without checking the applicable rules.
Under the Employment Act, eligible employees may receive different payments depending on:
- Whether work was performed on a rest day.
- Whether the employer or employee requested the work.
- The number of hours worked.
- Whether work continued beyond normal daily working hours.
- Whether the day was a public holiday.
The attendance system should identify these events separately and transfer the relevant details to payroll.
Useful fields include:
- Date of work.
- Rest-day or public-holiday classification.
- Hours worked.
- Normal daily working hours.
- Whether the employer or employee requested the work, where relevant.
- Approved additional hours.
- Applicable payment category.
For example, an employee who works on a scheduled rest day may be entitled to a different payment depending on how many hours were worked and who requested the work. Any additional work beyond normal daily hours may also attract overtime payment under the applicable rules.
What to test: Create separate test records for normal-day overtime, rest-day work and public-holiday work. Confirm that the payroll system applies the correct payment categories and does not duplicate compensation.
11. Transfer Approved Attendance and Overtime Data to Payroll
After attendance records have been reviewed and overtime has been approved, the information can be transferred to payroll.
Employers should define which fields must be included in the integration.
| Attendance information | Payroll purpose |
|---|---|
| Employee ID | Match the correct employee |
| Salary period | Identify the relevant payroll run |
| Working dates | Validate attendance periods |
| Regular working hours | Calculate hourly or time-based pay |
| Approved overtime hours | Calculate overtime earnings |
| Overtime category | Apply the correct rate |
| Rest-day work | Calculate applicable rest-day payment |
| Public-holiday work | Calculate applicable public-holiday payment |
| Unpaid leave | Support approved salary adjustments |
| Shift information | Calculate applicable shift payments |
| Approval status | Prevent unapproved records from being processed |
| Adjustment history | Maintain an audit trail |
The integration should transfer only the necessary information and preserve the original records for verification.
Employers should also establish how the system handles failed synchronisation, incomplete records and changes made after the initial transfer.
Practical tip: Generate a pre-payroll attendance export and compare its employee count and total hours with the payroll import report before approving the data transfer.
12. Configure Payroll Treatment for Attendance-Related Payments
Once attendance data reaches payroll, the system must map each approved record to the correct earnings or deduction component.
Possible payroll components include:
- Basic salary.
- Overtime payment.
- Rest-day payment.
- Public-holiday payment.
- Shift allowance.
- Attendance allowance.
- Unpaid leave deduction.
- Approved absence-related adjustment.
Each component should have a clear name, calculation rule and statutory treatment.
Employers should avoid mapping all additional working hours into one generic earning category. Different payments may have different legal, contractual, tax and CPF implications.
For example, overtime pay is generally treated as wages for CPF purposes. Its classification as Ordinary Wages or Additional Wages depends on the calendar month in which the overtime was performed and when the payment is contractually payable.
CPF Board guidance requires overtime pay to be apportioned to the calendar month in which the overtime was performed before classification. A payment is generally Ordinary Wages for a month when it relates to employment in that month and is payable by the 14th of the following month. Otherwise, it is Additional Wages.
Payroll teams should therefore avoid automatically classifying every overtime payment as Ordinary Wages simply because it appears in the monthly payroll run.
What to test: Process overtime performed in one month but paid in the following month. Verify that the payroll system applies the appropriate CPF wage classification based on the relevant dates and CPF rules.
13. Connect Leave and Absence Information to Payroll
Attendance integration should also account for approved leave and absence records.
Different types of leave may have different salary implications. For example, approved paid annual leave generally does not create the same salary adjustment as approved unpaid leave.
The system should distinguish between:
- Paid annual leave.
- Paid sick leave.
- Hospitalisation leave.
- Approved unpaid leave.
- Unauthorised absence.
- Public holidays.
- Other approved leave arrangements.
Only the relevant approved information should be transferred to payroll.
For example, if an employee takes two days of approved unpaid leave, payroll may need to calculate an appropriate salary adjustment based on the applicable rules and employment arrangement.
However, the system should not automatically deduct salary for every absence record. HR or payroll teams should verify the leave category, approval and applicable calculation method first.
What to test: Import approved paid leave and unpaid leave records into payroll. Confirm that the system treats each category correctly and that attendance records are not counted twice.
14. Set Payroll Cut-Off Dates and Synchronisation Schedules
A successful integration requires clear payroll cut-off dates.
If attendance information continues changing after payroll calculations begin, payroll teams may receive incomplete or inconsistent data.
Employers should establish a monthly schedule covering:
- Attendance cut-off date.
- Overtime submission deadline.
- Manager approval deadline.
- HR verification deadline.
- Attendance-to-payroll synchronisation date.
- Payroll review date.
- Salary payment date.
- Payslip release date.
For example, a company may close attendance records on the last calendar day of the month, require managers to approve overtime within the next two working days and transfer the final approved records to payroll before salary calculations begin.
The schedule should also allow for off-cycle payments and overtime that must be processed separately.
Under the Employment Act, salary is generally payable within seven days after the end of the salary period. Overtime pay for employees covered by the relevant provisions must be paid within 14 days after the end of the salary period.
The integration and approval workflow should support these deadlines rather than create delays.
What to test: Run a simulated monthly payroll cycle and verify that attendance closure, overtime approvals, data transfer and payroll processing can be completed within the required payment timelines.
15. Reconcile Attendance Records With Payroll Results
Before approving payroll, employers should reconcile the attendance information with the payroll results.
This helps identify missing records, duplicate entries, incorrect overtime calculations and unapproved adjustments.
Important reconciliation checks include:
- Total scheduled hours versus actual working hours.
- Approved overtime versus overtime imported into payroll.
- Overtime hours versus overtime earnings.
- Rest-day records versus rest-day payments.
- Public-holiday records versus public-holiday payments.
- Approved unpaid leave versus salary deductions.
- Employee attendance count versus payroll employee count.
- Payroll earnings versus generated payslips.
For example, if attendance software shows 15 approved overtime hours for an employee but payroll includes only 10 hours, the payroll team should investigate the difference before finalising the salary.
A reconciliation report should identify the employee, affected date, attendance record, approval status, payroll amount and reason for any adjustment.
16. Maintain Audit Trails and Payroll Approval Controls
Attendance and overtime data can affect employee earnings, so employers should maintain a clear record of changes and approvals.
Useful audit features include:
- Original check-in and check-out records.
- Manual attendance corrections.
- Overtime requests and approvals.
- Manager comments.
- Changes to working schedules.
- Changes to overtime rates.
- Payroll import history.
- Payroll adjustments.
- Payslip revisions.
- User activity logs.
Employers should also separate responsibilities where practical.
For example:
- Employees submit attendance corrections.
- Supervisors verify working hours.
- Managers approve overtime.
- HR reviews employees and leaves information.
- Payroll validates calculations.
- Finance authorises salary payments.
This structure reduces the risk of unauthorised changes and makes it easier to investigate employee queries.
Singapore employers covered by the Employment Act must also maintain the prescribed employment and salary records. These include working hours, meal and tea breaks, leave taken, overtime hours and overtime pay.
For covered employees, the general retention requirements are the latest two years of records for current employees and the last two years of records for former employees, retained for one year after they leave.
What to test: Change an attendance record after manager approval and verify that the system records the user, timestamp, original value, revised value and reason for the change.
17. Protect Employee Attendance and Payroll Information
Attendance and payroll integration involves personal and employment information. Employers should assess the security controls of both systems and the data exchanged between them.
Important safeguards include:
- Role-based access permissions.
- Secure API connections.
- Encryption during data transfer.
- Individual user accounts.
- Multi-factor authentication where available.
- Access logs.
- Restricted payroll exports.
- Secure data backups.
- Controlled access to employee records.
- Defined retention and deletion procedures.
Not every attendance user should have access to salary information. Similarly, payroll administrators may need access to approved working hours without requiring unrestricted access to all location or biometric data.
Employers should collect and transfer only information necessary for the intended payroll and employment purposes.
Where attendance systems use facial recognition, fingerprints or location tracking, employers should separately assess the applicable data protection requirements and the necessity of collecting that information.
The Personal Data Protection Act (PDPA) requires organisations to comply with relevant obligations concerning notification, purpose, protection, retention, access and overseas transfers.
What to test: Ask vendors to demonstrate how attendance and payroll data are encrypted, who can access the integration and how access and changes are logged.
Conclusion
Connecting attendance and overtime to payroll helps Singapore employers improve payroll accuracy, reduce manual work and manage employee working hours more effectively. A successful integration should transfer verified attendance records, approved overtime hours, shift information and relevant leave data into payroll using consistent employee records and clearly defined calculation rules.
Employers should pay particular attention to Singapore's overtime requirements. Part 4 of the Employment Act applies only to eligible employees, while other employees may have overtime entitlements under their employment contracts or company policies. Rest-day work, public-holiday work and CPF treatment of overtime payments also require separate consideration.
Before implementation, businesses should test the complete process, including attendance capture, overtime approval, payroll integration, calculation, reconciliation and payslip generation. They should also establish payroll cut-off dates, retain required employment records and protect employee information.
With the right integration and approval controls, Singapore employers can create a more efficient payroll process while maintaining transparency, accuracy and compliance.
Trace approved working time and overtime from attendance records to the payroll register. Ask InnBuilt to demonstrate the handoff for a Singapore shift team.