U.S. flag

An official website of the United States government

SAR Confidentiality Requirements and Information Sharing

SAR Confidentiality Requirements and Information Sharing

Table of Contents

  1. Overview of SAR Confidentiality
  2. The Confidentiality Requirement
  3. Safe Harbor Protections
  4. Prohibited Disclosures
  5. Permitted Disclosures
  6. 314(b) Information Sharing
  7. Information Sharing with Law Enforcement
  8. Sharing Within Financial Institutions
  9. Sharing with Regulators and Examiners
  10. Penalties for Violations
  11. Best Practices for SAR Confidentiality

Overview of SAR Confidentiality

Suspicious Activity Reports (SARs) are among the most confidential documents in banking. The confidentiality of SARs and the information contained therein is strictly protected by federal law. Understanding these confidentiality requirements is critical for compliance professionals, as violations can result in severe civil and criminal penalties.

Why SAR Confidentiality Matters

Protection of Investigations:

  • Prevents subjects from learning they are under suspicion
  • Preserves law enforcement investigations
  • Prevents destruction of evidence or flight by subjects
  • Maintains integrity of financial intelligence system

Protection of Financial Institutions:

  • Safe harbor from civil liability for good faith SAR filings
  • Encourages reporting without fear of retaliation
  • Protects institutions from customer lawsuits

Protection of the Financial System:

  • Maintains effectiveness of BSA/AML framework
  • Encourages voluntary cooperation
  • Preserves trust in the reporting system

31 U.S.C. § 5318(g)(2) - Confidentiality of SARs “A financial institution, and any director, officer, employee, or agent of such institution, who reports a suspicious transaction… shall not notify any person involved in the transaction that the transaction has been reported.”

31 CFR § 1020.320(e) - Implementation regulations (for banks) Similar provisions exist in regulations for other financial institution types.

The Confidentiality Requirement

Core Prohibition

The Rule: A financial institution and its employees shall not notify any person involved in the transaction that the transaction has been reported via SAR.

What This Means

Prohibited Actions

You may not:

  • Tell a customer that a SAR has been filed on their activity
  • Inform a customer that they are the subject of a SAR
  • Disclose to the customer that their activity is under investigation
  • Reference a SAR in communications with the customer
  • Suggest or hint that a SAR has been or will be filed
  • Respond to customer requests for copies of SARs
  • Produce SARs in civil discovery or litigation (absent court order requiring disclosure)
  • Disclose SAR information to persons not authorized to receive it

“Any Person Involved in the Transaction”

This includes:

  • The subject of the SAR
  • Account holders involved in the suspicious activity
  • Beneficiaries of transactions
  • Counterparties to suspicious transactions
  • Agents or representatives of any of the above
  • Attorneys representing subjects (in most circumstances)
  • Any other person involved in or related to the suspicious activity

The Absolute Nature of the Prohibition

The confidentiality requirement is absolute with respect to notifying persons involved in the reported transaction. There are very limited exceptions (discussed below).

Key Point: Even if a customer directly asks whether a SAR has been filed, you cannot confirm or deny. Confirmation would violate the prohibition; denial would potentially be a false statement.

Practical Examples

Violation Example 1: Direct Disclosure

Scenario: Customer calls to complain about account closure. Compliance officer says, “We closed your account because we filed a Suspicious Activity Report.”

Violation: Direct disclosure to the subject that a SAR was filed.

Penalty Risk: Civil penalties, potential criminal prosecution, institutional reputation damage.

Violation Example 2: Indirect Disclosure

Scenario: Customer asks why a wire was delayed. Employee says, “We had to conduct additional review because your activity triggered our suspicious activity monitoring.”

Violation: While not explicitly mentioning SAR, the statement suggests suspicious activity reporting processes, effectively tipping off the customer.

Violation Example 3: Suggestive Conduct

Scenario: Customer asks if there’s a problem with their account. Employee rolls their eyes and says, “Let’s just say we’ve made certain reports that banks are required to file.”

Violation: Indirect but clear suggestion that a SAR has been filed.

Non-Violation Example 1: Account Closure Without SAR Reference

