Transaction monitoring for Japanese AML operations
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
- 0–100AI score
- API+ batch
- Audittrail
- 30-daytrial
A sample transaction monitoring view: a transaction row, rules fired, AI risk score filling and an alert outcome.
Screening in production for
What every transaction check covers
Configurable rules
Scenarios from your risk assessment
AI risk score
0–100 score on every transaction
Alert scoring
By level of suspicion
Case investigation
Evidence and escalation
STR support
Suspicious transaction reports
Tuning recorded
Decisions kept for inspection
Scenarios from your risk assessment
The FSA expects scenarios and thresholds to reflect your own risk assessment rather than a vendor's defaults
- Configurable rules
- Per product and channel
- Thresholds you set
A sample monitoring timeline: daily re-screens with one alert on a new listing.
AI risk score on every transaction
The AI rules engine scores each transaction from 0 to 100, independently of rule results
- 0–100 score
- Rule breakdown
- Case from score
A sample weighted risk score: a score bar with the factors that contributed to it.
Case investigation and escalation
Alerts become cases with assignment, notes, evidence and a decision trail, escalated to senior review where the risk warrants it
- Assignment and notes
- Evidence attached
- Escalation workflow
A sample due diligence checklist: items completed in turn and a recorded decision.
Risk-based transaction monitoring for Japan
- 0–100
- AI risk score on every transaction
- API
- Real time or batch CSV upload
- Audit
- Case, rule and model changes logged
- 30 days
- Free trial with 500 test credits
Assurance
ISO/IEC 27001:2022
ISO/IEC 27701:2019
GDPR
DORA
Three ways to monitor
Web app
Interface in English and Japanese
Batch upload
CSV or XML with preview
REST API
Real-time transaction feeds
Common questions
Where does a suspicious transaction report go in Japan?
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.
What changed for monitoring in the March 2026 FSA guidelines?
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.
Can we set our own scenarios and thresholds?
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.
How is this different from the global transaction monitoring page?
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.
Further reading
More for Japan
See MemberCheck in action
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)