Why the Recipient and Purpose Change the Rule
The phrase “underlying facts may be shared” is incomplete until two questions are added: shared with whom, and for what purpose? This chapter examines how the joint statement and 31 CFR § 1020.320 distinguish customer communication from interbank collaboration, official disclosure, and limited internal sharing. The comparison gives readers a way to avoid two opposite errors—treating every fact as protected from discussion, or treating one authorized disclosure route as permission to reveal a SAR to a customer.
The same altered-check deposit can appear in several legitimate conversations. A customer may need an explanation of why the deposit was rejected. Another financial institution may need transaction information to prepare a joint report. FinCEN or a law-enforcement agency may need information for official duties. Personnel within a bank’s corporate structure may need to share information for a purpose consistent with the Bank Secrecy Act. The transaction is the common subject, but the recipient and purpose change the legal path.
Sharing underlying information with another institution
The customer-facing rule starts with the underlying activity. The joint statement says banks and credit unions are not prohibited from discussing potentially fraudulent or suspicious transactions with a customer, a person who may be the subject of a SAR, or certain third parties, including other banks or credit unions, as long as the communication does not reveal the existence of a SAR. That language does not create a general duty to disclose facts, and it does not make every form of sharing permissible. It preserves a category of fact-based communication while keeping the reporting event confidential.
The regulation provides a more specific example for another financial institution. Section 1020.320(e)(1)(ii)(A)(2) allows disclosure of underlying facts, transactions, and documents to another financial institution, or to its directors, officers, employees, or agents, for preparation of a joint SAR. The purpose is not incidental. The information is being shared to support collaborative reporting, not to inform the person involved in the transaction that a report exists.
That difference can be seen by holding the facts constant. Suppose Bank A is examining a transfer that passed through an account and Bank B handled another part of the transaction. Bank A may need to discuss dates, amounts, parties, and documents with Bank B if the institutions are preparing a joint SAR. The information remains tied to the underlying transaction and to the specified reporting purpose. If Bank A then tells the customer that the two banks are preparing or have filed a joint SAR about the transfer, the communication has changed direction. It has become notification of the protected reporting event.
The no-notification condition remains in force even when the underlying information can be shared with another institution. The regulation says that the provision for underlying facts, transactions, and documents must not be construed to notify a person involved in a reported suspicious transaction that the transaction has been reported. The joint statement applies the same practical boundary to communications with customers and third parties. A bank cannot use an authorized collaboration as a reason to reveal the collaboration or the report to the subject.
This is why the recipient-purpose test is stronger than a simple content test. “This is a transaction date” describes content. “This transaction date is being supplied to another institution to prepare a joint SAR” adds purpose and reporting status. The first may be an underlying fact; the second may reveal the existence of a report or an impending reporting process. The analysis must consider what the exchange communicates to the recipient, not just whether the material originated in an account record.
The test also prevents a customer example from being overextended in the other direction.