Suspicious activity reports built from data you already hold

DetectX® Regulatory Reporting turns an alert and the data in your systems into a report for your Financial Intelligence Unit, in the goAML XML structure it requires. The client, accounts and transactions are filled in for you, the analyst reviews and completes the facts, and every report is kept in one inventory.

Request a demoTalk to us
  1. 1Collect
  2. 2Create
  3. 3Archive
  4. 4Platform tour
DetectX - One Platform. Total Compliance (FINAL CAPTIONS)

One Platform. Total Compliance.

The DetectX® Approach

The report starts where the investigation ended.

A suspicious activity report is the notice a regulated firm files with its Financial Intelligence Unit when it suspects money laundering or terrorist financing. Many FIUs receive these reports through goAML. DetectX® prepares them in the goAML XML structure from the alert and the client, account and transaction data your bank already holds.

From an alert to a report your FIU can read. A report starts from the alert or investigation, or from scratch. Regulatory Reporting fills it from the client, account and transaction data you already hold, and produces it in the goAML XML structure.

Starting pointThe Alert or InvestigationAlert details carried into the report.
From your dataClients and AccountsProducts and accounts the client used.
From your dataTransactions and PaymentsThe history behind the suspicion.
Regulatory ReportingReport PreparedFilled from your data and your templates, then reviewed and completed by the analyst.
PaymentTransaction historyBookingActivity
How client and account data is prepared
OutputgoAML XMLIn the structure your Financial Intelligence Unit requires.
KeptReport InventoryEvery report, with its creator, dates, status and alert.

Reports can also be created from scratch, without an alert.Example structure: goAML for MROS, Switzerland.

Key Benefits & Impact

A submission nobody can reconstruct is not a defensible submission.

Regulatory Reporting builds each report from records you already hold, in the structure your Financial Intelligence Unit expects, and keeps every report it builds. Your analysts write the facts, not the account numbers.

No Retyping

Your analysts write the facts, not the account numbers.

The client, the products and accounts they used and their transaction history are carried into the report from the data you already hold. The analyst’s time goes on the presentation of the facts and the reason for suspicion.

Reports that start from a closed investigation
The Right Transactions

A report that carries what matters, and only that.

Transactions are selected by groups your bank defines, by account, customer, period, direction and amount. The estimated count is shown before the report is generated, so nothing irrelevant goes in by accident.

Where the transaction history comes from
The Codes Your FIU Expects

Every analyst picks from the same list.

Report types, reasons, predicate offences, attachments and report indicators are set as templates for your bank. The codes your FIU’s specification requires are chosen, not looked up and typed.

Templates configured for your bank
Reviewed Before It Leaves

Checked in the report, not in the XML.

The generated report opens section by section for review. Corrections can apply everywhere the same information appears, and the XML is produced only when the analyst is done.

How client and account data is prepared
Every Report on File

Which reports went out, who filed them, and when.

Every generated report is kept in one inventory with its creator, dates, status, type, client, accounts and the alert it came from. It can be searched by ID or text, opened, or downloaded again.

The client’s risk history, beside the report
Management and Audit Reports

The questions a supervisor asks, answered from one place.

Standard and custom reports, charts and exports cover alerts, investigations and processing. Session, list and import reports show whether screening data is current, and the audit report records every interaction.

Screening lists the reports check

Why DetectX®

Most reports are retyped from the core system. DetectX® builds them from it.

Request a demoTalk to our team
  • The client, filled inName, address, accounts and products retyped from the core systemFilled from your data, with the accounts and products usedHow client data is prepared
  • The right transactions214 transactions copied in one by oneSelected by transaction group and counted before generatingTransaction Monitoring
  • The codes your FIU expectsReasons, offences and indicators looked up in the specificationChosen from templates your bank has setTemplates configured for your bank
  • In the structure requiredA form filled to match the XML by handProduced as goAML XML, reviewed section by section firstHow a report is built
  • Every report on fileA folder of files, and nobody sure who filed whatOne inventory with creator, dates, status and alert, plus an audit reportKey benefits
  • Picks up where the case endsThe investigation and the report kept apartStarts from the alert or investigation in WorkflowsWorkflows

In production

Report Types

Hundreds of transactions, selected rather than copied.

4 Report Types

Payment, transaction history, booking and activity reports, each with the fields its purpose needs.

Where the transaction history comes from

Your Next Step

