How to Set Up Overtime Approvals in Singapore Attendance Software

A well-designed overtime approval process helps Singapore employers control additional working hours, prevent unauthorized overtime, maintain accurate attendance records, and ensure that approved overtime information reaches payroll correctly. Without a structured process, managers may struggle to verify extra hours, employees may dispute recorded time, and payroll teams may receive incomplete or inconsistent information.

Attendance software can simplify this process by identifying potential overtime, allowing employees to submit requests, routing approvals to managers, applying employee-specific rules, and maintaining an audit trail.

However, overtime approval workflows must reflect Singapore's employment requirements. In particular, employers should distinguish employees covered by Part 4 of the Employment Act from those whose overtime arrangements are governed primarily by their employment contracts.

1. Understand Singapore's Overtime Rules Before Configuring the Software

Before setting up overtime approvals, employers should identify which employees are covered by the overtime provisions of Singapore's Employment Act.

Part 4 of the Employment Act provides specific working-hour and overtime protections for eligible employees. It generally covers:

• Non-workmen earning a monthly basic salary of up to SGD 2,600.
• Workmen earning a monthly basic salary of up to SGD 4,500.

Managers and executives are excluded from Part 4. Employees who are not covered generally have their overtime arrangements determined by their employment contracts and applicable workplace policies.

For employees covered under Part 4, important requirements include:

• Overtime pay must generally be at least 1.5 times the hourly basic rate of pay.
• The general maximum overtime limit is 72 hours per month, subject to applicable exemptions.
• Employees should generally not work more than 12 hours a day, subject to specified exceptions and exemptions.
• Overtime pay must be made within 14 days after the end of the salary period.

Attendance software should allow employers to configure different overtime rules for different employee categories. It should not automatically apply the same statutory calculations to every employee.

Employers should review the latest Ministry of Manpower (MOM) guidance and their employment terms before configuring the system.

Reference: MOM – Hours of Work, Overtime and Rest Days

2. Create Employee Categories and Overtime Eligibility Rules

The first configuration step is to organise employees according to their overtime eligibility and employment arrangements.

A company may have office administrators, factory workers, retail assistants, warehouse employees, managers, executives, and part-time employees. Their working hours and overtime entitlements may differ.

Attendance software should allow HR administrators to create employee categories and assign suitable overtime rules.

Example employee configuration:

Employee category	Overtime configuration
Eligible workmen	Configure applicable Part 4 overtime rules
Eligible non-workmen	Configure applicable Part 4 overtime rules
Managers and executives	Follow contractual overtime arrangements
Part-time employees	Configure according to applicable statutory provisions and employment terms
Shift workers	Support shift-specific working-hour and overtime calculations
Temporary employees	Configure according to their employment arrangements and eligibility

For each employee, HR should verify:

• Employee classification.
• Basic salary.
• Normal working hours.
• Scheduled working days.
• Overtime eligibility.
• Applicable overtime rate.
• Approval manager.
• Salary period.
• Relevant employment terms.

For example, a manufacturing company may have eligible production workers who receive statutory overtime pay and managers whose additional working arrangements are governed by their contracts.

The software should keep these configurations separate to avoid incorrect calculations.

3. Configure Normal Working Hours and Shift Schedules

Overtime cannot be identified accurately unless the system knows an employee's normal working schedule.

Employers should configure daily working hours, weekly schedules, shift timings, and break periods before activating overtime calculations.

Important settings include:

• Standard start and finish times.
• Working days per week.
• Daily normal working hours.
• Weekly normal working hours.
• Meal and rest breaks.
• Rotating shift schedules.
• Overnight shifts.
• Rest days.
• Public holidays.
• Flexible working arrangements.

For example, an employee may be scheduled to work from 9:00 a.m. to 6:00 p.m., with a one-hour unpaid lunch break.

The software should recognise eight working hours rather than nine hours of attendance time.

If the employee works until 8:00 p.m., the system can identify the additional time for review. However, it should calculate payable overtime only after applying the relevant employee eligibility and working-hour rules.

Employers should also test alternative schedules, including six-day working weeks, part-time arrangements, and rotating shifts.

4. Enable Automatic Overtime Identification

Once employee schedules and overtime rules are configured, attendance software can identify potential overtime using actual clock-in and clock-out records.

The system compares recorded working hours against the employee's normal working schedule and applicable rules.

Example:

