BSA audit: what the independent test covers and how to prepare
A BSA audit is the independent test of a bank's or credit union's BSA/AML compliance program, one of the program's required parts. A qualified party who does not run the program tests whether it is adequate, followed in practice and fits the institution's risk, and reports the results to the board.
Updated on
What a BSA audit is, and why it is required
Every US bank and credit union must run a BSA/AML compliance program, and one of its required parts is independent testing. The bank rule is at 31 CFR 1020.210, and the federal banking agencies and the NCUA have their own program rules that say the same. In practice, everyone calls the independent test the BSA audit.
The audit answers one question for the board: does our BSA/AML program work, and does it fit the risks we actually take? It is different from a regulatory examination. Your bank commissions the audit; your regulator conducts the exam. Examiners read the audit report, check whether its scope fit your risk profile and look at how management responded. A strong audit makes the exam easier; a weak one becomes an exam finding itself. For the exam side, see our guide to bank exam preparation.
Who performs it and how often
The test can be done by internal audit, an outside auditor or consultant, or other qualified staff. What matters is independence and competence. The person testing the program should not be involved in running it, should not report to the BSA officer, and should know BSA/AML well enough to test it properly.
Results should be reported directly to the board of directors or a designated board committee, not filtered through the BSA function.
Federal rules do not set a fixed frequency. The test should be risk-based, and it should happen often enough to catch problems before they grow, with more frequent or broader testing after major changes such as a merger, a new product line, a new core or monitoring system, or significant exam findings. Agree the cycle with your board and confirm it fits your examiner's expectations.
What a BSA audit covers: scope per the FFIEC manual
The FFIEC BSA/AML Examination Manual describes what examiners expect independent testing to cover. A risk-based scope usually includes:
- Overall program. Whether the program is adequate and effective given the bank's risk profile, and whether policies are current and board-approved.
- Risk assessment. Whether the BSA/AML risk assessment is reasonable, current and covers the bank's products, services, customers and geographies.
- Customer Identification Program. Transaction testing of new accounts: required information collected, identity verified, discrepancies resolved, notice given, records kept.
- Customer due diligence and beneficial ownership. Whether risk profiles are built, beneficial owners identified and verified, risk ratings supported, and EDD applied where policy requires.
- Suspicious activity monitoring. Whether the monitoring system, manual or automated, is set up to catch the bank's risks; whether the data feeding it is complete and accurate; whether alerts are worked on time; and whether SAR decisions are sound and documented.
- SAR and CTR filing. Sampled reports checked for timeliness, completeness and accuracy, including CTR exemptions.
- Recordkeeping and other requirements. Funds transfer recordkeeping, monetary instrument records, 314(a) and 314(b) information sharing, and other rules that apply to the bank.
- OFAC. Often tested alongside BSA: screening coverage, list updates, match review and reporting.
- Training. Whether training reaches the right staff and the board, fits their roles and is documented.
- BSA officer and resources. Whether the BSA officer has the authority, independence, staff and systems to run the program.
- Prior findings. Whether management fixed issues raised in earlier audits and exams.
Transaction testing is the core of the work. The auditor samples real files and checks them against your policy and the rules, which is why gaps in individual KYC files show up here first.
How to prepare for a BSA audit
- Agree the scope early. Share your latest risk assessment with the auditor so the scope follows your actual risks, and note any new products, systems or exam findings since the last test.
- Update the risk assessment. If it has not been refreshed since your products, customers or geography changed, refresh it first. An out-of-date risk assessment undermines everything tested against it.
- Gather the program documents. Board-approved policy and procedures, BSA officer appointment, committee minutes, training records, monitoring system documentation and any model validation or tuning work.
- Close prior findings. Show each earlier audit and exam issue, the corrective action, the owner and the evidence it is done.
- Self-test a sample. Pull a sample of new accounts, high-risk customers, alerts, SARs and CTRs and check them the way the auditor will. Fix what you find and record that you fixed it.
- Make files easy to retrieve. An auditor who can find the CIP record, beneficial ownership certification, risk rating rationale and approval in one place tests faster and finds fewer documentation gaps.
- Plan the response. Decide who drafts management responses and how corrective actions will be tracked to the board.
Common BSA audit findings
Findings vary by bank, but the same themes come up repeatedly in audit reports and supervisory guidance:
- A risk assessment that has not kept up with new products, customers or channels.
- CIP exceptions: missing information, identity not verified or discrepancies not documented.
- Beneficial ownership certifications missing, incomplete or inconsistent with entity documents.
- Customer risk ratings that do not match the policy, or overrides without a written reason.
- Periodic reviews of higher-risk customers past due.
- Alert backlogs, or alerts closed without enough documentation.
- Late SARs, or SAR narratives that do not explain who, what, when, where and why.
- CTR errors and CTR exemptions not reviewed as required.
- Monitoring scenarios and thresholds that have not been reviewed or tuned, or data that is not reconciled between the core and the monitoring system.
- Training that is generic or not documented for the right staff.
- Prior findings still open.
Most of these are documentation and timeliness problems in individual files, not failures of policy. That is why they are good candidates for automation.
What can be automated
The audit itself must stay independent, and conclusions belong to the auditor. But a lot of the evidence an audit relies on is created, or not created, during day-to-day BSA work. Automation helps in two places.
Before the audit: the files themselves
- Checking every new account file against the CIP and beneficial ownership checklist at intake, so exceptions are caught at the time rather than in a sample months later.
- Recording the reason for every risk rating and every override.
- Preparing periodic reviews on schedule so they do not fall past due.
- Drafting alert dispositions and SAR narratives for an analyst to review and finish.
During the audit: evidence and self-testing
- Pulling a sample and assembling each file's documents, decisions and approvals into one package.
- Running a self-test of a sample against your own checklist and listing exceptions for staff to resolve.
- Tracking prior findings, owners and evidence of closure.
How a community bank automates this
On Lamatic, a community bank can run a pre-audit self-test as an AI agent workflow:
- Inputs. The bank's BSA policy and procedures, the KYC checklist, a sample list of accounts, and read access to the document store and core records for those accounts.
- Assemble. The agent gathers each sampled file's CIP record, beneficial ownership certification, risk rating, EDD work and approvals.
- Test. It checks each file against the bank's own checklist and notes exceptions with the document it relied on.
- Draft. It drafts an exceptions list and a summary by theme for the BSA officer.
- Review. The BSA officer reviews every exception, rejects false positives and assigns fixes. The agent does not change files or mark issues closed.
- Audit trail. The sample, each test result, the reviewer's decisions and the follow-up are logged, so the bank can show the auditor what it tested and fixed.
The same checks run on new files every day as part of KYC and onboarding on Lamatic, which is where fewer findings really come from. Explore more banking workflows, or read how the audit fits the wider AML compliance program.
Frequently Asked Questions
Yes. Independent testing is a required part of the BSA/AML compliance program for banks and credit unions under FinCEN's rules and the program rules of the federal banking agencies and the NCUA.
The rules do not set a fixed frequency. Testing should be risk-based, with more frequent or broader testing when risk or the program changes. Agree the cycle with your board and confirm it with your examiner.
Internal audit, an outside auditor or consultant, or other qualified staff, as long as they are independent of the BSA function and competent to test it. Results go directly to the board or a board committee.
The audit is commissioned by the bank to test its own program. The exam is conducted by the bank's regulator, which also reviews the audit's scope, results and management's response.
No. The independent test must be performed and concluded by qualified people. AI can help the bank keep files complete during the year and help prepare samples and self-tests, with staff reviewing every result.
Run a pre-audit self-test on Lamatic
See an AI agent assemble and check a KYC sample against your own procedures before the auditor arrives.
Book a Demo