How Specific Do I Need to Be About Dates and Transactions?

If you are raising a concern about possible Bank Secrecy Act (BSA) or anti-money laundering (AML) failures, specificity matters. A report saying “the bank ignores suspicious activity” may express a genuine concern, but it gives an investigator little to test. A report identifying a date range, account or transaction reference, observed activity, relevant control and supporting record is much more useful.

That does not mean you need to prove a violation before speaking up. Your role is to describe what you observed, distinguish it from what you suspect, and preserve relevant information lawfully. An incomplete date or an approximate amount is better than a guessed one if you label it honestly.

This article explains how to describe transaction dates and account activity, what may distinguish a BSA violation from a mistake, how to document a concern and why timing and anonymity need careful thought. It is general information, not legal advice. Whistleblower protections and deadlines depend on the facts, the reporting route and the law that applies.

Why dates and transactions make a report useful

Investigators need to work out what happened, when it happened and which records might confirm it. “A customer moved money suspiciously” is hard to assess. “Between 4 and 18 March, the account received six cash deposits just below the branch’s review threshold, followed by same-day international wires; I saw no documented escalation in the case file I reviewed” gives an investigator something concrete to examine.

Transaction dates help locate records and establish sequence. Amounts, channels, counterparties, account identifiers and internal case references can help distinguish one event from another. That detail improves investigator usability: the reviewer can search relevant systems, compare activity with policies and determine whether the issue was isolated, repeated or handled appropriately.

Be precise where you can, but do not invent precision. If you remember only that an event occurred in the second week of a month, say so. If you have a date from a system, identify it as the system date and, where relevant, note that the posting date, processing date and date you observed the record may differ.

What may count as a BSA violation—and what may be a mistake?

The BSA and its implementing regulations impose obligations on covered financial institutions, including certain requirements relating to recordkeeping, customer identification and suspicious activity reporting. The exact duties depend on the institution, the activity and the applicable rule. The FFIEC’s BSA/AML Examination Manual is a useful public reference for understanding how examiners assess compliance programmes and controls. It is guidance for examination, not a substitute for the law or a finding that a particular institution violated it.

A reporting concern is not automatically proof of a legal violation. A missed alert, late case note or inconsistent decision may reflect human error, a process weakness, a misunderstanding of policy or a technical problem. Willful misconduct is different: it may involve deliberate concealment, falsified records, knowingly bypassed controls or pressure to suppress a concern. Do not label conduct “fraud” or “willful” unless the facts support that description. Report the evidence and explain what you know versus what you infer.

For example, one analyst’s failure to document a rationale may be a mistake requiring correction. A dated instruction to remove a customer from review despite repeated, documented escalation—and a record altered afterwards—could raise a more serious concern. Even then, the investigator must assess the full context, including whether the instruction was authorised, whether the record was changed and why.

Observation What it may indicate Useful detail to provide A case note is missing Possible documentation gap, human error or control weakness Case reference, review date, applicable procedure and what you checked Similar alerts repeatedly closed without explanation Possible pattern needing review; not proof by itself of a violation Alert dates, closure reasons, roles involved and relevant policy version A record appears deliberately changed after escalation Potentially serious conduct, depending on the facts Original and later versions, timestamps, access history and how you obtained them lawfully

How specific should you be about transaction dates?

For each event or pattern, include the most reliable information available. A useful report often states:

Date or date range: Give the transaction date, posting date or review date as shown in the relevant system. Clarify which one you mean.
Transaction details: Include the amount and currency, transaction type, channel and direction of funds, if known.
Account or customer reference: Use an approved identifier or a masked reference where appropriate. Do not send unnecessary personal data.
Pattern: Explain how many transactions occurred, over what period and what made the activity concerning in context.
Internal handling: Note when an alert, escalation, review or decision occurred and the role or team involved, if known.
Source of your knowledge: Say whether you saw the transaction in a system, reviewed a case file, received an instruction or heard about it from someone else.

Where there are many transactions, summarise the pattern and provide a small, representative set of examples with dates. If you have a longer list, identify the total period and number of items, and explain how the list was compiled. Avoid attaching a large data dump without an index: it can obscure the most important facts and create privacy or security risks.

Evidence and documentation that holds up

