Information About Approval Layer Process & Logic

    Last updated on 

    Introduction

    This article outlines the approval flow logic used in Staffinc Suite for multi-layered approval scenarios—such as leave, overtime, and dispute requests. It emphasizes that a request’s status is only considered final when it reaches and receives a decision from the final approver. Notably, this final approver holds ultimate authority and can override decisions made by previous approver layers.

    Creation of Approval Rule

    Core Logic & Process Flow

    1. Multi-Layer Approval Structure
      • Staffinc Suite allows setting up hierarchical approval chains, named Approval Rules, where each request may pass through multiple approval levels (e.g., Supervisor → Manager → HR) depending on the configuration.
      • Default Approvers can be configured in each Approval Rule.
        • They can:
          • View all requests across all layers.
          • Take approval actions regardless of which layer the request is currently in.
        • This role is intended for HR Admins or Operational Supervisors who need broad visibility and control over workflows.
    2. Request Initiation
      • When an employee submits a leave, overtime, or dispute request, it enters into the defined approval chain and appears as Pending Approval in the system.
    3. Sequential Review by Layers
      • Each approver in the chain must take action—approve or reject—before the request advances to the next layer.
      • If an approver approves, the request is forwarded to the next connector in the chain.
      • If an approver rejects, the request is immediately finalized as Rejected, regardless of whether subsequent approvals were pending.
    4. Final Approver’s Authority
      • Only after the request is approved by every layer, including the final approver, is the request status truly finalized.
      • The final approver has absolute decision-making power—even if earlier approvers approved—meaning they can overturn those decisions (e.g. reject despite earlier approval).
    5. Finalization Effects Upon Approval
      • Leave: If approved by final layer:
        • For paid leave: Deduct leave balance and update attendance status to “Paid Leave.”.
        • For unpaid leave: No balance deduction, but status updates to “Unpaid Leave”.
      • Overtime: Functions similarly—once finalized, the approved overtime duration is reflected in attendance and payroll as appropriate.
      • Dispute: Upon final approval, the attendance records are corrected or updated, based on the dispute resolution.

    Why This Matters

    • Ensures clear governance, with each decision traceable through the approval chain.
    • Prevents premature finalization—only the final approver can truly confirm the request outcome.
    • Maximizes transparency, with a documented trail and potential for reversal by the final layer, maintaining control and accountability.

    Reference for More Detail

    For a detailed walkthrough of the leave approval process, including screenshots and step-by-step navigation, refer to: