Transaction monitoring software for Mauritius

SonarPulse TMX is real-time transaction monitoring software for Mauritius banks, payment providers and other reporting persons. It screens every transaction as it happens, runs fraud, AML and sanctions rules in one engine, finds smurfing, layering and round-trip patterns across counterparties, explains every alert and generates goAML filings under four-eyes control. TMX runs on-premises inside your payment perimeter, on the same customer record as SonarPulse KYC and screening.

What Mauritius asks of your monitoring and reporting

  • STRs promptly, and within 5 working days at most. Section 14(1) of FIAMLA sets the outer limit. The FIU’s Guidance Note 4.1, in effect since 19 August 2026, starts the count when the MLRO determines that reasonable grounds for suspicion exist, expects same-day filing where reasonably practicable and says delays caused by a lack of human or IT resources are not acceptable. When the STR clock starts.
  • Alerts straight to the MLRO. The same guidance says staff who review automated monitoring alerts must be able to raise an internal STR directly to the MLRO or deputy MLRO, without mandatory management approvals first.
  • Suspension orders. Since Act No. 3 of 2026, the FIU can order a suspicious transaction suspended for up to 72 hours (120 hours where the deadline falls on a Sunday, public holiday or FIU non-working day), with further information due within 24 hours of a request. What Act No. 3 of 2026 changed.
  • Real-time screening of transactions. The National AML/CFT Strategy 2026-2029 promotes automated systems that screen individuals, entities, beneficial owners and transactions against UN lists and domestic designations in real time, and monitoring of small-value transactions and micro-financing patterns typical of terrorist financing. What the national strategy plans.
  • Terrorist and proliferation financing. Where reasonable grounds to suspect TF or PF exist, the FIU expects the STR to be submitted immediately.

How TMX monitors transactions

  • Real-time ingestion. Transaction screening on an ISO 20022-aligned payment schema with country and currency validation.
  • Fraud, AML and sanctions in one engine. Unified FRAML rule sets rather than three systems reconciled after the fact.
  • Graph typologies. Smurfing, layering and round-trip patterns resolved across counterparties at depth.
  • Behavioural signals. Velocity, geography and device history scored against a rolling baseline per subject.
  • Machine-learning anomaly detection. Isolation-forest anomaly scoring under champion/challenger model governance with version tracking.
  • Explainable decisions. A per-alert narrative rationale behind every APPROVE, FLAG or DENY, with the input vector retained.
  • goAML filing. goAML and FinCEN SAR generation under four-eyes control, over a tamper-evident SHA-256 hash-chain audit log.
  • Connected to your core systems. TMX Connect is on-premises middleware that feeds TMX from core banking and payment systems.

Questions about transaction monitoring in Mauritius

Can TMX file STRs to the FIU through goAML?

Yes. TMX generates goAML filings under four-eyes control, and every step is written to a tamper-evident hash-chain audit log.

Does transaction data leave our premises?

No. TMX runs on-premises inside your payment perimeter, where the payment traffic already sits.

How does monitoring use what we learned at onboarding?

TMX and SonarPulse KYC share one customer record, so a monitoring rule fires against the risk rating, beneficial owners and screening results gathered at onboarding.

How long do we have to file an STR?

FIAMLA section 14(1) says promptly but not later than 5 working days after the suspicion arose. The FIU’s Guidance Note 4.1, in effect since 19 August 2026, says the five days start when the MLRO or deputy MLRO determines that reasonable grounds for suspicion exist, and that it expects the STR the same day where reasonably practicable.

Further reading

Latest briefings on Mauritius

Start with a compliance health check.

A working session with your compliance team, then a walkthrough against your own risk appetite: the lifecycle end to end, scoring weights set to your policy, and a review of the audit trail the system produces.

Or write to info@sonarpulse.mu