About custom approvals for Purchasing

Apply approval rules based on the document number.

For example, route transactions with specific document number patterns to a designated approver.

Apply approval rules based on the document ID.

For example, route transactions created from a specific transaction definition to a specialized approval path.

Apply approval rules based on the transaction subtotal.

For example, apply approval thresholds based on the transaction amount before taxes, fees, or other adjustments.

Apply approval rules based on the transaction total

For example, route transactions with a transaction total greater than $25,000 to executive approval.

Approve based on transaction subtotal.

For example, apply approval thresholds based on the transaction amount before taxes, fees, or other adjustments.

Approve based on transaction total.

For example, route transactions with a transaction total greater than $25,000 to executive approval.

Route transactions created by specific users or teams to a designated approver.

For example, route transactions created by temporary staff to a manager for review.

Require review when a transaction has been modified by specific users before approval.

For example, route transactions modified after initial submission to an additional approver.

Approve based on when the transaction is due.

For example, require expedited approval when payments are due within seven days.

Route transactions in a particular processing state for additional review.

Apply approval rules based on the transaction state.

Apply different approval paths based on the status of a transaction.

Apply approval rules based on the transaction status.

Apply approval rules based on the reference number.

Route transactions with a specific reference number prefix to a designated approval group.

Apply approval rules based on the supplier document number.

Route supplier invoices with specific supplier reference numbers for additional review.

Apply approval rules based on the payment term assigned to the transaction.

Route transactions with extended payment terms to Finance for review.

Apply approval rules based on the message entered on the transaction.

Route transactions containing specific business justification text for additional review.

Approve based on the shipping method.

Route overnight or priority shipments to an Operations manager for review.

Apply approval rules based on the company's base currency.

Route transactions entered in a base currency used by a specific entity to a designated approver.

Approve based on the currency of the transaction.

Route transactions in foreign currencies to Finance for review.

Approve based on the project of the transaction.

Route transactions associated with a specific project to the project manager.

Project is available as both a header-level and line-level field. Use the header-level field to evaluate the transaction's overall project and the line-level field to evaluate the project assigned to an individual transaction line.

Route transactions from specific suppliers to designated approvers.

Route approvals based on Supplier name.

For example, route transactions from a strategic supplier to a dedicated approval group.

Route approvals based on supplier payment priority.

For example, route transactions from suppliers with a payment priority of High to a senior approver.

Route approvals based on Supplier type.

For example, route transactions from suppliers classified as Contractors or Professional Services to specialized approvers.

Choose to require additional approval when transactions involve suppliers currently marked as On Hold.

Route transactions for one-time suppliers through an additional approval process.

Route approvals based on the preferred payment method of the supplier.

For example, route transactions paid by wire transfer to Treasury for review before payment.

Route transactions based on item of the line item.

For example, route purchases of laptops, servers, or software subscriptions to the IT department.

Route transactions based on the item description.

For example, route purchases containing specific keywords or descriptions to specialized approvers.

Route transactions containing specific notes or business justification text for additional review.

Apply approval rules based on the unit of measure assigned to the line item.

For example, route purchases measured in a specific unit of measure to a designated approver.

Apply approval rules based on the unit quantity assigned to the line item.

For example, route purchases measured in a specific unit quantity to a designated approver.

Apply approval rules based on the extended price of the line item.

Require approval when the total value of a line item exceeds a specified threshold.

Apply approval rules based on the unit price of the line item.

For example, require approval when the unit price exceeds a defined amount, such as $1,000.

Apply approval rules based on the extended price in the transaction currency.

Require approval when a line item's value exceeds a defined threshold in the transaction currency.

Apply approval rules based on the user who created the transaction line.

Route lines created by specific users or teams to a designated approver.

Apply approval rules based on the user who last modified the transaction line.

Require review when a transaction line has been modified after initial submission.

Approve based on warehouse of the line item.

For example, route lines associated with Warehouse D to the warehouse manager.

Approve based on department of the line item.

For example, route lines assigned to the IT department to the IT director.

Approve based on the task.

Require approval from the task lead when purchases are assigned to a specific project task.

Apply approval rules based on whether the transaction line is billable.

Route billable expenses to project accounting before approval.

Apply approval rules based on Form 1099 reporting requirements.

Route transactions subject to Form 1099 reporting to Finance for review.

Apply approval rules based on the Form 1099 type assigned to the line item.

Route transactions mapped to specific 1099 reporting types for additional review.

Apply approval rules based on the Form 1099 box assigned to the line item.

Route transactions mapped to specific 1099 reporting boxes for additional review.

Apply based on the customer of the line item.

Require review for purchases associated with strategic or high-value customers.

Approve based on the supplier of the line item.

For example, route purchases from specific suppliers to specialized approvers.

Apply based on the employee.

Route employee-related purchasing requests to the employee's manager.

Apply based on the task.

Apply different approval paths for capital expenditures versus operating expenses.

Approve based on item group of the line item.

For example, route capital equipment purchases to Operations for review.

Approve based on location of the line item.

Route purchases associated with a specific office or business location to a local manager.