SAR Quality Review Checklist

What is the SAR Quality Review Checklist?

A SAR Quality Review Checklist is the internal quality gate AML teams use before a Suspicious Activity Report leaves the institution. It's a line-by-line review document that verifies the report is complete, accurate, and meets the standard regulators expect to see. It's not a filing form. It's the process that sits between "we've identified suspicious activity" and "we've filed a defensible report."

The obligation is specific. Under 31 CFR 1020.320, U.S. banks must file SARs within 30 days of detecting suspicious activity, or 60 days when no subject can be identified. FinCEN's SAR filing guidance makes clear that reports must contain sufficient detail for law enforcement to act on them. Examiner findings at institutions with SAR quality deficiencies tend to cluster around the same failure modes: incomplete subject identification, transaction data that doesn't reconcile to the narrative dollar amounts, and narratives that describe what happened without explaining why it's suspicious.

In the UK, Part 7 of the Proceeds of Crime Act 2002 requires reporting entities to submit Suspicious Activity Reports to the National Crime Agency's UKFIU. The same quality standards apply. A report the UKFIU can't act on is a missed intelligence opportunity, and a pattern of poor-quality filings will surface in a supervisory review.

Transaction Monitoring alert data feeds most SAR investigations, which means the quality of what gets filed reflects on the monitoring program as a whole. Examiners read SARs against your Customer Due Diligence records. Gaps between what you knew and what you filed are difficult to explain after the fact. This checklist closes that gap before filing.

Who needs the SAR Quality Review Checklist?

The primary users are AML analysts and SAR reviewers who draft and approve reports, the MLRO or BSA Officer who carries ultimate reporting responsibility, and the compliance QA function that samples filed SARs during periodic reviews.

Reach for this checklist at these specific moments:

• An analyst has drafted a SAR and is handing it to a reviewer for pre-filing sign-off
• A second-level reviewer is completing a quality gate before the report goes to FinCEN or the NCA
• A compliance QA team is sampling filed SARs for a quarterly or annual review
• The institution is preparing for a BSA/AML examination and wants to test recent filings against examiner expectations
• A new analyst is being trained and needs a concrete framework for what a quality SAR looks like
• The institution is under an MRA or consent order citing SAR quality deficiencies and needs a documented remediation process

MLROs managing volume pressure will find the checklist useful as a structured triage tool. Clearing the SAR filing backlog gets harder when every review depends on individual judgment. A shared checklist makes the standard explicit and speeds up the review cycle without trading off quality.

Community banks, credit unions, broker-dealers, MSBs, and crypto asset service providers all face SAR or STR filing obligations. The checklist scales to any institution size.

What's inside the SAR Quality Review Checklist

The document is organized into six review sections. Each covers a distinct dimension of SAR quality, with specific line items a reviewer can confirm or flag before sign-off.

1. Subject Identification

• Full legal name, date of birth, and government-issued ID type and number recorded
• Address confirmed against account records (flag if PO Box only, or inconsistent with other records)
• TIN or SSN present, or absence explained with the applicable reason code
• Role of subject clearly coded: originator, beneficiary, account holder, or third party
• PEP Screening and Sanctions Screening status documented for each named subject

2. Account and Relationship Data

• Account number(s) and product types referenced in the SAR body
• Account opening date and CDD tier at onboarding, with source document cited
• Prior SARs filed on the same subject cross-referenced by FinCEN confirmation number
• Any relevant adverse media or watchlist hits noted alongside screening date

3. Transaction Data Completeness

• Date range of suspicious activity matches the date fields in the filing form
• Total dollar amount in the narrative reconciles to the summed transaction log
• Transaction types (wire, cash, ACH, check, crypto) coded correctly in the form
• Supporting transaction records attached or referenced in the case file

4. Narrative Quality

• Opening paragraph answers: who conducted the activity, what happened, when, where, and why it's suspicious relative to the customer's expected behavior
• Legal conclusions avoided (state observations, not determinations)
• Continuing activity election: prior SAR confirmation number cited where applicable
• Narrative length proportionate to complexity; not padded, not truncated
• Structural alignment checked against the institution's SAR Narrative Template

5. Typology and Characterization

• SAR activity type field(s) selected and consistent with the narrative description
• Supporting typology reference attached (internal red flag list, regulatory typology guidance, or FATF Recommendation 1 risk-based approach context)

