A well-written suspicious activity report starts with a well-run investigation. Clear prose cannot repair missing transactions, unexplained assumptions or an undocumented decision. The investigation file should allow another competent reviewer to understand the concern, the evidence examined, the uncertainty remaining and the basis for escalation or closure.

In the UK, the National Crime Agency’s SAR guidance explains reporting routes and distinguishes SARs from crime reports. Its submission guidance emphasises useful information and a coherent reason for suspicion. The practices below are recommendations for investigation quality; local reporting law determines duties, thresholds and deadlines.

Establish the question the investigation must answer

Record why the case opened and what information is available at that point. An alert is a starting signal, not a conclusion that criminal conduct occurred. Distinguish an unusual event, an unresolved explanation and the eventual assessment of suspicion.

Create a proportionate investigation plan. Identify relevant customer records, transactions, connected cases and reliable external information. Preserve the observation period and search scope. A reviewer should be able to tell whether no relevant activity was found or whether the activity was never examined.

Keep facts, customer explanations and analyst interpretations separate. For example, the existence of a payment is a recorded fact; its stated commercial purpose is an explanation; and an analyst’s view of that explanation is an assessment. Combining them in one sentence can make an unsupported inference look established.

Build a chronology that preserves context

Arrange material events in time and identify the source of each event. Use consistent dates, currencies and identifiers. Explain relationships between parties without relying on internal abbreviations that an external reader cannot interpret.

Where an amount is aggregated, record the underlying population and avoid double counting reversals or transfers between the same customer’s accounts. An accurate total is valuable only if its meaning is clear. If data are incomplete, state the limitation and assess whether additional information is necessary before a decision can be made.

A good narrative also records relevant information that weakens the initial concern. Investigations should test explanations, not merely collect material supporting the first hypothesis. This improves both escalation decisions and the quality of justified closures.

A hypothetical investigation with an incomplete explanation

Suppose a business customer’s account activity differs substantially from the description recorded at onboarding. The investigator reviews the relevant transactions and obtains an explanation through authorised channels. Some information is consistent with legitimate expansion, but a material part of the activity remains unexplained.

The decision record should describe what was resolved and what remains concerning. It should not turn the unresolved element into an allegation of a specific offence without evidence. The responsible reporting officer then applies the relevant legal threshold and records the reporting decision.

This example is about evidential discipline. It does not prescribe a reporting outcome, transaction threshold or investigative technique for every institution. Those choices depend on the facts, legal obligations and the bank’s authorised procedures.

Use quality assurance without delaying required reporting

Quality checks should address the issues that make a report intelligible: party identification, chronology, relevant activity, the reason for suspicion and clear separation of evidence from inference. Check that attachments or referenced records are handled through the permitted reporting route and that the narrative stands on its own where required.

Design review arrangements around applicable reporting deadlines. A quality-control queue must not become a reason for missing an obligation. Define escalation for urgent cases and preserve a controlled mechanism for correcting or supplementing information when the reporting framework allows it.

Access should be restricted to authorised staff. Customer communications and information-sharing decisions need assessment against confidentiality, data-protection and tipping-off restrictions. A polished report is not successful if its handling creates a separate breach.

Learn from cases after the decision

Capture recurring data gaps, unclear procedures and investigation rework. Feed those findings to onboarding, monitoring and training owners. Do not use the number of reports filed as a stand-alone measure of investigator quality; it can reward volume without demonstrating better decisions.

More useful measures include material factual corrections, unsupported conclusions, repeat requests for missing information and the quality of closure reasoning. An effective investigation process helps the bank reach defensible decisions and gives the receiving authority information it can understand and use.