Skip to content

Commit e758bbf

Browse files
feat: add eleave faq
1 parent b4a00b2 commit e758bbf

File tree

7 files changed

+138
-0
lines changed

7 files changed

+138
-0
lines changed
Lines changed: 138 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,138 @@
1+
---
2+
sidebar_position: 4
3+
title: FAQ
4+
description: E-Leave Frequently Asked Questions
5+
---
6+
7+
<!-- markdownlint-disable-next-line MD041 -->
8+
## Leave Applications & Approvals
9+
10+
### 1. Leave application stays “Pending” in HRMS and doesn’t appear in Payroll after Sync Cloud
11+
12+
![request-pending-leave](../../../../static/img/integration/hrms/e-leave/request-pending-leave.png)
13+
14+
By default, only **Approved** leave status is shown in Payroll. Open **Sync Cloud** and tick **Request** and **Pending Leave** to view all pending applications.
15+
16+
### 2. Why don’t I see an option to add attachments?
17+
18+
Your company hasn’t enabled SQL Drive storage. Follow [the setup guide](https://docs.sql.com.my/sqlpay/integration/hrms/payroll-setup#sql-drive) to activate SQL Drive. (Requires an active SQL Drive subscription—contact your service agent for details.)
19+
20+
### 3. Why is my leave auto-approved instantly?
21+
22+
If your HR assigns you the **Manager** role and enables **Auto approve own leave**, your leave requests are approved automatically.
23+
24+
![auto-approved-manager](../../../../static/img/integration/hrms/e-leave/auto-approved-manager.png)
25+
26+
### 4. Why can’t I edit certain approved leave applications?
27+
28+
- **Approved (Sync)** status means the leave is already committed to SQL Payroll and cannot be edited.
29+
- **Approved** (without Sync) can still be edited in HRMS.
30+
31+
:::info
32+
Review the full set of HRMS leave status icons in the [app usage guide](https://docs.sql.com.my/sqlpay/integration/hrms/e-leave/app-usage#leave-status).
33+
:::
34+
35+
---
36+
37+
## Leave Limits & Calculations
38+
39+
### 5. What is the Month-to-Date (MTD) limit formula?
40+
41+
- **Worked more than 1 year / Join date not set:**
42+
43+
```text
44+
Leave Entitlement ÷ 12 × Current Month + B/F Days – Taken Days
45+
46+
Example:
47+
Calculation Month: October 2025
48+
Join Date: 01/01/2019
49+
Year 2025 Entitlement: 16 Days
50+
B/F: 3 Days
51+
Taken: 4 Days
52+
53+
Calculation: 16 ÷ 12 × 10 + 3 – 4
54+
= 13.33 + 3 – 4
55+
= 12.33 Days
56+
```
57+
58+
- **Worked less than 1 year:**
59+
60+
```text
61+
Leave Entitlement × (Report Month – Join Month + 1)
62+
÷ (12 – Join Month + 1) – Taken Days
63+
64+
Example:
65+
Calculation Month: October 2025
66+
Join Date: 01/07/2025
67+
Year 2025 Entitlement: 6 Days (Prorated)
68+
Taken Leave: 0 Days
69+
70+
Calculation: 6 × (10 – 7 + 1) ÷ (12 – 7 + 1) – 0
71+
= 6 × 4 ÷ 6
72+
= 4 Days
73+
```
74+
75+
### 6. Why doesn’t my MTD calculation match HRMS?
76+
77+
MTD balance should only include leave taken **up to** the calculation month. For example, October MTD should exclude leave applications dated in November or later.
78+
79+
### 7. What happens when leave exceeds the MTD limit?
80+
81+
- **Employee:** Can still submit the leave request.
82+
83+
![leave-exceed-mtd](../../../../static/img/integration/hrms/e-leave/leave-exceed-mtd.png)
84+
85+
- **Manager:** Receives a prompt during approval and can keep the same leave type or switch to another type.
86+
87+
### 8. What happens when leave exceeds the Year-to-Date (YTD) limit?
88+
89+
- **Employee:** Sees a prompt indicating the leave exceeds the YTD limit and must reapply using a different leave type.
90+
91+
![leave-exceed-ytd](../../../../static/img/integration/hrms/e-leave/leave-exceed-ytd.png)
92+
93+
- **Manager:** Can transfer the submission to another (e.g., unpaid) leave type during approval.
94+
95+
---
96+
97+
## Troubleshooting & Usage Tips
98+
99+
### 9. Error: `OOPS! We have encountered some problems... type 'NULL' is not a subtype of type 'String'`
100+
101+
![error-null-cast-string](../../../../static/img/integration/hrms/e-leave/error-null-cast-string.png)
102+
103+
Cause: Leave or claim descriptions are blank.
104+
105+
- **Claims:** SQL Payroll → **Payroll** → **Maintenance** → **Maintain Claim**. Ensure every claim code has a description.
106+
- **Leave:** SQL Payroll → **Leave** → **Maintain Leave Type**. Ensure every leave type has a description.
107+
108+
### 10. Why doesn’t the HRMS birthday calendar show my team’s birthdays?
109+
110+
The birthday calendar displays only colleagues in the **same branch and department** as the logged-in user.
111+
112+
### 11. Why does the Leave Balance Summary show different taken days versus Manager Approval view?
113+
114+
- **Leave Balance Summary:** Includes all submitted leave, even if approval is pending.
115+
- **Manager Approval view:** Shows only approved leave.
116+
117+
### 12. Why does HRMS show duplicate leave applications while Payroll shows only one?
118+
119+
This occurs when:
120+
121+
- An employee applies via HRMS but the request hasn’t been posted to Payroll yet.
122+
- Another leave entry for the same date was keyed directly into Payroll.
123+
124+
**How to investigate:**
125+
126+
- **HRMS:** Open the duplicate date → select **View Change Log**.
127+
![hrms-duplicate-leave-changelog](../../../../static/img/integration/hrms/e-leave/hrms-duplicate-leave-changelog.png)
128+
- **Payroll:** Cloud → **Sync Cloud**. If the leave still appears under the **Leave** tab, it hasn’t been posted. Once posted, it disappears from Sync Cloud.
129+
130+
**Fix:**
131+
132+
1. Reject the HRMS leave application (in HRMS or Payroll). If rejected in Payroll, click **Update Payroll** afterwards.
133+
2. Delete the duplicate leave record in Payroll.
134+
3. Post the HRMS leave from Sync Cloud and click **Update Payroll** to push it into Leave Application.
135+
136+
:::info[Reminder]
137+
If you rely on HRMS for leave and claim applications, always finish with **Update Payroll** so records are posted to SQL Payroll.
138+
:::
45.1 KB
Loading
81.1 KB
Loading
78.1 KB
Loading
226 KB
Loading
176 KB
Loading
29.7 KB
Loading

0 commit comments

Comments
 (0)