Scenario: Customer asks why account was closed. Compliance officer says, “We have determined that the account no longer meets our risk appetite and have decided to exit the relationship.”

Compliant: Account closure explanation does not reference SAR or suggest suspicious activity reporting.

Note: Customer may suspect a SAR was filed, but institution has not confirmed or disclosed it.

Non-Violation Example 2: Transaction Hold Explanation

Scenario: Customer asks why wire is on hold. Employee says, “We’re conducting additional due diligence as part of our standard procedures. We’ll complete our review as quickly as possible.”

Compliant: Explanation does not reference SAR or suspicious activity determination.

Timeline of Confidentiality

When does confidentiality begin? Confidentiality obligations begin as soon as the decision is made to file a SAR, not just after the SAR is filed.

When does confidentiality end? Never. SAR confidentiality is permanent. There is no expiration of the obligation.

Safe Harbor Protections

Overview of Safe Harbor

Federal law provides financial institutions and their employees with immunity from civil liability for filing SARs and cooperating with law enforcement, provided the filings are made in good faith.

31 U.S.C. § 5318(g)(3) - Liability Protection

“Any financial institution that makes a disclosure of any possible violation of law or regulation, including in a report filed under subsection (g)(1), and any director, officer, employee, or agent of such institution, shall not be liable to any person under any law or regulation of the United States, any constitution, law, or regulation of any State or political subdivision thereof, or under any contract or other legally enforceable agreement (including any arbitration agreement), for such disclosure or for any failure to provide notice of such disclosure to the person who is the subject of such disclosure or any other person identified in the disclosure.”

What the Safe Harbor Protects

Civil Liability Protection:

  • Protects institutions from lawsuits by SAR subjects
  • Protects employees from individual liability
  • Applies to state and federal claims
  • Covers breach of contract claims
  • Covers tort claims (e.g., defamation, invasion of privacy)
  • Applies even if underlying facts prove to be innocent

Protected Activities:

  • Filing SARs
  • Providing information to law enforcement
  • Reporting to FinCEN
  • Cooperating with investigations
  • Internal reporting and investigation of suspicious activity

Requirements for Safe Harbor Protection

To qualify for safe harbor protection, SAR filings must be made in good faith.

Good Faith Requirement

Good faith means:

  • Reasonable basis for suspicion based on facts known at the time
  • Honest belief that activity is suspicious
  • Compliance with SAR filing requirements
  • No malicious or reckless disregard for the truth

Good faith does NOT require:

  • Proof that criminal activity actually occurred
  • Certainty that activity is illegal
  • Complete investigation establishing all facts
  • Accuracy of every detail in the SAR

When Safe Harbor May Not Apply

Safe harbor protection may not apply if:

  • SAR filed with malicious intent to harm the subject
  • SAR filed with reckless disregard for the truth
  • SAR intentionally includes false information
  • No reasonable basis for the suspicious activity determination
  • Filing violates regulatory requirements (e.g., far below thresholds with no legitimate reason)

Safe Harbor in Practice

Example 1: Customer Lawsuit Customer sues bank for defamation and breach of contract, claiming the bank wrongly filed a SAR that damaged their reputation.

Safe Harbor Application: Bank is immune from liability if SAR was filed in good faith based on reasonable suspicion. Customer’s lawsuit will be dismissed.

Example 2: Innocent Explanation Bank files SAR on customer for suspicious wire activity. Investigation later reveals customer had legitimate business reason for wires.

Safe Harbor Application: Bank is protected even though activity was ultimately innocent. Good faith suspicion at time of filing is sufficient.

Example 3: Malicious Filing Bank officer files SAR on ex-spouse’s account with no legitimate basis, intending to harm ex-spouse.

No Safe Harbor: Malicious intent negates good faith. Officer and potentially institution could face liability.

Prohibited Disclosures

Categories of Prohibited Disclosures

1. Disclosures to SAR Subjects

Absolutely Prohibited:

  • Telling subject that SAR was filed
  • Confirming or denying SAR filing in response to inquiry
  • Providing copies of SARs to subjects
  • Allowing subjects to review SARs
  • Referencing SAR in communications with subject