An employee is scheduled to work from 9:00 a.m. to 6:00 p.m., with a one-hour unpaid break. The employee records a clock-out time of 8:00 p.m.

Detail	Time
Scheduled start	9:00 a.m.
Scheduled finish	6:00 p.m.
Actual clock-in	9:00 a.m.
Actual clock-out	8:00 p.m.
Unpaid break	1 hour
Actual working hours	10 hours
Scheduled working hours	8 hours
Additional working time	2 hours

The software should flag the two additional hours for review.

However, additional attendance time does not automatically mean that all of it qualifies for statutory overtime. The system must consider the employee's normal hours, statutory eligibility, contractual terms, and the circumstances of the work.

Employers should check whether the software can:

• Detect additional working hours automatically.
• Separate ordinary hours from potential overtime.
• Identify overtime by employee and department.
• Apply different rules to different employee categories.
• Flag incomplete or unusual attendance records.
• Send notifications to employees and managers.

5. Set Up Employee Overtime Request Forms

A structured overtime request process helps employees communicate additional work requirements before they work beyond their normal schedules.

Attendance software should provide an employee self-service option for submitting overtime requests.

A typical overtime request form should capture:

Field	Purpose
Employee name and ID	Identifies the employee
Department	Identifies the business unit
Overtime date	Records when additional work is required
Scheduled working hours	Shows the normal shift
Requested start time	Identifies when overtime begins
Requested end time	Identifies when overtime finishes
Expected overtime duration	Shows the estimated additional hours
Reason for overtime	Explains the business requirement
Project or task	Identifies the work involved
Reporting manager	Identifies the approving authority
Supporting comments	Provides additional context

For example, a warehouse employee may request two additional hours to complete an urgent shipment.

The employee submits the request through the attendance application, and the system forwards it to the supervisor for approval.

The software should allow employees to view the request status, including pending, approved, rejected, and returned for clarification.

6. Configure Multi-Level Overtime Approval Workflows

Different organisations require different approval structures. A small business may need only one manager's approval, while a large organisation may require multiple approval levels.

Attendance software should support configurable workflows based on employee roles, departments, locations, and overtime duration.

Example approval structure:

1. Employee submits an overtime request.
2. The reporting manager reviews the reason and expected hours.
3. The department head approves requests above a defined threshold.
4. HR reviews exceptions or unusual working-hour patterns.
5. Payroll receives approved overtime information.

For example, a request for one additional hour may require only the reporting manager's approval. A request for six additional hours may require department-head and HR review.

Employers should be able to configure:

• Single-level approval.
• Multi-level approval.
• Department-specific approval.
• Location-based approval.
• Escalation for delayed approvals.
• Delegated approval during manager absence.
• Rejection and resubmission.
• Approval limits based on overtime duration.

Approval rules should be documented and communicated to employees and managers.

7. Establish Pre-Approval and Emergency Overtime Procedures

Employers should decide how employees request overtime and how managers handle urgent work requirements.

A pre-approval process helps managers control workloads, review business needs, and plan labour costs before additional work takes place.

However, businesses should also account for situations in which overtime is necessary at short notice.

A practical policy can include two workflows.

Pre-approved overtime

• Employee or manager identifies the need for additional work.
• Employee submits an overtime request.
• Manager reviews the reason and expected duration.
• Authorised manager approves the request.
• Employee completes the additional work.
• Attendance software compares approved hours with actual attendance.
• Manager verifies the final hours.

Emergency or unplanned overtime

• Employee performs additional work because of an urgent operational requirement.
• Employee or manager records the reason.
• A retrospective request is submitted as soon as practicable.
• The manager verifies actual attendance.
• HR reviews the exception where necessary.
• The approved record is sent to payroll.

Employers should not assume that an internal approval policy automatically removes an overtime payment obligation. MOM states that overtime pay applies when the employer requires an employee covered by Part 4 to work beyond normal working hours. Employees are encouraged to seek approval to avoid disputes, and employers should communicate their overtime policies clearly.

8. Configure Overtime Calculation Rules

Attendance software should calculate overtime using the appropriate employee-specific rules.

For eligible employees covered under Part 4, the statutory overtime rate is generally at least 1.5 times the hourly basic rate of pay.

The general formula is:

Overtime pay = Hourly basic rate of pay × 1.5 × Overtime hours

For monthly-rated employees, the hourly basic rate is generally calculated as:

