Skip to main content
Category: Laws and Regulations

314(a) Request

Also known as: Section 314(a) Request, 314(a) Information Request
Simply put

A 314(a) request is a mechanism under the USA PATRIOT Act that allows US law enforcement to reach into the financial system to locate accounts and transactions connected to a person or entity under investigation. Investigators submit the names of subjects, and participating financial institutions check their records to identify any matches. It is a locating tool that helps investigators find where a suspect has touched the banking system, rather than a finding that any wrongdoing has occurred.

Formal definition

Section 314(a) of the USA PATRIOT Act establishes a channel, administered by FinCEN, through which US law enforcement can disseminate subject lists to financial institutions to help locate accounts and recent transactions relating to persons reasonably suspected, based on credible evidence, of engaging in money laundering or terrorist activity. Participating institutions are generally required to search their records for named subjects and report matches back through the designated system, while maintaining confidentiality to avoid tipping off subjects. A 314(a) request should be distinguished from Section 314(b), which provides a voluntary safe harbor for information sharing between financial institutions rather than a law-enforcement-initiated locating request. A positive match indicates a records correspondence only and does not itself establish criminal conduct; specific operational parameters and search obligations should be confirmed against current FinCEN guidance and the FFIEC BSA/AML Examination Manual.

Why it matters

The 314(a) mechanism addresses a fundamental challenge for investigators: a subject under investigation may hold accounts or conduct transactions across many financial institutions, and there is no single directory that reveals where in the banking system a given person has been active. By providing a channel administered by FinCEN through which law enforcement can distribute subject lists to a broad population of financial institutions, Section 314(a) of the USA PATRIOT Act helps investigators locate relevant accounts and recent transactions connected to persons reasonably suspected, based on credible evidence, of money laundering or terrorist activity. It functions as a locating tool rather than an accusatory finding.

For compliance teams, participation carries operational significance because participating institutions are generally required to search their records against the named subjects and report matches back through the designated system, while preserving confidentiality so as not to tip off subjects. The obligation is procedural: a match reflects a records correspondence only and does not itself establish that the matched customer has engaged in criminal conduct. Treating a positive match as proof of wrongdoing would misread the purpose of the process, which is to point investigators toward records they may then pursue through separate legal means.

It is also important to distinguish 314(a) from Section 314(b), with which it is frequently confused. Section 314(a) is a law-enforcement-initiated request that reaches into the financial industry to locate subjects. Section 314(b), by contrast, provides a voluntary safe harbor from liability for financial institutions that choose to share information with one another. Conflating the two can lead to errors in how an institution documents, authorizes, and governs its information-sharing activities. Specific operational parameters and search obligations should be confirmed against current FinCEN guidance and the FFIEC BSA/AML Examination Manual.

Who it's relevant to

BSA/AML Compliance Officers
Compliance officers at participating financial institutions are responsible for ensuring their institution can receive 314(a) subject lists, search records for matches, report matches back through the designated system, and maintain the required confidentiality. They should confirm their institution's specific search obligations and procedures against current FinCEN guidance and the FFIEC BSA/AML Examination Manual, and ensure staff understand that a match is a records correspondence, not a determination of wrongdoing.
Financial Intelligence and Investigations Analysts
Analysts who process incoming 314(a) requests carry out the record searches and evaluate whether the institution holds accounts or recent transactions matching named subjects. They need to understand the distinction between a locating match and evidence of criminal conduct, and to handle results with appropriate confidentiality so as not to tip off subjects.
Law Enforcement Investigators
Investigators use the 314(a) channel, administered by FinCEN, to locate accounts and recent transactions relating to persons reasonably suspected, based on credible evidence, of money laundering or terrorist activity. It helps them identify where in the financial system a subject has been active, which they can then pursue through separate legal processes.
AML Governance and Audit Teams
Teams overseeing program governance and independent testing should verify that 314(a) handling procedures are documented, that confidentiality controls are in place, and that the institution does not conflate 314(a) law-enforcement-initiated requests with the voluntary Section 314(b) information-sharing safe harbor, as the two operate under different authorities and obligations.

