Approval Is Controlled By Its Type

The overpayment process type contains the rules that define if and how an overpayment process is approved. If an overpayment process type does not reference an approval details, the related overpayment processes do not require third-party approval before they proceed. If an overpayment process type references approval detail, the approval hierarchy defines if the overpayment process requires approval and who the authorized approvers are. For example, an overpayment process type can be configured with the following approval hierarchy:

The overpayment process type includes a setting to indicate if the overpayment process requires Single approval or Multiple levels of approval. If there is an overpayment process for $200 and the overpayment process type is configured for Single approval, only one approval is needed by the "level 2 approvers role". If instead the overpayment process type for this record indicates Multiple levels of approval: first a user that belongs to the "level 1 approvers role" must approve the overpayment process; afterwards, the overpayment process must be approved by a user that belongs to the "level 2 approvers role".

Note: Separation of Duties. The base product logic includes validation that prevents a user from approving an overpayment process if that user was the one that created the record or if that user already approved a previous approval "level" (for approvals that define Multiple levels).
Note: Different Approval Logic. If an implementation has approval logic that is not based on threshold amount but on some other condition, the base Determine Approval algorithm on the Standard Overpayment Process business object would need to be inactivated and a different Determine Approval algorithm is required. If no configuration is required for the custom approval logic, configuring the overpayment process type using the base Standard Overpayment Process Type business object may still be possible. Simply leave the threshold details blank.