Three ways in, depending on where you are.

Each one is a conversation with the people who build DetectX®, with no obligation.

Start Here

Request a Demo

Watch Regulatory Reporting work through real alerts with a product specialist.

  • Alerts explained, field by field
  • Thresholds tuned in front of you
  • Your questions answered on the call
30 min · Video callRequest

Talk to Our Team

Bring your data, volumes and core banking system. We map where DetectX® fits.

  • How DetectX® connects to your systems
  • Which data you would use
  • A realistic plan for going live
45 min · Video callBook a call

Ask for a Reference

Speak with a compliance team already running DetectX®.

  • A peer with a set-up close to yours
  • Their experience, in their words
  • Arranged with their agreement
By arrangement · CallAsk us

How Regulatory Reporting Works

Try it yourself: five steps, from an FIU request to a filed, audited report, and the management reports built from the same data.

Every report comes from data DetectX® already holds: alerts, customers, accounts, transactions and the work done on them. Suspicious activity reports go to the FIU in its goAML structure, MROS for Switzerland and goAML elsewhere. Management gets reports and charts on the same data. Every step is yours to drive.

Illustrative exampleInvented Names & Data

Explore the DetectX® Platform

Start with Regulatory Reporting. See where its reports begin.

Every DetectX® solution runs on the same underlying platform and shares its capabilities, AlertViewer and audit trail. Pick a solution to see what it brings to a report for your Financial Intelligence Unit.

All solutions

Regulatory Reporting FAQs

What compliance teams ask before choosing DetectX®.

Something we have not covered?Talk to our team

A suspicious activity report (SAR) is the notice a regulated firm files with its Financial Intelligence Unit when it suspects money laundering or terrorist financing. Where the report carries the payments or transactions behind the suspicion, it is often filed as a suspicious transaction report (STR). DetectX® prepares both, from the alert and the client, account and transaction data your bank already holds.

Reports are produced in the goAML XML structure, which many Financial Intelligence Units use to receive reports. The structure is documented in full for MROS, the FIU in Switzerland. Reports for other goAML FIUs follow the same structure, with templates for that FIU’s specification. The process of creating, managing, submitting and archiving each report is the same.

Both. A report can be opened from an alert or an investigation, with the alert’s details and the client carried over. It can also be created from scratch when the case began outside DetectX®.

SolutionReports that start from a closed investigation

The client, the products and accounts they used and their transaction history come from your data. Transactions are selected by groups your bank defines, and the estimated count is shown before the report is generated. Report types, reasons, predicate offences and indicators are chosen from your templates. The analyst writes the presentation of the facts and the reason for suspicion.

SolutionWhere the transaction history comes from

It is kept in the report inventory with its creator, dates, status, type, client, accounts and the alert it came from. It can be searched by ID or text, opened again, or downloaded as XML for submission. Review and editing happen in AlertViewer, because once downloaded as XML a report can no longer be edited.

SolutionThe client’s risk history, beside the report

Yes. The Reports section includes standard and custom reports, statistical charts and exports on alerts, investigations, users and processing. Session, active list and list import reports show whether screening data is current. The audit report records every interaction in AlertViewer.

SolutionScreening lists the reports check

Go Deeper

All resources
InsightAML in Action: Building a Smarter Compliance Framework for Finance

What a working AML framework needs, from customer checks and monitoring to escalation and reporting to the authorities. It also covers where reporting fits once a suspicion is confirmed.

Read the articleInsightUnderstanding Fin Crime: Compliance and Risk Management Guide

The main financial crime threats, from fraud to money laundering, and the compliance and risk measures institutions use against them. It includes the obligation to report suspicions to the Financial Intelligence Unit.

Read the articleInsightThe Future of Financial Compliance Trends to Watch in 2025: Top Insights and Priorities

The regulatory and technology trends expected to shape financial compliance in 2025, and what they mean for how institutions detect, document and report.

Read the article

Regulatory Reporting · DetectX®

See Regulatory Reporting in a demo

Book a demonstration on your own reporting questions: which source systems feed the report, what the goAML XML holds, and what the repository keeps once a submission is finalised.

Request a demoTalk to us
goAML XML
Generated from the source data, to the Fedpol / MROS technical requirements.
Audit-ready by default
Version control, access management and full audit traceability on every generated report.
One platform
Built on the AlertViewer, with p.Lib.Admin holding the data dictionaries and reference tables.