FinCEN 314(a) and 314(b) Information Sharing

1. Why This Topic Matters

Section 314 of the USA PATRIOT Act (2001) was written on the premise that criminals and terrorist financiers exploit the gaps between institutions and between the private sector and government. Before 2001, a bank that noticed suspicious activity had no clear legal path to compare notes with another bank, and law enforcement had no efficient way to ask thousands of institutions whether a suspect held accounts. Section 314 created two complementary channels: 314(a), a government-to-industry channel, and 314(b), an industry-to-industry channel.

For the CAMS exam, this topic sits inside the domain covering AML/CFT compliance programs, controls and investigations. It is tested frequently because it combines regulatory detail (timelines, record scope, notices) with judgment (confidentiality, permitted uses, interaction with SAR rules). Candidates who confuse the two provisions, or who mix up the numbers, lose easy points. Understanding 314 also matters in practice: a mishandled 314(a) request can tip off a terrorism suspect, and a careless 314(b) exchange can forfeit the safe harbor and expose the institution to liability.

2. What Section 314(a) Is

Section 314(a), implemented at 31 CFR 1010.520, authorizes FinCEN to act as an intermediary between law enforcement and the financial industry. A federal, state, local, or (since 2010) foreign law enforcement agency investigating terrorism or significant money laundering can ask FinCEN to canvass financial institutions nationwide for information about named subjects (individuals, entities or organizations).

Key features:
• Mandatory. Covered institutions must search and respond. Participation is not optional.
• Who is covered. Financial institutions required to maintain an AML program under the BSA: banks, credit unions, broker-dealers, mutual funds, futures commission merchants, money services businesses, casinos, insurance companies, and others as designated.
• Law enforcement certification. The requesting agency must certify that the subject is engaged in, or reasonably suspected of engaging in, terrorist activity or money laundering, and that it has not been able to obtain the information through other means (or that other means would be ineffective or would compromise the investigation).
• Delivery. FinCEN transmits requests through its secure 314(a) system to each institution's designated point of contact, typically on a bi-weekly (every two weeks) cycle, although urgent requests can be sent at any time.

3. How 314(a) Works Step by Step

Step 1 – Designate a point of contact. Each institution provides FinCEN (via its primary federal regulator) with contact details for the person who will receive 314(a) requests. Keeping this information current is itself a compliance obligation.

Step 2 – Receive the request. The request lists subject names and identifiers (dates of birth, addresses, taxpayer numbers, passport numbers, etc.).

Step 3 – Search the required records. The institution must conduct a one-time search of:
• Any current account maintained for a named subject;
• Any account maintained for a named subject during the preceding 12 months; and
• Any transaction conducted outside an account (e.g., funds transfers, monetary instrument sales) by or on behalf of a named subject during the preceding 6 months.
The institution is not required to search historical records beyond these windows, and it is not required to treat the request as an ongoing monitoring obligation (although many institutions choose to add names to internal watch lists as a risk-based practice).

Step 4 – Respond within 14 days. If a match is found, the institution reports it to FinCEN through the secure system within 14 calendar days of the request date (unless FinCEN specifies otherwise). The response generally identifies the matching subject and the fact that an account or transaction exists; it does not transmit copies of records. Law enforcement follows up directly with a subpoena, court order or other legal process to obtain the actual documents. If no match is found, no response is required (a 'positive-match-only' regime).

Step 5 – Protect confidentiality. The institution may not disclose to anyone, including the customer, that FinCEN has requested or obtained information, except as necessary to comply with the request. Access should be restricted to personnel who need it to perform the search.

Step 6 – Use the information only as permitted. The regulation limits use of 314(a) information to: (1) reporting to FinCEN as required; (2) determining whether to establish or maintain an account or engage in a transaction; and (3) assisting the institution in complying with BSA requirements. It may not be used for marketing, general business decisions, or sharing with third parties.

Step 7 – Document. Maintain evidence that the search was performed, who performed it, the date, and the result, so that examiners can verify compliance. Records of the request itself should be handled per FinCEN instructions on retention and destruction.

Important interpretive points on 314(a):
• A 314(a) match does not automatically require a SAR. The institution should review the matched account or transaction and apply its normal SAR decision process. Conversely, a match does not prohibit a SAR if suspicious activity is otherwise identified.
• A match does not require closing the account; that decision is risk-based and left to the institution.
• The 314(a) list is not a sanctions list. Unlike OFAC, there is no blocking or rejection obligation; it is an investigative canvass.
• Requests may come from foreign law enforcement through FinCEN under the 2010 amendments, a point sometimes tested.

