DataWorld-Bench: shard p000384 case_narratives (10530 files/dir > 10k limit) into shard-00..10; contents byte-identical (part 21)
Browse filesThis view is limited to 50 files because it contains too many changes. See raw diff
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004221.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004222.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004223.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004224.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004225.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004226.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004227.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004228.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004229.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004230.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004231.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004232.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004233.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004234.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004235.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004236.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004237.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004238.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004239.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004240.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004241.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004242.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004243.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004244.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004245.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004246.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004247.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004248.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004249.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004250.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004251.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004252.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004253.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004254.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004255.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004256.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004257.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004258.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004259.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004260.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004261.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004262.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004263.txt +1 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004264.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004265.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004266.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004267.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004268.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004269.txt +18 -0
- dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004270.txt +18 -0
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004221.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004221
|
| 2 |
+
Opened: 2024-08-09 Investigator: INV-007 Severity: high
|
| 3 |
+
Customer: CUST-01279 — distribution operating in WA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a distribution licensed in WA. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_threshold generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004222.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004222 opened 2019-03-25 re: customer CUST-01280 (testing_lab, WA). Alert type: cash_threshold. 1 alert(s) reviewed. Risk tier at open: high. Investigator: INV-002. Suspicious activity identified consistent with cash_threshold. SAR filed. Severity: critical. [REDACTED] account activity reviewed. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004223.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004223 opened 2019-12-04 re: customer CUST-01280 (testing_lab, WA). Alert type: structuring. 1 alert(s) reviewed. Risk tier at open: high. Investigator: INV-004. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004224.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004224 opened 2020-01-06 re: customer CUST-01280 (testing_lab, WA). Alert type: structuring. 1 alert(s) reviewed. Risk tier at open: high. Investigator: INV-001. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004225.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004225
|
| 2 |
+
Opened: 2022-03-21 Investigator: INV-006 Severity: high
|
| 3 |
+
Customer: CUST-01280 — testing_lab operating in WA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a testing_lab licensed in WA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type structuring generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004226.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004226 opened 2020-02-05 re: customer CUST-01281 (dispensary, WA). Alert type: cash_threshold. 1 alert(s) reviewed. Risk tier at open: prohibited. Investigator: INV-006. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004227.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004227 opened 2020-10-05 re: customer CUST-01281 (dispensary, WA). Alert type: high_risk_jurisdiction. 1 alert(s) reviewed. Risk tier at open: prohibited. Investigator: INV-004. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004228.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004228 opened 2020-12-03 re: customer CUST-01281 (dispensary, WA). Alert type: high_risk_jurisdiction. 1 alert(s) reviewed. Risk tier at open: high. Investigator: INV-004. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004229.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004229
|
| 2 |
+
Opened: 2021-08-04 Investigator: INV-002 Severity: critical
|
| 3 |
+
Customer: CUST-01281 — dispensary operating in WA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a dispensary licensed in WA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type structuring generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004230.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004230
|
| 2 |
+
Opened: 2021-12-02 Investigator: INV-008 Severity: high
|
| 3 |
+
Customer: CUST-01281 — dispensary operating in WA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a dispensary licensed in WA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_threshold generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004231.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004231
|
| 2 |
+
Opened: 2022-10-04 Investigator: INV-008 Severity: high
|
| 3 |
+
Customer: CUST-01282 — cultivation operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a cultivation licensed in CA. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_intensity_spike generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004232.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004232
|
| 2 |
+
Opened: 2023-02-06 Investigator: INV-004 Severity: high
|
| 3 |
+
Customer: CUST-01282 — cultivation operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a cultivation licensed in CA. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cross_state_transfer generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004233.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004233
|
| 2 |
+
Opened: 2023-04-11 Investigator: INV-009 Severity: critical
|
| 3 |
+
Customer: CUST-01282 — cultivation operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a cultivation licensed in CA. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_threshold generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004234.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004234
|
| 2 |
+
Opened: 2022-12-30 Investigator: INV-007 Severity: high
|
| 3 |
+
Customer: CUST-01283 — manufacturing operating in NV.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in NV. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_deposit_frequency generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004235.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004235
|
| 2 |
+
Opened: 2023-11-07 Investigator: INV-001 Severity: high
|
| 3 |
+
Customer: CUST-01283 — manufacturing operating in NV.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in NV. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_intensity_spike generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004236.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004236
|
| 2 |
+
Opened: 2024-03-18 Investigator: INV-003 Severity: high
|
| 3 |
+
Customer: CUST-01283 — manufacturing operating in NV.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in NV. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type high_risk_jurisdiction generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004237.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004237
|
| 2 |
+
Opened: 2024-04-02 Investigator: INV-007 Severity: high
|
| 3 |
+
Customer: CUST-01283 — manufacturing operating in NV.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in NV. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type negative_news generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004238.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004238
|
| 2 |
+
Opened: 2024-06-07 Investigator: INV-010 Severity: high
|
| 3 |
+
Customer: CUST-01283 — manufacturing operating in NV.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in NV. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_intensity_spike generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004239.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004239
|
| 2 |
+
Opened: 2024-07-05 Investigator: INV-003 Severity: high
|
| 3 |
+
Customer: CUST-01283 — manufacturing operating in NV.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in NV. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_intensity_spike generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004240.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004240
|
| 2 |
+
Opened: 2024-10-07 Investigator: INV-010 Severity: high
|
| 3 |
+
Customer: CUST-01283 — manufacturing operating in NV.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in NV. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_threshold generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004241.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004241
|
| 2 |
+
Opened: 2022-10-27 Investigator: INV-006 Severity: moderate
|
| 3 |
+
Customer: CUST-01284 — testing_lab operating in CO.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a testing_lab licensed in CO. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_intensity_spike generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004242.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004242
|
| 2 |
+
Opened: 2023-01-16 Investigator: INV-009 Severity: critical
|
| 3 |
+
Customer: CUST-01284 — testing_lab operating in CO.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a testing_lab licensed in CO. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type structuring generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004243.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004243
|
| 2 |
+
Opened: 2023-03-03 Investigator: INV-008 Severity: high
|
| 3 |
+
Customer: CUST-01284 — testing_lab operating in CO.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a testing_lab licensed in CO. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_intensity_spike generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004244.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004244
|
| 2 |
+
Opened: 2023-06-16 Investigator: INV-005 Severity: high
|
| 3 |
+
Customer: CUST-01284 — testing_lab operating in CO.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a testing_lab licensed in CO. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type nighttime_activity generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004245.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004245
|
| 2 |
+
Opened: 2023-10-25 Investigator: INV-001 Severity: high
|
| 3 |
+
Customer: CUST-01285 — event_organizer operating in WA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a event_organizer licensed in WA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_threshold generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004246.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004246
|
| 2 |
+
Opened: 2023-11-17 Investigator: INV-006 Severity: high
|
| 3 |
+
Customer: CUST-01285 — event_organizer operating in WA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a event_organizer licensed in WA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_intensity_spike generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004247.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004247
|
| 2 |
+
Opened: 2024-03-11 Investigator: INV-003 Severity: critical
|
| 3 |
+
Customer: CUST-01285 — event_organizer operating in WA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a event_organizer licensed in WA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_threshold generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004248.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004248
|
| 2 |
+
Opened: 2024-11-18 Investigator: INV-001 Severity: high
|
| 3 |
+
Customer: CUST-01285 — event_organizer operating in WA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a event_organizer licensed in WA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type structuring generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004249.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004249 opened 2020-03-05 re: customer CUST-01287 (delivery, WA). Alert type: structuring. 1 alert(s) reviewed. Risk tier at open: high. Investigator: INV-001. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004250.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004250 opened 2020-11-09 re: customer CUST-01287 (delivery, WA). Alert type: velocity. 1 alert(s) reviewed. Risk tier at open: high. Investigator: INV-004. Suspicious activity identified consistent with velocity. SAR filed. Severity: critical. [REDACTED] account activity reviewed. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004251.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004251
|
| 2 |
+
Opened: 2021-08-02 Investigator: INV-007 Severity: high
|
| 3 |
+
Customer: CUST-01287 — delivery operating in WA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a delivery licensed in WA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type velocity generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004252.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004252
|
| 2 |
+
Opened: 2021-11-08 Investigator: INV-001 Severity: high
|
| 3 |
+
Customer: CUST-01287 — delivery operating in WA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a delivery licensed in WA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type velocity generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004253.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004253
|
| 2 |
+
Opened: 2021-03-16 Investigator: INV-001 Severity: high
|
| 3 |
+
Customer: CUST-01288 — cultivation operating in NV.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a cultivation licensed in NV. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type structuring generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004254.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004254
|
| 2 |
+
Opened: 2021-11-02 Investigator: INV-002 Severity: high
|
| 3 |
+
Customer: CUST-01288 — cultivation operating in NV.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a cultivation licensed in NV. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type structuring generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004255.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004255 opened 2019-03-18 re: customer CUST-01289 (distribution, CA). Alert type: cash_threshold. 1 alert(s) reviewed. Risk tier at open: high. Investigator: INV-004. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004256.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004256 opened 2019-05-14 re: customer CUST-01289 (distribution, CA). Alert type: cash_threshold. 1 alert(s) reviewed. Risk tier at open: high. Investigator: INV-003. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004257.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004257 opened 2020-10-12 re: customer CUST-01289 (distribution, CA). Alert type: structuring. 1 alert(s) reviewed. Risk tier at open: high. Investigator: INV-007. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004258.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004258 opened 2020-12-14 re: customer CUST-01289 (distribution, CA). Alert type: cross_state_transfer. 1 alert(s) reviewed. Risk tier at open: high. Investigator: INV-005. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004259.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004259
|
| 2 |
+
Opened: 2022-05-30 Investigator: INV-005 Severity: high
|
| 3 |
+
Customer: CUST-01289 — distribution operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a distribution licensed in CA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cross_state_transfer generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004260.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004260
|
| 2 |
+
Opened: 2022-07-06 Investigator: INV-004 Severity: critical
|
| 3 |
+
Customer: CUST-01289 — distribution operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a distribution licensed in CA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_threshold generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004261.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004261
|
| 2 |
+
Opened: 2023-01-10 Investigator: INV-006 Severity: high
|
| 3 |
+
Customer: CUST-01289 — distribution operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a distribution licensed in CA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_threshold generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004262.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004262 opened 2020-04-06 re: customer CUST-01291 (manufacturing, CA). Alert type: structuring. 1 alert(s) reviewed. Risk tier at open: prohibited. Investigator: INV-001. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004263.txt
ADDED
|
@@ -0,0 +1 @@
|
|
|
|
|
|
|
| 1 |
+
Case CASE-004263 opened 2020-06-03 re: customer CUST-01291 (manufacturing, CA). Alert type: cash_threshold. 1 alert(s) reviewed. Risk tier at open: prohibited. Investigator: INV-006. No actionable suspicious activity confirmed. Case closed. Severity: high. Documentation retained per BSA recordkeeping requirements.
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004264.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004264
|
| 2 |
+
Opened: 2022-05-02 Investigator: INV-006 Severity: high
|
| 3 |
+
Customer: CUST-01291 — manufacturing operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in CA. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type structuring generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004265.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004265
|
| 2 |
+
Opened: 2022-08-08 Investigator: INV-008 Severity: critical
|
| 3 |
+
Customer: CUST-01291 — manufacturing operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in CA. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type large_cash_deposit generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004266.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004266
|
| 2 |
+
Opened: 2022-09-02 Investigator: INV-004 Severity: critical
|
| 3 |
+
Customer: CUST-01291 — manufacturing operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in CA. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type cash_threshold generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004267.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004267
|
| 2 |
+
Opened: 2024-04-17 Investigator: INV-003 Severity: critical
|
| 3 |
+
Customer: CUST-01291 — manufacturing operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a manufacturing licensed in CA. At case open the point-in-time risk tier was prohibited, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type geo_anomaly generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion of money laundering / suspicious activity reached the moderate threshold. A Suspicious Activity Report has been filed with FinCEN per 31 CFR 1020.320. Filing made within regulatory timeframe from initial detection.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004268.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004268
|
| 2 |
+
Opened: 2021-12-03 Investigator: INV-002 Severity: high
|
| 3 |
+
Customer: CUST-01292 — cultivation operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a cultivation licensed in CA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type structuring generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004269.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004269
|
| 2 |
+
Opened: 2022-07-13 Investigator: INV-009 Severity: high
|
| 3 |
+
Customer: CUST-01292 — cultivation operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a cultivation licensed in CA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type structuring generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|
dataworld-p000384-consequence-1/environment/data/aml/case_narratives/shard-04/CASE-004270.txt
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
INVESTIGATION NARRATIVE — CASE-004270
|
| 2 |
+
Opened: 2024-08-26 Investigator: INV-004 Severity: high
|
| 3 |
+
Customer: CUST-01292 — cultivation operating in CA.
|
| 4 |
+
|
| 5 |
+
1. BACKGROUND
|
| 6 |
+
The customer is a cultivation licensed in CA. At case open the point-in-time risk tier was high, reflecting the institution's CRB risk-rating model. This case consolidates 1 alert(s) of type high_risk_jurisdiction generated by the AML monitoring engine.
|
| 7 |
+
|
| 8 |
+
2. ALERT REVIEW
|
| 9 |
+
The triggering alert(s) flagged deviation from the customer's established transaction baseline. Reviewed settlement-level transaction data, counterparty patterns, and geographic indicators. Cross-referenced against the customer's KYC profile including beneficial-ownership structure and source-of-funds documentation.
|
| 10 |
+
|
| 11 |
+
3. ANALYSIS
|
| 12 |
+
The activity pattern is consistent with potential structuring and/or layering behaviour. Transaction amounts cluster near reporting thresholds; velocity exceeds the customer's 12-month baseline. [REDACTED] specific counterparties reviewed for round-tripping indicators.
|
| 13 |
+
|
| 14 |
+
4. DETERMINATION
|
| 15 |
+
Suspicion did not meet the filing threshold. Case closed with no further action. Monitoring continues; the customer remains on the standard review cycle.
|
| 16 |
+
|
| 17 |
+
5. RECORDKEEPING
|
| 18 |
+
Supporting documentation, transaction extracts, and analyst notes retained in the case management system per BSA/AML recordkeeping requirements (5-year retention).
|