6. Filing Mechanics and Sign-Off

• Filing deadline calculated and confirmed not breached
• Reviewer name, credentials, and sign-off date recorded
• Case management system reference number noted
• Voluntary disclosure fields completed if law enforcement contact is applicable

How to use the SAR Quality Review Checklist

Step 1: Assign the reviewer at case opening, not at drafting. Don't assign a reviewer after the SAR is written. In high-volume environments, pair each analyst with a designated reviewer when the investigation is opened. The reviewer then knows they own the quality gate and can ask questions during the investigation, not at the end.

Step 2: Analyst completes their checklist section while drafting. The checklist shouldn't be an afterthought filled in at the end. The analyst works through the checklist fields in parallel with the SAR form. When they can't source a required piece of information, they flag it immediately rather than leaving a gap that surfaces at review.

Step 3: Reviewer completes an independent assessment. The reviewer reads the SAR narrative against the checklist line items and pulls the underlying transaction data to verify that the dollar amounts reconcile to the narrative. This step catches the discrepancies that are invisible when you're close to the investigation.

Step 4: Remediate flagged items, then re-review. Any line the reviewer can't confirm goes back to the analyst with a specific comment against the checklist field. This is faster than free-text feedback and creates a documented revision trail that's useful if the filing is ever questioned.

Step 5: Sign off, file, and attach the completed checklist. Both analyst and reviewer sign the completed checklist. Attach it to the SAR case file. This creates the audit trail examiners ask for when they want to understand the institution's quality review process. It's also the record that shows a pre-filing review actually happened.

Step 6: Run periodic QA sampling with the same checklist. The checklist fields work equally well for retrospective reviews of already-filed SARs. Pull a random sample each quarter, apply the checklist, score each report, and feed the results into your exam readiness posture and the BSA Officer's annual program assessment. For a deeper look at what examiners focus on in narrative reviews specifically, the Improving SAR narrative quality page is worth reading alongside this checklist.

For teams running concurrent EDD reviews, the EDD Checklist for High-Risk Customers covers the upstream customer risk documentation that gets cross-referenced when examiners pull SARs on high-risk accounts.

Common mistakes to avoid

Treating narrative quality as a judgment call without criteria. "Good narrative" means different things to different reviewers if there's no rubric. Examiners use the 5 W's as a baseline: who, what, when, where, and why it's suspicious relative to the customer's normal profile. If the checklist only has a yes/no narrative pass, you'll get inconsistent sign-offs across reviewers. Add specific scoring criteria for structure, the presence of a behavioral baseline, and the absence of legal conclusions.

Summarizing transactions instead of documenting them. "Multiple wire transfers" doesn't satisfy FinCEN's requirements. The SAR form asks for the total dollar amount and the specific transaction types that make it up. If the narrative says $480,000 and the transaction log totals $463,000, that discrepancy will surface in an examination. Require the reviewer to reconcile the narrative total against the transaction attachment before sign-off.

Skipping the prior-SAR cross-reference. Continuing activity SARs require the confirmation number from the prior filing. Institutions that don't track this create fragmented filing histories that law enforcement can't connect across reports. A mandatory "prior SAR filed: Y/N" field with the confirmation number required as a blocking item fixes this in seconds.

Filing without current screening results. A SAR that goes out without an up-to-date PEP or sanctions check misses context that could change the typology coding, the narrative, or the voluntary disclosure decision. Make current screening status a blocking field in the checklist, not an optional note in the case file.

Conflating the quality review with the filing decision. The quality review checklist checks completeness and accuracy. It doesn't advise on whether to file. When the filing decision is genuinely uncertain, that's a separate escalation path involving the MLRO and, where appropriate, legal counsel. Mixing the two in the same document creates a record that's harder to defend if the institution's judgment is later questioned.

How FluxForce automates this

Manual SAR quality reviews take time, and volume pressure at most institutions means some filings don't get the scrutiny they need. FluxForce's AI agents monitor transactions in real time, run continuous PEP and sanctions screening, and produce structured SAR drafts with pre-populated subject data, reconciled transaction summaries, and narrative frameworks built to FATF Recommendation 11 record-keeping standards. Every decision includes full, audit-ready evidence. The checklist becomes a confirmation step rather than a discovery process. Request a demo to see how it works in practice.