Inside 314(a) Request

Statutory Basis
The 314(a) information-sharing mechanism derives from Section 314(a) of the USA PATRIOT Act, implemented through FinCEN regulations under the US Bank Secrecy Act framework. It enables federal, state, local, and certain foreign law enforcement agencies to reach financial institutions through FinCEN to locate accounts and transactions.
FinCEN as Intermediary
Requests are not sent directly by law enforcement to financial institutions. FinCEN acts as the central conduit, collecting requests from qualified investigative agencies and distributing consolidated subject lists to participating institutions, typically on a periodic basis.
Subject of Investigation
A 314(a) request names individuals, entities, or organizations reasonably suspected, based on credible evidence, of engaging in money laundering or terrorist financing. The threshold and scope are set by the requesting agency and FinCEN's process, not by the receiving institution.
Search Obligation
Upon receipt, covered financial institutions are generally required to search their records to determine whether they maintain or maintained accounts for, or engaged in transactions with, the named subjects, over the lookback periods specified by the applicable FinCEN guidance.
Match Reporting
If a search identifies a match, the institution reports the positive match back to FinCEN through the designated secure channel. A match indicates a record relationship to locate, not a finding of wrongdoing by the institution or the subject.
Confidentiality Requirements
Institutions are generally prohibited from disclosing to any person, other than as permitted by the applicable rules, the fact that FinCEN has requested or obtained information, subject to the confidentiality provisions governing the 314(a) program.
Distinction from 314(b)
314(a) is government-initiated information sharing between law enforcement and institutions via FinCEN, whereas 314(b) is a separate, voluntary provision permitting financial institutions to share information with one another under a safe harbor. The two should not be conflated.

Common questions

Answers to the questions practitioners most commonly ask about 314(a) Request.

Does receiving a 314(a) request mean the named individual or entity is under investigation for money laundering?
No. A 314(a) request does not establish that the named subject has committed a crime, nor does it constitute an accusation against your institution's customer. Under the information-sharing provisions of the USA PATRIOT Act as implemented by FinCEN, a 314(a) request is a mechanism by which a law enforcement agency, through FinCEN, asks financial institutions to search their records for accounts and transactions matching a named subject believed to be engaged in, or reasonably suspected of engaging in, terrorist activity or money laundering. A match indicates only that your institution holds or held a relevant relationship or transaction; it is not proof of wrongdoing by the customer and does not by itself determine any criminal-law question. The determination of criminal liability rests with the requesting authority and the courts.
Is a positive match to a 314(a) request the same as filing a SAR, or does one automatically trigger the other?
No, these are distinct processes and a match does not automatically require a SAR. Responding to a 314(a) request means reporting to FinCEN that you have a matching record; it is a search-and-report obligation directed at identifying relationships. A SAR (Suspicious Activity Report) is a separate filing based on your institution's own assessment of suspicious activity under the Bank Secrecy Act and applicable FinCEN rules. FinCEN has generally taken the position that the receipt of a 314(a) request does not, by itself, obligate an institution to file a SAR. However, the information in the request may be a factor an institution considers, alongside its own monitoring and knowledge of the customer, in deciding whether a SAR is warranted. The two decisions should be evaluated separately.
Which records must a financial institution search when responding to a 314(a) request?
The scope is defined by FinCEN's implementing guidance and typically covers current accounts and certain records for a defined look-back period, as well as accounts and transactions within the parameters set out in the specific request. Institutions should search according to the search instructions accompanying each request rather than applying a fixed internal assumption, because the specified account types, time periods, and transaction categories can vary. Records or products falling outside the parameters of the request are generally out of scope. Because exact look-back periods and record categories are set by FinCEN and may be updated, institutions should confirm the applicable requirements against current FinCEN 314(a) guidance.
How quickly must an institution respond, and what should it do if there are no matches?
FinCEN generally sets a defined response window for each 314(a) batch, and institutions are expected to complete their searches and report results within that period. Procedures for negative results differ from positive results: in many cases institutions are instructed to report only positive matches to FinCEN through the designated secure channel, while retaining internal documentation that the search was conducted even where no match is found. Institutions should follow the specific response instructions issued with each request, and confirm the current timing and reporting mechanics against FinCEN's 314(a) guidance, as these operational details are set by FinCEN and may change.
Can information received in a 314(a) request be used for purposes other than responding to the request?
The use of 314(a) information is restricted under FinCEN's rules. It is generally provided for the limited purpose of determining whether the institution maintains or has maintained accounts for, or has engaged in transactions with, the named subject, and to enable a response to the request. Institutions are typically prohibited from using the information as the sole basis for taking adverse action against a customer, such as denying service, and from disclosing the request to persons other than as permitted. The information may, however, inform an institution's own risk assessment and suspicious activity determinations, provided confidentiality and use limitations are observed. Institutions should confirm the precise permitted and prohibited uses against current FinCEN guidance.
What internal controls help an institution manage 314(a) obligations effectively?
Institutions generally establish documented procedures assigning responsibility for receiving requests, conducting searches across the relevant systems, evaluating potential matches, reporting positive results to FinCEN within the required timeframe, and retaining evidence of searches performed. Measures such as designating a point of contact, maintaining secure access to the FinCEN system, applying consistent matching criteria to reduce both missed matches and false positives, and safeguarding the confidentiality of request contents support reliable compliance. These controls are designed to help the institution meet its search-and-report obligations and manage associated regulatory risk; they do not guarantee prevention of financial crime, and their design should be proportionate to the institution's size and risk profile and aligned with current FinCEN requirements.

