Request-to-payment process

Context

Employees submit requests in Approvals; each follows its request type chain; money parts (advances, settlements) are paid through the same payment approval gate as every other payout and posted to the right accounts.

Who is involved

• Employee: submit, settle
• Approvers: per request type chain
• Accountant: disburse advances, settle
• Payout approver: payments:approve

Apps & switches to turn on

• Request & Approvals, Finance, Employee Service
• Switches: return_for_revision, partial_approval, fulfillment_stage, approval delegation

Flow

1. Request (type catalog) → approval chain
2. Approve / return for revision
3. Advance payout (debit 141) via the payout queue
4. Settlement → return surplus or top-up

Initial setup

1. Create request types and chains.
2. Enable the extension flags you need.
3. Grant payout approval rights.

Daily / monthly operations

• Daily: work the Inbox and payout queue.
• Monthly: review unsettled advances.

Common scenarios

• An approval chain per request type
• Returning a request for more information
• Employee advances and settlement
• Payment approval queue
• A payment waits for approval
• Submitters cannot approve their own requests
• Delegating approvals while away

AI assistants

• Assistants can summarise a request; approval decisions are always made by people.