Includes:

  • Direct statements
  • Indirect suggestions
  • Implications or hints
  • Documents that reference SAR filings

2. Disclosures in Discovery or Litigation

Generally Prohibited: SARs are privileged and generally not discoverable in civil litigation.

Rule: Financial institutions shall not disclose SARs or underlying information in response to:

  • Civil discovery requests
  • Subpoenas in civil cases
  • Depositions
  • Interrogatories
  • Requests for production

Exception: SARs may be disclosed pursuant to court order after FinCEN determination (see below).

3. Public Disclosures

Prohibited:

  • Publishing SAR information
  • Posting SAR details online or on social media
  • Discussing SARs with media
  • Including SAR information in public documents
  • Inadvertent public disclosure through unsecured systems

4. Disclosures to Unauthorized Third Parties

Prohibited Recipients:

  • Customer’s attorney (in most circumstances)
  • Insurance companies
  • Private investigators
  • Creditors in bankruptcy proceedings
  • Third-party auditors (unless specifically authorized)
  • Service providers without legitimate need-to-know

Exceptions to Discovery Prohibition

SARs may be disclosed in civil litigation only under very limited circumstances:

Requirements:

  1. Court Order: Court must issue order compelling disclosure
  2. FinCEN Notification: Parties must notify FinCEN of the request
  3. FinCEN Determination: FinCEN determines whether disclosure is appropriate
  4. Balancing Test: Court weighs need for disclosure against confidentiality interests

Process:

  • Party seeking SAR must file motion to compel with court
  • Institution must notify FinCEN of the request
  • FinCEN has opportunity to object or file brief
  • Court determines whether to order disclosure
  • If ordered, protective order typically issued to limit further disclosure

In Practice: Courts rarely order SAR disclosure, recognizing the strong confidentiality interests and that SARs are rarely relevant to civil disputes.

Criminal Proceedings

In criminal cases, SARs may be disclosed to defendants pursuant to criminal discovery rules and constitutional requirements (Brady, Giglio). However, disclosure is still subject to protective orders limiting further dissemination.

Permitted Disclosures

Categories of Permitted Disclosures

While SAR confidentiality is strict, certain disclosures are permitted or required:

1. Disclosures to Law Enforcement

Permitted:

  • Voluntarily providing SAR information to law enforcement
  • Responding to law enforcement requests for SAR information
  • Providing supporting documentation for filed SARs
  • Cooperating with investigations
  • Testifying in criminal proceedings

Best Practice: Document law enforcement requests and responses.

2. Disclosures to Regulators and Examiners

Permitted:

  • Providing SARs to federal or state regulators during examinations
  • Responding to regulatory inquiries about SAR filings
  • Discussing SAR decisions with examiners
  • Providing SAR documentation during audits

3. Disclosures Within the Institution

Permitted:

  • Sharing SAR information with employees who have legitimate need to know
  • Discussing SARs in compliance committee meetings
  • BSA officer reporting to senior management or board
  • Sharing with internal audit
  • Sharing with risk management personnel

Limitation: Limit disclosure to those with legitimate business need. Do not disclose to personnel who do not need the information for BSA/AML purposes.

4. Disclosures to Head Office or Parent Company

Permitted:

  • Branch or subsidiary sharing SAR information with head office or parent company for BSA/AML purposes
  • Consolidated SAR reporting
  • Parent company oversight of subsidiary SAR programs

Limitation: Must be within the same corporate structure and for legitimate BSA/AML purposes.

5. Disclosures to Service Providers

Permitted (with limitations):

  • Sharing SAR information with service providers who perform BSA/AML functions on behalf of the institution
  • Third-party monitoring vendors
  • Third-party SAR preparation services

Requirements:

  • Service provider must be performing function on behalf of the institution
  • Contractual confidentiality obligations required
  • Service provider subject to same confidentiality requirements
  • Limit disclosure to minimum necessary

