Solutions

AML/CFT solutions by institution and by role

The obligations rhyme across Nigerian regulated entities. The operating reality does not. A Tier-1 bank is coordinating eleven people around one decision; a microfinance bank is asking two people to cover the whole programme; a law firm is starting from a spreadsheet. These pages take each of those seriously on its own terms rather than describing an average institution that does not exist.

Book a demo Take the guided tour

By institution

Seven supervisory realities

Each page states the segment's obligations qualitatively, the operational pain that makes them expensive to meet, and which parts of the platform answer them.

Commercial banks

Tier-1 and Tier-2 scale, complex operating structures.

Learn more

Microfinance banks

Proportionate controls for smaller compliance teams.

Learn more

Fintechs and PSPs

High-volume machine intake with human adjudication.

Learn more

DNFBPs

SCUML-registered lawyers, accountants and agents.

Learn more

Bureaux de change

Cash-intensive CDD, thresholds and reporting.

Learn more

Insurance

Policy, beneficiary and claims-side risk review.

Learn more

Capital markets

Broker-dealer and asset manager obligations.

Learn more

By role

Five people who evaluate this differently

A CCO, an MLRO, an analyst, an internal auditor and a CISO can be shown the same screen and judge it against five unrelated criteria. These pages lead with the criterion rather than the screen.

Chief Compliance Officer

Board reporting and programme-level assurance.

Learn more

MLRO

Filing accountability and decision defensibility.

Learn more

AML analyst

Queue throughput and investigation quality.

Learn more

Internal audit

Independent review and evidence retrieval.

Learn more

CISO

Tenancy, access control and data protection.

Learn more

Choosing a page

Where the segments genuinely diverge

If more than one of these describes you — a bank with a bureau de change subsidiary, a fintech that also onboards DNFBP merchants — read both. The platform is one tenant either way; the operating model is what changes.

Dominant constraint by institution type
Institution type	Dominant constraint	Where the work concentrates
Commercial banks	Federated teams and volume	Consistency of decisions across branches, subsidiaries and org units
Microfinance banks	A compliance function of two or three people	Proportionate control design and a workable false-positive load
Fintechs and PSPs	Machine-speed intake	API ingest quality, and adjudication that stays human
DNFBPs	Often no compliance software at all	A retrievable customer file and a defensible basic programme
Bureaux de change	Cash and one-off customers	Counter-side identification, aggregation and threshold reporting
Insurance	Risk sits in lifecycle events, not daily activity	Beneficiaries, third-party payers, surrenders and claims
Capital markets	Ownership opacity and cross-border investors	Beneficial ownership, source of wealth and settlement flows

Constant across segments

What does not change, whichever page you came from

Segment configuration changes what is monitored, what evidence is collected and what is reported. It never changes how a decision becomes defensible.

Deployment footprint

Who is running this today

This section will carry the segment breakdown of live deployments once there is one that can be sourced and approved for publication.

Placeholder — deployment counts by institution type have not been sourced or approved for publication. Replace with sourced, approved content before this page is made public.

Segment adoption — awaiting sourced figures

Live institution counts, segment mix and reference availability belong here. Until each figure has a named internal owner and written customer approval, this block stays a shell: an unverifiable adoption number on an AML vendor's site is the first thing a buyer's own compliance function will ask us to evidence.

—

Institutions live

Awaiting a figure with a named owner and an as-at date.

—

Segments represented

Awaiting confirmation of which of the seven segments are in production.

—

Reference customers

Awaiting written approval to describe any customer, named or anonymised.

Start the conversation

Start from your segment, not from a feature list

Bring your licence category, your alert volume and the size of your compliance team. We will walk the workflow that fits them, and be explicit about what is configuration, what is integration work and what is still pending an authoritative regulatory artefact.

Book a demo Talk to a compliance specialist