AML, fraud monitoring & investigations
Turn suspicious activity into decisions you can defend.
Give your bank a clear path from transaction monitoring to investigation and verifiable evidence. Tune the rules. Govern the response. Keep the facts behind the decision.
For banks, microfinance institutions and payment providers
Start with a supported template
AML · TRANSACTION MONITORING
Repeated sub-ceiling credits
Review repeated incoming payments below a bank-selected amount within a defined window.
- 1Confirm required data
- 2Adapt the rule draft
- 3Back-test the saved revision
- 4Obtain independent approval
23
Editable detection templates
Adapt a supported scenario into a bank-owned rule draft.
16
Data-readiness mappings
See the source fields and history a scenario needs.
3
Behavioural response modes
Observe, alert or permit approved bank actions.
Explore the rule library, data requirements and response controls built into Indelible. Explore the capabilities →
A stronger basis for the buying decision
Buy a control you can examine.
Your board needs assurance. Your investigators need context. Your technology team needs a system it can test. Bring all three to the demonstration.
For bank management
Ask what is covered, who authorised a change and what the bank can prove. Review reports and their supporting records before accepting the control.
For compliance and investigations
Move from an alert to its facts, customer context and case record. Keep the explanation, review and evidence together.
For technology and assurance
Inspect data requirements, test your integrations and verify recovery and export. Evaluate the system against your own acceptance criteria.
Governed rule authoring
Start with 23 templates.
Make the rules your bank’s.
From repeated sub-ceiling credits to dormant-account activity and agent cash-out bursts, the deployed library gives analysts a concrete starting point.
Each supported template creates a draft. Your team confirms the required data, calibrates the parameters, tests historical behaviour and obtains independent approval.
Coverage you can inspect
- Transaction patterns & CDD12
- Fraud indicators5
- Recorded country & corridor risk3
- Small-payment patterns1
- Agent-account activity2
The catalogue also contains 7 workflow reference cards, kept separate from the 23 editable templates.
Explore all 23 templates and the workflow reference cards
Transaction patterns & CDD · 12
- Large single transaction
- Repeated sub-ceiling credits
- Two-way turnover in a short period
- Activity after an inactive period
- Amount above past account average
- Material movement by a high-risk customer
- Material activity with expired CDD
- Repeated activity with incomplete CDD
- High-risk account turnover burst
- Repeated cash credits
- Total movement in a time window
- Payments below approved named anchors
Fraud indicators · 5
- Elevated reversal proportion
- Rapid outgoing payment count
- Payment involving a confirmed fraud flag
- Debit activity on a restricted profile
- Concentrated outgoing value
Recorded country & corridor risk · 3
- Material movement on a corridor the bank treats as higher risk
- Material activity by a high-risk customer recorded outside Nigeria
- Repeated payments on a corridor the bank treats as higher risk
Small-payment patterns · 1
- Frequent small incoming payments
Agent-account activity · 2
- Agent-account cash-out burst
- Agent turnover with expired CDD
Workflow reference cards · 7
- CFT collection and distribution review
- Sanctions and designation screening
- Proliferation-financing exposure review
- Regulatory reporting versus suspicion
- Device/session account-takeover correlation
- Connected parties and ownership networks
- Agent peer and terminal outliers
Template settings are advisory and bank-tunable, not statutory thresholds. Data readiness and coverage must be validated for your institution. Country and corridor scenarios use recorded customer-country data; they do not track a person’s physical location. Reference cards require specialist workflows or additional bank data.
The work behind the numbers
Follow the signal. Keep the evidence.
Connect the work of data, compliance, fraud and investigation teams in a shared financial-crime workspace.
Start with data you can assess
Map incoming transactions and profiles, inspect quarantined records and check completeness. Scenario requirements expose missing inputs before a rule is relied on.
Bring customer risk into view
Work with versioned customer risk profiles, CDD context and screening workspaces. Identity checks and sanctions, PEP and watchlist data depend on the providers your bank connects.
Make rule changes accountable
Start from a template, adjust the bank’s parameters and back-test a saved revision on historical data. Submit the change for independent review before activation.
Investigate with the facts attached
Review alert reasons, rule versions and customer context; assign cases and retain notes and attachments. Workspace search includes pending work.
Take the case evidence with you
Export a readable offline case with retained decision facts, rule and policy context, transaction links and an attachment inventory. A separate verifier checks the exported package.
Keep reporting under review
Use management reporting, report approvals and filing workspaces to prepare and track the record. The bank’s MLRO retains the filing and submission decision.
Access with accountable approvals
Role-based staff access, bank sign-in with MFA and reviewed access requests support separation of duties. Bank Admin approval governs Security Reviewer appointments.
Optional assistance, human judgement
Analyst assistance can explain retained alert facts and draft case handovers for review. It does not decide the outcome or change the score. Bank enablement and provider/privacy approval are required.
Control the operational impact
Three modes. A deliberate choice.
Choose how approved behavioural rules affect operations, with the bank’s authority and connected systems defining what can happen.
01
Observation mode
Record behavioural decisions so your team can assess the rules before enabling their alerts or actions.
Assess the behaviour
02
Alert-only mode
Create alerts for staff review without requesting behavioural holds or challenges.
Investigate the signal
03
Actions permitted
Allow approved rules to request bank actions within configured authority. Connected systems determine the actual outcome, which is recorded.
Act within bank authority
Separate sanctions policy: applicable sanctions controls follow their own approved policy in every mode. These behavioural modes do not switch off those obligations. Actions require the appropriate bank connector and permissions.
Infrastructure, ownership and exit
Keep control beyond the dashboard.
Plan your dedicated bank environment with explicit decisions about hosting, data residency, access and key custody.
Portable case evidence and institution export give your team a way to examine retained records outside the working interface. Recovery and exit tests belong in the procurement conversation from the start.
Put these questions in your demonstration
- 01Can we trace this alert to its inputs and the rule version used?
- 02Can a different reviewer approve the proposed rule or access change?
- 03Can we read and verify the exported case outside the application?
- 04Can we restore the records and reproduce the tested decisions?
Your path to deployment
Bring Indelible into your bank.
A defined implementation process for Nigerian banks, microfinance institutions and payment providers, with your compliance and technology teams involved from the start.
Step 1
See the complete workflow
Bring your compliance, technology and procurement leads. Walk through rule authoring, an investigation and a verifiable case export.
A demonstration focused on your priorities
Step 2
Configure for your bank
Agree integrations, scenarios and representative test data. Calibrate the rules and measure alert yield, review effort and coverage alongside your existing controls.
Bank-specific configuration and validation
Step 3
Accept a controlled rollout
Complete integration, security, recovery and operating-model checks. Agree production acceptance, training and support before cutover.
An agreed deployment and acceptance plan
FAQ
Frequently asked questions
Can’t find what you need? Ask us directly.
How do we get Indelible for our bank?
Start with a product demonstration and a deployment consultation. We scope the modules, data, integrations and operating model with your team, configure the bank environment and agree acceptance checks before production cutover.
Are all 30 catalogue entries automated detection templates?
No. There are 23 entries that can create editable rule drafts and 7 workflow reference cards. The reference cards cover areas needing a specialist workflow or additional institutional data; they are not counted as editable templates. Rules require bank calibration, suitable data and approval.
Can we compare it with our existing AML system?
Yes. Plan an evaluation alongside your current controls using agreed scenarios, the same evaluation data and recorded review outcomes. Alert volumes, false positives, investigation effort and operating costs should be measured in that evaluation. We do not claim an unmeasured improvement or a competitor benchmark.
Which integrations and data sources are included?
The application supports transaction and profile ingestion and integration workspaces. Your core banking and channel interfaces, identity providers, screening sources and action permissions are scoped and tested during commissioning. Licensed data, connector work and third-party charges must be agreed explicitly.
Where will our bank’s data be hosted?
Deployment infrastructure, data residency, access, encryption and key custody are agreed with your institution and verified during commissioning. The dedicated environment and export capabilities support institutional control; a website description is not a substitute for your hosting and security agreement.
Does this guarantee compliance or regulatory acceptance?
No. Indelible supports your institution’s control programme and evidence handling. We make no claim of regulator approval, endorsement or certification. Your bank remains responsible for applicable obligations, reporting decisions and acceptance of filing formats and channels.
How is the deployment priced?
We scope the modules, environments, data volumes, integrations, training and support with your team, then provide a proposal. Screening and identity-data fees and other third-party costs are identified separately so procurement can compare the complete scope.
Bring your hardest AML questions.
Explore the workflows, discuss your priorities and plan the right deployment for your bank. Start with a demonstration for your compliance and technology leads.