Not Permitted:

  • Disclosure to general third-party auditors without SAR-specific authorization
  • Disclosure to consultants not performing BSA/AML functions
  • Disclosure to vendors for marketing or other non-BSA purposes

6. 314(b) Information Sharing

Permitted: Financial institutions may share SAR information with other financial institutions pursuant to Section 314(b) of the USA PATRIOT Act (discussed in detail below).

314(b) Information Sharing

Overview of Section 314(b)

Section 314(b) of the USA PATRIOT Act (codified at 31 U.S.C. § 5318(g)(3)) authorizes financial institutions to share information with one another regarding suspicious activities and possible money laundering or terrorist activities.

31 U.S.C. § 5318(g)(3): “Financial institutions may share information with one another regarding individuals, entities, organizations, and countries suspected of possible terrorist or money laundering activities.”

31 CFR § 1010.540: Implementing regulations

Registration Requirement

To participate in 314(b) information sharing, institutions must:

  1. File notice with FinCEN
  2. Provide notification annually (by certification on BSA E-Filing system)
  3. Maintain documentation of participation

Registration Process:

  • Submit 314(b) fact sheet through BSA E-Filing system
  • Include institution information and contact person
  • Update annually

What Can Be Shared Under 314(b)

Permitted Information:

  • SAR information (contents of filed SARs)
  • Information that may be relevant to determining whether to file a SAR
  • Information about individuals, entities, organizations, or countries suspected of money laundering or terrorist financing
  • Transaction information
  • Customer due diligence information
  • Account information

Purpose Limitation: Information may only be shared for purposes of identifying and reporting money laundering, terrorist financing, or other suspicious activity.

Requirements for 314(b) Sharing

1. Both Institutions Must Be Registered

Both the sharing and receiving institutions must be registered with FinCEN for 314(b) participation.

2. Legitimate Purpose

Sharing must be for the purpose of identifying and reporting suspicious activity, money laundering, or terrorist financing.

3. Confidentiality Protections

Receiving institution must:

  • Maintain confidentiality of received information
  • Not disclose to subject of the information
  • Use information only for BSA/AML purposes

4. Secure Transmission

Information should be transmitted securely to prevent interception or unauthorized access.

5. Documentation

Document:

  • What information was shared
  • With whom
  • Date of sharing
  • Purpose of sharing
  • Response received (if any)

Process for 314(b) Information Sharing

Step 1: Identify Need Determine that information sharing would assist in detecting, preventing, or reporting money laundering or terrorist financing.

Step 2: Verify Registration Confirm both institutions are registered for 314(b) (check FinCEN’s 314(b) fact sheet database if available, or confirm directly with the other institution).

Step 3: Contact Other Institution Reach out to the other institution’s BSA officer or designated 314(b) contact person.

Step 4: Share Information Provide relevant information securely (encrypted email, secure portal, etc.).

Step 5: Document Document the information sharing in compliance files.

Step 6: Follow Up If receiving information, analyze it, take appropriate action (additional due diligence, SAR filing, etc.), and provide feedback if appropriate.

Examples of 314(b) Use Cases

Example 1: Structuring Pattern Bank A detects structuring pattern by customer who has accounts at multiple banks. Bank A contacts Bank B (where customer also banks) to inquire if Bank B has observed similar activity. Both banks share transaction information and determine customer is structuring across multiple institutions. Both file SARs referencing the information sharing.

Example 2: Wire Fraud Victim Bank A’s commercial customer is victim of wire fraud. Fraudulent wire was sent to account at Bank B. Bank A contacts Bank B to share fraud information. Bank B investigates the receiving account, identifies suspicious patterns, and files SAR. Bank B provides feedback to Bank A about the investigation.

Example 3: Identity Theft Bank A’s customer reports identity theft and fraudulent account opening. Bank A learns the identity thief opened accounts at multiple institutions using stolen identity. Bank A contacts other institutions to share information about the identity theft and fraudster’s methods. Other institutions file SARs on fraudulent accounts.

Limitations of 314(b)

