Monitor customer transactions in Japan against scenarios you set from your own risk assessment, match the response to the level of suspicion, and keep the record behind each report.
Last updated
What this covers
Screening in production for
The revised FSA guidelines ask for scenarios grounded in your own risk assessment, a feedback loop from filed suspicious transaction reports, and, since March 2026, mitigation matched to the level of suspicion. A system that raises alerts but handles a weak one and a strong one identically no longer meets the required actions. The monitoring has to show its reasoning, not only its output.
Transaction monitoring systems in Japan, a buying guideThe FSA guidelines expect scenarios and thresholds to reflect the result of the institution's own risk assessment rather than a vendor's defaults. Rules, thresholds and scenarios are configured per product, customer type and channel.
Since 31 March 2026 the guidelines require risk mitigation measures according to the level of suspicion of detected transactions. Alert scoring separates weak signals from strong ones, so the two are not treated the same way.
Analyse the characteristics of transactions you have reported, including line of business and geography, and adjust scenarios against what they show. Each change is recorded.
Alerts become cases with assignment, notes, evidence and a decision trail, escalated to senior review where the risk warrants it.
The activity, findings and decisions behind an alert are compiled to support a suspicious transaction report to your sector's competent administrative authority.
ISO/IEC 27001:2022Information security management, independently audited.
ISO/IEC 27701:2019Privacy information management, extending ISO 27001.
GDPRPersonal data handled to EU standards, wherever you operate.
DORAOperational resilience for EU financial entities and their vendors.To the competent administrative authority for your sector, not directly to JAFIC. That authority notifies the National Public Safety Commission, and JAFIC collects, organises and analyses the reports centrally. The Act sets no monetary floor and no fixed filing clock.
A new required action obliges institutions to implement risk mitigation measures according to the level of suspicion of detected transactions and trends in ML/FT risk, alongside the existing expectations on risk-based scenarios and the feedback loop from filed reports.
Yes. Rules, thresholds and scenarios are configurable to your products, customer types and risk appetite, which is what lets them reflect your own risk assessment rather than a fixed template.
The monitoring product is the same. This page covers how it applies in Japan: the FSA's expectations for monitoring, suspicious transaction report routing, and what an inspection asks for. The global page describes the product for every market.
A short walkthrough of screening, verification and ongoing monitoring in one platform, set to the thresholds and jurisdictions your programme actually uses.
Transaction monitoring runs on its own platform, with its own credentials, separate from the MemberCheck screening app. An existing screening account does not sign you in to it. Open the monitoring platform (opens in a new tab)
