NewAI rules engine for transaction monitoringAI rules engine for monitoringLearn more
Blog

Jurisdictions & Regulation

From Alert to STR, How NFIU's 2026 Reporting Standards Shape Transaction Monitoring Workflows

NFIU transaction monitoring Nigeria: the 2026 goAML changes, mandatory fields and 24-hour rule, and how to build an alert-to-STR workflow.

NFIU transaction monitoring Nigeria discussions usually stop at detection. The Nigerian Financial Intelligence Unit has been clear that detection is only half the job: reports must be complete, correctly typed and useful for analysis. In January 2026 it announced a goAML platform upgrade with stricter validation, and it has published guidance on preparing a complete suspicious transaction report, noting inconsistencies in report narratives that affect its analysis.

This article sets out what changed, what the NFIU asks of reporters, and how to design the workflow between an alert and a filed report so reports pass validation and carry intelligence value.

What the 2026 goAML upgrade changed

A January 2026 legal update on the NFIU announcement describes an upgrade built around precision and data quality. Reporters must select the correct report type before filing. Every report must be tied to at least one predicate offence and the applicable indicators. The system was set to automatically reject reports that fail the revised validation rules from 1 February 2026, and the NFIU scheduled virtual training from 5 January 2026.

The update also described a new monthly PEP Transaction Report covering all transactions by politically exposed persons whether or not suspicious, and a currency transaction report limited to domestic transactions at ₦5 million for individuals and ₦10 million for corporates. Entities using system-to-system integrations were advised to update their mappings urgently to avoid repeated rejections. The update also introduced six suspicion-based STR categories (terrorism financing, kidnapping for ransom, corruption, fraud, drug trafficking and a general category) and limited the foreign transaction report to cross-border transactions of USD 10,000 or more.

The 24-hour rule and what starts the clock

Section 7(2) of the Money Laundering (Prevention and Prohibition) Act 2022 requires reporting entities to report a suspicious transaction to the NFIU within 24 hours. The NFIU's December 2024 guidelines for identifying, verifying and reporting suspicious transactions explain that the period is triggered once a transaction is termed suspicious after a thorough review by the reporting entity, not when an automated alert is first generated.

That distinction shapes workflow design. An alert is not a determination. The institution needs a defined step at which an analyst, having reviewed the case, decides that the transaction is suspicious, and that decision should be time-stamped, because it starts the clock and will be the first thing tested if a report is questioned.

What a complete report needs

The NFIU's guidance on preparing a complete STR organises the narrative around who, what, when, where, why and how, and it expects supporting material such as customer identification documents. It observes that inconsistencies in narratives on goAML reduce the usefulness and timeliness of analysis and dissemination to authorities. A report that says only that a transaction was unusual gives the NFIU little to work with.

Case-management tooling can help by structuring the investigation to mirror those headings, so that the narrative is largely assembled by the time the analyst decides to file. It also reduces the risk of rejection under the new validation rules, because mandatory fields are captured at the point of investigation, not retyped at the point of filing.

Designing the workflow

A workable design has five steps. Alerts are triaged against documented criteria. Cases are investigated using a template aligned with the NFIU's narrative structure. A named decision-maker records the suspicion decision and timestamp. The report type and predicate offence are selected from controlled lists, and the filing is made by integration or web upload with a stored copy of the acknowledgement. Finally, outcomes feed back into scenario tuning.

Measure the workflow. Track time from alert to decision, rejection rates, and the share of reports needing correction. Those figures show whether the programme is producing reports the NFIU can use, and they are a good basis for management reporting. Strong NFIU transaction monitoring Nigeria practice ends with a report the NFIU can analyse, not just an alert that was raised.

FAQ

Common questions.

What is the deadline for filing a suspicious transaction report with the NFIU?
Section 7(2) of the MLPPA 2022 requires reporting within 24 hours, counted from when the reporting entity terms the transaction suspicious after review.
What changed in the NFIU's goAML platform in 2026?
A January 2026 update described stricter validation, mandatory report type and predicate offence selection, automatic rejection from 1 February 2026 for non-compliant reports, and a new monthly PEP Transaction Report.
Does an automated alert start the 24-hour clock?
According to the NFIU's guidelines, the period is triggered once a transaction is termed suspicious after thorough review, not when an alert is generated.
What should an STR narrative contain?
The NFIU's guidance structures it around when, where, why and how the activity occurred, supported by customer identification documents and the entity's investigation.
Are PEP transactions reported even if not suspicious?
The goAML update described a monthly PEP Transaction Report covering all PEP transactions, whether suspicious or not. Entities should confirm current requirements with the NFIU.

See MemberCheck against your own risk data.

Book a walkthrough with our compliance team and screen a real case in the first session.