HR and payroll troubleshooting

This page is organised by what you see, not by which screen you were on. Find the sentence that matches your problem, read why it happens, then work the steps.

Prerequisites

Most checks here need an HR admin or payroll officer account with access to Human Resources. A few checks need a Super Admin, because they change who can open a screen. Where a step needs access you may not have, the text says so.

Before you start, run the four checks on the Troubleshooting page. They cover the wrong academic session, the wrong campus, missing permissions, and a save that never went through. Those four resolve a large share of HR reports on their own, and everything below assumes you have already tried them.

Employee records

The employee I just added isn't in the list

You saved a new employee, the confirmation appeared, and the row is nowhere in Human Resources > Employees.

Why it happens. The list shows only Active employees until you tell it otherwise. If you used Save Draft, or the record was never activated, the default view hides it.

What to do.

1. Open the Advance Filter panel above the table.
2. Set Status to Draft and look again. The record appears with an amber Draft chip.
3. If it is still missing, set Status to Inactive and check there.
4. Clear the other filters with Reset. Branch, Department, and Designation all narrow the list, and Designation only offers designations belonging to the department you picked.

The Status filter offers Active, Inactive, and Draft only. Records that were deactivated show up under Inactive as well, so Inactive returns more than you might expect.

There is no Edit button on the employee list, and no Delete anywhere

You want to correct an employee's details and cannot find a way in from the list.

Why it happens. There is no single edit form. An employee is edited section by section from their profile, and FEMS has no delete for employees at all.

What to do.

1. Click the row, or the eye icon, to open the employee's profile.
2. Find the section you need and use its own Edit button. Each section opens its own panel with its own save action.
3. To retire someone rather than correct them, use the Exit Info tab.

The row icons have no labels. The eye opens the profile, the key opens that person's permissions, and the last icon in the row signs you in as that employee.

The icon for logging in as an employee is missing

Why it happens. That action needs two things at once: permission to impersonate an employee, and one of the two built-in administrator roles. Granting the permission on its own leaves the icon hidden.

What to do. Ask your Super Admin to check both. If the person is not on an administrator role, the permission alone will not bring the icon back.

Saving an employee's official email is refused

You see either a message naming another employee, or the generic This official email is already assigned to another FEMS account. Contact an administrator.

Why it happens. An official email has to be unique across every FEMS account, not just yours. When the address belongs to someone in your school, the message names them. When it belongs to another school, the message stays deliberately vague so no other school's data leaks.

What to do.

• If the message names an employee, remove the address from that employee's record first, then assign it here.
• If the message is the generic one, only an administrator can resolve it. Raise a ticket.
• Another official email change is in progress. Please try again. and Official email validation is temporarily unavailable. Please try again. are both temporary. Wait a moment and retry.

The emergency contact section refuses to save

Why it happens. The create wizard makes every emergency-contact field optional. Once the employee exists, the edit drawer requires Name, Relation, and Primary Phone. Alternative phone, email, and address stay optional.

What to do. Add the name, relation, and primary phone for every emergency contact listed, then save.

Exit information shows a green message but nothing was stored

You saved resignation or charge handover details, saw a success message, and the values were gone when you came back.

Why it happens. The resignation and charge handover saves report success even when the write failed underneath. The confirmation is not proof. The clearance and exit feedback saves on the same tab behave normally and surface a real error when they fail.

What to do. Reload the tab after every resignation or charge handover save on Exit Info and confirm the values are there. If they are not, try once more, then raise a ticket with the employee's ID and what you entered.

The Absent Employees card looks wrong

Why it happens. The five cards under Statistics are counted differently from each other. New Hires This Month is a rolling calendar month, not the calendar month you are in, so on the tenth of a month it counts back to the tenth of the previous month. Absent Employees counts the opposite of its label: it is the number of employees who have an attendance record for today, which means the ones who are present. It is also limited to the employees the list is currently showing you.

