Banking compliance workflow for Tallyfy

Stay ahead of suspicious activity before regulators come knocking

Alert backlogs invite regulatory scrutiny. This daily monitoring workflow ensures BSA analysts review alerts promptly, document investigations thoroughly, and escalate suspicious activity for SAR consideration.

3 steps
2 fields

Run this workflow in Tallyfy with people, AI, and conditions

BSA/AML Daily Monitoring Run #2,481 Running now
Status Step Assignee Deadline
Status: Completed

1. Review new alerts from monitoring system

TM
Team member
Status: Active

2. Investigate and document alerts

Claude
AI agent
Status: Waiting

3. Complete monitoring log

TM
Team member

Tallyfy is the accountability layer that lets this template mix people, AI agents, and conditions in one auditable flow

Process steps

1

Review new alerts from monitoring system

2 hours from previous step
task
Log into your BSA monitoring system and pull up all new alerts that have come in since your last review. Sort them by category - structuring, unusual patterns, high-risk geography, large dollar amounts, and so on. Pay special attention to the severity level and how old each alert is. Here is a practical tip that experienced analysts swear by: always tackle your oldest alerts first. Regulators during exams will specifically look at alert aging reports, and anything sitting untouched for more than 5 business days raises red flags. If you have got a backlog building up, that is a sign your thresholds might need tuning or you need more staffing - either way, document it. Pro tip: Keep a quick tally of alerts by type each day. After a few weeks, you will start spotting patterns - like a spike in structuring alerts after a new branch opens, or seasonal changes around tax time. These patterns are gold for your next BSA risk assessment.
Form fields in this step
Total New Alerts *
High Priority Alerts *
Alerts Over 5 Days Old
2

Investigate and document alerts

4 hours from previous step
task
For each alert that needs a closer look, dig into the underlying transactions, the account history, and the customer profile. Your goal is to determine whether the activity makes sense given what you know about the customer - or whether it is actually suspicious. When you clear a false positive, don't just mark it as cleared - write a brief explanation of why. Something like "Customer runs a cash-intensive laundromat, deposits consistent with known business pattern" is far more useful during an exam than just "false positive." Examiners want to see your reasoning, not just your conclusion. If something does look suspicious, escalate it for SAR (Suspicious Activity Report) consideration right away. Don't sit on it - FinCEN's 30-day filing clock starts when you identify the suspicious activity, not when you get around to writing it up. One thing we've learned from working with compliance teams: the biggest mistake isn't filing too many SARs - it is waiting too long to start the process on the ones that clearly need attention.
Form fields in this step
Alerts Investigated *
False Positives Cleared *
Escalated for SAR Review
3

Complete monitoring log

4 hours from previous step
task
Document everything you did today in your monitoring log. Record the total number of alerts reviewed, investigations you conducted, how each alert was resolved (cleared, escalated, pending), and any notable patterns you spotted. This log isn't busywork - it is your primary proof that your bank is actively monitoring transactions as required by the BSA. During exams, regulators will pull your monitoring logs and compare them against your alert volumes. If there are gaps (days with no entries) or the numbers don't add up, that creates uncomfortable questions. Be accurate and consistent. Also note any trends or concerns in the free-text field. Things like "seeing increased wire activity to Country X across multiple accounts" or "three new accounts opened this week showing near-threshold cash deposits" are exactly the kind of observations that feed into your institution's broader risk picture. Your daily notes today become the data points that shape next quarter's risk assessment.
Form fields in this step
Monitoring Log Completed *
Trends or Concerns Noted

Why Tallyfy is the AI control layer

Phase 1

Set up

Define the recipe
1
Define process steps
You can't automate without a recipe.
2
Set deadlines and conditions
AI needs structure.
3
Assign each step
Person, AI, or rule. The right doer.
Phase 2

Run

People + AI working together
4
Launch
One click. No glue code.
5
AI handles routine tasks
Fewer mistakes and hallucinations.
6
People approve
Accountability. You can't blame AI.
Phase 3

Track and improve

Audit and learn
7
Track real-time status
AI sessions are a nightmare to track alone.
8
Audit and improve
Gradual shift, never total re-do.

Ready to use this template?

Sign up free and start running this process in minutes.