Important: This article is about the Dext Payments Beta, an upcoming feature currently in development.
Overview
Use Approval Workflows to control who reviews and approves a payment run before it’s submitted.
Workflows help you enforce spending thresholds, keep payments secure, and maintain strong internal controls. You can configure one or more approvers, add staged approvals, and apply rules by amount or currency.
Who can do what
Access approvals settings: Payment Owners, Admins, and Standard Users with Payments access can open the Approvals settings.
Create or edit workflows: Only Payment Admins and Standard Users with Payments access can create or modify approval workflows (as defined in Payment Permissions). This ensures that only authorized users control who approves payment runs.
Important: Changes to workflows apply to future payment runs only. Existing runs continue under their original configuration.
Where to manage payment run approvals
Payment Owners, Admins, and Standard Users with Payments access can set up and manage approval workflows directly from:
Business Settings > Approvals > Payment Runs
Business Settings > Payments > Permissions > Approvals
Create a payment approval workflow
Open Approvals from Business Settings.
Create a new workflow for Payment Runs.
Choose your approval logic (see options below).
Add approvers and any conditions (amount, currency, sequence).
Save.
The workflow automatically applies to new payment runs that meet your conditions.
Approval options you can combine
Single or multi‑approver: Require one approver or several.
Multi‑tier (staged) approvals: Collect approvals in sequence (e.g., Tier 1 then Tier 2).
Conditional thresholds: Trigger extra approval only when a payment run is ≥ a set amount (e.g., £1,000).
Parallel vs. sequential: Have all approvers act at the same time (parallel) or in a defined order (sequential).
Currency filters: Apply the workflow to all currencies or only specific ones (e.g, GBP, EUR, USD).
Managing payment approval workflows
After creation, workflows can be:
Enabled or disabled as needed.
Edited to change approvers, thresholds, or conditions.
Only Payment Admins and Standard Users with Payments access (as defined in Payment Permissions) can create or modify workflows. This ensures only authorised users can control who approves payment runs.
Important: Any changes to workflows apply to future payment runs only. Existing payment runs will continue under their original workflow configuration.
How approvals and notifications work
When a payment run needs approval:
Assigned approvers receive an email and an in‑app notification.
If a notification fails to deliver, it’s automatically re‑triggered.
If an approver doesn’t respond within your set time window (e.g., a mobile delivery timeout), an authorized user can manually re‑send notifications from the Web App (requires appropriate payment permissions).
Approvers can:
View payment run details and supporting info
Edit the run by removing invoices (with a reason)
Modify payment reference
Approve or reject (with a reason)
Approval vs. submission (funds and queueing)
Approval doesn’t depend on wallet balance. Approvers can review and approve even if the wallet doesn’t yet have enough funds.
Submission is blocked until sufficient funds are available. You’ll see a clear warning if funds are insufficient.
An authorized user can submit the payment run for processing once it has been approved and sufficient funds are available in the wallet.
Submit an approved payment run
When your wallet is funded:
An authorized user submits the payment run to the payment provider (AWX).
Strong Customer Authentication (SCA) is required at submission. Follow the on‑screen prompts to complete SCA.
After SCA succeeds, the payment run is sent for processing.
Tip: If submission is blocked, check wallet balance first, then complete SCA.
Best practices
Review workflows regularly to keep the right approvers in place.
Use thresholds to fast‑track smaller payments while adding checks for larger ones.
Audit permissions so approvers have the correct access under Roles and Permissions.
FAQs
Do I need funds to approve a payment run?
No. Approval can happen without available funds. Funds are only required to submit the run for processing.
Why can’t I submit an approved run?
Most often, it’s an insufficient wallet balance or SCA not completed. Fund the wallet and finish SCA, then try again.
Can I change a workflow for a run that’s already in progress?
No. Workflow changes only apply to future payment runs.
Who gets approval notifications?
The designated approvers on the workflow. If delivery fails, notifications are automatically retried, and authorized users can manually resend from the Web App.
Payments Beta Videos
Payments Beta: Enabling for client or business account | |
Payments Beta: Setup and KYC | |
Payments Beta: Managing Roles and Permissions | |
Payments Beta: Building Approval Workflows | |
Payments Beta: Making Your First Payment | |
Payments Beta: Funding Your Wallet | |
Payments Beta: Registering a Device for Payments Authentication | |
Payments Beta: End-to-End Setup: Payment Runs for Accounting Teams |