| Indonesian typology coverage | Configurable transaction-monitoring rules feeding a compliance-case queue, with goAML LTKM staging under dual control. We will walk you through the exact rule coverage rather than quote a typology count. | Global typology and risk framing. No published PPATK typology set. | Not a monitoring engine — World-Check is risk-intelligence reference data. | Whatever your compliance officer translated into SQL, maintained on their own time. |
|---|
| STR / LTKM reporting | Suspicious Transaction Reports (LTKM) drafted with pre-filled data for officer review and exported as goAML XML behind maker-checker approval. Cash Transaction Reports (LTKT) are on the roadmap. | Alert and case output aimed at global SAR/STR processes. Indonesian STR/LTKM artefacts are not a published feature. | Screening evidence only — reporting is not part of the data product. | Assembled by hand, per case, usually under deadline. |
|---|
| Pattern detection | Structuring, layering, and placement patterns detected across time, alongside your own custom rules. | Transaction-monitoring rules and typologies as a product line, framed globally. | Not applicable — this is a database, not a detection engine. | Threshold rules on the core system. Anything time-windowed is a project. |
|---|
| Watchlist / PEP / sanctions screening | Customers and counterparties screened against global PEP and sanctions lists as part of the same module. | This is the vendor's core strength — a proprietary, continuously updated global sanctions, PEP, and adverse-media database. | This is the product — one of the most widely licensed risk-intelligence databases in the market. | A list someone downloads and re-imports, at a cadence nobody audits. |
|---|
| Case management | Assign, investigate, and close AML cases with a full audit trail, in the same system that raised the alert. | Case management included in the platform. | No native case management — pair it with a separate workflow or case tool. | A shared spreadsheet, an email trail, and institutional memory. |
|---|
| Deployment and residency | SaaS or on-premise inside your own infrastructure, including restricted-egress and air-gapped environments. Self-hosted means customer and transaction records never leave your environment. | SaaS only. | Delivered as SaaS, API, or a data feed into your systems. | Your infrastructure — with none of the tooling. |
|---|
| Regulatory mapping | Mapped to PPATK goAML LTKM reporting, OJK AML/CFT programme requirements, and BI payment transaction-monitoring standards. | Global AML/CFT framing; local mapping is your work. | Global sanctions and PEP framing; local mapping is your work. | Entirely your work, and entirely your risk in an examination. |
|---|
| Ships integrated with fraud, KYC, and settlement | Yes — one estate. AML sits beside Fraud Detection, KYC/KYB, and the Reconciliation Engine, sharing one deployment and one audit posture. | A point solution to integrate. | A data feed to integrate. | Integrated with your core system only. |
|---|
| Pricing model | Flat Rp 3.000.000/mo (same at Starter and Growth). On-premise: contact us. Directional — billing not yet active. | Tiered/volume-based subscription, quoted on request. No published list price. | Licensed by user and/or record volume, quoted on request. No published list price. | No licence fee, and no defence when the examiner asks how the rule was validated. |
|---|