Not a Blanket Information-Sharing Authorization:

  • Cannot share customer information for marketing purposes
  • Cannot share for general due diligence unrelated to suspicious activity
  • Cannot share with non-financial institutions (e.g., retailers, insurers not covered by BSA)
  • Cannot share with foreign financial institutions (unless specific authorization)

Still Subject to Other Privacy Laws:

  • Gramm-Leach-Bliley Act privacy requirements still apply
  • State privacy laws still apply
  • Sharing must comply with institution’s privacy policies

Information Sharing with Law Enforcement

Voluntary Sharing

Permitted: Financial institutions may voluntarily share SAR information with federal, state, or local law enforcement.

No Legal Obligation: Institutions are not required to voluntarily share beyond filing the SAR with FinCEN (though cooperation is encouraged).

Best Practice:

  • Maintain contact with local law enforcement and FBI financial crimes task forces
  • Establish relationships before suspicious activity occurs
  • Provide SAR supporting documentation when requested
  • Cooperate with investigations

Responding to Law Enforcement Requests

Grand Jury Subpoenas: SARs and supporting documentation may be subpoenaed by grand juries investigating criminal activity. Institutions must comply with valid grand jury subpoenas.

Administrative Subpoenas: Law enforcement agencies with administrative subpoena authority may subpoena SAR information.

Search Warrants: SARs and supporting documentation may be seized pursuant to valid search warrants.

Process:

  1. Verify validity of subpoena or warrant
  2. Consult with legal counsel
  3. Provide responsive documents
  4. Document the production
  5. Maintain confidentiality (do not notify subject)

Section 314(a) Requests

Overview: Section 314(a) of the USA PATRIOT Act authorizes FinCEN to require financial institutions to search their records for accounts or transactions involving persons suspected of terrorism or money laundering.

Process:

  • Law enforcement submits 314(a) request to FinCEN
  • FinCEN distributes request to financial institutions
  • Institutions search records and respond within 14 days (or 2 weeks)
  • Responses go to FinCEN, which shares with law enforcement

Confidentiality: Institutions must not notify subject of 314(a) search or disclosure.

National Security Letters (NSLs)

Overview: FBI may issue National Security Letters requiring production of certain financial records in national security investigations.

Characteristics:

  • Administrative subpoena (no court order required)
  • Often includes nondisclosure requirement (gag order)
  • Very limited disclosure of NSL existence permitted

Compliance:

  • Verify legitimacy of NSL
  • Consult with legal counsel immediately
  • Comply with nondisclosure requirements
  • Provide responsive records

Sharing Within Financial Institutions

Need-to-Know Principle

General Rule: Share SAR information only with employees who have a legitimate business need to know for BSA/AML purposes.

Who Typically Needs to Know

Usually Have Need-to-Know:

  • BSA/AML compliance officers and staff
  • SAR investigators
  • Compliance committee members
  • Senior management receiving BSA/AML reports
  • Board of directors (summary information)
  • Internal audit (reviewing BSA program)
  • Risk management staff (for risk assessment purposes)
  • Legal counsel (advising on SAR issues)

May Have Need-to-Know (Case-by-Case):

  • Account officers (when account action needed)
  • Branch managers (for specific cases)
  • Fraud department personnel (for related investigations)
  • Security officers (for certain types of SARs)

Generally Do Not Have Need-to-Know:

  • Tellers and frontline staff (unless involved in detection)
  • Customer service representatives
  • Marketing staff
  • IT personnel (unless specifically needed for technical support)
  • General employees

Limiting Disclosures

Best Practices:

  • Implement role-based access controls for SAR files
  • Restrict electronic access to SAR documentation
  • Maintain physical SAR files in secure, access-controlled areas
  • Log access to SAR files
  • Train staff on need-to-know requirements
  • Remind staff regularly of confidentiality obligations

Board Reporting

Appropriate Board Disclosures:

  • Summary statistics (number of SARs filed, types of activity)
  • Trends in suspicious activity
  • Regulatory examination findings related to SAR program
  • Program enhancements or issues

Inappropriate Board Disclosures:

  • Customer names or identifying information
  • Specific SAR details
  • Detailed narratives
  • Individual case files

