Use caseBSA/AML compliance
Each quarter, 286 high-risk files come due. Every one starts with a hunt for what expired or changed, and the hunt eats half the review.
Every file is pre-checked before a reviewer opens itHealth data sent by mistake leaves the recordTwo people sign every high-risk review
Good standing certificate and signature cards are valid. Three items are outdated, starting with the manager's passport, expired on 10/14/2026.
source · 9 documents on the customer fileItems outdated or activity to explain · the AI lists each one
On January 4, 286 review files open, and 41 of them are already overdue. Most are hard for the same reason: the file itself, built over years, with an ID that expired last month, a declaration from two springs ago, and an activity nobody has set beside the profile since the last review. The reviewer spends the morning discovering that, while the overdue count grows. Half of each review is an inventory done by hand, before any judgment starts.
Now the inventory runs ahead of the reviewer. The AI pre-checks every file in the campaign against your review rules, lists what is outdated with its document, and sets the activity beside the declared profile. Luis starts from a list of facts and spends his time on the judgment, which stays with two people.
A BSA team has seen every one of these screens before. What it has not seen is this order: every file in the campaign is pre-checked before assignment, the customer is asked once through the advisor who knows them, and the rating is confirmed by a reviewer and signed by a second. The nine steps below follow one of the 286, Gulfport Import Export, from the campaign run on January 4 to the second signature on January 19.
The quarter's reviews open at once, and each file is checked before anyone reads it.
On January 4, your scheduler calls the repository API: one review case opens for every customer rated High whose review date falls in the quarter. Priya Natarajan, BSA officer, finds 286 of them, with the 41 overdue from last quarter at the top of each queue.
The workflow assigns them to her five reviewers by branch and by workload.
With 286 files, the AI check runs asynchronously. It reads each customer file against the review rules your team wrote in plain language.
Each result lands on the case as a status and its reasoning. Luis Ortega's queue can be sorted by it, so he sees which files need the customer and which he can review today.
Luis opens Gulfport Import Export, a food wholesaler trading with North Africa. The pre-check lists three items: the manager's passport expired in October, the ownership certification is from March 2025, and the 2025 financial statements are missing. Each line opens its document in the viewer.
Luis needs new documents and two explanations, so he goes through the advisor who knows the customer.
The yearly activity statement is filed on the case. Luis asks the assistant to compare it with the profile recorded at the last review. The answer names two differences, each with both sources.
Luis asks for a draft listing the three documents and the two questions. Megan Fowler, the relationship manager, softens the opening and sends it under her name, since Sam Haddad knows her. The case moves to Waiting for customer, with an SLA timer on the step.
Sam Haddad uploads a 9-page scan: passport, certification, financial statements, invoices for a market stall paid in cash, and contracts with two olive oil suppliers. Page 6 is an employee's medical certificate, sent by mistake. The AI flags it as personal data the review does not need.
Luis splits the scan in the viewer, files the business pages in their slots and removes the certificate. The action is recorded with his name.
The file is current again. Luis confirms the rating, and Priya countersigns.
With the new pages in their slots, the analysis runs again. The documents pass. The activity point stays open on purpose: the explanation is for a person to accept.
Luis reads the invoices and the contracts. He accepts the explanation, adds Tunisia to the declared countries, keeps the rating at High because of cash volumes and cross-border flows, and writes his conclusion. He asks for a summary to hand over.
Priya opens the case from her signing queue, reads the summary and the two supporting documents, and signs. The customer file gets its next review date, twelve months out. Her campaign report moves Gulfport Import Export to Done.
Gulfport came back with three outdated items. Any file in the campaign comes back one of three ways, judged against your review rules, and each way starts different work.
IDs valid, certification recent, financials on file. The pre-check records each date it read.
Then: the reviewer looks at the activity, rates, and sends for signature.An expired ID, an old declaration, a difference with the declared profile. Each item names its document.
Then: one request through the advisor; the check runs again when the reply arrives.A document your policy requires that the customer can no longer produce. The AI names the rule that blocks.
Then: the BSA officer reviews the file and decides what follows.It rates nobody. It files no SAR. It closes no relationship. Across the nine steps on this page, the rating and the signatures belong to two people, each with their own rights and their own trace.
The AI pre-checks, compares, flags and drafts. The control is in the review rules and in the second signature, so it holds when the campaign is three hundred files long.
One campaign of 286 files, with one of them followed end to end. A smaller portfolio or stricter rules would move these counts.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
A reviewer, a BSA officer and an architect all sign off before a campaign runs this way. Each of them is looking for something different.
Mornings vanish into finding out what a file is missing.
Examiners open with one question: how many reviews are overdue?
Each campaign still means an extract, a spreadsheet and a mail merge.
Begin with the check your reviewers do first on every file, such as ID validity on the review date, and run it across next quarter's campaign before assignment. One quarter is enough to compare queues with and without it.
Your customer files, review cases and documents stay in the systems that hold them today.
Your move
Bring a few anonymized high-risk files and your review checklist. We will pre-check them in front of you and leave the judgment with your reviewers.