- Before
- Edits last year's narrative each fall, and answers an examiner's why from a spreadsheet tab whose source nobody wrote down.
- Now
- Opens a cited draft, resolves seven challenges with reasons and submits, and answers an examiner who asks why a row moved by clicking the word.
The annual BSA/AML risk assessment: overnight draft to the board's vote
A $3.4 billion community bank with 41 branches, and a sponsor bank for fintech partner programs, builds this year's BSA/AML risk assessment with data as of September 30. Here is what happens, screen by screen, in the working solution.
A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.
- 01The night of the run, 11:31 PM
The draft is built overnight, step by step
The agentsThe Data Gatherer pulls 112 data points from six systems: 48 from the core banking system, 17 from transaction monitoring, 9 counts from case management, 19 from the general ledger, 15 from the partner records and 4 from the board portal. The Risk Scorer scores 38 categories with Methodology v4, the Control Assessor rates 41 controls (14 Strong, 24 Adequate, 3 Needs improvement), and the Narrative Writer drafts nine sections. The Challenger finds 7 claims out of date, and the draft goes to the BSA Officer.
The Data Gatherer reads SAR figures as counts only. A missing value is marked provisional for the analyst, not estimated.
- 02About a week later, morning
The whole BSA/AML risk assessment in five rows
BSA OfficerEach row reads inherent risk, control strength and residual risk. Fintech partner programs reads High → Adequate → Moderate-High, up from Moderate; products and services and delivery channels rose too. Customers and entities and geographies are unchanged, and overall residual risk stays Moderate. Above the rows, the path to the board: Drafted, BSA Officer reviewed, Committee reviewed, Board approved.
Next step: the challenger says §5 still reads “six partner programs”; the register says 11.
- 03One click
“High” opens the data behind it
Risk ScorerThe BSA Officer clicks High on fintech partner programs. The panel shows why: the program book nearly doubled, to 11 programs, 214,000 end customers and $1.9 billion of ACH a month, with 44% of monitoring alerts. A weighted score of 4.6 of 5 under the bank's methodology, last year Moderate-High, confidence 0.96, and all 24 data points with this year's and last year's values.
Each of the 15 rating words on the five rows opens its data, its rule and its sources.
- 04One more click
Each figure cites its source passage
BSA analystA citation opens the record a figure came from: the partner program register, exported on the as-of date, with the 11 active programs named and the count highlighted. The analyst confirmed all 112 data points against their sources two days after the run.
“Pulled by the Data Gatherer, read-only connection, kept five years.”
- 05The row, opened
Five categories under fintech partner programs
BSA OfficerDeposit and card programs and payments programs read High → Adequate → Moderate-High; lending programs read Moderate → Strong → Low. The partner performs CIP in 7 of the 11 programs, and partner data feeds and monitoring is the control that needs improvement. Below, the 11 sponsored programs with their end customers and monthly ACH, the largest at 48,000 end customers and $120 million a month.
- 06The challenge
Last year's sentence, still in this year's draft
ChallengerThe challenger read the draft against last year's board-approved assessment, the FFIEC manual and FinCEN's publications. Of its seven claims, the BSA Officer has accepted five fixes, one after editing it, and dismissed one with the reason code “Claim still accurate”: the eight national priorities have not been revised. One is open. §5 still says “The bank sponsors six fintech partner programs, serving about 88,400 end customers,” carried from last year, while the register shows 11 programs and 214,000 end customers.
The challenger never edits the draft. Sign-off stays closed while a claim is open.
- 07Fix accepted
The narrative the board reads, each figure cited
BSA OfficerThe BSA Officer accepts the fix. §5 now reads “The bank sponsors eleven fintech partner programs serving 214,000 end customers, with $1.9 billion of ACH a month,” cited to the register, the partner files and the payments hub, and marked with what changed and who changed it. Program activity produced 4,310 of 9,840 monitoring alerts and 61 of 138 SARs, shown as counts.
The Narrative Writer writes no figure without a citation and names no individual SAR or customer.
- 08The gaps
An action plan for each control that needs improvement
Chief risk officerEach of the three controls rated Needs improvement has a plan with an owner and a due date: partner data feed exceptions tracked to closure by December 18, instant payment scenarios validated and tuned by January 29, a liveness check on online account opening by February 26. Last year's plan to finish site visits for money services businesses is 22 days overdue with 20 of 23 done, so it was escalated to the Chief Risk Officer.
A due date moves only with the checker.
- 09Submitted
The officer submits as maker and cannot approve
BSA OfficerWith 7 of 7 challenges resolved, 112 of 112 data points confirmed and 41 of 41 controls rated, the BSA Officer submits the assessment and the committee pack goes to the Chief Risk Officer for the BSA Committee. For the maker, the approve button stays locked, and the screen says why.
“You submitted this draft. A maker cannot approve their own work.”
- 10The board meeting
The board reads it in plain words, asks, and approves
Board committee chairAfter the committee's review, the chair reads the board view: overall risk unchanged, three areas that rose and why, three new action plans, one late plan escalated to the Chief Risk Officer, and seven out-of-date statements found and resolved. The chair's questions to the agents are answered with citations and go into the minutes record, and the chair records the board's approval.
“Our overall risk is unchanged.”