The pressures you deal with, and how TXN-Monitor helps

  • A small compliance team, a large transaction volume

    Every transaction is screened automatically, and only those that need a person become alerts, prioritised by risk band. Analysts start with the most serious activity.

  • Reporting deadlines that can’t be missed

    Reporting rules trigger draft STRs and CTRs, including at the ₦5 million CTR threshold, with reminders before each filing deadline and a daily CTR batch.

  • Channels where risk moves quickly

    NIP, USSD, POS, agent banking and mobile money transactions are screened as they post, with velocity and dispersal patterns checked against each account’s recent activity.

  • Customers on different KYC tiers

    CBN tiered KYC limits are checked on every transaction, using customer data synced from your existing records.

  • Proving your programme works at examination

    Each alert has a recorded disposition, each case an MLRO decision, and every action sits in an append-only audit trail. Analytics show alert trends, case resolution and filing rates.

  • Core banking on Apache Fineract

    TXN-Monitor reads Fineract business events for savings and loan transactions directly, so there is no export job to build.

What it means for each team

MLROs and compliance officers
Approve case outcomes, oversee reporting, manage monitoring exemptions under maker-checker control, and track how the programme is performing.
Analysts
Work a prioritised alert queue, investigate cases and record findings, with the transaction, customer and rule context in one place.
Auditors
Review an audit trail that can’t be edited or deleted, with role-based access that limits what each person can change.
IT and operations
Run TXN-Monitor on your own Kubernetes cluster, connected to Fineract, your event stream or the REST API.