Salary Liquidation Workflow
A salary liquidation is the process of calculating and approving an employee’s pay for a given period. Houra walks you through each step in a structured workflow to reduce errors and ensure nothing is missed.Open the Payroll module and start a new liquidation
In the Admin Panel sidebar, click Payroll. Then click + New liquidation. Select the employee and the pay period (month and year) you want to process.
Review attendance and hours
Houra automatically pulls in the employee’s attendance data for the selected period — days worked, total hours, late arrivals, and absences. Review this data and correct any discrepancies before proceeding. If an attendance record needs adjustment, click the link to open it directly in the Attendance module.
Apply deductions and additions
Add any one-off items that apply to this pay period: bonuses, commissions, overtime pay, or deductions such as penalties or previously approved advances being recovered. Each line item requires a note explaining the reason.
Review the summary
The liquidation summary shows the gross salary, all additions and deductions itemized, and the final net pay. Confirm that every figure is correct before proceeding.
Approving Salary Advances
Employees can submit advance requests through the Employee Portal. When a request arrives, you receive a notification in the Admin Panel and it appears in the Advances tab of the Payroll module. For each advance request you can:- Review the amount and reason — The employee’s stated reason is displayed alongside their current balance of any outstanding advances.
- Approve — Click Approve to authorize the advance. Houra logs the approval with your name, the date, and the amount.
- Reject — Click Reject and optionally add a note. The employee is notified and can see your note in their portal.
Approved advances are tracked as pending recoveries against the employee’s account. When you process their next salary liquidation, Houra surfaces the outstanding advance and offers to deduct it from the net pay automatically.
Managing Leave Types
The Leave section of the Payroll module lets you define and manage the leave types available to your employees, as well as review and action individual leave requests.Configuring Leave Types
Go to Payroll → Leave → Leave Types to see all the leave categories your organization uses. Common examples include:- Vacation leave — Paid time off accrued over the year.
- Sick leave — Paid or partially paid leave for illness.
- Unpaid leave — Time off without compensation.
- Parental leave — Maternity or paternity leave, often with distinct rules.
Reviewing Leave Requests
Employees submit leave requests through the Employee Portal. Pending requests appear in Payroll → Leave → Requests.Open the leave request
Click on the request to see the employee’s name, the leave type, the dates requested, and any note they attached.
Check remaining balance
Houra displays the employee’s current balance for the requested leave type alongside the request, so you can approve with confidence.
Audit Trail and Traceability
Every action taken in the Payroll module — creating a liquidation, approving an advance, updating a leave balance, modifying a deduction — is recorded in the audit trail with the following details:- The action performed
- The employee it relates to
- The administrator who performed the action
- The exact date and time
The audit trail is read-only and cannot be edited or deleted. This ensures a tamper-proof record for compliance purposes or internal reviews.
How Payroll Connects to Attendance
The Payroll module draws on attendance data automatically, but it’s worth understanding what that connection means in practice:- Hours worked — Clock-in and clock-out records from the Attendance module feed directly into the liquidation’s hours calculation, removing the need for manual time entry.
- Absences and lateness — Unexcused absences or excessive lateness can trigger automatic deduction rules you configure in Payroll settings.
- Approved leave — Leave approved through the Payroll module is written back to the Attendance record so both modules stay in sync.