A clear, contemporaneous note is often more valuable than a later reconstruction. Record what happened, when you observed it, what system or document you used and what you did next. Separate direct knowledge from hearsay. For instance: “On 12 June, I reviewed case ABC-123 and saw the closure reason ‘no concern’. I did not see a rationale in the notes” is stronger and fairer than “Management hid the suspicious activity”.

What to write down

The date you made the note and the dates of the underlying events.
Relevant transaction references, account activity and system or case identifiers.
The specific policy, control or instruction you believe may be relevant, if known.
What you personally observed, what another person told you and what remains uncertain.
Who you raised the concern with, when, how, and any response or follow-up deadline.
Any changes in duties, access, performance treatment or other events that may be relevant to retaliation concerns, with dates and witnesses.

Keep notes factual and professional. Record corrections transparently rather than silently editing an earlier account. Preserve original documents and metadata only through authorised channels. Do not access accounts or files outside your role, copy customer data to personal devices, alter records, or take confidential material you are not permitted to retain. If you are unsure what you may preserve or disclose, ask a lawyer before doing so.

A simple transaction schedule can help:

Date shown Reference Activity observed Why it matters Source 7 May (posting date) Masked account ending 4821 Three cash deposits, followed by an outgoing wire Appears similar to activity escalated in two earlier reviews Case system viewed 10 May

This is an illustrative format, not a conclusion that the activity is unlawful. Describe the facts and let the appropriate reviewer assess them.

Timing pressure and limitation periods

Do not assume that an internal report pauses a legal deadline. Different claims and reporting routes can have different time limits, and the relevant clock may depend on when an event happened, when it was discovered, the type of claim and the agency or court involved. Some deadlines are short. A deadline to bring a retaliation claim, for example, may differ from a limitation period for an underlying BSA offence or a deadline associated with a particular whistleblower process.

The National Law Review has published material on filing AML/BSA whistleblower lawsuits; use it as a starting point, not as a substitute for checking the current statute, regulations and procedural requirements. The route and deadline should be verified with a qualified lawyer promptly, especially if you have already experienced adverse treatment or are considering a formal claim.

For practical purposes, make a dated timeline now: the transactions or control failures, when you learned of them, each internal or external report, responses received and any employment action. Keep copies only where lawfully permitted. If a deadline may be close, do not wait for an internal investigation to finish before getting legal advice.

Anonymous versus identified submissions

An anonymous report may feel safer, particularly where you fear retaliation. It can also limit follow-up: investigators may not be able to ask what a system field means, clarify a date or assess how you obtained the information. In some whistleblower programmes, anonymity may be available only if a lawyer submits information on the person’s behalf, or eligibility and award rules may require later identification. Requirements vary, so check the specific programme before relying on anonymity.

An identified submission can make follow-up easier and may help establish your firsthand knowledge, but it can expose your identity to people involved in the process or create workplace risks. Confidentiality is not the same as guaranteed anonymity. Before choosing a route, consider who receives the report, what protections apply, whether there is a secure channel and how retaliation concerns should be raised.

Keep a record of the submission date, the channel used, any confirmation number and the exact materials provided. If you are worried about retaliation, document relevant events promptly and seek independent legal advice about protections and reporting options. Do not assume that a general internal policy or a manager’s assurance replaces statutory protections.

A practical report structure

State the concern neutrally: Identify the possible control or reporting issue without declaring a legal conclusion.
Give the time period: Use exact transaction dates where available and label estimates clearly.
Describe the activity: Include relevant amounts, transaction types, account references and pattern.
Explain the basis: Identify what you saw directly and what you learned from others.
Identify the handling: Note alert, escalation, review and decision dates, plus the relevant process or policy.
List supporting records: Give file names, case IDs or system locations, without sending material you are not authorised to disclose.
Flag uncertainty and urgency: Say what needs verification and whether there is a concern about ongoing activity, record changes or retaliation.

Useful references

FFIEC website — includes the BSA/AML Examination Manual and related examination resources.
National Law Review search for AML/BSA whistleblower lawsuit coverage — locate its discussion of filing an AML/BSA whistleblower lawsuit and verify the current legal requirements independently.

The practical standard is not “include every fact you have ever seen”. It is “give enough reliable detail for someone else to find and assess the relevant records”. lawyer-monthly.com Specific transaction dates, a clear account activity timeline, a careful distinction between human error and possible willful misconduct, and dated notes make a concern more credible and more usable—without asking you to overstate what you know.