Fraud Awareness Week is here! Discover your hidden fraud risks with Dojah’s free assessments.Review Your Defences
arrow
Skip to content
back

Go back to Blog

Jennifer Edidiong

Marketing

11 min read

Share to

How to Justify the Cost of AML Transaction Monitoring Software to Your Management Team

You walk into the budget meeting with a request for AML transaction monitoring software. The first question comes quickly: “Why do we need to spend this much on something that flags transactions?” If your answer starts with features, you have already lost the room.

Management responds to deadlines, exposure and numbers. This guide shows how to build a case around all three, size the real cost, tailor it to the people in the room, and prove it with a pilot.

 

Start With What Is Required

For CBN-regulated institutions in Nigeria, automated AML is no longer a nice-to-have. The CBN’s Baseline Standards for Automated AML Solutions, issued on 10 March 2026, list transaction monitoring among their minimum functions and say plainly that manual controls are no longer sufficient.

Milestone

Date

Who

Implementation roadmap to the CBN’s Compliance Department10 June 2026 (passed)All covered institutions
Full compliance10 September 2027Deposit money banks
Full compliance10 March 2028Other financial institutions

Check which group your licence places you in. The Standards cover every CBN-regulated institution, including banks, mobile money operators, international money transfer operators and payment service providers. The amount you must build scales with your size, products, risk, and transaction volumes, but everyone must use an automated solution.

Two details change what you should ask for. First, monitoring must connect to customer data. The CBN says a solution without effective links to KYC and KYB information and customer risk assessments will not be regarded as compliant, so budget for integration with your onboarding data, not just a monitoring engine.

 Second, the CBN will check. It will use off-site surveillance, on-site examinations, and thematic reviews, and anyone seeking authorisation after 10 March 2026 must show compliance, or a credible plan to reach it, to get licensed. You must also tell your supervisory department which AML solutions you use and what each one does.

That leaves management with a different question: not whether, but when and which. Work backwards from your deadline. Vendor selection, integration, data clean-up, testing, a pilot and tuning all have to fit inside it. As an example, an institution facing March 2028 might decide in early 2027, pilot in the second quarter, connect all channels in the second half and spend early 2028 tuning and gathering evidence. A bank facing September 2027 has less room, so its decision cannot wait.

Check the roadmap you filed by 10 June 2026, because the case you make now should match it. If you have not filed one, that is the first item in the meeting.

 

Show the Cost of Doing Nothing

Penalty exposure is the second argument. The Standards say institutions that miss them, or run systems that fail to control risk effectively, may face remedial directives and administrative sanctions. These can land on the institution and on accountable individuals, under BOFIA, the Money Laundering Act and the CBN’s AML, CFT and CPF Administrative Sanctions Regulations 2023. That second group matters in the room, because it includes the people deciding the budget. Ask your compliance team for the current penalty schedule so you can put real figures on the page.

Then add the costs of the manual route:

  • Analyst hours: Time spent reviewing alerts by hand and chasing the same customer across spreadsheets.
  • Backlog: Alerts that wait days for a decision.
  • Missed patterns: Activity that only looks suspicious when many transactions are viewed together, such as a payout split into smaller amounts.
  • Audit evidence: The Standards expect case actions recorded with timestamps, users, decisions and rationale. Email threads and spreadsheets make that hard to show an examiner.
  • Blocked growth: A new product or licence application depends on showing you can monitor it.

To size the first one, use this formula: alerts per day × minutes per alert ÷ 60 = analyst hours per day. For example, 150 alerts at 10 minutes each is 25 hours a day, or about three full-time analysts doing nothing but review. Replace those numbers with your own.

 

Build the Case in Five Steps

With the requirement and the risk clear, the case comes together in five steps:

  1. Take a baseline: Count alerts per day, minutes per alert, the size of the backlog and how many cases lead to a filing. These are your “before” numbers. The Standards also expect internal timeframes for reviewing high-risk alerts and defined false positive thresholds, so this data does double duty.
  2. Map to the standards: List the functions the CBN expects and mark each as covered, partly covered or missing. The table below does this.
  3. Count the full cost: Include every line, not just the licence. The list after the table shows the ones finance usually misses.
  4. Put a value on the risk: Combine penalty exposure with likely fraud and laundering losses. Be honest about what is an estimate.
  5. Offer options: A phased plan with a pilot is easier to approve than a single large commitment. Show what you will have learned by the end of each phase.

Step 2 in detail. For each row, mark your setup as covered, partly covered or missing.

Function

What the CBN expects

Question to ask about your setup

Customer identificationAutomated or semi-automated onboarding with real-time data checks. BVN and NIN checks are one component, not complete verification on their own.Do onboarding results feed your customer risk profile?
Customer risk profilingRatings that update as new data and behaviour arrive, with reports on what changed and why.Is risk set once at onboarding, or does it move?
Sanctions and PEP screeningReal-time or near real-time list updates, adverse media monitoring, logs that prove screening is timely, and the ability to hold a transaction on a confirmed match.Can you show when lists were last updated and what you did with each hit?
Transaction monitoringConfigurable rules across several scenarios, using KYC data as well as transactions, with documented thresholds and annual independent validation of any AI or ML models.Can an analyst see the customer’s profile and past alerts on every alert?
Case managementCreation, assignment, prioritisation and tracking, with maker-checker workflows and reports on volumes, ageing and outcomes.Can you show who decided what, when and why?
ReportingAutomated or semi-automated STRs, SARs, CTRs and FTRs, plus regular reports to the compliance officer, senior management and the Board.How long does it take to build one STR today?
Audit and governanceA tamper-proof audit trail covering configuration changes, access, alert decisions and report generation.Would your logs survive an on-site examination?
Integration and securityTwo-way links to core banking and KYC systems, documented APIs, encryption, role-based access and recovery targets.Is monitoring fed by a standalone transaction feed?

