Sanctions Screening for Payments: Screen Every Transaction Before Settlement
Your onboarding screen cleared the client months ago. That does not clear today's payment. When sanctions compliance runs as an overnight batch, or after the instruction has already settled, money moves first and the hold arrives too late for FIC or SARB scrutiny.
We embed sanctions screening into the payment pipeline so clean payments pass in milliseconds and hits auto-hold before settlement.
Sound Familiar?
These are the exact issues Heads of Payments and MLROs bring us before a payment hold workflow exists:
- Payments settle before sanctions results return, so money has already moved when a hit appears
- Overnight or batch transaction screening leaves a settlement window with no hold control
- False positives stall legitimate outbound and inbound payments for hours while analysts clear them by hand
- Hold, release, and reject decisions live in email threads instead of a compliance review queue
- FIC and SARB expect every EFT screened before processing, yet your audit trail cannot prove it payment by payment
FIC Guidance Note 8 requires every electronic funds transfer to be scrutinised against targeted financial sanctions lists, regardless of amount, for both domestic and cross-border EFTs. If your screening still runs after settlement, or only at onboarding, the payment pipeline itself is the compliance gap.
What Payment Screening Actually Does
Instruction arrives → screen before settlement → hold hits → release or reject with a full audit trail.
Payment Instruction Raised
Outbound or inbound payment hits your hub, treasury system, or remittance engine
Screen Before Settlement
Parties, banks, and narrative fields screened against sanctions lists in real time
Auto-Hold or Pass
Clear payments settle. Potential matches freeze into the compliance review queue
Release, Reject, Report
Analyst disposition with evidence, then settle, reject, or freeze and report to the FIC
Everything You Need for Transaction Screening Controls
Pre-Settlement Screening Gate
Every outbound and inbound payment instruction hits your sanctions engine before settlement. Clear payments pass in milliseconds. Hits never leave the hold queue unreviewed.
Automatic Payment Holds
Potential matches freeze the instruction automatically. Funds stay under your control until compliance releases, rejects, or escalates the case.
Compliance Review Queues
Hits land in a structured queue with party fields, list sources, match scores, and payment context attached. Your MLRO works decisions, not detective work.
Release and Reject Workflows
Documented release, reject, and escalate paths with analyst ID, timestamp, and rationale. Every disposition is inspection-ready for FIC scrutiny.
False-Positive Tuning
Secondary identifiers, known non-match suppression, and threshold calibration keep clean payments moving while true risk stays visible.
Full Payment Audit Trail
Screen result, hold event, decision, and settlement outcome write back to the payment record. Prove coverage when SARB, FIC, or correspondent banks ask.
Systems We've Wired into Payment Screening
From 6-Hour Holds to 40-Minute Reviews
How a South African remittance operator stopped overnight batch screening and put a pre-settlement gate in front of every outbound payment.
The Batch Process
- Payments screened in overnight batches after many had already left the hub
- Hits discovered next morning with no reliable freeze on funds already moved
- Analysts spent most of the day clearing false positives at roughly R250–R415 each
- Legitimate customer payouts delayed 2–8 hours while the queue cleared
- Audit packs for FIC queries rebuilt from emails and spreadsheet extracts
The Pre-Settlement Gate
- Every payment instruction screened before settlement against live list sources
- Clear payments pass in under a second; hits auto-hold with context attached
- Compliance queue shows only potential matches, not the entire book
- Release and reject decisions logged with analyst ID, rationale, and timestamps
- Inspection packs export payment by payment without reconstructing the trail
Before vs After Payment Screening Integration
How It Works
From first conversation to a live pre-settlement gate in 4–7 weeks.
Tell Us Your Rails
Which payment systems settle today, how you screen (or do not), and where hold gaps create the most risk.
Free Scoping Call
30-minute call to map pre-settlement gates, hold SLAs, release authority, and list sources your MLRO requires.
Build & Test
We wire screening into the payment path, run parallel on live volumes, and validate hold/release with compliance before cutover.
Go Live & Monitor
Switch off post-settlement batch checks. Latency, hold volumes, and disposition SLAs stay under continuous monitoring.
Frequently Asked Questions
How is payment screening different from onboarding sanctions checks?
Onboarding clears the client once. Payment screening checks every instruction before money moves, because beneficiaries, intermediaries, free-text references, and ownership can change after take-on. Cleared at onboarding does not mean this payment is clear.
How long does a payment sanctions screening integration take?
A focused pre-settlement gate with hold and release workflows typically takes 4–7 weeks from scoping to go-live. Multi-rail setups (domestic EFT, SWIFT, remittance) with custom review queues take closer to 6–10 weeks.
Will clear payments still settle quickly?
Yes. Well-tuned screening completes in under a second for clean instructions, which is the industry best-in-class latency target for wires and ACH-class rails. Only potential matches enter the hold queue. Legitimate payments are not parked overnight by default.
Does this satisfy South African FICA and SARB expectations?
FIC Guidance Note 8 and SARB Directive 1 of 2022 require accountable institutions to scrutinise all electronic funds transfers against targeted financial sanctions lists, regardless of amount, for both domestic and cross-border EFTs. Hits must be frozen and reported under section 28A. We build the operational gate and audit trail that make that obligation executable in your payment pipeline.
How do you handle false positives without delaying customers?
Industry reports put false-positive rates on cross-border payment alerts as high as 99%. We combine secondary identifiers, threshold calibration, and auto-clear rules for obvious non-matches so analysts only see genuine potential hits. Every auto-clear still leaves a documented decision trail.
How much does payment sanctions screening integration cost?
Focused pre-settlement screens with hold workflows typically start from around R40,000. Multi-rail integrations with custom compliance queues usually sit in the R60,000–R120,000 range. Most payment operations clearing hundreds of instructions a day recover the build cost within one to two quarters from analyst time alone, before counting avoided enforcement exposure.
Stop Letting Payments Move Ahead of Sanctions Checks
If your hold workflow still depends on overnight batches, email escalations, or onboarding clearance alone, you are carrying settlement risk your MLRO cannot defend under scrutiny.
Tell us which payment rails you run, how screening works today, and where false positives or late hits hurt most. We will show you exactly how a pre-settlement sanctions gate would sit in your pipeline.