Skip to main content

Payment requests with a configured approval workflow

Payment-request entry and approval must be enabled and accessible to the requester and approvers.

Check whether payment requests are enabled and accessible to the current role.

Use the payment-request operation offered from the source purchase document or the request list provided by your administrator. If neither is available, confirm the feature setup and access before entering requests. Cash forecast is used later for funding allocation; an error opening it must be resolved before that stage.

Procedure​

  1. Open the available request list or create a request from the supplier invoice/order or other supported source. Choose the actual operation, such as supplier payment or employee advance.
  2. Check company, payee, source settlement object, contract and payment purpose. Enter requested amount, currency and expected payment date.
  3. Review payment method, settlement currency and any exchange basis separately. Inspect the cash flow item and priority rather than trusting inherited defaults.
  4. Save in the unapproved state and submit through the configured approval route. An ordinary requester should not bypass approval by setting a final state.
  5. The responsible approver reviews purpose, documents, limits and timing in the approval work list, then approves, rejects or returns it for correction.
  6. The treasurer selects the funding account/cash desk and date in the available planning workspace, then authorizes payment according to assigned rights.
  7. Generate the outgoing payment from the approved request and verify its amount and basis. Reconcile request paid/remaining amount after actual payment.

Check the result​

Approval history identifies the authorizer and the generated payment is linked to the intended request without exceeding its remaining amount.

If the result differs​

Request commands are unavailable: check feature configuration and user rights with the administrator. Cash forecast fails to open: retry once; if the unexpected-error page persists, record it and contact support without treating requests as paid.