Leave Data: What to Look Out For and What to Do If Something Doesn't Match
This article lists what to look out for in each Leave data group before you sign off, and what to do if something you see in brioHR doesn't match your template.
Audience & Scope
Audience: HR and admin teams setting up brioHR for the first time
Module: Leave
Country: Malaysia, Singapore
Pre-requisites: Implementation kick-off meeting with your Implementation Manager (IM) completed; Steps 1 to 10 completed
This article is part of the Leave data verification series. It follows the Leave Data Verification Guide (PDF).
What to look out for
A final scan of the trickiest spots for each data group, before you sign off.
| Data group | Look out for |
|---|---|
| Approvers |
|
| Unpaid leave formula |
|
| Leave types and rules |
|
| Custom Configuration |
|
| Policy assignment and entitlements |
|
| Leave already taken |
|
| Credit balances |
|
| Carry forward |
|
If something doesn't match
Find what you're seeing in the first column. If a fix doesn't work, or you can't see why, raise it with your IM.
| What you see | Likely cause | What to do |
|---|---|---|
| An employee's balance is out by some days | Carry forward loaded as at today (or the migration date) instead of 1 January; or this year's Leaves History left out. | Reload carry forward as at 1 January and include this year's Leaves History (Carry Forward Leave and Leaves History tabs). |
| A leave type is not visible to some employees | Eligibility restriction on the policy (office, department, gender, job grade or employment type). | Check and correct the restriction (Leave Policy tab). |
| An employee cannot backdate leave | Backdating or advance notice rule on the policy. | Check the rule. If it is not what you intended, correct the policy (Leave Policy tab). |
| A leave type is credit-based but should be fixed (or the reverse) | This cannot be changed after the leave type is created. | Contact your IM before recreating anything. The leave type must be recreated and its history re-migrated. |
| A request went to the wrong person, or never reached the manager | Manager missing or wrong on the employee profile, or the approver is set to a named person instead of "Manager". | Correct the manager email (Employee List) and check the approver setting (General & Approval Workflow). |
| An unpaid leave deduction is not as expected | Not added to the payroll cycle, or Leave and Payroll settings use different formulas. | Add approved unpaid leave to the ongoing payroll cycle. Confirm the formula in both settings. |
| A replacement-type balance is missing | Existing credits not loaded. | Load existing credits with the reference date (Credit Leave Request History tab). |
| History rows not matching a leave type | Leave type name differs from the Leave Policy tab. | Make the names identical on both tabs. |
| An employee's entitlement, carry forward or approver differs from the rest of their policy | Wrong policy assigned, General Configuration not as intended, or a Custom Configuration overriding it for that employee. | Check the employee's policy, then the General and Custom Configuration. Correct or remove an exception that is not intended. Remember exceptions are set policy by policy. |
| An employee is on the wrong leave policy | Assignment or eligibility restriction does not match your policy. | Check the policy's eligibility and the employee's office, department, grade and employment type (Leave Policy tab; Employee List). |
← Previous: How to Verify Leave Approvers, Entitlements and Balances
Next: How to Sign Off Your Leave Data →
Back to Leave Data Migration and Verification: Start Here
Ownership
By: Aqilah