Batch payments, scheduled runs and approval workflows for companies paying more than a handful of counterparties. Upload a file or build a run in the app, approve once, and every payment executes together.
Each payment carries its reference through to the recipient, so reconciliation on their side does not become an email thread on yours.
What it gives you
Approve a run, not a row
One approval covers a batch, with per-payment exceptions surfaced before it executes.
References survive
The reference you set arrives with the payment, in every corridor that carries one.
Failures isolated
A rejected payment does not hold up the rest of the run, and the reason is stated per payment.
What is included
- Batch payments by upload or in-app
- Multi-step approval thresholds
- Scheduled and recurring runs
- Per-payment references carried to the recipient
- Isolated failure handling with stated reasons
- Full audit trail per run
Who it is for
Finance teams running regular supplier or contractor payments.
Questions
There is no fixed cap; large runs execute in sequence with per-payment status.
Yes. Thresholds can require a second or third approver above a set amount.