feat: add hrms faq

Author: changsheng1239

docs/integration/hrms/e-claim/_category_.json

@@ -1,6 +1,6 @@
 {
     "label": "E Claim",
-    "position": 7,
+    "position": 8,
     "link": {
       "type": "generated-index",
       "description": "A guide on E Claim features"

docs/integration/hrms/e-claim/faq.md

@@ -0,0 +1,33 @@
+---
+sidebar_position: 4
+title: FAQ
+description: E-Claim Frequently Asked Questions
+---
+
+## Approvals & Audit Trail
+
+### 1. Why does the change log show “ADMIN” instead of the manager’s name?
+
+When a claim is approved or rejected directly in **SQL Payroll** (rather than in HRMS), the audit log records the action under **ADMIN**. Approvals completed within HRMS display the actual manager’s name.
+
+---
+
+## E-Invoice Claim Workflow
+
+### 2. What is an E-Invoice Claim?
+
+This submission type requires an attachment containing a **valid e-invoice QR code**. SQL HRMS scans the file, validates the QR code, and auto-populates the invoice details in the claim form.
+
+### 3. Why do I see “No QR detected” after attaching an e-invoice?
+
+Common reasons include:
+
+- No QR code present in the attachment.
+- QR code is too small or low quality to be read.
+- The e-invoice itself is invalid.
+
+Upload a clear, valid e-invoice and attach it again.
+
+### 4. Why is the Supplier Name or E-Invoice No truncated in `Ref 1` / `Ref 2`?
+
+Each reference field supports up to **80 characters**. Values longer than that are automatically shortened to fit the limit.

docs/integration/hrms/e-leave/_category_.json

@@ -1,6 +1,6 @@
 {
     "label": "E Leave",
-    "position": 6,
+    "position": 7,
     "link": {
       "type": "generated-index",
       "description": "A guide on E Leave features"

docs/integration/hrms/e-leave/faq.md

@@ -4,7 +4,6 @@ title: FAQ
 description: E-Leave Frequently Asked Questions
 ---
 
-<!-- markdownlint-disable-next-line MD041 -->
 ## Leave Applications & Approvals
 
 ### 1. Leave application stays “Pending” in HRMS and doesn’t appear in Payroll after Sync Cloud

docs/integration/hrms/e-payroll/_category_.json

@@ -1,6 +1,6 @@
 {
     "label": "E Payroll",
-    "position": 8,
+    "position": 9,
     "link": {
       "type": "generated-index",
       "description": "A guide on E Payroll features"

docs/integration/hrms/e-payroll/faq.md

@@ -0,0 +1,54 @@
+---
+sidebar_position: 3
+title: FAQ
+description: E-Payroll Frequently Asked Questions
+---
+
+## Access & Sync Issues
+
+### 1. Why can’t I click the **Latest Payslip**, **Monthly Payroll**, or **EA Form** buttons?
+
+![top-row-disabled](../../../../static/img/integration/hrms/e-payroll/top-row-disabled.png)
+
+Enable the payroll data sync in SQL Payroll:
+
+1. In SQL Payroll, click the **☁** icon.
+2. Choose **Payroll**.
+3. Tick **Include Employee Payroll Info**, then click **Sync All**.
+
+### 2. Error: `Unauthorized`
+
+Re-enable SQL Drive and sync again:
+
+1. In SQL Payroll, go to **File → Company Profile**.
+2. Click the **☁** icon.
+3. Toggle **SQL Drive** off and click **Save**.
+4. Click **Edit**, toggle **SQL Drive** back on, then save.
+5. Re-sync Payslip/EA data in HRMS.
+
+---
+
+## Payslip Availability
+
+### 3. Why are some payslips missing after I change the filter and resync?
+
+Starting with Payroll version **v216**, the sync behaviour differs for Payroll Info versus Payslips:
+
+- **Payroll Info** → syncs from the first month-end up to the month selected in the filter.
+- **Payslips** → syncs **only** the exact month selected.
+
+![sync-payroll-logic](../../../../static/img/integration/hrms/e-payroll/sync-payroll-logic.png)
+
+If you select **September 2025**:
+
+- Payroll Info updates from the first month-end through September 2025.
+- Payslips sync only for September 2025.
+
+:::warning Important
+If you re-sync an earlier month (for example, **June 2024**):
+
+- Payroll Info refreshes from the first month-end through June 2024.
+- Payslips overwrite with only June 2024 data.
+
+Any payroll info and payslips **after June 2024 are removed** and must be re-synced month by month.
+:::

docs/integration/hrms/e-tms/_category_.json

@@ -1,6 +1,6 @@
 {
     "label": "E TMS",
-    "position": 5,
+    "position": 6,
     "link": {
       "type": "generated-index",
       "description": "A guide on E TMS features"

docs/integration/hrms/e-tms/faq.md

@@ -4,7 +4,6 @@ title: FAQ
 description: E-TMS Frequently Asked Questions
 ---
 
-<!-- markdownlint-disable-next-line MD041 -->
 ## Clock In & Attendance
 
 ### 1. Why do I see `Exception: [500] Error` or `Exception: [500] Insufficient Storage` when clocking in/out with attachments?

docs/integration/hrms/faq.md

@@ -0,0 +1,47 @@
+---
+sidebar_position: 5
+title: FAQ
+description: HRMS Frequently Asked Questions
+---
+
+<!-- markdownlint-disable-next-line MD041 -->
+## Connectivity & Login
+
+### 1. Error: “OOPS! We have encountered some problems while trying to connect to the server. Please try again.”
+
+![500-error](../../../static/img/integration/hrms/faq/500-error.png)
+
+Verify branch settings in SQL Payroll:
+
+- **Radius** is blank → SQL Payroll → **Human Resource → Maintain Branch** → enter a radius value.
+- **Branch description** is empty → SQL Payroll → **Human Resource → Maintain Branch** → fill in the description.
+
+### 2. Error: `[SQL HRMS] Exception: [404] User Name 'xxxx' not found in Payroll`
+
+Confirm these items before logging in:
+
+- You’re using the correct email address.
+- If the email was just added in **Maintain Employee**, run **Sync Cloud** so HRMS picks it up.
+- The employer email field in **Maintain Employee** is populated.
+
+---
+
+## Device Requirements
+
+### 3. What are the minimum mobile OS versions for SQL HRMS?
+
+- **Android:** 5.0 (Lollipop) or newer.
+- **iOS:** 12 or newer.
+
+---
+
+## Payroll & Sync Settings
+
+### 4. Error: `Cannot cast Object into String` during Sync Cloud
+
+This error occurs when a leave type or claim code description is blank.
+
+**Fix it in SQL Payroll:**
+
+- **Claims:** Payroll → **Maintenance → Maintain Claim** → ensure every claim code has a description.
+- **Leave:** Payroll → **Leave → Maintain Leave Type** → ensure every leave type has a description.