The data collection component enables secure electronic submission of reports (UTRs, STRs, CTRs, and EFTRs) from reporting entities using 512-bit SSL encryption. It supports the registration of reporting entities, management of contact details, report uploads, and data entry.

Reports can be submitted via:

• Offline XML (e.g., email attachments, CDs, hard drives)

• Online XML upload through the goAML portal

• Online web forms on the FIU’s secure goAML website

Report formats are predefined. Paper submissions can be manually entered by the FIU. Additional data (e.g., bank statements, account details) can be submitted online or offline.

goAML Web offers a secure platform for communication and reporting. It supports:

• XML file uploads

• Web-based report forms

• Secure email submission

The platform also allows for targeted or bulk communication, links to relevant websites, and customization to meet local requirements.

Web-based forms simplify the reporting of multi-party transactions—especially useful for high-value goods dealers who typically report only one party per transaction.

Report Collection is made easier by configuring Customizable Report Forms where manual data entry form for each report type can be customized for each reporting sector. This enables simpler forms based on needs of each sector especially Designated Non-Financial Sectors.

The Additional Information Report (AIR) feature allows FIUs to request and receive follow-up data (e.g., transaction histories) electronically. This information is uploaded in XML format and becomes instantly accessible to analysts via the goAML database.

The Workflow System enables FIU management to define and automate sequenced steps for handling information, aligned with the FIU’s standard operating procedures. It governs the full cycle—from report receipt and analysis to intelligence dissemination and feedback—while remaining flexible to accommodate urgent or exceptional cases.

Multiple customizable workflows can be configured for different tasks, such as initial report analysis, case proposal, and full case investigation, with each stage following its own defined process.

The system can visually display workflows as diagrams, which update automatically with changes. It also generates statistical and status reports, providing management with real-time insights into ongoing tasks and overall workflow performance.

The Charting and Diagramming tool in goAML is fully integrated and continuously maps analytical activities as they occur. It allows analysts to visualize transactional flows and relationships between parties, such as individuals, entities, accounts, addresses, and phone numbers.

Analysts can toggle between chart and data table views or use both simultaneously on dual screens. The tool supports drill-down analysis by automatically retrieving and linking data from the database to reveal flows and associations. Analysts can also build charts step-by-step from selected objects or create diagrams manually, independent of the database.

Charts are compatible with i2 Analyst’s Notebook©, enabling seamless sharing and continued development by external agencies during investigations.

Diagramming works at the operational analytical level where a case officer starts the diagram with a target in mind. A new tool Graph Database extends the analytical capabilities to a more strategic level. Graph allows for looking at data to understand and detect trends and patterns. It uses a special query language called Ciphers which provides a very enriched method to ask strategic questions to be analyzed visually.

The Case Proposals component initiates the escalation phase in the FIU’s intelligence cycle, automating case building to save analysts significant time. Once an analyst decides a matter warrants further investigation, they create a case proposal.

When data (e.g., a name) is added to the case proposal, all related information—addresses, accounts, transactions, associates—is automatically linked and included. The case proposal becomes a central, collaborative workspace accessible to others in the FIU, with progress monitored by supervisors.

Case proposals can also be generated automatically via data matching. The complete case or parts of it can be shared as an intelligence package with law enforcement or authorities.

Typically, cases escalate from proposal to full case files, though the proposal step can be skipped for direct escalation from analysis.

FIU personnel can manually review, accept, or reject individual or all reports submitted by reporting entities.
Alternatively, the Data Clean-Up component automatically validates incoming electronic data in a secure staging area (DMZ), checking for completeness and XML schema compliance. XML Schema compliance is made more flexible by allowing to add schema-assert rules. These rules provide a very robust and fast mechanism for real-time data checks based on conditions such as passport number must be filled for a foreign national. Valid data is transferred to the main database; invalid data is returned for correction.

XML Rules Editor

The XML Rules Editor allows customizable rules to validate individual transactions after schema checks. It enables:

• Syntax checks (against XML schema)
• Semantic checks (e.g., non-alphabetic characters in names, age thresholds)

Invalid transactions can be isolated and sent back for correction, while valid ones proceed. All validation activity is logged, providing FIU compliance staff with detailed insight into reporting quality, frequency, and patterns by entity, location, or sector. This data can be visualized in compliance reports.

Subject Unification

Post-validation, Subject Unification enables merging or splitting of database objects based on user-defined rules—without altering original data. This supports accurate identity resolution and is fully logged for auditability.

Virtual Object