What to do. Do not use these cards as a reporting figure. Use Human Resources > Reports for attendance numbers you intend to act on. Raise a ticket so the Absent Employees label gets corrected, and do not quote that number to anyone in the meantime.

Staff attendance

Staff attendance numbers do not match the class register

Why it happens. Staff attendance and student attendance are two separate systems. They share no records and no rules. Staff attendance has late marks and feeds payroll. Student attendance does not have a late state at all.

What to do. Never reconcile the two. If the conversation is about a class, a section, or a class teacher, it is student attendance and nothing on this page applies. If it is about a device punch, a late mark, or a salary deduction, it is staff attendance and you are in the right place.

A day an employee worked is missing from the attendance report

Why it happens. A day only exists once there is a punch. When nobody punched in, no record is created, and the attendance report has nothing to show for that date. The attendance dashboard works out absence from the calendar instead, which is why the two screens can disagree about the same day.

What to do.

1. Check the date range on the report. Generate Report does nothing at all when either date is blank.
2. Ask the employee to file a Manual Attendance application for the missing day.
3. Use the dashboard when you want absence counted from the calendar, and the report when you want the punches that exist.

Attendance from the device stopped arriving

Why it happens. A new attendance device connection starts in monitoring mode. It records what arrives but writes nothing into staff attendance until someone switches it over. Individual punches can also fail with Employee record not found when the punch carries an ID that matches no employee, or Device time needs checking when the device clock is outside the accepted window. Punches rejected for a device clock problem are never retried.

What to do. Ask a platform administrator to enable processing for that connection. Once processing is on, the retry sweep applies the saved backlog. Fix the device clock and the employee ID mapping separately, since those punches will not come back on their own.

An employee arrived after the start time but no late mark appeared

Why it happens. A late mark needs a scheduled start time on the employee's record. Without one, nobody is ever late. New punches use no grace period, while a later recalculation can apply an institution or employee grace value that is not shown on any FEMS screen.

What to do. Confirm the employee has a work schedule with a start time. If they do and the punch is genuinely after it, raise a ticket rather than adjusting records by hand, because the grace value has to be checked by support.

A holiday or extra working day I set up applies to nobody

You created a schedule override for a campus, and staff are still marked absent, or payroll still counts the day as a working day.

Why it happens. An override only reaches an employee when both their campus and their department match the override. Selecting a campus without ticking the departments under it stores nothing, so the override applies to nobody.

What to do.

1. Open the override and tick every department under each campus you selected.
2. Save, then check one affected employee before you rely on it.
3. Remember there is no delete for a schedule override. Editing it is the only way to neutralise it.