4. What Section 314(b) Is

Section 314(b), implemented at 31 CFR 1010.540, permits financial institutions, and associations of financial institutions, to share information with one another for the purpose of identifying and, where appropriate, reporting activities that may involve money laundering or terrorist activity. In exchange for following the rules, participants receive a safe harbor from civil liability (including liability under privacy laws and for breach of contract) for the sharing itself.

Key features:
• Voluntary. No institution is required to participate, and participating institutions are not required to respond to every request.
• Who may participate. Financial institutions required to have an AML program under the BSA, plus associations of such institutions. A compliance consultant, a law firm or a non-covered business cannot participate in its own right.
• Purpose limitation. Sharing must be for identifying or reporting suspected money laundering or terrorist activity. FinCEN's 2020 guidance clarified that participants may share information about activities they suspect may involve money laundering even if they cannot yet identify the specific underlying crime (specified unlawful activity), and that attempted transactions and information relevant to multiple possible predicate offences are in scope.
• Not a general-purpose channel. Information cannot be shared for competitive, marketing or unrelated purposes, and the safe harbor would not cover such disclosures.

5. How 314(b) Works Step by Step

Step 1 – File a notice with FinCEN. Before sharing, the institution (or association) submits a notice through FinCEN's secure system identifying the institution and its point of contact. The notice is valid for one year and must be renewed annually to maintain the safe harbor.

Step 2 – Verify the counterparty. Before sharing, the institution must take reasonable steps to verify that the other institution has also filed a current 314(b) notice. FinCEN provides a list of registered participants for this purpose. Sharing with a non-registered institution falls outside the safe harbor.

Step 3 – Share within the permitted purpose. Participants may exchange customer, account and transaction information relevant to the suspected activity. They may also jointly file a SAR where appropriate.

Step 4 – Maintain confidentiality and security. Shared information must be protected and used only for the permitted purposes. It may not be disclosed to the customer or to unrelated third parties.

Step 5 – Respect SAR confidentiality. This is the most tested nuance. 314(b) does not override SAR confidentiality rules. An institution may share the underlying facts (for example, 'customer X moved funds through these accounts in this pattern'), but it may not disclose that a SAR has been filed, or share the SAR itself or any information that would reveal its existence, except as specifically permitted by the SAR regulations (such as joint filers sharing the joint SAR among themselves).

Step 6 – Document. Keep records of requests made and received, verification of counterparty registration, and the information exchanged, as evidence that the safe harbor conditions were met.

Practical uses of 314(b): tracing funds flows across institutions, confirming whether a suspected fraud or laundering scheme touches other banks, resolving suspicious wire activity, identifying mule account networks, and strengthening SAR narratives. FinCEN actively encourages participation and highlights that information shared under 314(b) frequently improves SAR quality.

6. Side-by-Side Comparison (memorize this)

Direction of flow: 314(a) = government (via FinCEN) to financial institutions; 314(b) = financial institution to financial institution.
Nature: 314(a) = mandatory; 314(b) = voluntary.
Legal basis: 314(a) = 31 CFR 1010.520; 314(b) = 31 CFR 1010.540.
Trigger: 314(a) = FinCEN request on behalf of law enforcement investigating terrorism or significant money laundering; 314(b) = institution's own suspicion of money laundering or terrorist activity.
Prerequisite: 314(a) = designated point of contact; 314(b) = annual notice to FinCEN and verification that counterparty has filed.
Search scope (314(a) only): current accounts, accounts in prior 12 months, non-account transactions in prior 6 months.
Timing: 314(a) = respond within 14 days, positive matches only, requests typically bi-weekly; 314(b) = notice valid one year, no fixed response deadline.
Protection: 314(a) = strict confidentiality of the request; 314(b) = safe harbor from liability if conditions met.
Relationship to SAR: 314(a) match does not by itself require a SAR; 314(b) sharing may support a SAR or joint SAR but cannot reveal SAR existence.
Use restrictions: 314(a) = reporting to FinCEN, account decisions, BSA compliance; 314(b) = identifying and reporting possible money laundering or terrorist financing only.

7. Common Misconceptions to Avoid

