Approval workflow: every leave request goes to the right person in the right order
Approval matrix: location-based approval workflow and approval standard
Approval standards show a location's standard approval topics and their scope; today, the standard topic is the leave request workflow. The topic's approval steps and active status are updated here.
Approval hierarchy: approver setup by role, job title, department and duty
An approval template is created; steps are added, edited or deleted. The approver is selected from the department tree, with helper lists for job title, position and shift; this builds a multi-stage approval chain.
Pending approvals on web and mobile: a digital approval process
Approvals the user must decide on are listed separately for web and mobile. The department supervisor switches to manager mode on their phone and opens leave requests routed by the approval matrix on the Pending Requests (Bekleyen Talepler) screen.
Approval routing: approve, reject with a reason or cancel the process
At each step, an approve or reject decision is made; the approval process can be canceled when necessary. On mobile, a reason of at least three characters is required for rejection, and the reason appears in the result notification sent to the employee.
HR approval workflow: notification, leave balance and timesheet after approval
With the final approval, the leave is confirmed and deducted from the balance; a leave notification arrives on the employee's phone and the employee acknowledges receipt. The acknowledgement of receipt is not a leave approval or an electronic signature; the screen states this clearly. Approved leave is written to the work schedule and the timesheet is recalculated.
Overtime authorization workflow and policy revision approval
Overtime requests are approved in bulk by an authorized user in Overtime Management (FM Yönetimi) and reflected in the timesheet; the employees and departments for which requests can be opened are filtered by the user's permission scope. A change to working-time rules is opened as a revision; it is sent for approval, approved or rejected, and put into effect.
Request approval system: which requests go through the approval workflow?
Today the Pulsar HRM approval workflow handles leave requests as its standard subject: the request passes through the steps in the location's approval matrix in order. Overtime requests are approved by an authorized user in Overtime Management (FM Yönetimi); a change to working-time rules is opened as a revision and sent for approval.
Frequently asked questions
What is an approval matrix?
An approval matrix is a structure that defines which steps a request goes through and whose approval it needs. In Pulsar HRM, it is kept per location; at each step, the approver is determined by role, job title, department or position.
How does a leave approval hierarchy work?
The employee's leave request lands on the first step of the approval matrix; the steps decide in order. With the final approval, the leave is confirmed, deducted from the balance and a leave notification is sent to the employee; if rejected, the reason is communicated to the employee.
Who approves leave in the approval chain?
The person in the role, job title, department or position defined for that step in the approval matrix gives the approval. The user who must decide sees the request in pending approvals on the web or in the mobile app.
How to set up a multi level approval workflow?
First, a topic is selected in the location's approval standard, then steps are added to the approval template, and each step's approver is determined from the department tree, job title, position or shift list. Steps can be edited or deleted later.
What happens if a leave request is rejected?
A rejection reason is required; on mobile, a request cannot be rejected without at least three characters. The employee sees the result, together with the rejection reason, in the notification on their phone.
Who approves overtime?
In Pulsar HRM, overtime requests are approved one by one or in bulk by an authorized user with "Approve OT" ("FM Onayla") in Overtime Management (FM Yönetimi). Approved overtime is reflected in the timesheet and, if notifications are enabled, arrives on the employee's phone.
Is mobile approval of leave possible?
Yes. The department supervisor switches to the manager account on their phone, opens the requests routed by the approval matrix on the Pending Requests (Bekleyen Talepler) screen, and approves them or rejects them with a reason.
How to set up a department-based approval workflow?
For example, the department supervisor is added as the first step in the leave request's approval template; the employee's request lands on this person's Pending Requests (Bekleyen Talepler) screen, and with the final approval the leave is confirmed. If needed, a second step is added by department, job title or position.
Where are pending approvals shown in the electronic approval system?
Approvals the user must decide on appear in the pending approvals list on the web, and on the Pending Requests (Bekleyen Talepler) screen in manager mode on mobile.
Can an approval process be cancelled?
Yes. An approval process that has started can be canceled by an authorized user; the cancellation is written to the approval record.
What is an approval workflow system?
It is the structure that moves a request through defined steps in order, with an approval at each step. In Pulsar HRM the steps are defined in the location's approval matrix; the approver is set by role, job title, department or duty, and the decision is made on the web or in the mobile app.
Let's talk about Pulsar HRM and your own processes.
Start with PDKS; add the field and enterprise layers as you need them.