---
sourceDocument: Yokohama Finance and Supply Chain
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/source-to-pay-operations

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Finance and Supply Chain

ft:clusterId :

    - stpop

bundleId :

    - stpop

workflow :

    - Employee


---

# Approval rule types

# Approval rule types {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Approval rule types determine how approvals are created and routed during the invoice approval process.
The approval rule types determine the conditions under which approval plans are created and routed.
{#invoice-approval-rule-types__table_l5g_fn5_4wb__entry__2}

| Approval rule type | Description |
|-|-|
| Dynamic Users or Groups | Approvals are dynamically created and sent to the specified user or group. Approvals are triggered based on the purchasing user's attributes. The approval routing method is restricted to just sending approvals in parallel. |
| Managerial Job Code Hierarchy | Approvals are triggered based on the purchasing user's job code and manager's job code. The approval routing method can be parallel or sequential, and the approval decision method can be all approvers or any approver. |
| Managerial Hierarchy | Approvals are triggered based on the purchasing user's manager's hierarchy. The approval routing method can be parallel or sequential, and the approval decision method can be all approvers or any approver. |
| Specified Users or Groups | Approvals are triggered based on the specified users or groups. The approval routing method is restricted to just sending approvals in parallel. |
[Table 1. Approval rule types]

{#invoice-approval-rule-types__table_l5g_fn5_4wb}