SLS absence
See which absence is in SLS, which is still to be sent, and which needs a resync — per employee and day.
Overview
The SLS absence report is the HR specialist’s view of the SLS integration. It answers “is this absence in SLS?” without the Integration Log’s technical rows: one grid per month, with the employees under their org unit and their absence activities under each employee, and a coloured bar for every stretch of days.
Navigate to in the sidebar.
The report shows what mTime wants SLS to hold, worked out the same way the integration works it out when it sends — so a bar that says To be sent is what the next approval or retry will send, and a bar that says Needs resync is what the resync job will fix.
Reading the grid
Each month is a block with the days 1–31 across the top, the newest month first. Under the month, the org units (with their SLS pay group), under each unit the employees, and under each employee one row per absence activity, named by its SLS code and activity: 100 QA Sickness.
A bar is one record in SLS: a period spans its days, single days sent one by one are separate boxes. A day with less absence than the norm is drawn lower.
The colour says who acts:
- In SLS (teal) — SLS holds the day as the timesheet says.
- To be sent (amber) — the integration sends it by itself: the statement is not approved yet, or a send failed and is still being retried.
- Needs resync (red) — a send or removal failed and its retries are used up. A person has to run the resync.
Point at a bar to see what happens to the day — Create, Update or Delete — the code, the employee, the date and the hours. For a bar in SLS, the record’s dates and length.
A check mark after the employee’s name means the whole month’s statement is approved; ✓ 1–13 means only those days are. Point at it to see the statements.
Click a month, unit or employee to fold it. A folded row keeps one bar per day for everything under it, in the most urgent colour; point at a bar to see what is behind it.
Filtering
- Employee — one or more employees
- Status — which bars to show. By default To be sent and Needs resync, so the report opens on what is still outstanding; tick In SLS to see what is already there.
- Period — defaults to the previous month, the one whose absence is being sent. Always whole months.
- Org unit and Employment terms under Add filter
- Weekends — shade the weekend columns
The filters offer only what the report holds for the period, so a choice never leads to an empty report.
SLS absence codes opens the list of codes with their rules and the activities under each — the same list as on the integration page, without editing.
Exporting
Click the export button to download the current view as an .xlsx file: one row per activity and month, the days in the columns 1–31, a period as one merged cell. A cell says SLS, Create, Update or Delete, and Resync (…) where a person has to act.
Troubleshooting
| Problem | Solution |
|---|---|
| No pay group on a unit | Absence in that unit never reaches SLS. Set the SLS Pay Group on the org unit, then run the Integration resync. |
| A bar says Needs resync | Run the Integration resync for SLS. The Integration Log row says why the send failed. |
| Absence is missing from the report | Its activity has no SLS Absence Code , or the day is before the Cut-Off Date . |
| The page says absence is not sent to SLS from this workspace | Turn on Send Time Off on the SLS integration. |