Best Practice: Provide board with aggregated, anonymized information sufficient for oversight without unnecessary disclosure of confidential details.

Sharing with Regulators and Examiners

Regulatory Access to SARs

Examination Access: Federal and state regulators have full access to SARs during examinations.

Regulators with Access:

  • Federal Reserve
  • OCC
  • FDIC
  • NCUA
  • FinCEN
  • State banking regulators
  • Securities and Exchange Commission (for broker-dealers)
  • Commodity Futures Trading Commission (for FCMs)
  • Other functional regulators

Examination Procedures

What Examiners Review:

  • SAR filings for completeness and timeliness
  • SAR decision-making documentation
  • Quality of SAR narratives
  • Supporting documentation
  • Adequacy of investigations
  • Whether all required SARs were filed
  • SAR trends and patterns

Examiner Expectations:

  • SARs readily accessible and organized
  • Supporting documentation maintained
  • Decision documentation clear
  • Timely filing
  • Complete narratives

Responding to Regulatory Inquiries

Process:

  1. Examiner requests SAR files
  2. Institution provides access to SAR files and supporting documentation
  3. Examiner reviews materials
  4. Examiner may ask questions about specific SARs or SAR decisions
  5. Institution responds fully and cooperatively

Best Practice:

  • Maintain well-organized SAR files for easy retrieval
  • Be prepared to explain SAR decisions and timelines
  • Document all aspects of SAR process for examiner review

Examination Reports

Confidentiality of Examination Findings: Regulatory examination reports discussing SARs are also confidential and subject to protection from disclosure.

Penalties for Violations

Civil Penalties

Statutory Authority: 31 U.S.C. § 5321 - Civil penalties for BSA violations

Penalty Amounts:

  • Up to $100,000 per violation for disclosure violations
  • Up to $100,000 per day for continuing violations

Factors Affecting Penalties:

  • Intent (willful violations vs. negligence)
  • Harm caused
  • Prior violations
  • Cooperation with investigation
  • Remedial actions taken

Criminal Penalties

Criminal Prosecution: Willful violations of SAR confidentiality requirements can result in criminal prosecution.

Statutory Authority: 31 U.S.C. § 5322 - Criminal penalties

Penalties:

  • Fines up to $250,000 for individuals
  • Fines up to $500,000 for institutions
  • Imprisonment up to 5 years
  • Or both fine and imprisonment

“Willful” Requirement: Criminal penalties require proof that the violation was willful (intentional or with reckless disregard).

Regulatory Enforcement Actions

Potential Actions:

  • Cease and desist orders
  • Civil money penalties
  • Removal or prohibition orders (against individuals)
  • Written agreements or consent orders
  • Memoranda of understanding
  • Heightened supervision

Employment Consequences

Individual Consequences:

  • Termination of employment
  • Prohibition from industry (regulatory bar)
  • Professional reputation damage
  • Loss of professional licenses

Civil Liability

Despite Safe Harbor: If institution violates confidentiality requirements, it may lose safe harbor protection and face civil liability from affected parties.

Examination Findings

Consequences:

  • Matters Requiring Attention (MRA)
  • Matters Requiring Immediate Attention (MRIA)
  • Violations cited in examination reports
  • Downgrade of BSA/AML rating
  • Increased examination frequency
  • Potential enforcement actions

Examples of Violations and Consequences

Example 1: Teller Discloses SAR to Customer Teller tells customer that a SAR was filed on their account activity.

Consequences:

  • Teller terminated
  • Institution issued civil money penalty
  • MRA issued requiring enhanced training
  • Incident reported to other regulators

Example 2: SAR Produced in Discovery Without Court Order Institution provides copies of SARs in civil discovery without court order or FinCEN determination.

Consequences:

  • Civil money penalty
  • Consent order requiring compliance program enhancements
  • Independent compliance consultant required
  • Remedial training mandated

Example 3: Employee Accesses SARs Without Need-to-Know Bank employee accesses ex-spouse’s SAR file out of curiosity.

Consequences:

  • Employee terminated
  • Individual civil money penalty
  • Criminal referral for unauthorized access to confidential information
  • Institution receives MRA for inadequate access controls