When identities cannot be definitively merged, analysts can create a Virtual Object—a temporary link between potentially identical records—preserving individual entries while flagging potential connections for further analysis.

This component enables managers and supervisors to assign tasks—with or without deadlines—and monitor their progress throughout the workflow cycle. Task owners are notified within the goAML system and via email when tasks are assigned, reassigned, or due.

Supervisors receive alerts for due, overdue, reassigned, or terminated tasks, as well as when standard workflows are overridden. The system also generates performance metrics, offering insights into workflow efficiency and individual staff performance.

The Intelligence Report Writer is the final step in the analytical process, providing a customizable template for preparing and disseminating intelligence reports to end-user agencies. Reports can be tailored to meet FIU-specific requirements in both format and content, and are fully populated with data from the goAML system.

Reports may include components such as an executive summary, intelligence hypothesis, main body, and conclusions. Users can choose which sections or data to include. Supporting documents, charts, and attachments can be added.

Reports can be exported in XML, printed, or emailed. Associated data can be converted to Excel format for separate dissemination. The tool supports custom report formats and integration with external data sources, with all outputs stored securely in the database.

goAML offers multiple options for the FIU to request and collect data from external sources, ranging from high-tech online queries to traditional letter delivery.

At the advanced end, goAML provides External System Services (ESS) module. ESS connects to the various external systems and allows for searching in and receiving data from the external databases - such as criminal records, vehicle registries, and company registers - by entering details once. This integration is customized for each installation and is not included in the standard goAML package.

If automation isn’t feasible, goAML supports generating standardized request forms populated with case data. Requests can be sent to multiple agencies via email, fax, print, or hand delivery. This all-in-one functionality streamlines the data request process, saving analysts valuable time without needing additional systems.

Profiling is a versatile tool that enables analysts—especially strategic analysts—to run flexible queries and scenarios across the FIU’s data. It functions like an Excel-style filter builder, allowing users to create, save, and share complex or simple queries on any database object.

Queries can be executed once, saved for future use, or scheduled to run automatically, providing powerful, tailored insights from the data.

The Ad Hoc Queries and Matching component allows users to search for matches using various criteria such as name, address, country, account number, or ID details. Searches can be conducted using full or partial information.

Quick Finder

Quick Finder performs a full database search and returns all matching entities, highlighting existing links between them.

Data Matching Module

This module imports external data—such as person, account, or entity records—in any format and matches it against the FIU’s database. Matching can be done manually or scheduled to run automatically, with the option to generate analytical case proposals based on results.

The Document Management component enables document capture via electronic transfer, scanning, and optical character recognition (OCR). Documents are indexed using Elastic-search by various attributes, and their text content is extracted and stored in the database- making it fully searchable.

Documents can be retrieved through direct links in lookup screens or by keyword searches. General text searches return all documents containing the specified or similar content, ensuring easy access to relevant information.

The Rule-based Analysis component in goAML consists of three parts:

• Rules Engine: Continuously scans the database for patterns or conditions defined by the FIU, such as transaction types, frequency changes, or specific account behaviors. There is no limit to the number or complexity of rules.

• Rules Editor: A user-friendly interface for authorized FIU staff to create and submit rules without coding. Rules are built using conditions on standard intelligence objects (persons, entities, accounts) similar to Excel filters. The submission and approval process is customizable.

• Report Dashboard: The reports scored by rules can be reviewed and prioritized in the report dashboard which provides a very well readable overview of each report using dashboard widgets and data elements.

The Statistics and Reporting component allows automatic or ad hoc generation of statistical reports covering all goAML activities. It supports compliance reporting by tracking the number, type, value, and origin of mandated reports, along with details of reporting entities.

FIUs can also analyze internal performance, producing general or targeted reports for management, annual reporting, parliamentary updates, or oversight bodies. These reports help identify trends, gaps, or resource needs, supporting informed decision-making and operational improvements.

The Analytical Tools component provides access to all report data and other information stored in the FIU database, based on user roles and clearance. It supports both tactical and strategic analysis through a wide range of integrated tools and views.

Analysts can sort, filter, and pivot data to identify patterns, anomalies, relationships, and key variables across individuals, entities, occupations, geographic areas, and more—all within a single application.

Tactical & Strategic Analysis

• Tactical analysis targets specific subjects using full database content.

• Strategic analysis examines broader trends, such as top transactors, event timelines, signatories, account activity, and occupation-based behaviors.

Virtual Object

Analysts can create Virtual Objects to group identities that may represent the same individual or related parties, such as family or gang networks. Queries run against any associated identity will retrieve the full Virtual Object data set.