Appearance
Deposit AML Monitoring
Deposit AML Monitoring helps compliance teams identify deposit-account activity that breaches configured transaction or turnover thresholds.
Workspace Reference
| Workspace | How Users Reach It | What Users Usually Do There |
|---|---|---|
| Deposit Products | Deposits -> Setup -> Products | Configure AML thresholds, notification behavior, and product-specific monitoring rules. |
| Deposit Accounts | Deposits -> Operations -> Accounts | Review the flagged account, holder, status, balance, and recent transaction context. |
| AML Monitoring View | Deposit account or monitoring workspace where exposed | Review threshold breaches, activity snapshots, and AML-only filters. |
| Account Holds, Blocked Funds, And Status Actions | Deposits -> Operations | Apply approved restrictions or follow-up controls after review where policy allows. |
| Reporting | Reporting -> Reports | Review recurring AML patterns and compliance summaries where configured. |
What It Monitors
The monitoring view is based on daily account activity and balance snapshots. It helps answer:
- Which accounts had unusually high deposits?
- Which accounts had unusually high withdrawals?
- Which accounts exceeded monthly turnover expectations?
- Which accounts require compliance review?
Product Thresholds
Thresholds are configured on the deposit product. Common controls include:
| Control | Meaning |
|---|---|
| Daily Deposit Threshold | Flags accounts whose total deposits for a day exceed the configured amount. |
| Daily Withdrawal Threshold | Flags accounts whose total withdrawals for a day exceed the configured amount. |
| Monthly Turnover Threshold | Flags accounts whose monthly activity exceeds the configured amount. |
| Notification Enabled | Controls whether a breach should raise a follow-up notification. |
Different products can carry different thresholds depending on risk, customer type, regulatory expectations, and operating policy.
Using The Monitoring View
From the deposit account or monitoring workspace, users can review:
- date-filtered balance history
- opening and closing balances
- daily deposit and withdrawal totals
- transaction counts
- blocked or held amounts
- AML flag indicator
- breach details where available
Use the AML-only filter to focus on flagged records.
Reviewing A Flag
When a record is flagged, review:
- breach type
- threshold amount
- actual amount
- transaction count
- account holder
- product type
- recent account activity
- any related notes or customer context
The system identifies the threshold breach. Compliance users still decide whether further action is needed.
Follow-Up Actions
Follow-up depends on policy and permissions. Common actions include:
- adding a compliance note
- contacting the customer
- requesting supporting documents
- escalating to a supervisor
- freezing or restricting the account through the normal account-status workflow
- closing the review if the activity is explained
Common Mistakes To Avoid
- Do not treat every threshold breach as suspicious activity. It is a review signal.
- Do not change product thresholds casually; they affect monitoring coverage.
- Do not freeze accounts directly from assumptions. Follow the institution's review and approval policy.
- Do not ignore repeated low-severity flags. Patterns can matter as much as single large breaches.