Skip to content
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.

A person at a desk reviewing documents on a screen, representing report preparation and review
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.

Readiness Onboarding

Work through a guided readiness checklist covering your institution profile, regulator contacts, field mapping, and schema settings before your first report goes out.

CTR, FTR, SAR, STR & PEP Preparation

Every report type follows the exact fields, disclosures, and structure your regulator expects, so nothing needs reshaping before it goes out.

goAML XML Generation, Validation & Submission

Generate goAML-schema XML, already validated against the NFIU portal's exact requirements, then submit it straight to the portal or download it, each in a single click.

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Settings, status & scheduling

Configure once. File consistently every time.

Reporting settings, status stages, and optional scheduling are configured once by your team and then apply to every report prepared afterward.

01

One-Time Setup, Reused For Every Report

Configure your institution's profile, regulator contact details, and the information each report needs once in Reporting settings, then reuse it across every report you prepare.

02

Clear Status At Every Stage

Each report moves through clear stages, from draft, through review, to filed, so status always reflects exactly where a filing stands.

03

Review and Approval Before Filing

Turn on a review and approval step so a report needs sign-off before it goes out. Choose how many levels of approval you require, up to ten, and name who can approve each level. A report's file can't be generated for submission until it's been approved at every required level.

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.

01

Submit Without Leaving the Report

Click Submit to goAML and the report is generated, validated, and sent straight to your configured goAML portal in one action, with no separate download-then-upload steps.

02

Works the Same Way for Every Report Type

CTR, FTR, SAR, STR, and PEP Transaction Reports all submit through the exact same one-click flow, so your team never has to remember a different process per report type.

03

Every Attempt Recorded

Every submission to the goAML portal is logged with its outcome, so your team always has a record of what was sent, when, and whether it went through.

Automatic generation & unlimited validation

Automatic report generation & validation

  1. 01

    Daily, Weekly, Or Monthly, Your Choice

    Generate reports automatically on a daily, weekly, or monthly schedule, whichever matches how often your team needs to file, whether that's threshold-based reports swept every day or a Politically Exposed Person Transaction Report rolled up once a month.

  2. 02

    Ready To Submit As Soon As It's Generated

    Every automatically generated report is ready to submit the moment it's created, with no separate assembly step. This cuts the effort a compliance analyst spends preparing a report by 99%, and cuts how long it takes to submit a report in half.

  3. 03

    Checked Against the Regulator's Latest Required Format

    Every check compares your report against the most current format your regulator accepts, not a cached or outdated version.

  4. 04

    Run It As Many Times As You Need

    Check a report again after every change, with no limit on how many times you run it, until you're confident it will be accepted.

Start a conversation

Ready 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.

Request a Reporting Demo