Approval policies within our system are organized by product, allowing for distinct policies tailored to various types of transactions and reimbursements, among other processes.
Each policy is made of layers that must be approved sequentially for the overall approval to be granted.
Assigning Layers:
Layers within a policy can be assigned to specific individuals, roles, or positions within the management hierarchy. For instance, layers can be designated to an employee's "Manager", their "Manager's Manager", or the "Department Head".
Layers can also be assigned to employees with roles such as "Admin" or "Accountant" or specific employees.
Notification Process:
If a layer is approved, employees assigned to the subsequent layer will receive notifications to review the bill, transaction, expense, etc.
If a layer is rejected, the submitter of the bill/transaction/expense is notified, and the transaction is rejected, preventing further layers from approval.
Admins Overrides:
Admins have the authority to override decisions and approve or reject policies at any time.
An override occurs when an admin decides on a layer not assigned to them.
For example, approving or rejecting a layer assigned to a specific individual or department where the admin is not directly involved is considered an override.
Note:
Approved card requests result in automatic card creation for the employee.
Approved card fund requests result in automatic increases in the employee's spending limits.
Every event, including "approvals, rejections, overrides, and comments" is documented in the activity log of the transaction, bill, expense, etc.
If the employee who initiated the transaction, bill, reimbursement, etc., is assigned to a layer, that layer is automatically approved.
If a layer is assigned to an employee who has been deleted from the organization, the layer is removed from the policy, unless it was the final layer, in which case it is replaced with an "Any Admin" layer.