Batch Leave Entitlement & Batch Delete Entitlement

Modified on Thu, 31 Jul at 6:42 PM

The Batch submodule under Leave module allows Admins to manage leave records for multiple employees at once. This guide will walk you through two key processes:

  1. Batch Leave EntitlementTop up, deduct, or correct leave or time off balances
  2. Batch Delete EntitlementCompletely remove leave entitlement from multiple employees


a) Batch Leave Entitlement

This feature allows Admins to manually top up, deduct, or correct leave/time off entitlements for multiple employees in bulk. It is useful for managing exceptional cases that fall outside standard leave policies.


Example:

  • Rewarding additional leave (e.g. incentive leave)

  • Adjusting carry forward balances

  • Correcting errors in entitlement allocation


Step 1

On left sidebar, go to Leave (a) > Batch (b) > Batch Leave (c)




Step 2

You’ll now be in the Batch Leave page.


On the left-hand column, start by selecting the Leave or Time Off types you’d like to adjust. In this demo, we’ll be working with Leave Types. 


Click on Leave Entitlement tab.



Step 3



Select the Leave (a) that you want to adjust, then choose the relevant Entitlement Year (b).


Enter Adjustment Amount (c) — whether you’re adding or reducing leave. Key in the amount in the field next to it.


You may also add a Remark (d) as a reference. This helps provide context when reviewing the adjustment history later.


Once everything is filled in, click Next to proceed.



Step 4


You’ll now be brought to the selection criteria section.


Here, select which employees the adjustment will apply to based on your preferred filters (e.g. company, department, employment type, location).



Once you are done with this criteria selection, click Next to continue



Step 5



You’ll see a summary list of selected employees.

  • You can make ad-hoc changes in "Your Selection" (a) tab to exclude specific employees.
  • Or click "Additional selection" (b) tab to add more employees manually if needed.


Once everything is confirmed, click Submit to apply the adjustment.


Reminder: Double-check your selections before submitting. Changes will immediately take effect on employees in the system.





b) Batch Delete Entitlement

This feature allows admins to manually delete leave entitlements for multiple employees in bulk. It is useful for managing exceptional cases that fall outside standard leave policies.


Once an entitlement is successfully deleted, the selected employees will no longer be entitled to that leave type, meaning they will no longer be able to apply for it.


If you need to reassign the entitlement, you must perform the Generate Entitlement process again.



Step 1

On the left menu, go to Leave (a) > Batch (b) > Batch Delete Entitlement (c)



Step 2

Select the relevant fields for batch deletion:

Type: e.g. Leave, Time Off, Unpaid Leave

Leave Type: e.g. Study Leave, Medical Leave, etc.

Year: e.g. 2025


In this example, we’ll delete Study Leave entitlement under Leave type for the year 2025.


Note:

  • If Force Delete is selected, entitlements will be deleted even if the employee has leave records or leave requests.
  • If Force Delete is not selected, only entitlements with no leave records or requests will be deleted. Others will remain unchanged.


Click Continue.




Step 3

Select the employees that you want delete their entitlement from. Once finalized, click Process.




Step 4

After processing, the system will display the status for each employee.



Unsuccessful deletions may happen due to:

  • Entitlement not yet generated for the employee
  • Existing leave request or balance (Force Delete must be selected in Step 2 to fix this)


We hope this explanation clarifies the matter. If you require additional assistance, do not hesitate to contact our support team.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article