Hourly basic rate = (12 × Monthly basic rate of pay) ÷ (52 × 44)

Example calculation:

Assume an eligible employee receives a monthly basic salary of SGD 2,200 and completes 10 qualifying overtime hours.

Calculation	Amount
Monthly basic salary	SGD 2,200
Annual basic salary	SGD 26,400
Annual normal working hours	2,288
Hourly basic rate (approximately)	SGD 11.54
Overtime multiplier	1.5
Overtime hours	10
Illustrative overtime pay	SGD 173.10

This is an illustrative calculation based on the stated assumptions. Actual payroll calculations should use the applicable statutory formula, employee classification, and current rules.

Employers should verify that attendance software can:

• Store employee basic salary information.
• Calculate the applicable hourly basic rate.
• Apply the correct overtime multiplier.
• Calculate approved overtime hours.
• Retain calculation details.
• Transfer the correct amount to payroll.

The software should also allow authorised payroll personnel to review calculations before processing.

Reference: MOM – Calculate Overtime Pay for a Monthly-Rated Employee

9. Set Up Overtime Limits and Compliance Alerts

Employers should configure alerts to help prevent excessive working hours and identify employees approaching applicable overtime limits.

For employees covered under Part 4, the general statutory limit is 72 overtime hours per month, subject to applicable exemptions.

The system should calculate accumulated overtime throughout the salary or calendar period as configured and alert managers before an employee reaches the relevant limit.

Recommended alerts include:

• Employees approaching the monthly overtime limit.
• Employee exceeding the configured overtime threshold.
• Employee approaching the daily working-hour limit.
• Unusually long shifts.
• Repeated overtime requests.
• Unapproved overtime entries.
• Missing clock-out records.
• Overtime requests exceeding departmental limits.

For example, if an eligible employee has already accumulated 65 overtime hours during a month, the system can notify HR and the reporting manager when another request is submitted.

Employers should not rely only on a warning generated at the end of the month. Alerts should be available during the scheduling and approval process.

If an employer has an applicable exemption, the software should allow authorised personnel to record the relevant approval and configure the permitted arrangement. The exemption should not be assumed or applied automatically.

10. Create Separate Workflows for Rest-Day and Public-Holiday Work

Overtime performed on an ordinary working day should be distinguished from work performed on a statutory rest day or public holiday.

These situations can involve different payment rules and approval requirements.

For employees covered under Part 4, work on a rest day has specific payment arrangements. The amount payable depends on how much work is performed and whether the work was requested by the employer or the employee.

The attendance system should therefore capture:

• Whether the date is a normal working day, rest day, or public holiday.
• Actual clock-in and clock-out times.
• The employee's designated rest-day schedule.
• Whether the work was requested by the employer or employee.
• Total hours worked.
• Approval details.
• Applicable payroll treatment.

Employers should not configure all additional hours as ordinary overtime. The system should distinguish the relevant work category so payroll can apply the correct rules.

Reference: MOM – Hours of Work, Overtime and Rest Days

11. Configure Notifications and Approval Reminders

A good approval process should prevent requests from remaining pending for long periods.

Attendance software should send automatic notifications to employees, managers, HR, and payroll users based on their responsibilities.

Employee notifications:

• Overtime request submitted successfully.
• Request approved.
• Request rejected.
• Request returned for clarification.
• Actual hours differ from approved hours.

Manager notifications:

• New overtime request received.
• Request awaiting approval.
• Employees have recorded additional working hours.
• Approved overtime has exceeded the requested duration.
• Employees are approaching a configured overtime limit.

HR and payroll notifications:

• Overtime approval is incomplete.
• Attendance records require correction.
• The monthly overtime threshold is approaching.
• Payroll export is ready.
• Approved overtime data contains validation errors.

Employers should also configure escalation reminders for requests that remain pending beyond the organisation's defined response time.

12. Connect Overtime Approvals with Payroll Software

After overtime has been verified and approved, the information should be transferred to payroll.

Manual data entry can create errors, especially when businesses process overtime for large numbers of employees.

Attendance software should support payroll integration through an API, direct connector, or structured file export.

Information to transfer includes:

• Employee ID.
• Payroll period.
• Overtime date.
• Approved overtime hours.
• Applicable overtime category.
• Hourly basic rate, where required.
• Approved overtime amount, where calculated by the attendance system.
• Approval status.
• Relevant adjustments.

