Go-AML Reporting

One Screen, From a Concurred Alert to a Filed goAML Report

Go-AML Reporting only ever works alerts that compliance has already concurred for reporting — it auto-routes each one to the right report type, forces the fields FIU-Nepal requires, and generates a filing-ready goAML XML.

• Compliance-Concurred Queue — only alerts already concurred for reporting (approved) appear in the Go-AML Reporting queue, opened with a single Proceed action.
• Automatic STR/SAR Routing — the report builder opens as STR (transaction-based) or SAR (activity-based) automatically, driven by the originating flag or rule — no manual form selection.
• Report Indicators — a checklist of named indicators (large/unusual cash transaction, structuring/smurfing, rapid movement of funds, PEP involvement, sanctions/watchlist match, suspected terrorist financing, trade-based money laundering, adverse media, dormant account sudden activity, and more), with at least one mandatory before the report can proceed.
• Predicate Offence Capture — named predicate offences (corruption and bribery, fraud, drug trafficking, human trafficking, terrorism financing, tax crimes, organized crime, insider trading, and more), including a "Not Yet Determined" option where the offence is still under investigation.
• Mandatory Grounds of Suspicion Narrative — a required free-text field, so no report can be generated without a documented rationale for the filing.
• Action Taken Capture — records what the institution actually did: continued monitoring, restricted or debit-blocked the account, terminated the relationship, rejected or held the transaction, referred to law enforcement, or reporting only.
• Full Subject & Reporting-Person Fields — customer ID, subject type (natural or legal), account, party type, and Compliance Officer reporting-person details (name, designation, email, phone), captured against FIU-Nepal's goAML schema.
• Per-Transaction Suspicion Detail (STR) — a transaction-level table with suspicion flags (transaction, conductor, from, to), comments, and a running Total Suspicious Amount; SAR reports instead capture Activity Period and Total Value.
• One-Click goAML XML Generation & Submit to FIU — Generate goAML XML and Submit to FIU are the final two actions on the same screen, structured to FIU-Nepal's schema — entity, report code, indicators, predicate offences, subject, and transaction/activity detail.
• Download XML Report by Flag Type — pull already-generated XML by flag type (TTR/STR/SAR/AIF), date range, and account scope, preview the matching records, then download.
• Basic Branch-Side SAR Intake — a simpler SAR entry form for branch use, with full KYC-style subject fields (natural or legal, relationship, party type) for cases raised outside the automated alert flow.
• Need-to-Know Access Controls — Go-AML Reporting screens and FIU filing outcomes are restricted on a need-to-know basis to prevent tipping-off, keeping branch visibility separate from Central Compliance's filing decisions.