Common misconceptions

A positive 314(a) match means the institution has identified a criminal or must file a SAR.
A match indicates only that the institution holds or held records relating to a named subject, allowing law enforcement to locate accounts and transactions. It does not establish wrongdoing by the customer or the institution, and it is not itself a determination that a suspicious activity report is required. Any SAR decision remains a separate analysis under the institution's own suspicious activity monitoring obligations.
314(a) and 314(b) are the same information-sharing program.
They are distinct provisions. Under 314(a), law enforcement requests reach institutions through FinCEN so the government can locate relevant accounts and transactions. Under 314(b), institutions may voluntarily share information with each other under a statutory safe harbor. Confusing the two can lead to improper disclosures and misapplied confidentiality rules.
A 314(a) request functions like a subpoena requiring production of account documents.
A 314(a) request generally directs institutions to search their records and report whether a match exists, not to produce underlying documents in response to the request itself. Law enforcement typically must use separate legal process, such as a subpoena or other lawful mechanism, to obtain the actual records after a match is reported.

Best practices

Establish a documented process for retrieving, reviewing, and searching each 314(a) subject list within the response timeframes specified by the applicable FinCEN guidance, and confirm current requirements against the governing regulation.
Maintain strict confidentiality controls limiting knowledge of 314(a) requests to personnel with a need to know, consistent with the program's confidentiality provisions.
Keep clear internal records documenting that searches were performed and the results, including negative searches, to evidence compliance without disclosing the request improperly.
Ensure staff understand that a 314(a) match is a record-location result, not a determination of criminality, and that any suspicious activity reporting decision must proceed through the institution's separate, independent SAR analysis.
Train relevant staff to distinguish 314(a) government-initiated requests from 314(b) voluntary institution-to-institution sharing so that confidentiality and safe-harbor rules are applied to the correct mechanism.
Coordinate with legal or compliance leadership before responding to any follow-on law enforcement process, since obtaining underlying records typically requires separate legal authority beyond the 314(a) request itself.