The name of the user creating the approval request. Setup users to approve documents at a certain amount. Users unable to approve any of the documents need not be setup. Select the username from the drop-down list.

Description for the transaction approval.

The type of transaction that requires approval.

The department of the user that must approve the transaction. Select the department from the drop-down list.

The site from which the transaction approval routing is created. By default, the logged in site is displayed and is a read-only field. For Interco, users can select a preferred site from the drop-down list.

The location within the enterprise linked to the site selected. This field is activated only when a site other than Interco is selected. If the site Interco is selected, this field remains deactivated or disabled. Select the location from the drop-down list.

The maximum amount up to which the approver can approve a transaction. By default, the preferred currency is USD. Users can configure the preferred currency under Setup ➜ Currencies ➜ Currencies/Currency Rates.

This defines the escalation period for a transaction when the designated next approver does not approve the requisition within a defined timeline. Enter the time period, in days, observed prior to sending to next available approver if the document has not yet been approved.

The total number of days allocated for the user/approver to approve the transaction. Users can enter up to a maximum of 10 days. If the transaction/requisition is not approved within the allocated bump period, the transaction is automatically approved or moved to the next step in the process (status changes from Pending to Approved) or sent to the next level approver for the approval.

Enabling this flag allows the user/approver to mandatorily approve the document/transaction.

When this option is enabled for a user, any transaction assigned to the user will require the decision by this user to be mandatory. Without the approval of this approver, no other user can mark their decision. All other approvers can only view the particular transaction.

If Skip Level (at user level) is enabled and This Approver Requied is also enabled, the latter takes the precedence than the former.

If Skip Level Approval (System Preferences setting) is enabled as Yes, then This Approver Required (at user level) loses its predominance. Any higher level approver will be allowed to modify the statement pending with lower level approvers.

The skip level approver status. For example, Yes. When a user in the approval routing module is enabled with Skip Level option, the decision of this user is overridden by the user with higher approval limit than the current user. This is used to enforce a multiple approval requirement for a level where two or more approvers are necessary for a specific transaction type, location, and site combination. This setting will prevent a transaction from bump escalation.

Flag that indicates whether the transaction approval routing is active or inactive. By default, this flag appears toggled on (active) when creating a transaction approval routing and cannot be toggled off. This flag can be toggled off to deactivate the transaction approval routing when opened for modification. Once toggled off, the deactivated transaction approval routing will be displayed on the Transaction Approval Routing page only if the Show Active Only flag is toggled off.

The status of the substitute approver. For example, Yes.

Enable this flag to add a substitute approver. Users can delegate their approvals to another user or substitute approver who can approve the pending requisitions in the absence of first user. Enabling this flag to Yes displays the Substitute Approver section.