File goAML SAR and STR reports without leaving Bits

Reporting a suspicion should be the end of an investigation, not the start of a new data-entry project. In Bits, the Reports hub lets you build a Suspicious Activity Report (SAR) or a Suspicious Transaction Report (STR) in the goAML format for Sweden and Finland, right next to the cases and entities the report is about.

First, what these reports are. When an obliged entity suspects money laundering or terrorist financing, it must report to its national financial intelligence unit. Sweden’s Finanspolisen and Finland’s financial intelligence unit both receive these reports through goAML, the reporting system developed by the UN Office on Drugs and Crime, as structured XML files with a fixed schema for the reporting entity, the parties involved, the transactions, and the indicators that describe the suspicion. A SAR describes suspicious activity in general; an STR is tied to one or more specific transactions.

In practice, that filing step is where a lot of time goes. An analyst who has just closed an investigation has to retype names, identifiers, addresses, account numbers, and amounts into a separate portal, often for several parties, and a typo in an identifier can mean a report that does not match the customer record it came from. Common cases are an STR after a transaction monitoring case is confirmed, or a SAR when onboarding surfaces a pattern across several applications. The Reports hub is built to take most of the retyping out of both.

What’s new

Open the Reports hub, click Create new report, pick the country and the report type, and you get a guided form with a side navigation: report info, attachments, indicators, parties, goods and services, and a preview. STR drafts add a transactions section, with at least one transaction required and a CSV import for bulk entry.

Parties can be prefilled from entities that already live in Bits. For an individual you pick which fields to carry over, such as identifiers, citizenships, contact details, addresses, and PEP status. Organizations and bank accounts have their own prefill dialogs. Less retyping means fewer mismatches between the report and your customer record.

Save a draft and come back to it when a second reviewer has had a look. When the report is ready, the preview section shows every field as it will be exported, and one click downloads the goAML XML file for upload to the financial intelligence unit’s portal.

Set it up once

• Enabled countries: switch on Sweden, Finland, or both.

• Reporting entity id: your goAML identifier is stored once and reused in every report.

• Reporting users: the people who can appear as the reporting person.

Saved reports appear as tabs in the hub, so earlier SARs and STRs are easy to find per country. The same hub hosts the F880 annual AML/CFT report, with sections A to H, draft saving, and JSON or CSV export.

A report built from the case itself is faster to write and easier to defend, because the parties, transactions, and indicators come straight from the data you investigated.

Why this matters for compliance

Regulatory reporting is where good investigation work often gets lost in copy-paste. Keeping the report form inside the same platform as your entities and transactions shortens the path from decision to filing, keeps identifiers consistent, and leaves you with an archive of what was reported and when.

Want to see it in action? Reach out to learn how Bits Technology can streamline your compliance operations.