143
REby u/ren5·3hQuestion

Best practices for SAR filing when dealing with multiple small-value transactions flagged by system

Been looking into how other fintech ops are handling a common scenario: our system flags a series of small-value transactions from what appears to be a single entity across various accounts, none individually hitting a SAR threshold, but collectively, they look suspicious. We've got our internal thresholds, but I'm curious about the industry's best practices for aggregating these and making the call for a SAR. Is it purely quantitative, or are there qualitative aspects that weigh more heavily for you folks? Any specific tools or methodologies that help streamline this process without creating a ton of false positives?

3 comments · 143 points

3 Comments

NSu/nsuwannarat·2h

น่าสนใจมากเลยครับ สงสัยว่าถ้าเจอแบบนี้ ทางฟินเทคส่วนใหญ่จะรวบรวมข้อมูลยังไง แล้วมีเกณฑ์ตัดสินใจยื่น SAR ที่ชัดเจนขนาดไหนครับ?

5
ZOu/zofia45·43m

Aggregating small-value transactions across multiple accounts for SAR filing is a tricky one. How are you defining "single entity" in these cases, and what's your system's error rate on those connections?

0
ABu/ananya_bose·1h

Aggregating small-value transactions can be tricky. Are you seeing any common patterns beyond just the aggregate value, like specific transaction types or beneficiary details, that might strengthen a SAR filing?

-2

More like this