How Can Thailand Employers Track Annual Leave Requests and Balances?
How Can Thailand Employers Track Annual Leave Requests and Balances?
Introduction
Managing annual leave is an important responsibility for HR teams in Thailand. Employers need to ensure that employees receive their entitled leave, managers can plan staffing around absences and payroll teams have accurate information about leave taken and remaining balances.
Tracking annual leave manually through spreadsheets, paper forms or email approvals can become difficult as a business grows. HR teams may struggle to identify employees with outstanding requests, calculate remaining entitlements, monitor carry-forward days and resolve discrepancies between approved leave and payroll records.
A leave management system can simplify these activities by providing a centralised record of employee entitlements, applications, approvals and leave balances. Employees can submit requests through a self-service portal, managers can review applications and HR can monitor leave utilisation across departments and locations.
For Thailand employers, however, the system must reflect the country's labour requirements and the organisation's own leave policies. The Labour Protection Act B.E. 2541 (1998), particularly Section 30, establishes the minimum annual holiday entitlement and provides rules concerning the accumulation and postponement of unused annual leave.
This article explains how Thailand employers can track annual leave requests and balances, configure leave policies, reduce administrative errors and improve workforce planning.

1. Understand Thailand's Annual Leave Requirements
Before implementing an annual leave tracking process, employers should understand the statutory minimum entitlement.
Under Section 30 of Thailand's Labour Protection Act B.E. 2541 (1998):
- An employee who has worked continuously for one year is entitled to at least six working days of annual holidays per year.
- Employers may provide more than six working days in subsequent years.
- The employer must fix annual holidays in advance or arrange them in agreement with the employee.
- Employers and employees may agree in advance to accumulate and postpone unused annual holidays for inclusion in following years.
- Employers may provide annual holidays on a pro-rata basis to employees who have not completed one year of service.
These provisions establish a minimum standard. A company can provide more generous annual leave benefits through its employment contracts, work rules or internal policies.
For example, an employer may offer 10 working days of annual leave to employees after completing one year of service and increase the entitlement according to completed years of employment.
The leave management system should reflect both statutory requirements and the employer's approved benefits policy. It should not automatically assume that every employee receives exactly six days or that all unused days expire at the end of the year.
Official reference: Thailand Ministry of Labour – Labour Protection Act B.E. 2541.
2. Create a Clear Annual Leave Policy
A clear annual leave policy provides the foundation for accurate leave tracking.
Employers should explain how employees earn annual leave, when they can use it, how requests are approved and what happens to unused balances.
The policy should cover:
- Annual leave entitlement by employee category.
- Eligibility based on length of service.
- Pro-rata entitlement for employees who have not completed one year.
- Leave-year definition.
- Application procedures.
- Minimum notice periods.
- Approval responsibilities.
- Rules for cancelling or changing approved leave.
- Carry-forward arrangements.
- Treatment of unused leave.
- Leave balance adjustments.
- Procedures during resignation or termination.
For example, a company may define its leave year as January to December and provide employees with 10 working days of annual leave after one year of service. Another company may use an employee-specific anniversary year.
Both approaches require clear communication and consistent system configuration.
Employers with 10 or more employees should also ensure that their work rules comply with Section 108 of the Labour Protection Act. These rules must be in Thai and include holidays, leave and the rules for taking leave, among other required subjects.
A written policy reduces misunderstandings and gives HR teams a consistent basis for handling applications.
3. Maintain Accurate Employee Leave Records
Accurate employee information is essential for calculating annual leave entitlement.
The HR system should maintain a central employee record containing the information needed to determine leave eligibility and balances.
Important fields include:
| Employee information | Purpose |
|---|---|
| Employee ID | Identifies the employee's leave account |
| Employee name | Connects leave records with the correct person |
| Date of joining | Determines service length and eligibility |
| Employment status | Identifies active, inactive or separated employees |
| Department | Supports departmental leave reporting |
| Job location | Helps manage location-specific leave administration |
| Employment category | Connects the employee with the correct leave policy |
| Leave-year setting | Determines the period for balance calculations |
| Annual leave entitlement | Defines the employee's approved annual allowance |
| Carry-forward balance | Tracks eligible unused leave from previous periods |
| Leave history | Records previous applications and approved absences |
HR should update these records whenever an employee joins, transfers departments, changes employment category or receives an approved change to their leave entitlement.
A centralised employee record helps prevent different departments from maintaining conflicting leave balances.
4. Configure Annual Leave Entitlements by Employee Category
Not all employees necessarily receive the same annual leave benefits.
Employers may offer different entitlements according to service length, job grade, employment terms or company policy, provided the applicable statutory minimums are respected.
For example:
| Employee category | Illustrative annual entitlement |
|---|---|
| Employees after one year of service | 6 working days |
| Employees with 2–4 years of service | 8 working days |
| Employees with 5–9 years of service | 10 working days |
| Employees with 10 or more years of service | 12 working days |
These figures are illustrative company-policy examples, not statutory entitlement levels for each service category.
A leave management system should allow HR administrators to configure different entitlement rules without manually updating every employee account.
Useful configuration options include:
- Entitlement based on service length.
- Different annual allowances by employee group.
- Effective dates for policy changes.
- Pro-rata calculations.
- Different leave-year arrangements.
- Manual adjustments with approval.
- Historical entitlement records.
The system should also preserve the reason for any manual entitlement change so that HR can explain how a particular balance was calculated.
5. Calculate Pro-Rata Annual Leave for Eligible Employees
Employees who have not completed one year of service may receive annual leave on a pro-rata basis under Section 30. Employers should define a consistent calculation method in their policy.
For example, suppose a company provides 12 working days of annual leave per year under its policy. An eligible employee who has completed six months of service may receive a pro-rata entitlement.
The employee would receive six working days under this illustrative monthly pro-rata method.
The employer must define how it handles partial months, rounding, eligibility dates and any policy-specific conditions. Section 30 permits pro-rata annual leave for employees who have not completed one year; it does not prescribe one universal monthly calculation formula for every employer.
The software should therefore support configurable calculations rather than imposing an inflexible formula.
HR should test the calculation using different joining dates to confirm that employees receive the correct entitlement under the company's policy.
6. Allow Employees to Submit Annual Leave Requests Online
A self-service leave application process can reduce the administrative workload for HR teams.
Instead of completing paper forms or sending separate emails, employees can submit annual leave requests through a web portal or mobile application.
A useful leave request form should capture:
- Employee identification.
- Leave type.
- Start date.
- End date.
- Number of working days requested.
- Reason for leave, if required by policy.
- Supporting documents, where appropriate.
- Contact details during absence, if needed.
- Handover information for important responsibilities.
The system should calculate the number of working days requested based on the employee's work schedule and applicable holiday calendar.
For example, an employee requesting leave from Monday to Friday should not automatically be charged for a weekly rest day or a company holiday falling within that period.
Once the employee submits the application, the system should provide a confirmation and display its status.
Typical statuses include:
- Draft.
- Submitted.
- Pending approval.
- Approved.
- Rejected.
- Cancelled.
- Withdrawn.
A clear status system helps employees understand whether they can make personal arrangements or still need to wait for approval.
7. Automate the Annual Leave Approval Workflow
An effective leave management system should route applications to the correct approver.
For example, a company may require the employee's immediate supervisor to review the request before HR performs a final policy check.
The approval workflow may include:
- Employee submits an annual leave request.
- The system checks the available balance.
- The request is sent to the assigned manager.
- The manager reviews staffing requirements.
- The manager approves or rejects the application.
- HR receives the approved record where further review is required.
- The employee receives a notification.
- The approved leave is added to the employee's leave history.
Businesses with multiple departments or branches may need different approval structures.
For example, a manufacturing employee's request may go to a production supervisor, while a finance employee's application may require approval from a department head.
The system should support delegated approval when managers are absent. It should also retain the approval history, including the person who made the decision and the date of approval.
Automated workflows reduce delays and prevent applications from remaining unnoticed in email inboxes.
8. Check Available Leave Balances Before Approval
One of the most useful features of leave management software is the ability to display an employee's available balance when a request is submitted.
The system can compare the requested working days with the employee's available entitlement.
For example:
| Annual leave calculation | Working days |
|---|---|
| Annual entitlement | 12 |
| Eligible carry-forward | 2 |
| Total available | 14 |
| Leave already taken | 4 |
| Pending approved deduction or reserved leave | 1 |
| Available balance before new request | 9 |
| New request | 5 |
| Balance after approval | 4 |
The system should clearly distinguish approved leave from pending applications.
A pending request should not necessarily be treated as a final leave deduction. However, employers may choose to reserve the requested days temporarily to prevent employees from submitting overlapping applications that exceed their available balance.
The system should also identify cases where an employee requests more leave than is currently available.
Depending on company policy, the application may be blocked, sent for special approval or allowed as an advance leave request.
9. Track Carry-Forward Annual Leave
Thailand's Section 30 allows employers and employees to agree in advance to accumulate and postpone unused annual holidays for inclusion in subsequent years.
This means employers should define their carry-forward arrangements clearly rather than assuming that unused annual leave automatically expires or automatically carries over.
A company policy should explain:
- Whether unused leave can be carried forward.
- The maximum number of days that may be carried forward.
- Whether carried-forward days have an expiry date.
- The period within which employees must use them.
- Whether manager approval is required.
- How carried-forward leave is treated when employment ends.
For example, a company may allow employees to carry forward up to five unused working days into the following leave year, subject to an advance agreement and a requirement to use those days by a specified date.
The leave management system should maintain separate records for current-year entitlement and carried-forward entitlement.
An example balance may look like this:
| Leave balance category | Days |
|---|---|
| Current-year entitlement | 12 |
| Eligible carry-forward | 3 |
| Total available | 15 |
| Current-year leave taken | 4 |
| Carry-forward leave taken | 1 |
| Remaining balance | 10 |
Separate tracking helps HR determine which leave days should be used first and which balances may be approaching a policy deadline.
10. Configure Leave-Year Rules and Balance Reset Dates
Annual leave balances need to be calculated consistently across the organisation.
Employers may use a calendar-year system or an employee-specific anniversary system, depending on their policy.
Calendar-year method: Employees receive their annual entitlement for a defined period, such as 1 January to 31 December.
Anniversary-year method: Employees receive their entitlement according to their employment anniversary or another defined service period.
The chosen method should be documented and applied consistently.
A leave management system should support:
- Defined leave-year start and end dates.
- Employee-specific entitlement periods where applicable.
- Automated entitlement allocation.
- Carry-forward calculations.
- Balance adjustments.
- Historical leave-year records.
- Effective dates for policy changes.
Employers should avoid resetting balances without first checking eligible carry-forward arrangements and any outstanding approved adjustments.
A year-end review should confirm that the system has correctly transferred eligible unused leave and closed the previous leave period.
11. Account for Weekly Rest Days and Traditional Holidays
Annual leave should be calculated using the employee's applicable working schedule.
Thailand's Labour Protection Act distinguishes between annual holidays, weekly holidays and traditional holidays. Section 29 requires employers to announce at least 13 traditional holidays per year, including National Labour Day, subject to the Act's provisions.
A leave management system should maintain the relevant holiday calendar and employee work schedules so that non-working days are not incorrectly deducted from annual leave.
For example, if an employee requests leave from Monday through Friday and Saturday and Sunday are the employee's weekly rest days, the system should normally deduct only the five scheduled working days, assuming there are no other applicable holidays or schedule variations.
For employees working rotating shifts or different weekly schedules, the system should calculate leave according to their actual scheduled working days.
Employers should also check how substitute traditional holidays are configured when a traditional holiday falls on an employee's weekly rest day.
Incorrect holiday-calendar settings can lead to inaccurate balances and disputes over leave deductions.
12. Monitor Pending, Approved and Cancelled Requests
HR teams need visibility into all stages of the leave application process.
A centralised dashboard can show which requests are waiting for approval, which have been approved and which have been cancelled.
Useful dashboard categories include:
| Dashboard category | What HR can monitor |
|---|---|
| Pending requests | Applications awaiting manager or HR approval |
| Approved requests | Confirmed future and historical leave |
| Rejected requests | Applications declined with recorded reasons |
| Cancelled requests | Approved leave subsequently cancelled |
| Withdrawn requests | Applications withdrawn by employees |
| Overlapping requests | Multiple employees requesting the same dates |
| Low leave balances | Employees with limited remaining entitlement |
| Carry-forward balances | Unused days transferred from previous periods |
This visibility helps HR follow up on delayed approvals and coordinate staffing before absences begin.
Managers should also receive reminders when applications remain pending beyond the company's target approval period.
13. Identify Overlapping Leave Requests and Staffing Gaps
Multiple employees may request annual leave for the same dates, particularly during holiday periods, school vacations or major festivals.
If several employees from one department are absent simultaneously, the organisation may experience staffing shortages.
A leave management system can help managers identify these conflicts before approving requests.
Useful features include:
- Team leave calendars.
- Department-level absence summaries.
- Minimum staffing indicators.
- Overlapping leave alerts.
- Critical-role coverage checks.
- Branch and location filters.
- Shared calendar views.
For example, a customer support department may need at least eight employees available each working day. If five employees have already received approval for a particular date, the manager can review the operational impact before approving additional requests.
Employers should apply approval criteria consistently and transparently. A system should support fair decision-making rather than automatically rejecting leave simply because other employees have already applied.
14. Give Employees Access to Their Leave Balances
Employee self-service is an important part of modern leave administration.
Employees should be able to view their current annual leave balance without contacting HR every time they want to plan a holiday.
A self-service portal may display:
- Total annual leave entitlement.
- Leave already taken.
- Approved upcoming leave.
- Pending applications.
- Remaining available balance.
- Eligible carry-forward days.
- Leave history.
- Applicable policy information.
For example, an employee may see that they have 12 working days of annual leave, have taken four days and have two days of approved future leave.
The system should show the resulting available balance clearly.
Employees should also be able to download or view their application history and receive notifications when requests are approved, rejected or changed.
Transparent balance information reduces repeated HR enquiries and helps employees plan absences more responsibly.
15. Integrate Annual Leave With Payroll Processing
Annual leave records can affect payroll administration, particularly when employees take paid leave, have adjustments to their balances or leave the organisation.
Section 56 of the Labour Protection Act provides for wages equivalent to wages for a working day for annual holidays. Payroll teams should therefore ensure that approved annual leave is handled correctly under the employee's applicable pay arrangements.
A leave management system should transfer approved leave information to payroll without requiring manual re-entry.
Useful payroll integration data includes:
- Employee ID.
- Leave type.
- Approved leave dates.
- Number of working days taken.
- Paid or unpaid classification, where relevant.
- Leave adjustments.
- Cancellation details.
- Relevant termination information.
The integration should distinguish annual leave from sick leave, necessary business leave, maternity leave and other leave categories.
For example, if an employee takes three approved annual leave days during a payroll period, the payroll system should receive the correct approved leave record and avoid treating those days as unauthorised absence.
HR and payroll teams should reconcile leave records before each payroll cut-off.
16. Manage Annual Leave During Resignation and Termination
Employee departures require careful review of outstanding annual leave balances.
HR should identify:
- Annual leave entitlement up to the relevant date.
- Leave already taken.
- Approved future leave.
- Eligible accumulated or carried-forward days.
- Outstanding balance adjustments.
- Applicable payment obligations.
Section 67 of the Labour Protection Act addresses payment for annual holidays in specified termination circumstances, including termination by the employer without the employee's fault under Section 119. It also addresses accumulated annual holidays under Section 30 in the circumstances covered by that provision.
Employers should not assume that every resignation or termination has identical annual leave payment consequences. The applicable statutory provisions, employment agreement, work rules and facts of the separation should be reviewed.
A leave management system should preserve the employee's complete leave history and provide a final balance report for HR and payroll review.
This reduces the risk of overlooking accrued or accumulated leave during final settlement.
17. Maintain an Audit Trail for Leave Applications and Adjustments
Leave balances may change because of new entitlements, approved requests, carry-forward transfers, cancellations and manual corrections.
Employers should maintain a clear record of these changes.
A suitable system should capture:
- Original leave entitlement.
- Date the entitlement was allocated.
- Leave application date.
- Requested dates.
- Approved dates.
- Number of days deducted.
- Approval or rejection details.
- Cancellation history.
- Carry-forward adjustments.
- Manual balance corrections.
- Name of the administrator making each change.
For example, if HR corrects an employee's balance from eight days to 10 days because of an earlier entitlement error, the system should record the previous balance, revised balance, reason and authorising the person.
An audit trail makes it easier to investigate employee queries and prepare internal reviews.
It also discourages unauthorised changes to leave records.
18. Protect Employee Leave Information Under Thailand's PDPA
Annual leave records contain personal information about identifiable employees. Depending on the leave category and supporting documents, they may also contain sensitive information.
For example, a general annual leave request may reveal only the requested dates. However, supporting documents or information attached to a leave application may reveal medical or other sensitive personal details.
Employers should consider their obligations under Thailand's Personal Data Protection Act B.E. 2562 (2019).
Important safeguards include:
- Collect only information necessary for leave administration.
- Explain why employee information is collected.
- Restrict access according to job responsibilities.
- Protect leave records against unauthorised access.
- Establish appropriate retention periods.
- Secure uploaded supporting documents.
- Review access by software vendors and other service providers.
- Provide a process for handling applicable employee data-subject requests.
Managers generally need to know whether an employee's absence is approved and when the employee will be away. They may not need access to every personal document submitted to HR.
Employers should also identify an appropriate legal basis for processing personal data rather than automatically relying on employee consent for every leave-related activity.
Official reference: Thailand Ministry of Digital Economy and Society – Personal Data Protection Act.
19. Generate Annual Leave Reports for HR and Management
Leave reports help employers understand employee absence patterns and plan workforce requirements.
A leave management system should provide reports that can be filtered by employee, department, branch, job category and reporting period.
Useful reports include:
| Report | Business purpose |
|---|---|
| Annual leave balance report | Shows each employee's remaining entitlement |
| Leave utilisation report | Tracks the number of days employees have taken |
| Pending request report | Identifies applications awaiting approval |
| Carry-forward report | Shows eligible unused leave transferred between years |
| Department leave report | Reviews absences across teams |
| Monthly leave calendar | Displays planned employee absences |
| Leave adjustment report | Tracks manual changes to balances |
| Leave history report | Provides a record of previous applications |
| Low-balance report | Identifies employees with limited remaining leave |
| Year-end reconciliation report | Helps HR verify balances before a new leave year |
Management can use these reports to identify periods of high leave demand, departments with insufficient coverage and employees who may need reminders to plan their annual leave.
Reports should be based on accurate and approved records rather than unverified draft applications.
20. Choose Annual Leave Management Software With the Right Features
When selecting leave management software in Thailand, employers should evaluate whether the system supports both statutory requirements and company-specific policies.
Important features include:
Flexible entitlement configuration: The system should support different annual leave allowances based on service length and employee category.
Pro-rata calculations: HR should be able to configure appropriate entitlement calculations for employees who have not completed one year.
Carry-forward management: The platform should track eligible unused days and apply the company's agreed carry-forward conditions.
Automated approval workflows: Applications should be routed to the correct manager or HR approver.
Employee self-service: Employees should be able to view balances and submit requests through a web or mobile interface.
Holiday calendar integration: Weekly rest days, traditional holidays and employee work schedules should be considered when calculating leave days.
Payroll integration: Approved annual leave records should be transferred accurately to payroll.
Audit trails: Entitlement changes, applications, approvals and adjustments should be traceable.
Reports and dashboards: HR and managers should be able to review leave balances, upcoming absences and utilisation patterns.
Privacy and access controls: The platform should provide appropriate safeguards for employee information under the PDPA.
Employers should ask vendors to demonstrate real scenarios, such as a new employee receiving pro-rata leave, an employee carrying forward unused days and a manager approving overlapping requests.
Conclusion
Thailand employers can improve annual leave administration by combining clear policies, accurate entitlement calculations and centralised leave tracking. A well-managed process helps employees understand their available leave, allows managers to plan staffing and gives HR teams reliable information for compliance and payroll administration.
The most important starting point is understanding Section 30 of the Labour Protection Act, including the minimum annual leave entitlement after one year of uninterrupted service, the option to provide pro-rata leave before completing one year and the possibility of agreeing in advance to carry unused leave forward.
Leave management software can make these requirements easier to administer through employee self-service, automated approvals, balance calculations, carry-forward tracking, holiday calendars and reporting.
However, technology alone cannot ensure accurate leave administration. Employers must configure their policies correctly, maintain reliable employee records, document approval decisions and protect personal information.
By reviewing leave balances regularly and reconciling them before payroll and year-end processing, Thailand businesses can create a transparent and dependable annual leave management process.
Leave requests are easier to approve when everyone sees the same remaining balance. InnBuilt leave workflows can help Thailand HR record applications, decisions and balance updates together.