Unit21 Automated AML Remediation Action Chaser
Every morning, WebRun opens Unit21 and reads customer entities with remediation actions that have passed their due date, captures the entity, action type, risk tier, and days overdue, logs them to a Google Sheets remediation register, and posts a ranked chase list to the compliance Slack channel so the team works the highest-risk overdue items first.
How do I automatically flag customers with overdue AML remediation actions?
WebRun opens Unit21 every morning and reads all customer entities with remediation actions that have passed their due date, ranks them by risk tier and days overdue, and logs the list to a Google Sheets register. It posts a risk-ranked chase list to the compliance Slack channel so the team works the most critical items first, and completed actions drop off the list automatically.
- High-risk overdue remediation actions are visible to the team each morning before they escalate
- Actions over 14 days overdue are flagged as critical so escalation happens the same day
- Completed actions drop off the list automatically from live Unit21 status
Built for AML compliance teams · BSA officers · compliance managers · fintechs · banks
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.unit21.aiin a real browser with your saved login - no setup, no API keys. -
1
Unit21 - read overdue remediation actions by risk tier
WebRun opens Unit21 to read overdue remediation actions by risk tier. - Open Unit21 and navigate to the Entities or Cases section
- Filter for entities with open remediation actions whose due date has passed
- Capture entity name, action type, risk tier, assigned analyst, due date, and days overdue for each
- Sort by risk tier first and then by days overdue descending
Done when Every overdue remediation action is captured with its entity context and ranked.
-
2
Google Sheets - log remediation register
WebRun opens Google Sheets to log remediation register. - Open the Remediation Action Register sheet
- Update the days overdue and status columns for existing rows
- Add new rows for any remediation actions that became overdue since the last run
Done when The register is current with all overdue actions and their overdue duration.
-
3
Slack - post ranked chase list
WebRun opens Slack to post ranked chase list. - Post a chase list to the compliance channel: high-risk entities first, then sorted by days overdue
- For each item, show entity name, action type, days overdue, and the assigned analyst
- Flag items over 14 days overdue as critical so the team escalates them today
Done when The compliance team has today's overdue remediation chase list in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it contact the customer about overdue remediation items?
No. WebRun only posts an internal chase list to the compliance Slack channel. Any outreach to the customer is always initiated and reviewed by a compliance officer.
What kinds of remediation actions does it track?
It tracks whatever actions are recorded against entities in Unit21 with a due date: for example, document requests, risk-rating reviews, enhanced monitoring checks, and case closure conditions.
What happens when a remediation action is completed?
It reads live status from Unit21 each morning, so completed actions are automatically removed from the next day's chase list without any manual update needed.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.