Compliance

The Compliance app houses the institution's anti-money-laundering, sanctions-screening and regulatory-reporting machinery within the BridgeERP MFI Suite. It manages watchlists, transaction monitoring, suspicious- and cash-transaction reporting, goAML submission to the financial-intelligence unit, and member de-duplication.

This section covers:

  • Dashboard — The compliance command centre, summarising open alerts, pending screening matches, due STR/CTR filings and goAML submission status
  • Watchlist Sources — Registers the sanction- and watchlist sources the institution screens against (mfi.aml.watchlist.source) - such as UN, OFAC, EU an
  • Watchlist Entries — The consolidated store of individual watchlist records (mfi.aml.watchlist.entry) imported from every registered source - names, al
  • Screening Matches — Holds the hits the screening engine raises when a member or counterparty resembles a watchlist entry (mfi.aml.screening.match), ea
  • STR Reports — Manages Suspicious Transaction Reports (mfi.aml.str.report) raised when activity indicates possible money laundering or terrorist
  • CTR Reports — Manages Cash Transaction Reports (mfi.aml.ctr.report) for cash movements at or above the regulatory threshold, regardless of suspi
  • Monitoring Rules — Defines the automated transaction-monitoring rules (mfi.aml.monitoring.rule) that scan activity for red flags - structuring, veloc
  • Alerts — The work queue of alerts (mfi.aml.alert) raised by monitoring rules and screening, each flagging a member or transaction for revie
  • goAML Export — A wizard (mfi.goaml.export.wizard) that compiles approved STRs and CTRs into the goAML-format XML the financial-intelligence unit
  • Submission Log — An audit register of every regulatory submission made (mfi.goaml.submission.log) - goAML filings and other regulator reports, with
  • Duplicate Candidates — Surfaces likely duplicate member records (mfi.member.duplicate.candidate) detected by matching names, identity documents and conta
Was this page helpful?