Transaction screening

Every transaction is screened as it is posted, before it ever reaches an analyst’s queue.

  • Real-time screening

    Transactions are screened as they arrive from your core banking system or the API, and a transaction is never screened twice.

    Suspicious activity is visible within moments, not at the end of the day.

  • Rules across five areas

    Rules cover anti-money laundering (reporting threshold, structuring, velocity, layering), counter-terrorist financing (sanctions matches, dispersal patterns), fraud patterns, KYC limits and NFIU reporting triggers.

    One engine covers your monitoring obligations instead of several disconnected checks.

  • Configurable rules

    Rules and their settings live in configuration, so your team can tune them to your institution without changing the software.

    Tuning follows your risk assessment, not the vendor’s release schedule.

  • Sanctions screening

    Senders and beneficiaries are checked against the OFAC and UN lists, refreshed daily, plus locally maintained Nigerian watchlists. Names are matched fuzzily, and BVN, NIN and account numbers exactly.

    Misspelt or transliterated names are still caught.

  • Behavioural anomaly detection

    A machine-learning model, retrained every night on your recent activity, flags transactions that are unusual for the customer making them.

    Catches patterns no fixed rule describes.

  • Explainable risk scores

    Rules drive the score; the model can only add a limited uplift. Each transaction gets a 0–100 score and a band: Critical (75–100), High (50–74), Medium (30–49) or Low (0–29).

    Every score can be explained to an examiner by the rules that fired.

Alerts and case management

Alerts turn into decisions, with a record of who did what and when.

  • Prioritised alerts

    Alerts carry the risk band and the rules that fired. Repeat alerts on the same pattern are grouped, and unattended alerts escalate automatically.

    Analysts work the most serious activity first.

  • Assignment and disposition

    Alerts are assigned to named analysts and can’t be closed without a recorded disposition.

    No alert disappears without an explanation.

  • Investigation workflow

    Cases move from open, to under investigation, to pending MLRO approval, and close as filed or with a recorded outcome. Each case has an owner, an approver, a due date, findings and its own history.

    The MLRO signs off on decisions, with the evidence trail in one place.

  • Customer risk view

    A customer-level risk score and a list of high-risk customers sit alongside live transaction risk.

    See which relationships need enhanced due diligence.

NFIU reporting

Reporting duties are built into the workflow rather than handled in a separate spreadsheet.

  • STR and CTR drafts

    When a reporting rule fires, a draft Suspicious Transaction Report or Currency Transaction Report is prepared automatically as PDF and XML.

    Reports start from the transaction data, not from a blank form.

  • Deadline reminders

    Reports carry their filing deadlines, and the team is reminded before they fall due.

    Fewer late filings.

  • Daily summaries

    A daily compliance summary and a daily CTR batch are produced on schedule.

    The MLRO starts each day knowing what needs attention.

Dashboards and analytics

See the state of monitoring at a glance.

  • Risk monitor

    Risk distribution across transactions, high-risk customers, and a live view of transactions as they are screened.

    Spot a change in risk as it happens.

  • Compliance analytics

    Alert trends by week, case resolution times, filing rates and transaction volume history.

    Evidence for board and regulator reporting on how the programme is performing.

Notifications

The right people hear about urgent activity without watching a screen.

  • Email, SMS and Slack

    Alerts can be sent by email, by SMS through Termii, and to a Slack channel.

    Critical alerts reach the team wherever they are.