Best Practices for SAR Confidentiality

Policy and Procedures

Implement Comprehensive Policies:

  • Written confidentiality policy
  • Clear explanation of prohibited and permitted disclosures
  • Procedures for information sharing (314(b), law enforcement)
  • Escalation procedures for confidentiality questions
  • Consequences for violations

Training

Regular Training:

  • Annual SAR confidentiality training for all employees with SAR access
  • Training upon hire and role change
  • Refresher training for compliance staff
  • Scenario-based training on handling customer inquiries
  • Training on tipping off risks

Training Content:

  • Legal requirements and penalties
  • What can and cannot be disclosed
  • How to handle customer inquiries
  • Information sharing protocols
  • Consequences of violations

Access Controls

Physical Controls:

  • Secure SAR files in locked, access-controlled areas
  • Sign-out logs for physical SAR files
  • Limited key or combination access
  • Separate storage from general compliance files

Electronic Controls:

  • Role-based access to SAR systems
  • Audit logs of all SAR system access
  • Multi-factor authentication
  • Encrypted storage
  • Secure transmission protocols
  • Automatic timeouts
  • Restricted printing and copying

Handling Customer Inquiries

When Customer Asks About SARs:

DO:

  • Remain calm and professional
  • Decline to confirm or deny SAR filing
  • Provide alternative explanation for account actions (if applicable)
  • Document the inquiry
  • Escalate to supervisor or compliance officer

DON’T:

  • Confirm a SAR was filed
  • Deny a SAR was filed
  • Become defensive or evasive
  • Reference suspicious activity monitoring
  • Hint at or suggest SAR filing
  • Provide SAR copies or details

Sample Response: “I’m not able to provide information about our internal compliance processes. If you have questions about your account, I’d be happy to discuss your account activity and any actions we’ve taken, but I cannot discuss our reporting obligations.”

Documentation

Document:

  • All information sharing (314(b), law enforcement)
  • Customer inquiries about SARs
  • Access to SAR files (audit logs)
  • Training provided
  • Policy acknowledgments
  • Confidentiality violations and responses

Quality Assurance

Regular Reviews:

  • Periodic audit of SAR access logs
  • Review of information sharing practices
  • Assessment of physical and electronic controls
  • Testing of access controls
  • Evaluation of training effectiveness

Incident Response

If Confidentiality Violation Occurs:

  1. Contain the disclosure immediately
  2. Assess scope and impact
  3. Notify senior management and legal counsel
  4. Determine if notification to regulators required
  5. Investigate root cause
  6. Take disciplinary action if appropriate
  7. Implement remedial measures
  8. Document thoroughly
  9. Consider self-reporting to regulators

Summary

SAR confidentiality is one of the most critical aspects of BSA/AML compliance. Key takeaways:

Core Requirements:

  • Never notify subjects that SARs have been filed
  • Maintain strict confidentiality of SAR information
  • Limit access to need-to-know personnel
  • Protect SARs from disclosure in litigation (absent court order)

Permitted Disclosures:

  • To law enforcement (voluntary or pursuant to legal process)
  • To regulators and examiners
  • Within institution on need-to-know basis
  • To other financial institutions pursuant to 314(b)
  • To parent company or head office for BSA/AML purposes

Protections:

  • Safe harbor from civil liability for good faith SAR filings
  • Encourages reporting without fear of lawsuits

Consequences of Violations:

  • Civil penalties up to $100,000 per violation
  • Criminal penalties up to $250,000 and 5 years imprisonment
  • Regulatory enforcement actions
  • Employment termination
  • Loss of safe harbor protection

Best Practices:

  • Comprehensive policies and training
  • Strict access controls
  • Need-to-know limitations
  • Secure systems and storage
  • Documentation of all disclosures
  • Regular quality assurance reviews

Document Version: 1.0 Last Updated: December 5, 2023 Next Review Date: December 5, 2024

This guidance is for informational purposes only and does not constitute legal advice. Financial institutions should consult with legal counsel regarding SAR confidentiality requirements and information sharing practices.