Fraud, Rejected Deposits, and Account Closures

The joint statement’s most consequential application is a familiar one: a bank sees signs of possible payment fraud and must decide both what to do and what to tell the customer. This chapter focuses on the second question. It shows how a bank can describe a suspicious transaction, a rejected deposit, a service restriction, or an account closure without turning that explanation into confirmation of a Suspicious Activity Report (SAR). The distinction helps separate an operational decision from the confidential reporting event behind an investigation.

A customer’s experience may unfold quickly. A check is deposited, the bank delays or rejects it, access to a service changes, and the customer asks why. The bank may be examining whether the item was altered, whether the transaction fits the customer’s expected activity, or whether additional information would clarify its source. The customer might be a victim, a legitimate business with incomplete records, or someone participating in a fraud scheme knowingly or unknowingly. The visible action does not answer those questions by itself, and it does not establish whether a SAR was filed.

Explaining the transaction while investigating fraud

The agencies’ starting point is practical: banks and credit unions may discuss the transaction in question, their concerns about it, remediation efforts, and potential mitigation steps, so long as the communication does not reveal the existence of a SAR. That permission is important because an investigation needs facts from the person who controls or understands part of the transaction. A customer may be the only person who can explain why a payment was made, where a check came from, or who was expected to receive funds.

The customer-facing explanation can therefore stay close to the observable event. It can identify a deposit or transfer, describe a concern about suspected fraud or other suspicious activity, ask for information that may clarify what happened, and explain what practical measure the bank is taking. The explanation does not need to disclose the bank’s internal reporting analysis. It should not identify a confidential report as the reason for the inquiry.

Imagine that a business deposits a check from a new client. The bank detects signs that the check may be altered and pauses the deposit while it examines the item. An explanation focused on the transaction might say that the deposit is being reviewed because of concerns about possible alteration, ask the business for the source of the check and the purpose of the payment, and describe how the deposit will be handled while the review continues. This communicates facts, the nature of the concern, and an operational consequence.

That kind of explanation is different from announcing the institution’s reporting status. “We filed a SAR about this check” does not merely describe the check. It tells the customer that a protected reporting event exists. “This is the transaction we reported to the government” communicates the same event in different words. The problem is the meaning supplied by the communication, not whether the speaker uses a particular acronym.

The distinction also protects against an unfair assumption about the customer. A concern about a transaction is not the same as a finding that the customer committed fraud. The joint statement speaks of potentially fraudulent transactions and other suspicious activity. That wording leaves room for investigation and explanation without declaring a final conclusion about the person involved.