The payroll system should receive only verified information according to the organisation's workflow.

Employers should test whether the integration can identify:

• Duplicate overtime entries.
• Missing employee IDs.
• Rejected requests.
• Unapproved overtime.
• Corrected attendance records.
• Changes made after the initial export.

For employees covered under Part 4, employers must ensure overtime pay is made within 14 days after the end of the salary period. The payroll workflow should therefore include deadlines and validation checks to support timely payment.

Reference: MOM – Paying Salary

13. Maintain Overtime Approval Records and Audit Trails

Overtime approval records are useful when investigating payroll discrepancies, employee complaints, or working-hour disputes.

Attendance software should maintain a complete history of requests, approvals, rejections, changes, and payroll transfers.

Important information to retain includes:

• Original overtime request.
• Requested date and duration.
• Reason for additional work.
• Actual attendance records.
• Manager's decision.
• Approval or rejection timestamp.
• Comments and supporting information.
• Changes to approved hours.
• HR verification details.
• Payroll export status.

For example, if an employee requests three hours of overtime but records only two hours of additional work, the system should preserve both the original request and the verified attendance information.

If a manager changes an overtime record, the system should identify who made the change, when it was made, and why.

Employers should also ensure that relevant employment records are retained for the periods required by MOM.

14. Generate Overtime Reports for HR and Management

Reporting helps employers understand overtime costs, identify recurring workload problems, and monitor workforce utilisation.

Attendance software should provide reports that can be filtered by employee, department, location, manager, and payroll period.

Important overtime reports include:

Report	Business purpose
Daily overtime report	Shows additional working hours by date
Monthly overtime summary	Tracks accumulated monthly overtime
Employee-wise overtime report	Identifies individual overtime patterns
Department-wise report	Compares overtime across departments
Pending approval report	Identifies requests awaiting action
Rejected request report	Tracks declined overtime requests
Rest-day work report	Separates rest-day work from ordinary overtime
Overtime cost report	Supports payroll and labour-cost analysis
Overtime exception report	Highlights unusual or unverified entries

Managers can use these reports to identify departments that repeatedly depend on overtime.

For example, if a warehouse team records high overtime every month, management can investigate staffing levels, shift planning, delivery schedules, and workload distribution.

Reports should also support export to Excel, CSV, or PDF for payroll reconciliation and management reviews.

15. Test the Overtime Approval Workflow Before Launch

Before making the system available to all employees, employers should conduct practical tests using representative workforce scenarios.

The objective is to confirm that overtime requests, approvals, attendance records, calculations, and payroll transfers work together correctly.

Recommended testing scenarios:

Test scenario	Expected system behaviour
Employee requests two hours of overtime	Request is routed to the correct manager
Manager approves a request	Approval status and timestamp are recorded
Manager rejects a request	Employee receives a rejection notification
Employee works longer than approved	System flags the difference for review
Employee works overtime without prior approval	Actual work is recorded and routed for review
Employee approaches 72 monthly overtime hours	Applicable alert is generated
Employee works on a rest day	Work is classified separately
Employee works an overnight shift	Hours are assigned to the correct shift
Payroll export is generated	Approved information transfers accurately
Manager changes an approval	Audit trail records the change

Employers should also test different employee categories to confirm that statutory overtime calculations are applied only where appropriate.

A successful test should verify both the system's calculations and its handling of exceptions.

Conclusion

Setting up overtime approvals in Singapore attendance software requires more than enabling an overtime calculation feature. Employers must configure employee eligibility, normal working hours, shift schedules, approval workflows, overtime limits, and payroll integration according to their workforce requirements.

A structured process allows employees to submit requests, managers to verify additional work, HR teams to monitor working-hour exceptions, and payroll administrators to process approved overtime accurately.

Singapore employers should pay particular attention to Part 4 of the Employment Act, including employee eligibility, the applicable overtime rate, the general monthly overtime limit, and payment deadlines. They should also distinguish ordinary overtime from work performed on rest days and public holidays.

Most importantly, an internal approval process should not be treated as a substitute for statutory payment obligations. Employers should record actual working time, investigate exceptions, and ensure that work required by the employer is handled in accordance with applicable employment requirements.

With the right configuration, attendance software can make overtime administration more transparent, reduce manual work, improve workforce planning, and support accurate payroll processing.

Map request, approval and payroll handoff for extra hours across teams. Test InnBuilt overtime settings against your company rules before rollout.