Approvals & payouts
Common operating scenarios for Approvals & payouts. Each page answers: what to do, why, the steps and what to avoid.
| Scenario | Short answer |
|---|---|
| A payment waits for approval | Someone with payment approval rights approves it in the queue; only then is it posted. |
| Payment approval queue | Work them in the payment approval queue in Finance; creators can withdraw. |
| Delegating approvals while away | Turn on delegation and create a delegation rule; new work goes to the delegate’s Inbox. |
| Returning a request for more information | Turn on return-for-revision; the submitter edits and resubmits the same request. |
| An approval chain per request type | Configure the chain on the request type — it is the workflow pinned to that type. |
| Submitters cannot approve their own requests | Let someone else approve (maker-checker); requests with a workflow are decided via the Inbox. |
| Approving part of the OT hours | Turn on partial approval for the request type with quantity field ot_hours. |
| Requesting IT support | Create a generic request of type IT Support; it follows the type’s chain into the Inbox. |