The Reports page lists every report with its reference, type, status and institution profile. Search by reference, filter by type or status, export the list to CSV, and start a new report. An Awaiting review tab collects the reports waiting for you.
Reporting
File every report your regulator requires, from one workspace.
Prepare each required report, review the transactions and people behind it, and generate a file that's already checked and ready to submit, with optional scheduling and sign-off built in.
Reporting workspace
Everything a filing team needs, in one module.
Reporting covers the full path from getting your institution set up to a validated file ready for the NFIU GOAML portal, not just the export step at the end.
Open a report to see the institution profile snapshotted onto it and the reporting contact who is the officer of record. The narrative, the reason for the report and the action taken, is required on every report, and AI can draft it for you. The local currency can be filled with AI too.
Search the full catalog of goAML indicators by code or label, grouped by category, and tick the ones that apply. At least one indicator is required before a report can be submitted, and AI can suggest them from the transaction.
CTR, FTR, SAR, STR & PEP
Know exactly what each report is for.
Each report type follows its own regulatory trigger and its own format. Reporting keeps them side by side so your team always prepares the right one.
- 01
CTR: Currency Transaction Report
Filed for large Naira transactions: a single transfer that crosses the ₦5,000,000 individual or ₦10,000,000 corporate threshold, or several smaller transactions from the same customer that add up to it within one day.
- 02
FTR: Foreign Transaction Report
Filed for cross-border transactions once a customer's cumulative same-day US Dollar total passes $10,000, whether that came from one transfer or several.
- 03
SAR: Suspicious Activity Report
Filed by an analyst for a pattern of activity that looks suspicious on review, regardless of amount or whether any single transaction crossed a threshold.
- 04
STR: Suspicious Transaction Report
Filed by an analyst for a specific transaction that looks suspicious on review, regardless of amount or whether it crossed a threshold.
- 05
PEP: Politically Exposed Person Transaction Report
Filed for every transaction with a confirmed Politically Exposed Person match on screening, regardless of amount or suspicion, rolled up and filed once a month.
Validation and approval
Checked, and approved, before it goes out.
Validate against the goAML schema as often as you need, choose the schema that applies, and add approval levels before anything is exported.
Validate a report against the active goAML schema at any time, as many times as you need, to confirm it is correct and meets NFIU reporting guidelines before you submit it. Every validation attempt is kept in a history showing when, by whom, against which schema, and whether it passed.
Choose OneView-managed XSD schema definitions or upload your institution's own, then activate the one OneView should use to validate generated report XML. Older versions can be retired and reactivated.
Turn on maker-checker approval and a report must clear every configured level, in order, before it can be exported. Set between 1 and 10 levels, name the approvers for each, and each user can sit on only one level. The Reviews tab shows the approval chain and every approval, rejection and comment.
goAML Portal Submission
Submit straight to goAML. One click, not three.
A validated report doesn't need to leave the workspace to reach the NFIU. Submit it to the goAML portal directly, from the same place you prepared it.
From the Export & Submission tab, Auto submit to goAML portal generates the goAML XML if it has not been generated yet and uploads it to the goAML portal with your goAML credentials in one action. Download XML generates and downloads it instead. Every upload attempt and every generation is kept, whether or not it succeeded.
Add your goAML credentials in Reporting Settings, and analysts can upload a validated report directly instead of only downloading it. Your credentials are never shown once saved.
Each report has its own audit log. Creating the report, attaching a transaction, generating an AI draft, updating it and validating its XML are each recorded with who did it and when, so your team can show exactly how a filing came together.
Automatic generation
Reports drafted for you, on your schedule.
Set a schedule once and OneView drafts the reports that your rules call for, so your team starts from a ready draft instead of a blank page.
Turn on automatic generation for each report type and choose how often it runs. A sweep reads executed transactions one calendar day at a time and drafts a report when that type's rule is met, never including today's unfinished day. CTR and FTR are set to run daily, and PEP reports are filed monthly.
The run history lists every calendar day the sweep has examined, including days with no matching transactions, with the report type, the status and when it ran. Generate reports for a specific date on demand when you need to.
Start a conversation
Request a demoReady to bring your filing workflow into one module?
See how getting set up, preparing a report, reviewing the transactions and people involved, and generating a regulator-ready file fit together in one Reporting workspace.