
On October 13, the Treasury Department announced enforcement actions imposing “more than $1.21 billion in penalties” on Bank of America for violations of anti-money laundering and sanctions laws. The largest piece was a $1.2 billion penalty from the Financial Crimes Enforcement Network, which said the bank “failed to timely report to FinCEN over $5 billion dollars in suspicious transactions.” The bank admitted that it willfully violated the Bank Secrecy Act, including by failing to file suspicious activity reports, the confidential filings known as SARs.
Account holders don’t see that reporting system directly, because SARs are confidential. What they do see are its effects: a check deposit held longer than usual, a transfer out of savings that doesn’t go through, a call asking where some money came from, or a letter saying the account will be closed. Explanations at that point can be thin. When regulators asked the public about payments fraud last year, commenters raised concerns about whether bank staff could communicate with a customer at all once a SAR might be involved.
The law is less restrictive than that. About six weeks before the Bank of America announcement, on September 2, the Federal Reserve, the FDIC, the National Credit Union Administration, the Office of the Comptroller of the Currency and FinCEN issued a joint statement on what banks and credit unions may tell customers about suspected fraud, account restrictions and closures. Its conclusion is that the law doesn’t prohibit a bank from discussing the transactions behind a hold or closure, or from saying a closure is tied to suspected fraud, “so long as that communication does not reveal the existence of a SAR.”
The statement also has limits. It “does not alter existing Bank Secrecy Act (BSA) legal or regulatory requirements or establish new supervisory expectations.” It says what banks may say. It doesn’t require them to say it.
This article draws on the Joint Statement on Suspicious Activity Report Confidentiality Considerations Regarding Communications with Customers, as posted by the NCUA; the Treasury Department’s October 13 release on the Bank of America actions; FinCEN’s SAR rule for banks at 31 CFR 1020.320; the OCC’s consumer answers on account closures, exception holds and large deposits; Executive Order 14331, “Guaranteeing Fair Banking for All Americans”; and the final reputation-risk rules from the OCC and FDIC and the NCUA.
Why regulators issued the statement
The statement grew out of check fraud. On June 20, 2025, the Federal Reserve, the FDIC and the OCC asked the public for ideas on how to reduce payments fraud, “with a particular focus on check fraud.” Among the concerns commenters raised was bank personnel’s ability to communicate with a customer when a bank may file or has filed a SAR on potentially fraudulent activity. They asked the agencies and FinCEN to clarify how banks can keep SARs confidential while giving customers “transparent and timely communication as part of the bank’s fraud investigation, which may result in one or more SAR filings and potential closure of a customer’s account.”
The statement ties itself to a second policy thread as well. It “recognizes the concerns expressed in Executive Order 14331,” the August 2025 order on so-called debanking, and says the agencies “intend for this statement to enhance customer engagement and provide customers with greater assurance that their banks and credit unions will provide them with fair access to financial services.”
Although the statement uses “banks” throughout, a footnote explains that the term in FinCEN’s rules includes savings associations and credit unions. The same principles apply at a credit union, whose SAR confidentiality rule appears in the NCUA’s regulations at 12 CFR 748.1(d).
The rule being interpreted
A SAR is a report a bank files with FinCEN about a transaction it suspects. Under the bank rule, a transaction must be reported if it “involves or aggregates at least $5,000 in funds or other assets” and the bank knows, suspects or has reason to suspect one of three things: the money comes from illegal activity or the transaction is meant to hide such money; the transaction is designed to evade Bank Secrecy Act requirements; or the transaction “has no business or apparent lawful purpose or is not the sort in which the particular customer would normally be expected to engage, and the bank knows of no reasonable explanation for the transaction after examining the available facts, including the background and possible purpose of the transaction.”
The third test is the one that turns on a particular customer’s usual activity. A large transfer, a run of cash deposits or a sudden flow of payments from strangers can look out of place for a particular account even when nothing illegal happened. The test turns on whether the bank knows of no reasonable explanation after examining the available facts, and a question about where money came from is one way a bank gathers those facts.
Timing is set too. A SAR is due “no later than 30 calendar days after the date of initial detection by the bank of facts that may constitute a basis for filing a SAR,” with up to 30 more days if no suspect has been identified, and never more than 60 days after initial detection.
Paragraph (e) adds the secrecy rule. It says a SAR, “and any information that would reveal the existence of a SAR, are confidential.” No bank, director, officer, employee or agent “shall disclose a SAR or any information that would reveal the existence of a SAR.” The statute behind it, quoted in the joint statement, bars a financial institution from notifying “any person involved in the transaction that the transaction has been reported.”
The same paragraph contains the opening the September statement builds on. FinCEN’s rule says the confidentiality provision doesn’t prohibit disclosure of “The underlying facts, transactions, and documents upon which a SAR is based.” The joint statement quotes that language and draws the consequence: “the BSA and its implementing regulations do not prohibit banks and credit unions from communicating with a customer or other person who is the subject of a SAR” about the suspicious transactions, or “notifying the customer of the bank’s or credit union’s intention to close the account for potentially fraudulent or other suspicious activity.”
Facts can be discussed, the report can’t
The statement draws the line between the facts behind a SAR and the SAR itself. Banks may discuss “the factual information related to transactions, including, but not limited to, transaction dates, amounts, and parties,” provided nothing is said that would reveal a SAR.
It also deals with the customer who can read between the lines. “Although a reasonable and prudent person familiar with the SAR filing requirement may suspect or be able to deduce from these underlying facts, transactions, and documents that a SAR was or may have been filed, the underlying information alone would not constitute information revealing the existence of a SAR for confidentiality purposes.” In other words, an employee can walk through the transactions that worried the bank even if an informed customer could guess what the bank did next. What the employee can’t do is confirm it.
The statement asks banks to “consider customer communication on a case-by-case basis and take precautions when discussing information that could reveal the existence of a SAR.” In general terms, it says banks “could discuss the transaction(s) in question and concerns thereof, the bank’s or credit union’s remediation efforts, and what potential mitigation steps are available to the customer.”
Seven things a bank may say or ask
The statement gives “a non-exhaustive list of communications that would not typically reveal the existence of a SAR.” Here is each item, followed by what it can look like on a savings or checking account.
- “Requesting customer due diligence-related information or documentation to understand the nature and purpose of customer relationships for the purpose of developing a customer risk profile.” A bank may ask what an account will be used for, what kind of deposits to expect, or for documents that explain a pattern of activity.
- “Notifying a customer that a delay, limitation, or restriction on an account or service or closure of an account may be related to suspected fraud or other suspicious activity.” This item covers holds and closures directly. A bank isn’t barred from saying a hold, a block on outgoing transfers or a closure may be tied to suspected fraud.
- “Notifying a customer that a deposit has been rejected because of suspected fraud or other suspicious activity, for example, in the context of altered or counterfeit checks.” A saver who deposits a check that turns out to be altered can be told that is why it was rejected.
- “Asking a customer about the purpose of a transaction or the source of funds.” A question about where money came from is permitted.
- “Providing warnings or educational resources to a customer about fraud schemes or typologies.” The statement includes cases where “a customer may be defrauded or a customer may be participating, knowingly or unknowingly in a fraud scheme,” and names known “money mule” schemes as an example.
- “Communicating policies or decisions related to account maintenance or services, such as declining a transaction or closing an account.” A bank can tell you it has declined a payment or decided to close the account.
- “Requesting information on the originator or beneficiary of a funds transfer.” A bank may ask who sent an incoming wire or who is receiving an outgoing one.
The statement defines money mules in a footnote: “persons and their accounts that are used to receive and transfer illegally acquired funds, generally on behalf of or at the direction of another and can be witting or unwitting.” In other words, someone who receives money into a savings account and passes it along at another person’s direction can be a mule without knowing it, and the bank is allowed to warn that customer.
What a bank still can’t say
None of that loosens the core prohibition. A bank can’t tell a customer that it filed a SAR or that a transaction “has been reported.” It can’t hand over the report itself. Under the rule, a bank that is “subpoenaed or otherwise requested to disclose a SAR or any information that would reveal the existence of a SAR, shall decline to produce the SAR or such information” and must notify FinCEN of the request.
So a direct question about whether a SAR was filed can’t be answered. Questions about which transactions raised concerns, what the bank needs from the customer and what steps might resolve the problem are different, and the statement says those are topics a bank may discuss.
The rule also protects the bank. A bank that files a SAR is “protected from liability to any person for any such disclosure, or for failure to provide notice of such disclosure to any person identified in the disclosure,” to the full extent of the statute. It covers both the report and the bank’s not telling the person identified in it that the report was made. It isn’t a general shield for how a bank handles restrictions or closures.
Why a bank may still say little
The statement permits communication. It doesn’t mandate it, and it leaves the decision to banks “on a case-by-case basis.” A customer can ask and still get little or no explanation.
For closures, the OCC points customers to the account contract. Its consumer site answers the question “The bank closed my checking account and did not notify me. Is this legal?” this way: “It may be lawful for banks to close a customer’s account under certain circumstances—which may include account inactivity, low account usage, or fraudulent activity—and to do so without providing prior notice.” It adds that “Your deposit account agreement provided at the time the account was opened will include information about your bank’s policies specific to your account.”
The deposit agreement is where the bank’s own policies for an account are written down.
Holds on deposits follow a separate rule
Not every delay is about a SAR. Holds on check deposits to checking accounts come under Regulation CC (12 CFR part 229), which sets a normal availability schedule and then six exceptions that let a bank hold funds longer. The OCC lists them:
- “Checks deposited to new accounts (accounts that were opened 30 or fewer days ago).”
- “Large deposits ($6,725 or more in checks in any one day) but only for the amount in excess of $6,725.”
- “Re-deposited checks.”
- “Deposits made by check to accounts that have been repeatedly overdrawn in the last six months.”
- “Deposits of checks for which the bank doubts collectability.”
- “Deposits made under certain emergency conditions.”
Exception holds come with a disclosure duty that SARs don’t. The OCC summarizes it this way: “If a bank places a longer hold on a deposit under one of these exceptions, it must give you a notice. The notice must give the reason for the hold and tell you when your deposit will be available for withdrawal.” In the regulation itself, 12 CFR 229.13(g) requires that written notice for the large-deposit, redeposited-check, repeated-overdraft and doubtful-collectability exceptions, with alternative forms of notice in some cases. The new-account and emergency exceptions follow their own provisions. Regulation CC allows the schedule to be extended “by a reasonable period of time,” with examples including “An extension of up to five business days for most checks.” The OCC says “a check that is subject to an exception hold would generally be available no later than the seventh business day after deposit,” and a bank that wants longer must “be able to establish that the additional time is reasonable.” That figure lines up with the OCC’s general schedule, under which the rest of a check deposit “should generally be available on the second business day,” plus a five-business-day extension.
There is a catch for savers. Regulation CC’s schedule applies to transaction accounts such as checking. Its definition of “account” for the availability rules says the term “does not include savings deposits or accounts described in 12 CFR 204.2(d)(2) even though such accounts permit third party transfers.” Regulation D, which supplies those definitions, refers to “an MMDA or any other savings deposit,” so a check deposited straight into a savings account or a money market deposit account falls outside Regulation CC’s deadlines and its exception-hold notice. How long the bank holds it depends on the bank’s own policy, which is another reason to read the deposit agreement.
On a checking account, two of the exceptions are relevant when moving money between banks. An account is new “during the first 30 calendar days after the account is established,” unless each customer on it already had another account at the same bank for at least 30 days within the 30 days before. In a new account, the regulation’s availability requirements cover only certain checks, such as U.S. Treasury checks and cashier’s, certified and teller’s checks. For those, the first $6,725 deposited in a day follows the usual rules, and the excess must be available “not later than the ninth business day following the banking day on which funds are deposited.” Other checks deposited to a new account aren’t subject to the regulation’s availability schedule during those 30 days. A large check, such as the proceeds of a home sale paid by check, can trigger the large-deposit exception. The OCC’s answer for a $10,000 check deposit is that “the bank generally must make the first $6,725 available consistent with the bank’s normal availability schedule” and “may place a hold on the amount deposited over $6,725.” Electronic transfers and cash work differently. In the OCC’s words, “Funds deposited electronically or by cash are generally available by the business day after the banking day they were deposited.” There’s more on these schedules in our guide to funds availability rules.
A check-collectability hold and a fraud review can overlap, but they aren’t the same thing. Most exception holds require a written notice with the reason and the availability date. A restriction tied to suspected fraud or other suspicious activity comes with no comparable notice requirement under the rules covered here, which is why the September statement’s list matters.
The Bank of America case, briefly
The October 13 actions show the other side of the system. According to Treasury’s release, as part of its resolution with FinCEN the bank admitted that it willfully violated the BSA and failed to “implement and maintain an AML program that met the minimum requirements of the BSA and FinCEN’s implementing regulations,” failed to “conduct due diligence for correspondent accounts for foreign financial institutions,” and failed to “file suspicious activity reports (SARs).”
Treasury said the bank relied so heavily on law enforcement inquiries and requests from other institutions, rather than its own automated controls, that it “effectively outsourced to third parties a substantial portion of its proactive detection and reporting obligations,” and “allowed suspicious activity to accumulate uninvestigated for extended periods.” Its customer due diligence “failed to account for customers’ extensive reliance on payments from unknown third parties.” The OCC, which assessed its own penalty, said the bank’s transaction monitoring system “resulted in the Bank failing to properly monitor trillions of dollars in transactions.”
The consent order requires the bank “to work with a third party to complete a lookback to identify and report to FinCEN suspicious transactions that went undetected,” and to undergo independent reviews of its monitoring and due diligence programs. The Office of Foreign Assets Control separately settled 475 apparent sanctions violations for $11.6 million.
The release deals with the bank’s obligations to the government and doesn’t address how any individual customer’s account was or will be handled. It does spell out the standard regulators apply: a bank is expected to find and report suspicious activity itself, promptly, with monitoring that fits its customers. The September statement covers the other half, what a bank may tell those customers along the way.
Debanking rules point at regulators
Executive Order 14331, signed August 7, 2025, states that “no American should be denied access to financial services because of their constitutionally or statutorily protected beliefs, affiliations, or political views,” and that “Banking decisions must instead be made on the basis of individualized, objective, and risk-based analyses.” It defines “politicized or unlawful debanking” as restricting or adversely changing a customer’s accounts or services “on the basis of the customer’s or potential customer’s political or religious beliefs,” or lawful business activities the provider “disagrees with or disfavors for political reasons.”
Two final rules followed. The OCC and FDIC rule, published April 10, 2026 and effective June 9, 2026, prohibits those agencies “from requiring, instructing, or encouraging an institution to close an account, to refrain from providing an account, product, or service, or to modify or terminate any product or service” on the basis of a person or entity’s “political, social, cultural, or religious views or beliefs, constitutionally protected speech, or solely on the basis of politically disfavored but lawful business activities perceived to present reputation risk.” The NCUA’s rule, published June 25 and effective July 27, 2026, says the agency “will not consider reputation risk—whether alone or in combination with other factors—in supervisory determinations or other decisions, nor will it take adverse actions on that basis.”
These rules are written as limits on the agencies. The OCC and FDIC rule bars them from “requiring, instructing, or encouraging” closures for the listed reasons. It doesn’t speak to a bank’s own decision to restrict or close an account over suspected fraud, and the order itself calls for decisions based on “individualized, objective, and risk-based analyses.” A customer who believes an account was closed for political or religious reasons has a different complaint from one whose account was closed over a suspicious transfer, but the OCC’s general guidance for a closure the customer believes was wrongful is the same in either case: a written complaint to the bank’s regulator.
Which rule applies to which delay
Holds, restrictions and closures can arrive together, but different rules govern each. In summary:
| What happened | Main rule | What the rules covered here require |
|---|---|---|
| Check deposited to a checking account is held past the normal schedule | Regulation CC exception holds | For most exceptions, a written notice giving the reason and when funds will be available |
| Check deposited to a savings or money market deposit account is held | The bank’s own policy, since the availability rules’ “account” excludes savings deposits | The bank’s availability policy and deposit agreement |
| Transfer blocked, account restricted, or questions about the source of funds | The bank’s fraud and Bank Secrecy Act monitoring, including the SAR rule | Neither the SAR rule nor the September statement requires an explanation; under the statement the bank may discuss the transactions and say the restriction may relate to suspected fraud |
| Account closed | The deposit agreement | The OCC says closing without prior notice may be lawful; a written complaint to the regulator is the route if you believe the closure was wrongful |
What to do when an account is restricted or closed
The statement gives customers a way to frame the conversation. These steps follow from it and from the OCC’s guidance:
- Ask about the transactions, not the report. Which deposits or transfers concerned the bank, on what dates and in what amounts, are facts the statement says can be discussed. A request to confirm whether a SAR was filed will be declined.
- Ask what would resolve it. The statement says banks may discuss “remediation efforts” and “what potential mitigation steps are available to the customer.” That may mean documents showing where funds came from, such as a closing statement for a home sale, a brokerage transfer confirmation or a pay stub.
- Answer source-of-funds questions directly. The rule’s third trigger turns on whether the bank “knows of no reasonable explanation” for a transaction. Documents are one way to give the bank that explanation.
- Ask how and when the balance will be returned. If the bank has decided to close the account, the deposit agreement is where its policies are written down. Ask in writing, and keep copies of statements in case access to online banking ends with the account.
- Read a money mule warning as being about your account. If the bank’s warning describes a pattern that matches what someone has asked you to do, it is one of the communications the statement lists (item 5 above), which covers customers who may be taking part in a fraud scheme “knowingly or unknowingly.”
- Complain to the regulator if you think the bank was wrong. The OCC says: “If you believe your bank wrongfully closed your account, file a written complaint with the bank’s regulator.” Its Who Regulates My Bank page identifies which agency supervises a given bank. National banks and federal savings associations go to the OCC’s Customer Assistance Group.
A closure for suspected fraud can also matter when you open an account somewhere else, if it shows up in a deposit-account screening report. The OCC notes that “Banks may set their own requirements for opening a checking account so long as those requirements are consistent with the law.” Our guide on what to do when you’re denied a bank account because of ChexSystems covers how to get those reports and dispute errors.
A note on keeping cash in one place
For savers, a restriction is more than an inconvenience if the restricted account holds all of their money. Money in a restricted account may not be available for rent or bills while the restriction lasts. Knowing the deposit agreement, keeping records that explain large deposits, and, for some households, keeping a smaller second account at a different institution are ways to limit the effect of a review at one bank. None of these is required by any rule.
The SAR rule’s third test compares a transaction with what “the particular customer would normally be expected to engage” in. A customer can tell the bank about a large, unusual transfer before it arrives, but no rule says the bank must take that into account or that it will prevent a review, and the bank may still ask for documents.
Questions customers ask
Can my bank tell me whether it filed a SAR about me?
No. The rule bars disclosing “a SAR or any information that would reveal the existence of a SAR,” and the statute bars telling a person involved that a transaction “has been reported.” The bank can discuss the transactions themselves.
Does the September statement require my bank to explain a freeze?
No. It says it “does not alter existing Bank Secrecy Act (BSA) legal or regulatory requirements or establish new supervisory expectations.” It describes what banks may say and leaves the choice to them, case by case.
Can the bank close my account without telling me first?
According to the OCC, it “may be lawful” for a bank to close an account for reasons that “may include account inactivity, low account usage, or fraudulent activity—and to do so without providing prior notice.” Your deposit agreement sets out the bank’s specific policies.
My check deposit is on hold. Is that a fraud investigation?
Not necessarily. On a checking account, Regulation CC lets banks hold checks longer under set exceptions, such as new accounts and deposits over $6,725 in a day, and most exception holds require a written notice giving the reason and when the funds will be available. Savings deposits are outside the definition of “account” used for Regulation CC’s availability rules, so for a check deposited to savings, the bank’s own availability policy applies.
Is the rule different at a credit union?
The joint statement covers credit unions. FinCEN’s definition of “bank” in its rules includes credit unions, and the NCUA joined the statement. The NCUA’s own SAR confidentiality rule is at 12 CFR 748.1(d).
Can I sue the bank for filing a report about me?
The rule protects a bank that reports a possible violation “from liability to any person for any such disclosure, or for failure to provide notice of such disclosure to any person identified in the disclosure, or both,” to the full extent of the statute.
The September statement gives customers no right to an explanation, and a bank still can’t confirm a report it is barred from discussing. Under the agencies’ reading of the rule, though, the law doesn’t forbid the conversation itself. A customer whose savings are held or whose account is being closed can ask about the transactions involved and what the bank needs to resolve the matter, and the bank is allowed to answer as long as it doesn’t reveal a SAR.
Further Reading
- How a T-Bill Auction Sets Your Rate: Noncompetitive Bids and the Oct. 15 Rule
- The Premium Tax Credit Has No Repayment Cap for 2026: How Savings Interest Counts
- The 2027 COLA Is 3.6%: Savings Interest, the $25,560 Earnings Limit and SSI
- ABLE Accounts in 2026: Age 46, a $20,000 Limit and SSI’s $100,000 Rule
- T-Bills and Short CDs Bought Now: Which Tax Year Gets the Interest