Release the payment file with every required check complete.
Duvo checks payees, bank details, approvals, duplicates, holds, and supporting records before treasury releases the bank file.
Checked
Before release
Each payment is tested against the agreed payee, approval, duplicate, and hold controls.
Separated
Exceptions from routine
A small number of held payments does not force the team to rebuild the whole payment run.
Recorded
Release decision
Every check, hold, approval, removal, and final bank-file change remains available for review.
Duvo establishes the baseline and validates the opportunity on your records before a live scope is agreed. No customer result is claimed for this solution yet.
Every held payment shows the failed control and supporting evidence.
The product view brings the proposed payment, payee, bank details, invoice history, approvals, holds, and release decision into one record.
Payment Run Control · Illustrative
Payee details, approvals, duplicates, holds, and supporting records are checked before the bank file is released.
24
5
2
4
3
0
10
Showing 5 of 24 cases
- 1
Approval
Exceptions pause for the named owner
Each exception carries the source records, applied rule, recommended action, and the person authorised to decide.
- 2
Release status
Release status is visible before the action
Each payment shows the checks completed and the exact hold or approval that must be resolved before bank release.
The final payment check is compressed into the release window.
Treasury and AP must confirm thousands of payments against several control sources before the bank deadline, often with little time to investigate exceptions.
The payment proposal brings several risks together.
Duplicate invoices, changed bank details, payment holds, missing approvals, and unusual amounts all need different checks.
Evidence sits outside the payment file.
The approval, invoice history, supplier change, and exception reason may sit across SAP, email, and separate control logs.
Review time is fixed by the bank cut-off.
The team either resolves the exception quickly, removes the payment, or delays the file while suppliers wait.
Check the proposed payments before the bank file leaves finance.
Routine payments clear the agreed controls. Anything unusual pauses with the evidence and the owner who can release or remove it.
- 01Intake
Read the payment proposal.
Duvo reads the proposed bank file, payment run, supplier records, invoices, approvals, and current payment holds.
- 02Check
Run the required controls.
Payee, bank change, duplicate, amount, approval, hold, and supporting-record checks run against the approved policy.
- 03Hold
Separate the exceptions from routine payments.
Payments that fail a check are held with the reason and evidence, while the rest of the file can continue.
- 04Approve
Send each exception to the right authority.
Treasury, AP, or the relevant business owner can release, remove, or investigate the payment without rebuilding the history.
- 05Release
Create the controlled bank file.
Approved payments proceed, removed payments remain on hold, and the release record shows every check and decision.
Treasury keeps authority over bank release.
Bank changes receive a separate check
A new or changed account follows the approved verification path before the payment can clear.
Release rights do not move to Duvo
The named treasury authority makes the final release decision under the customer’s existing controls.
The final file can be reconciled
Every payment added, held, removed, or released is tied back to the source proposal and decision.
Work across the payment controls already in place.
Duvo can read the ERP payment proposal, supplier records, approvals, control lists, and bank-file workflow without replacing treasury systems.
Works across
SAP payment runs, AP ledgers and invoice records, supplier master and bank changes, approval workflows, payment holds and block lists, bank-file tools, treasury workstations, email and shared inboxes
Contracted guarantee
5x ROI, guaranteed.
If measured results fall below 5x the total proposal price, the whole contract is free.
What teams ask about Payment Run Control
When does Payment Run Control run?
A payment proposal is ready for review before the bank file is released.
Who owns Payment Run Control?
Treasury, AP, financial controls, shared services
Which systems can Duvo work across?
Duvo can read the ERP payment proposal, supplier records, approvals, control lists, and bank-file workflow without replacing treasury systems. Typical sources include SAP payment runs, AP ledgers and invoice records, supplier master and bank changes, approval workflows.
Where does a person stay in control?
Bank changes receive a separate check: A new or changed account follows the approved verification path before the payment can clear.