An example of payment exception repair as a governed process: agents do the 8 steps, and a person signs 2 gates before anything irreversible happens. Download it, import it into your workspace, and adapt it to your systems.
Rejected and non-STP payments (bad BIC, malformed IBAN, missing purpose code, formatting NACKs) pile up in repair queues where ops analysts hand-correct 2M-6M exceptions a year, one field at a time, against the clock of cut-off windows and SLA penalties. Every manual re-key risks misrouting funds or altering a beneficiary, and a wrongly repaired high-value release is irreversible once it hits the rails. Routine formatting and reference exceptions are diagnosed, repaired against reference data, re-screened, and re-submitted straight-through with a full audit trail. Only repairs above the value threshold, those that would change beneficiary identity or account, and low-confidence ambiguous-reference cases reach a payments-ops lead, who signs the irreversible release.
The governed flow · branches, parallel work & a human on the irreversible step
sanctions clean, in-policy & high confidenceover threshold / beneficiary change / low confidencesanctions hit or un-repairable — reworkre-rejected / NACK — rework
Start
agent · low risk
Pull the rejected / non-STP payment, reject reason code and original NACK from the payment hub and exception queue
agent · low risk
Classify the exception type and diagnose root cause against reject codes, formatting rules and the original instruction
agent · medium risk
Validate and correct IBAN/BIC, resolve the purpose code and fix formatting against reference and routing data, scoring repair confidence
parallel · fan-out / join
Run sanctions re-screening and beneficiary-identity diff concurrently
agent · medium risk
Re-screen the repaired payment for sanctions hits
agent · low risk
Diff repaired payment vs. original instruction to flag any change to beneficiary identity or account
parallel · fan-out / join
Join screening + diff results once both complete
decision
Sanctions clean, and repair in-policy (below value threshold, no beneficiary change, high confidence)?
agent · medium risk
Stage the clean in-policy repair into the pre-authorized straight-through release batch
gate · human sign-off
Standing batch sign-off of the pre-authorized STP release tranche against policy limitssigns: Payment operations lead (release authority)
gate · human sign-off
Individually sign each repaired release above the value threshold, any beneficiary-identity/account change, and low-confidence ambiguous-reference repairsigns: Payment operations lead (release authority)
agent · high riskirreversible
Release the repaired payment to the rails: re-submit the corrected instruction for settlement
agent · low risk
Track ACK/confirmation and settlement status, auto-clear repaired items, and route un-repairable or re-rejected payments back to ops with the audit trail
Done
low riskmedium riskhigh riskbranch / reworkgate · human sign-off
Use this example
01
Download the file
A minctrl.process/v1 document: the graph and the hash of the process it becomes.
02
Import it in Processes
Import into Minctrl opens this example in your workspace; one click stores it as your first version. Import JSON does the same with the file, and a file changed after download is refused.
03
Connect your systems
Every connector starts in shadow: steps run, nothing leaves Minctrl until you configure a connector and switch it live.
04
Adapt it
Change signers, time limits and steps on the canvas. Each save is a new version; a running case stays on the version it started with.
Questions
How do I automate payment exception repair with Minctrl?+
Start from this example. Import the file in Processes, connect your own systems, and adapt the steps on the canvas. Agents run the reversible steps; every irreversible step waits at a gate for the role you choose. The example has 8 steps and 2 gates; you can change any of them.
Is payment exception repair in Minctrl auditable?+
Every run start, signature and change to the process is written to a hash-chained audit log your auditor can verify and export. The example is modelled on ISO 20022; whether your process meets it is a decision for your compliance team.
Does the AI decide everything?+
No. Minctrl will not make a process runnable while an irreversible step can be reached without a human gate, and one person cannot sign two gates of the same run.