Why would a level of approval get skipped?

An approval chain is a predefined sequence of approvals based on the hierarchical structure in the employee policy configuration. It is commonly set up for various requests like expense claims, leave requests, work from home permissions, etc. These requests require approval from specific authority figures, taking into account workload and business requirements.

However, there might be instances where it appears that a request has bypassed a level in the approval chain and not followed the designated hierarchy. In this article, we will explore the potential reasons behind such occurrences.

Firstly, if the settings "Auto-approve and skip this level if no action is taken in x days" is enabled at any level of the Approval Chain, then if no action is taken by the approver in the set number of days, the approval of that approver will get skipped and go to the next approver in the approval chain. 

In case of multi-level approval chain, this option will be available for all the approval levels except for the final level of the chain.

Secondly, if the option "Auto approve (and skip) approver level, in case approver is not yet registered with Keka, not yet assigned respective role, or has been relieved" is enabled, then the approval level will be skipped if the approver is not registered on the Keka portal, or if the employee has exited from the organization, or if they are not assigned to the particular role. 

 

Like for example, if the approver is set to be 'Reporting Manager' but there is no employee assigned to the role of Reporting Manager under the Roles and Permissions then the system will auto-approve and skip that request to the next approver in the defined approval chain.

The approver added in the final approval level will not be skipped unless they are not registered in Keka.