Institutions rated high risk or above average in their subsector are told it is unacceptable to rely on standalone transaction feeds alone. 

Tailor the Case to the Room

A full figure still has to land with different people, and each needs different proof.

Who

What they care about

What to show

Chief executiveLicence, reputation, growthThe deadline, the licensing requirement and the date to decide
Finance leadTotal cost and predictabilityThe three-year figure, a capped pilot and the cost of manual work
Compliance leadMeeting the Standards, evidenceYour gap table, audit trail and reporting
Technology leadIntegration effort and system riskThe integration plan and the data you will send
BoardAccountabilityThe Standards require regular reporting to the Board, so show what it will see

 

Prove It With a Pilot

A pilot turns your estimates into numbers management can check. Each phase ends with a go or no-go decision, so management approves a small amount at a time. This is an example, so fit it to your own roadmap:

  1. Baseline and pilot: Run one product or channel alongside your manual process, and compare the system’s alerts with what your analysts flagged. You learn alert volume, false positive rates and analyst time per case.
  2. Extend and connect: Add channels and link customer data. You learn where your coverage and data quality have gaps.
  3. Tune and evidence: Set thresholds, document your tuning decisions and check your reports. The Standards expect threshold settings and tuning to be documented at least annually. You learn whether you can show an examiner that the system works.

Agree on what success looks like before the pilot starts, so the result cannot be argued afterwards. Pick a target for each measure:

  • Alerts per day, and the share analysts close as false positives.
  • Analyst minutes per alert.
  • Time from alert to recorded decision, against your internal service standard.
  • Cases escalated for a filing.
  • Suspicious activity the system caught that manual review missed.
  • Integration effort in days.

 

Choose a Vendor You Can Defend

The Standards expect heightened due diligence on AML solution providers, so the questions you ask belong in your business case. Write down the answers:

  • Customer context: Does every alert show the customer’s KYC data, risk score and past cases in one place?
  • Audit trail: Is it tamper-proof, and does it cover configuration changes, alert decisions and report generation?
  • Explainability: Can we see why an alert fired, especially where AI or ML is involved, and get the data we need for independent validation?
  • Case workflow: Does it support maker-checker and reports on case volumes, ageing and outcomes?
  • Reporting and integration: Can it generate STRs and CTRs in the formats the CBN expects, and are the APIs documented?
  • Data and exit: Where is our data stored, and how do we get our data and cases out if we leave?

Even a strong vendor case meets resistance, so prepare for it.

 

Answer the Objections Before They Come

  • “It is too expensive.” Compare it with the full cost of manual work, and offer a pilot on one product or channel first.
  • “Our manual process works.” It works at today’s volume. Ask what happens when volume doubles. The CBN has also said manual controls are no longer sufficient.
  • “We can wait for the deadline.” Testing, integration and validation take real time, and the CBN will look at whether the system works, not just whether it was bought. Waiting shrinks your options.
  • “Will it block good customers?” Rules can be tuned, and a review step means flagged transactions get a human decision before anything is blocked. The Standards also expect you to document your false positive thresholds.
  • “We already have a fraud tool.” The Standards do not require one system for both, but fraud and AML tools must exchange risk signals without blind spots. Higher-risk institutions are expected to show a plan to integrate them.
  • “We will build it ourselves.” Nothing in the Standards says you must buy. A built system must still meet the same functions and validation rules, so price the engineering time and the team, not just the licence.
  • “A new product is launching soon.” The Standards expect you to review and upgrade your AML solution when your product mix or channels change, so the launch is a reason to act now.

 

How Dojah Supports AML Transaction Monitoring

Dojah’s Easy Detect monitors transactions in real time. You send it banking, payment or onboarding events through the API, and it scores each one and returns a decision to allow, flag for review or block.

  • Rules you build without code: The Rule Builder lets you set conditions, scores and thresholds visually, and an AI assistant can propose rules from a plain-language description. You review each one before it goes live.
  • A case queue for analysts: Flagged events become cases. An analyst sees the transaction, the user and the risk indicators, then chooses to allow or block and records the reason. An AI review can suggest a decision first.
  • Reports for filings: Reporting produces PDF reports, including a Suspicious Transaction Report from cases and events and a Cash Transaction Report from events.
  • A risk profile for each customer: Risk builds up from every event a customer generates. Because the Standards require monitoring to link to KYC data, plan how your onboarding data will feed monitoring during the pilot.
  • Historical data and a pilot: You can backfill past events so the models learn normal behaviour before real-time scoring starts. 
  • Screening that updates itself: AML Watchlist reports a customer’s status change in real time.

 

A strong business case ties a deadline to a cost, a risk and a plan. Bring all four, and the conversation changes from “why” to “when”.

Need a pilot to show your management team? Fintechs and banks can start with Dojah’s transaction monitoring and prove the case on a single product first.

Start using Dojah for all your business needs

Explore more

Subscribe to our newsletter

Get notified when we publish new stories, announcements, products and more. Subscribe to receive updates.