• 'A 314(a) hit means we must file a SAR and close the account.' Wrong. Review the activity; decide on a risk basis.
• 'We respond to every 314(a) request, even to say we found nothing.' Wrong. Only positive matches are reported.
• 'We must search all historical records for a 314(a) request.' Wrong. 12 months for accounts, 6 months for non-account transactions, unless FinCEN specifies otherwise.
• 'We can send the account statements straight to the detective who is named in the request.' Wrong. Report the match to FinCEN; law enforcement obtains records through legal process.
• 'Once registered for 314(b) we can share anything with any bank.' Wrong. Counterparty must be registered, purpose must be AML/CFT, and SAR confidentiality still applies.
• '314(b) registration is one-time.' Wrong. It must be renewed annually.
• 'Any company can join 314(b).' Wrong. Only BSA-covered financial institutions required to have AML programs, and associations of them.
• '314(a) is like OFAC screening.' Wrong. No blocking or rejecting; it is an investigative inquiry, not a sanctions program.

8. Exam Tips: Answering Questions on FinCEN 314(a) and 314(b) Information Sharing

Tip 1 – Identify the direction first. Read the scenario and ask: who is sharing with whom? If FinCEN or law enforcement is asking the institution, it is 314(a). If two or more institutions are exchanging information about a customer, it is 314(b). Most questions can be narrowed to the correct provision in the first sentence.

Tip 2 – Look for trigger words. 'Mandatory', 'FinCEN request', 'law enforcement', '14 days', 'point of contact', 'positive match' point to 314(a). 'Voluntary', 'safe harbor', 'notice to FinCEN', 'annual', 'verify the other institution is registered', 'another bank asks us' point to 314(b).

Tip 3 – Know the numbers cold. 14 days to respond; 12 months for accounts; 6 months for non-account transactions; requests roughly every 2 weeks; 314(b) notice valid 1 year. If an answer choice contains a different number (e.g., 30 days, 5 years), it is almost certainly a distractor.

Tip 4 – Remember 'positive matches only'. If a question asks what the institution must do when no match is found, the answer is: document the search internally and take no further action with FinCEN.

Tip 5 – Separate 'match' from 'SAR'. When a scenario describes a 314(a) hit and asks the next step, the best answer is usually to review the customer's activity and determine whether a SAR is warranted, not to file a SAR automatically or to close the account immediately.

Tip 6 – Confidentiality beats customer service. Any answer that involves telling the customer about a 314(a) request, or telling a 314(b) counterparty that a SAR was filed, is wrong. Tipping-off and SAR confidentiality principles are never overridden by Section 314.

Tip 7 – Safe harbor has conditions. If a 314(b) scenario describes sharing with an unregistered institution, sharing for a non-AML purpose, or sharing SAR existence, the institution has stepped outside the safe harbor. Expect questions asking which step was missed: usually the annual notice or the verification of the counterparty.

Tip 8 – Eligibility questions. If asked who can participate in 314(b), choose financial institutions required to have a BSA AML program (and associations of them). Eliminate options such as law firms, auditors, vendors or non-financial businesses.

Tip 9 – Records go through legal process. If a question asks how law enforcement obtains the actual account documents after a 314(a) match, the answer is via subpoena or other legal process, not through the 314(a) response itself.

Tip 10 – Apply the 'best answer' discipline. CAMS questions often present two plausible actions. Prefer the answer that (a) complies with the regulation's explicit requirement, (b) preserves confidentiality, and (c) reflects risk-based judgment rather than an automatic or extreme reaction. For example, 'conduct the required search and report any match to FinCEN within 14 days while restricting internal access to the request' beats 'immediately freeze the account and notify the customer'.

Tip 11 – Watch for 'scope creep' distractors. Statements such as 'the institution must monitor the 314(a) names on an ongoing basis' or 'the institution must search all affiliates worldwide' overstate the rule. The regulatory requirement is a one-time search of specified records; ongoing monitoring is a risk-based option, not a mandate.

Tip 12 – Connect to the bigger picture. Some questions test why 314 exists. The correct framing: it facilitates public-private and private-private information sharing to detect terrorist financing and money laundering, closing gaps that criminals exploit by spreading activity across institutions.

9. Quick Recall Summary

• 314(a): FinCEN asks, you must search (current accounts, 12 months of accounts, 6 months of non-account transactions), report only matches within 14 days, keep it confidential, use information only for reporting, account decisions and BSA compliance, and do not assume a SAR or closure is required.
• 314(b): You choose to share with another registered financial institution to detect or report money laundering or terrorist financing; file the annual notice, verify the counterparty, protect the information, never reveal SAR existence, and you receive a safe harbor from liability.
• Both: created by the USA PATRIOT Act, administered by FinCEN, intended to break down information silos, and heavily tested for the distinction between mandatory versus voluntary, direction of sharing, timelines and confidentiality.