Two more limits worth knowing. An override created on this screen changes late marks and payroll working days, but it does not change what the attendance dashboard shows (see #2468). And the All Campus switch selects everything on screen. It does not store the override as an institution-wide one, so overrides always list as targeted.

The Designation filter is greyed out

Why it happens. Designation is disabled until you choose a Department. This is by design on the attendance report, the attendance dashboard, and the payroll assign screen.

What to do. Pick a department first. Changing the department clears a designation that no longer fits.

The report is empty, or an employee only ever sees themselves

Why it happens. The report type my attendance replaces the employee filter with the person who is signed in, so it can only ever return their own rows. Separately, listing the whole school's attendance needs the attendance report access.

What to do. Switch the report type away from my attendance. If the report is still empty for an HR admin, ask your Super Admin to grant attendance report access to that role.

The Export button is disabled, missing, or produces nothing

Why it happens. Three separate causes. Export is hidden when the role does not have export access for that specific report. It is disabled when the current result set is empty. And the export on the leave summary does not download a file at all.

What to do. Run a filter that returns rows first, then export. Ask your Super Admin to grant export access for the specific report, since each report has its own. For the leave summary, raise a ticket rather than waiting for the file. Note that the attendance dashboard export covers the page you are looking at, not the whole result set.

Leave and applications

An employee is told they have no leave balance, but their balance card shows days left

The message reads You do not have sufficient leave balance for the selected leave type.

Why it happens. Balance is the allocation for a leave type minus what has been used, and used is worked out from the approved applications on record. The allocation is looked up for the academic session that is current for your school right now, not the session the requested dates fall in. A request for dates in next year's session is still checked against this year's allocation.

What to do.

1. Check the employee's allocation for the current academic session.
2. Check whether an approved application already consumed the days.
3. If the leave dates belong to a session that is not the current one, raise a ticket. The balance check cannot look that allocation up.

A new employee sees no leave balance and an empty leave type list

Why it happens. The employee has no leave allocation for the current session, or the allocation exists but is not being read back.

What to do. Confirm an allocation exists for the current academic session and the right leave types. If the allocation is on record and the screen is still empty, raise a ticket with the employee ID and academic session.

An employee cannot submit because they already have a pending request

The message reads You already have a pending leave application. Please contact HR before submitting another request.

Why it happens. Only requests sitting at Pending or Recommended block a new request for the same leave type. Approved, rejected, and cancelled requests do not block anything.

What to do. Reload the applications list first, since a stale browser tab can resubmit an old form. If a request is stuck at Recommended, the approver has to approve or reject it before the employee can apply for that type again.

An employee is told they already applied for those dates

Why it happens. FEMS checks the requested dates against the employee's existing applications, but the overlap message is not shown and the new request still goes through.

What to do. Check the employee's open requests before approving a familiar date range. Do not rely on FEMS to prevent duplicate dates.

The Approve, Reject, or Recommend buttons are missing, or the action is refused

The refusal reads You are not allowed to perform this action on this application.

Why it happens. FEMS decides this per person, not only per role. Nobody can recommend, approve, or reject their own request. Only the employee's reporting manager can recommend. Only an approver can approve or reject. For leave and attendance an approver is anyone holding hr.applications_leave_approve or hr.applications_attendance_approve. They can approve from Pending or Recommended, and a reporting manager who is also an approver can approve or reject too. For payroll applications, a reporting manager can never approve or reject, and the application must be recommended first.

What to do.

1. Check the employee's reporting person on their profile.
2. For leave or attendance, check in Role Management that the person's role has Approve Leave Applications or Approve Attendance Applications. Those two grants are what make someone an approver.
3. If the right person still sees no buttons, ask your Super Admin to grant the matching approve permission to their role. Recommending comes from being the reporting manager, not from a grant.

Approving is refused because the application was never recommended

The refusal reads Application must be recommended before it can be approved.

Why it happens. A payroll application has to travel Pending, then Recommended, then Approved. Approving it straight from Pending is refused, even when the person clicking is the correct approver. Leave and attendance applications do not need this step: their approver can approve straight from Pending, and FEMS adds a comment saying the application was approved without a line manager recommendation.

What to do. For a payroll application, ask the employee's reporting manager to recommend it first, then approve it. If the application already sits at Recommended and the approve is still refused, work the previous symptom instead.

Comments cannot be edited

The message reads Comments can only be edited while the leave application is pending.

Why it happens. Comments lock once a leave or attendance application leaves Pending. Payroll applications do not lock.

What to do. Add the note before you decide the application. Once decided, record the note elsewhere.

An employee cannot file an attendance correction for an earlier date

Why it happens. The server accepts attendance applications for today only. It rejects any earlier date before checking the pay-period deadline. A duplicate request for the same date and type also blocks a new one.

What to do. File the correction on the day it happens. For an earlier date, ask your FEMS administrator how your institution records the correction.

An approved application did not change the attendance record

Why it happens. Approving records the decision on the application. What is confirmed is the payroll effect: a late mark that is marked approved stops counting towards the late deduction, and an unapproved one keeps counting.

What to do. After approving, check the employee's attendance for that date before you tell them it is resolved. If the record is unchanged, raise a ticket rather than editing anything by hand.

A Late Arrival application shows the same time for in and out

Why it happens. Older Late Arrival and Early Departure records were saved without in and out times and fall back to a placeholder. This was corrected.

What to do. If you see it on a newly filed application, raise a ticket with the employee ID and application date. An early departure request with no matching attendance record legitimately shows blank times rather than a placeholder.

Re-applying for Late Arrival after a rejection fails with an error

Why it happens. A previous rejected or cancelled request used to keep hold of the slot for that date and type. This was corrected.

What to do. If it happens again, raise a ticket with the employee ID, application type, and exact message.

Leave the employee took is not on the attendance report

Why it happens. Only approved leave is picked up, and only when it overlaps the report dates. The attendance report screen does not display the leave overlay at all today.

What to do. Approve the leave first, then use Human Resources > Reports > Leave Summary to see leave, and the attendance report for punches. Do not expect one screen to show both.

Leave duration counts weekends and holidays

Why it happens. Leave duration counts every calendar day in the range. Weekends and holidays are not removed, and there is no half-day leave.

What to do. File leave in blocks that stop before the weekend when you do not want those days counted. Tell staff this before they submit, since the duration they see is the duration that gets deducted.

Approving a profile update request is refused

Why it happens. Approving writes straight to the employee's live record. When the part of the record being changed does not exist yet, there is nothing to write to.

What to do. Create the missing section on the employee's profile through the normal edit path first, then approve the request again.

Payroll and payslips

Start here: how a payslip is worked out

Almost every payroll question is one of the four terms below. Learn these and you can answer "why is the payslip short" without opening a ticket.

per-day rate    = gross salary / 30          (always 30, in every month)

working days    = every day in the pay period that is not Friday or Saturday,
                  adjusted by any schedule override

absent days     = working days
                  - days attended            (approved records only)
                  - paid leave days          (approved leave only)
                  - unpaid leave days        (approved leave only)
                                             (never less than zero)

absent deduction       = per-day rate x absent days
unpaid leave deduction = per-day rate x unpaid leave days
late deduction         = per-day rate x (unapproved late marks / late threshold,
                                         rounded down)

net pay = gross salary
          - absent deduction
          - unpaid leave deduction
          - late deduction

Seven things to hold on to:

• The divisor is always 30. February and a 31-day month both use gross divided by 30.
• Nothing adds to net pay. An adjustment or a bonus you enter does not reach the payslip today (#2458), and a deduction head such as tax or provident fund is shown in the breakdown but is not taken off the net figure (#2461).
• Weekends are Friday and Saturday. Your school's own work week is not used by payroll.
• Unpaid leave means a leave type marked as deducting salary. Every other leave type costs nothing.
• Only approved leave feeds the paid and unpaid leave terms. Leave still sitting at Pending or Recommended counts for nothing, so those days fall through to absent days and get deducted.
• A leave that starts or ends outside the pay period contributes its whole length, not just the part inside the period. A five day leave with two days in this month and three in the next deducts five days here, then five days again next month. Check the leave dates before you accept a large deduction near a period boundary.
• Only unapproved late marks count. Approving a late mark removes its share of the deduction.

Worked example, for a monthly gross of 30,000 in a pay period with 22 working days. The employee attended 19 days, took 1 paid leave day and 1 unpaid leave day, and has 6 unapproved late marks against a late threshold of 3.

The payslip is short and the employee disagrees

Why it happens. One of the three deduction terms above is larger than the employee expects. Work them in order.

What to do.

1. Read the absent days and late arrival counts on the payslip. They tell you which term to chase.
2. For absent days, open the employee's attendance for the period. Only approved attendance records count as days attended, so a day sitting on a pending correction request counts as absent.
3. For unpaid leave, check which leave type was used. A type marked as deducting salary costs a full day each. Check the leave dates too. A leave that runs across the end of the period is deducted at its full length in both periods.
4. For late deductions, count the late marks that are not approved.
5. Check the pay period dates match the month you have in mind before you conclude anything.

Everyone shows fully absent and net pay is near zero

Why it happens. Days attended counts only approved attendance records. If attendance was never brought in for the period, or every record is waiting on an application, the whole period reads as absent.

What to do.

1. Check attendance exists for the period at all. If it does not, see the device ingest symptom above.
2. Check the pay period's from and to dates.
3. Check whether a schedule override added working days that nobody was expected to attend.
4. Do not release payslips in this state. Fix the attendance first and generate again.

There is no late deduction at all

Why it happens. Three separate causes.

• The school has no late deduction threshold on record. Without it, the late deduction is skipped completely, whatever the late marks say. There is no screen in FEMS to set this.
• The late marks were approved. Approving them removes the deduction by design.
• The late fields you can edit on the pay period itself, such as the acceptable delay in minutes, are stored but not used by the calculation.

What to do. Raise a ticket asking support to set the school's late deduction threshold, which is the number of late marks that equals one day docked. Then reprocess the period and check one payslip. Early departures are counted but never deducted, so do not expect a charge for them.

Some employees have no payslip at all

Why it happens. Generation skips an employee silently. In the order worth checking:

1. The employee has no salary structure assigned. This is the most common cause.
2. The assignment was removed from the payroll group.
3. The employee is inactive, or the account is an administrator account.
4. The employee's campus is not one of the campuses on the pay period.
5. The employee has no employment record, so there is no campus or department to work with.

What to do. Open Human Resources > Payroll > Payroll Assign and search for the employee by name to see whether they have an assignment. Do not rely on the Status filter there, since it does not filter anything today. Assign the structure, then generate again.

The campus list on the pay period is not your campuses

Why it happens. The campus choices on the new and edit pay period panels are a fixed sample list rather than your school's campuses. Because generation works from the campuses stored on the period, this can produce payslips for the wrong people or for nobody.

What to do. After creating a period, open its details and check the campus column against your real campuses before you process anything. Raise a ticket if they do not match. Do not process a period whose campuses you cannot recognise.

I clicked Process and no payslips appeared

Why it happens. Process does not generate. It marks the period ready, and generation runs overnight. Three more causes stack on top: the period is not the one marked current, the period was created as upcoming so the overnight run skips it, and a second run for the same employee and period is refused while the first one is still working.

What to do. Use Reprocess to generate now. Generation runs in the background, one employee at a time, so payslips appear over a few minutes rather than instantly. If a reprocess appears to do nothing, the earlier run is probably still working through the queue: wait for it to finish, then check one employee before running it again. If nothing has generated by the next morning, raise a ticket.

Payslips generated but the Employee Payslip tab is empty

Why it happens. That tab anchors its whole list on a single pay period chosen automatically, and a period you have just reprocessed cannot be the one it picks. Filtering by month narrows within that anchor rather than choosing it, so a month that is not the anchor returns nothing.

What to do. Check the payslip from the employee's own salary and payslips view, which does not use that anchor. Raise a ticket quoting #2479 so the list can be corrected, and do not conclude the payslips are missing until you have checked the employee-side view.

The pay period I created is not in the list

Why it happens. A period is unique on its date range and academic session. Creating one that already exists returns the existing period with a normal confirmation message, so nothing new appears. You may also see Process already exists for this date.

What to do. Find the existing period for that date range and session and edit it instead of creating another.

An adjustment was saved but the payslip did not change

Why it happens. Adjustments made on this screen do not reach the payslip at all. The categories the Adjustment tab offers are not the kind the calculation reads, so the amount is stored and then ignored. This is a known defect (#2458). Two lesser causes sit on top of it: the payslip was generated before the adjustment existed, and the adjustment never saved even though a confirmation appeared.

What to do.

1. Go back to the Adjustment tab and confirm the row is there with a non-zero employee count. If it is not, it never saved.
2. Reprocess the period, wait for the run to finish, then read the payslip.
3. If the figure is still unchanged, do not keep retrying. Handle the amount outside FEMS for this pay run and raise a ticket quoting #2458.

Deduction-style adjustments such as fines are not applied either. The calculation only ever adds earnings, and today not even those arrive.

Save on the payroll assign screen is greyed out

Why it happens. Save is blocked while a calculation is running, and whenever the inputs on screen no longer match the ones the breakdown was calculated from. Clicking through shows Please recalculate payroll before saving.

What to do. Press Calculate again after every change, then save. Three related errors:

If every category calculates to zero, the formula on the category did not resolve. Check whether one head refers to another head that is ordered after it.

The per-day rate is the same in February as in a 31-day month

Why it happens. The divisor is fixed at 30. This is a deliberate approximation, not a fault.

What to do. Explain it to staff using the worked example above. Do not adjust gross salaries to compensate.

Your weekend is not Friday and Saturday

Why it happens. Payroll treats Friday and Saturday as non-working days. The work week you can configure elsewhere in FEMS is not read by payroll.

What to do. Use schedule overrides in both directions until this is changed: mark your real working Fridays and Saturdays as working days, and mark your actual weekend as a holiday. Remember both campus and department have to be selected for an override to apply. Raise a ticket so the limitation is on record for your school.

Tax and provident fund appear in the breakdown but the net pay does not change

Why it happens. The net figure is worked out from gross minus the attendance deductions only. Deduction heads assigned to the employee are listed in the breakdown but never subtracted, so the payslip shows a tax or provident fund line and still pays the employee as though it were not there. This is a known defect (#2461) and it is the largest open correctness problem in payroll.

What to do. Do not release payslips where the breakdown and the net figure disagree. Raise a ticket quoting #2461 with one example payslip before the pay run goes out.

Printing a payslip does nothing

Why it happens. The print window is blocked, the row has no payslip yet, or you are printing someone else's payslip without the access to see it.

What to do.

1. Allow pop-ups for FEMS in your browser, then print again. The message Please allow pop-ups to print the payslip means exactly this.
2. Payslip is not available for printing means the payslip has not been generated for that row.
3. Payslip not found on someone else's payslip means your access is limited to your own.

Note that the printed net payable is rounded down to a whole amount, with the fraction shown as a carry over round-off line. The screen shows the exact figure.

The printed payslip shows a school name that is not yours

Why it happens. When the payslip cannot work out which school it belongs to, the name printed on it falls back to a fixed value that belongs to another school. This is not a campus problem. A campus that cannot be worked out prints as blank, never as somebody else's name. This tenant-identity defect is tracked under umbrella issue #2463.

What to do. Stop. Do not distribute the payslips. Raise a ticket immediately and say that a payslip printed another school's name. This is treated as a serious incident, not a formatting problem.

Settings and access

I granted access to settings but the person still cannot open any settings screen

Why it happens. The parent settings access opens only one screen on its own, the leave settings screen. Every other HR settings screen is opened by its own separate grant, and granting the parent does not cascade to them.

What to do. Ask your Super Admin to grant each screen the person needs, one by one:

• Basic Settings
• Application Settings
• Application Config
• Leave Settings
• Payroll Settings
• HR Clearance
• HR Feedback Question

Roles created recently are the ones most likely to be affected, because a one-time correction only covered the roles that existed when it ran.

The whole Human Resources menu is missing for a user

Why it happens. The menu group disappears when every screen inside it is denied. It is not a fault.

What to do. Grant at least one HR screen to that role, such as Employees or Applications. People who review applications get the applications entry automatically because they are a reporting manager or hold a leave or attendance approve permission.

The screen opens but the Add and Edit buttons are missing

Why it happens. Opening a screen and changing it are separate grants. FEMS hides the buttons rather than disabling them, so a read-only role sees a list with no way in. On the feedback questions screen, deleting is a third separate grant, so someone can legitimately have add and edit but no delete.

What to do. Ask your Super Admin to grant the manage access for that specific screen, and the delete access separately where you need it.

The list loads but saving is refused

Why it happens. On the basic settings screens, reading is open to anyone signed in while saving is enforced strictly. A role can therefore open a tab, see everything, and be refused the moment it saves.

What to do. Grant the manage access for that tab. If reading fails too, this is not a permission problem, so raise a ticket instead.

I got a green message but nothing changed

This is the single most common settings complaint. Several HR settings screens report success when they did nothing.

Why it happens. The save path treats a no-op as a success. A duplicate name, a record that is in use, a value that is too long, or a row that no longer exists all end in a confirmation with no change.

What to do. Always reload the list after saving and confirm the change with your own eyes. Then match what you saw against this table.

What to do about each. Free the record first, then delete. Reassign employees off an employment type or category, detach a department from the roles that use it, and remove a qualification from the employees who list it. Keep clearance descriptions under 255 characters. Reload the page before editing anything.

Items I deleted came back

Why it happens. The HR clearance list and the feedback question list both restore their starter set whenever the list is empty.

What to do. Keep at least one item in each list. Edit the starter items instead of deleting them all.

The starter exit interview questions name a school that is not yours

Why it happens. The starter feedback questions include another school's name in their wording, and every school receives them as-is.

What to do. Edit or replace every starter question before your first exit interview. Raise a ticket so the starter wording gets corrected, since no school should see another school's name.

Adding an educational qualification does nothing and shows no error

Why it happens. Sorting is required by the server, and the screen does not show you the error when the save is refused. The panel just sits there.

What to do. Fill in Sorting as well as Qualification Label, then add. If it still does nothing, raise a ticket, because the missing error message is a defect.

Adding a feedback question fails with no reason

Why it happens. A question is limited to 500 characters and the box gives no counter or warning.

What to do. Shorten the question to 500 characters or fewer.

Searching Salary Settings finds nothing, but I can see the row on another page

Why it happens. That table pages the list first and searches only the page you are on.

What to do. Set Items per page high enough to hold the whole list, then search.

The Employment Type dropdown is greyed out with a red bar at the top

Why it happens. The employment type list failed to load, so the field is disabled rather than left empty.

What to do. Open the Employment Type tab and confirm it loads. Reload the page. If the red bar returns, raise a ticket with the message it shows.

The panel says Add Employee Category while I am editing one

Why it happens. The employee category panel keeps the create wording in its title when you are editing. The button below it is correct. It reads Update when you are editing and Add when you are creating.

What to do. Nothing. Read the button, not the title. The update is applied correctly. Confirm the fields are pre-filled before you save.

Payroll Settings is an empty screen

Why it happens. That screen carries a heading and nothing else today. It is one of the non-functional HR screens tracked under umbrella issue #2472.

What to do. All payroll configuration lives under Human Resources > Payroll, across the Employee Payslip, Payroll Assign, Payroll Process, and Adjustment tabs. See Payroll setup.

Leave Settings shows leave types you never created

Why it happens. The leave type tab on that screen shows a fixed sample list. It is not reading your school's leave types, and editing it changes nothing.

What to do. Do not use that screen to manage leave types, and do not use it to check what a leave type deducts. It is covered by umbrella issue #2472. Raise a ticket to find out where your school's leave types are maintained.

When to raise a ticket instead

Stop working the problem and raise a ticket in these two cases.

Money that has already been paid. If a payslip was released, an amount was disbursed, or an employee has been paid on a figure you now believe is wrong, do not regenerate or reprocess anything. Generating again changes the record you need to explain the difference from.

Anything that looks like another school's data. A payslip printing a school name that is not yours, an employee record you do not recognise, or a list showing people from elsewhere. Report it straight away and do not work around it.

Also raise a ticket for the items on this page that need an engineering change rather than a setting: the missing late deduction threshold, the fixed Friday and Saturday weekend, the campus list on a pay period, an empty payslip list after a successful generation (#2479), an adjustment that never reaches the payslip (#2458), and a deduction head that is shown but not subtracted (#2461).

See Getting help when you're stuck for how to raise a ticket and what to include. Quote the employee ID, the pay period dates, and the exact message you saw.

Related pages

• Troubleshooting
• Getting help when you're stuck
• Understanding roles and permissions
• Employee records
• Staff attendance
• Leave and applications
• Schedule overrides
• Running payroll
• HR settings