Skip to main content
SpireSlip

Reviewing portal employment requests

Employees can submit three kinds of HR-facing requests from the SpireSlip portal: a work location change, a leave encashment (cashing out unused paid leave days), and an employment confirmation letter. Each submission writes a notification to your bell with a link straight to that employee’s Employment requests page.

Finding pending requests

Open the employee’s profile and click Employment requests, or follow the link from the notification. The page groups all three request types in their own sections so you can scan the whole queue for an employee in one view.

Work location change

The header shows the employee’s current location (On-site, Remote, or Hybrid) so you can see the change at a glance. Approving updates employees.work_location immediately; the portal attendance check-in feature appears or hides based on the new value on the employee’s next page load. Rejecting requires a reason that is shown back to the employee.

Leave encashment

Each pending row shows the leave type and the number of days the employee wants to encash. Clicking Approve & compute calculates the payout as gross_salary ÷ 22 × days (the same daily rate used elsewhere in SpireSlip), deducts the days from the employee’s entitlement, and queues the amount for inclusion in the next payroll run. The encashment appears on the payslip as Leave encashment: [leave type]. It is paid as a one-off taxable payment: PAYE is worked out on it once, in the run that pays it, and no pension is taken from it. If you are unsure how encashment should be taxed for your staff, ask your accountant. Voiding a payroll run releases the encashment back into the queue for the following run.

Employment confirmation letter

Each pending row shows the purpose the employee picked (Visa, Loan, Tenancy, or General) plus their optional note to HR. Clicking Generate & publish letter renders a confirmation letter PDF using the entity’s letterhead and publishes it to the employee’s portal Documents tab automatically. The PDF includes the employee’s name, role, start date, current gross salary, and a salutation tailored to the chosen purpose.

Audit trail

Every state change writes an audit_log row so the activity is reviewable later: portal_*_requested on submission, work_location_approved, leave_encashment_approved, employment_letter_approved, or *_rejected on review. Voiding a payroll run also logs the encashment release.