How to Respond to a 314(a) FinCEN Information Request: Step-by-Step Guidance for Banks and MSBs
[Banks and MSBs typically have 14 calendar days to respond to a FinCEN 314(a) information request. These requests are part of a federal information-sharing program designed to identify accounts and transactions tied to suspected money laundering or terrorist financing. This article provides step-by-step, compliance-focused guidance for triage, searching, documenting, responding, and managing legal risk.]
FinCEN’s Section 314(a) program is one of the most operationally important federal information-sharing tools for banks and money services businesses (MSBs). When a 314(a) request arrives, the institution is being asked—on a time-sensitive basis—to search its records for specified subjects (individuals, businesses, accounts, addresses, identifiers) linked to law enforcement investigations of money laundering or terrorist financing. The response must be accurate, timely, and carefully documented, while maintaining strict confidentiality.
Below is a practical, step-by-step framework for handling 314(a) requests in a way that aligns with Bank Secrecy Act (BSA)/AML expectations, supports examination readiness, and reduces legal and operational risk.
1) Understand what a 314(a) request is—and what it is not
What it is: A FinCEN-facilitated request that asks participating financial institutions to search for accounts and transactions associated with named subjects. Requests are issued approximately every two weeks and are available to designated points of contact through FinCEN’s secure 314(a) system.
What it is not:
- Not a subpoena or summons (though it is a legally authorized, mandatory search obligation for participants).
- Not a request to freeze or close accounts (unless you separately identify legal obligations, e.g., OFAC blocking requirements or law enforcement legal process).
- Not an instruction to file a SAR—but it may trigger internal review that results in SAR filing if suspicious activity is identified.
Key timing point: Institutions generally have 14 calendar days to complete the search and report results (or “no matches”) through the 314(a) system, unless FinCEN specifies otherwise.
2) Triage immediately: assign ownership, confirm access, start a response clock
Time management is the first compliance control. As soon as the request is received:
Designate a primary owner and backup
Most institutions route 314(a) requests to the BSA Officer, AML investigations team, or a designated FinCEN 314(a) point of contact (POC). Confirm that (1) the assigned personnel have system access, (2) there is backup coverage for vacations or outages, and (3) there is a clear internal escalation path (Compliance → Legal → Business line leadership, as needed).
Open a case file with a documented timeline
Create a case record capturing:
- Date/time the request was received
- Response deadline (calculate and record)
- Unique request reference identifiers
- Names/identifiers of the subjects
- Who is assigned to search and who will quality-check
Run a confidentiality check
Limit distribution to staff with a need-to-know. 314(a) requests and the fact of their existence are highly sensitive; treat them as “restricted supervisory/law enforcement information” for internal handling purposes.
3) Parse the request carefully: identify search terms and match logic
314(a) lists can include multiple data points per subject—names (including aliases), dates of birth, addresses, tax IDs, passport numbers, business names, or other identifiers. Your first task is to translate the list into usable search criteria.
Create a structured search worksheet
For each subject, list:
- Primary name and aliases
- Unique identifiers (DOB, SSN/ITIN/EIN, passport, registration numbers)
- Known addresses, phone numbers, emails (if provided)
- Associated entities or related parties
Define what counts as a “match”
Institutions commonly use a tiered approach:
- Strong match: exact or near-exact name plus a unique identifier (DOB/Tax ID) or multiple corroborating fields.
- Possible match: name similarity with limited corroborating data; requires analyst review.
- False positive: name similarity only, clearly inconsistent identifiers, unrelated geography, etc.
Document your match thresholds. Examiners often focus less on whether you found a match and more on whether your methodology is reasonable, repeatable, and defensible.
4) Execute a defensible search across all required systems
A common pitfall is searching only the core account system. A well-designed 314(a) search typically includes customer, transactional, and ancillary systems that may store relevant identifiers.
Minimum systems to consider (tailor to your institution)
- CIP/KYC files: onboarding platforms, customer master records, beneficial ownership/ownership attestations
- Core banking or ledger: deposit accounts, loans, cards (where applicable)
- Transaction monitoring and payments: wires, ACH, checks, RDC, card activity, bill pay, RTP (if used)
- MSB-specific platforms: money transfer systems, prepaid, virtual currency rails (if applicable), agent/branch systems
- Trade names / DBA references: merchant onboarding systems, acquiring platforms (if relevant)
- Historical/closed accounts: include closed accounts within the applicable lookback window
Apply a clear lookback window
As a practical baseline, many institutions search current customers and a defined historical period (often aligned with retention requirements and internal procedures). Use your written policy, and if the request calls for a specific timeframe, follow that instruction.
Use name-matching tools appropriately
If you use automated screening (fuzzy logic, phonetic matching), record the parameters (e.g., match score threshold). If searches are manual, preserve screenshots or query logs showing how terms were run and which systems were checked.
5) Analyze potential matches and collect the right supporting data
When you identify a potential match, treat the next steps like a focused investigation—without over-collecting or over-sharing.
Confirm identity with corroborating data
For individuals, compare DOB, address history, ID numbers, phone/email, and known associates. For entities, compare EIN, formation state, registered agent, address, beneficial owners, and signers.
Gather reportable details commonly requested
While the 314(a) system response format governs what you submit, you should be prepared internally to assemble:
- Account numbers (or internal identifiers)
- Account opening date and current status (open/closed)
- Customer information (name, address, DOB/EIN)
- Transaction details that evidence activity (dates, amounts, counterparties, instruments)
Example (bank): name + DOB match with wire activity
A 314(a) subject list includes “Juan Martinez” with DOB 03/14/1985 and an address in Phoenix. Your system shows an open checking account for “Juan A. Martinez,” same DOB, and an address in Phoenix. In the last 60 days, the account sent multiple international wires just below internal thresholds to a high-risk corridor. This is a strong match for 314(a) reporting and may warrant an internal suspicious activity review.
Example (MSB): alias + phone match with remittance pattern
A request lists “Amina Hassan” and alias “Amina H.” with a phone number. Your remittance platform shows “Amina H.” using the same phone, multiple send-outs to a common recipient across different locations. Even if the name is abbreviated, the unique phone identifier supports a likely match requiring escalation.
6) Submit the 314(a) response correctly—and on time
Responses are submitted through FinCEN’s secure 314(a) mechanism. Institutions generally respond either:
- No matches found; or
- Matches found, with requested account/transaction details entered in the system.
Quality control before submission
Implement a “four-eyes” review for:
- Correct subject selection (avoid reporting on the wrong person/entity)
- Accurate account and identifier data
- Consistency with match rationale and internal documentation
- Timeliness (confirm submission before the deadline)
If you encounter technical issues (access problems, system outage), document the issue and escalate immediately to your FinCEN 314(a) administrator and internal IT/compliance leadership. Do not wait until the deadline day.
7) Maintain strict confidentiality and manage internal communications
Confidentiality is central to the 314(a) program. Treat the request as sensitive law enforcement information. As a best practice:
- Do not disclose the request or any response details to the customer or any unauthorized party.
- Limit internal discussion to staff directly involved in searching, investigating, and responding.
- Store related records in restricted-access compliance repositories.
SAR considerations: If your review results in a SAR decision, remember that SAR confidentiality rules apply. Separately, avoid blending “314(a) response communications” into customer-facing notes or ordinary servicing tickets that could be discoverable or inadvertently disclosed.
