In a default supplier approver workflow, an invoice is processed by assigning the approver specified in the supplier’s profile and then completing the approval flow logic with the single approver.
It uses the Assign default supplier approver and Final approval nodes. The first node assigns the approver for the invoice document, while the second one finishes the approval flow logic, removing the approver once approval has been given. Both of these nodes must be used in combination to create a cost object approval flow.
You can also configure this approval workflow with other approval flows.
Configuring the default supplier approval workflow
To configure a default supplier approval workflow:
| Step | Node(s) to use | Options required |
|---|---|---|
| 1a | New (status) | Submit action |
| 1b | Draft (status) | Submit action |
| 1c | Needs revision (status) | Submit action |
| 2 | Assign default supplier approver (activity) |
Requires reviewers: Select if you want to force an approver for the supplier from the supplier’s profile. Perk stops the flow if none are found. If not, if no approver is specified for the supplier, the document moves automatically to the next status. |
| 3 | Final approval (approval) | |
| 4a | Needs revision (status) | Send back action |
| 4b | Draft (status) | Recall action |
| 4c | In review (status) | No action |
Note: Nodes and actions to use after the approval node will depend on the specific scenario. The list given as an example is non-exhaustive. Remember to always connect an approval node to Need revision, Draft, Reject, and In review statuses.