Picture this: a PPATK auditor arrives at your office this morning. They ask for all the suspicious transaction report documentation filed over the last 12 months. Do those reports meet the standard?
For a compliance officer in financial services, the ability to produce an accurate Suspicious Transaction Report (LTKM, Laporan Transaksi Keuangan Mencurigakan) is not merely a regulatory obligation — it is the front line of Indonesia's anti-money-laundering system.
Contents
- What Is an LTKM?
- When Is Reporting Mandatory?
- LTKM Format and Contents
- 3 Complete LTKM Examples
- Common Reporting Mistakes
- Quality Control Checklist
- FAQ
What Is an LTKM?
An LTKM (Laporan Transaksi Keuangan Mencurigakan) — a Suspicious Transaction Report (STR) — is a mandatory report submitted by a Reporting Party to PPATK, Indonesia's financial intelligence unit, when a transaction meets the criteria for suspicion.
The Legal Basis for LTKM
- Law No. 8 of 2010 on the Prevention and Eradication of Money Laundering (Article 23(1))
- Government Regulation No. 43 of 2015 on Reporting Parties in Money Laundering Prevention
- POJK No. 12/POJK.01/2017 on Implementing the APU-PPT (AML/CFT) Programme in Financial Services (updated by POJK No. 8 of 2023)
A Reporting Party must submit an LTKM within 3 working days of the transaction being identified as suspicious.
When Is Reporting Mandatory? Thresholds and Triggers
Suspicious Transaction Indicators (Article 1(5), Law 8/2010)
- Deviates from the customer profile — Inconsistent with their characteristics or usual transaction pattern
- Suspected of evading reporting — Structuring or smurfing, for instance
- No clear economic purpose — Using assets suspected to be criminal proceeds
- Transactions involving criminal proceeds — Involving assets known or reasonably suspected to derive from a crime
Reporting Thresholds
| Report Type | Threshold | Deadline | Notes |
|---|---|---|---|
| LTKM (Suspicious) | No monetary threshold | 3 working days | Based on suspicion indicators |
| LTKT (Cash) | ≥ IDR 500,000,000 | 14 working days | Cash transactions reaching the threshold |
| LTKL (Cross-border transfer) | ≥ IDR 100,000,000 | 14 working days | International funds transfers |
Important: LTKM has no monetary threshold. Even an IDR 1 million transaction must be reported if it meets a suspicion indicator.
Build Your AML/CFT Competency
Learn investigation and LTKM reporting technique on the KYC & AML Compliance Professional course.
LTKM Format and Contents
Reports are filed through PPATK's goAML application.
| Section | Key Field | Notes |
|---|---|---|
| A. Reporting Party Data | Reporting Party name | The institution's legal name |
| Reporting Party code | The code issued by PPATK at goAML registration | |
| Reporting officer | Name and position of the compliance officer | |
| B. Related Party Data | Full name | As per national ID or passport |
| Identity number | NIK (national ID), passport, or tax number | |
| Account numbers | Every related account | |
| Relationship | Sender, recipient, beneficial owner | |
| C. Transaction Data | Date and time | DD/MM/YYYY HH:MM |
| Transaction type | Cash deposit, transfer, foreign exchange | |
| Transaction value | In rupiah | |
| Location | The branch where it took place | |
| D. Grounds for Suspicion | Suspicion indicator | From the PPATK indicator list |
| Chronological narrative | An account of why it is suspicious | |
| CDD/EDD findings | Due diligence results |
The Internal Process Before Filing
Before an LTKM reaches goAML, there is a tiered internal escalation process:
| Stage | Owner | SLA | Action |
|---|---|---|---|
| 1. Identification | Frontliner | D+0 | Detect the red flag, complete the internal form |
| 2. Verification | Branch Compliance | D+0 to D+1 | Verify the data, complete the customer profile |
| 3. Analysis | AML unit | D+1 to D+2 | In-depth analysis, EDD if needed, draft the narrative |
| 4. Approval | MLRO | D+2 | Review and approve before submission |
| 5. Filing | Reporting officer | D+2 to D+3 | Submit via goAML, keep the acknowledgment number |
Parallel reporting: Besides PPATK via goAML, institutions must also report through SIPESAT (the APU-PPT Reporting and Statistics System) to OJK, the Financial Services Authority.
Submitting via goAML
- Log in to goAML Web (goaml.ppatk.go.id)
- Select the report type (LTKM/LTKT/LTKL)
- Complete the reporting party data (auto-filled from the institution profile)
- Enter the related party and transaction data
- Select the suspicion indicator from the dropdown
- Write the suspicion narrative
- Attach supporting documents
- Review and submit — the system issues an acknowledgment number
goAML is also available as a desktop version for batch upload, and in XML format for system integration.
PPATK Red Flag Indicators
PPATK publishes Suspicious Transaction Identification Guidance per sector. The main categories in summary:
| Category | Example Indicators |
|---|---|
| Cash Transactions | Large deposits/withdrawals inconsistent with the profile; exchanging damaged banknotes in bulk |
| Funds Transfer | Transfers to/from high-risk countries; round-tripping; multiple transfers to many recipients |
| Structuring | Splitting transactions below the threshold; using several branches or banks; nominees |
| Insurance Products | Large single premium from a new entity; surrender before maturity; an implausible beneficiary |
| PEPs | PEP transactions with no clear source of funds; abrupt profile change; transfers to risky jurisdictions |
| Fintech/E-Money | Top-ups from many sources; multiple accounts for one individual; cross-border transactions via digital remittance |
3 Complete LTKM Examples
Note: all names and details are fictitious, for educational purposes.
Example 1: A Cash Transaction Inconsistent with the Profile
| Reporting Party | PT Bank Nusantara Tbk, Sudirman Branch |
| Customer | Budi Santoso, NIK: 3175XXXXXXXXXXXX |
| Profile | Private sector employee, salary IDR 15 million/month |
| Transaction | Cash deposit of IDR 750,000,000 (5 March 2026) |
Narrative: The customer made a cash deposit of IDR 750 million — the largest single transaction in 3 years. Their average balance over the last 12 months was IDR 22 million. When asked, the customer stated it was "proceeds from selling inherited land" but could not produce a deed of sale or inheritance documentation. The customer declined to complete a source-of-funds form.
An internal database check showed an average balance over the last 12 months of IDR 22 million with average monthly credits of IDR 16 million (salary). The IDR 750 million deposit departs from the normal pattern by more than 4,500%. Branch Compliance escalated to the AML unit the same day. Further verification found no record of property ownership in the customer's name in the OJK financial information system.
Suspicion indicators:
- The transaction deviates significantly from the customer's profile and transaction pattern
- The customer could not adequately explain the source of funds
- The customer refused to provide the information requested
Example 2: A Structuring (Smurfing) Pattern
| Customer | CV Maju Bersama (Director: Hendra Gunawan) |
| Profile | Stationery trading, turnover IDR 200 million/month |
| Transactions | 10 cash deposits @ IDR 480 million over 15 days = IDR 4.8 billion |
Narrative: The AML system detected 10 cash deposits of IDR 470-490 million each — consistently just under the IDR 500 million LTKT threshold. The IDR 4.8 billion total is inconsistent with turnover of IDR 200 million/month. EDD found: financial statements showing annual turnover of only IDR 2.1 billion, deposits made by 4 different individuals, and no supporting business contracts.
Indicators: Structuring to evade reporting, value inconsistent with the business profile, use of third parties.
Example 3: Beneficial Owner Mismatch
| Reporting Party | PT Asuransi Sejahtera |
| Customer | PT Global Investama (6 months old, capital IDR 500 million) |
| Transaction | Single premium life policy of IDR 5 billion |
Narrative: PT Global Investama purchased a single premium life insurance policy of IDR 5 billion. EDD found: 95% of shares held by a BVI entity (Oceanic Holdings Ltd) — the ultimate beneficial owner could not be identified. The company is 6 months old with capital of IDR 500 million. The policy beneficiary is not a family member of the insured but a Singapore company.
Indicators: Beneficial owner not identified, high-risk jurisdiction, placement typology via an insurance product.
PEP and Sanctions Screening
PEPs (Politically Exposed Persons)
Transactions involving a PEP require EDD and automatically fall into the high-risk category. Under POJK 8/2023, PEPs include heads of state, ministers, national and regional legislators, state-owned enterprise officials, judges, prosecutors, and their immediate family and close associates. A PEP transaction inconsistent with their income profile is a strong LTKM trigger.
Sanctions Screening
Every transaction must be screened against:
- DTTOT — Indonesia's domestic list of suspected terrorists and terrorist organisations
- UN sanctions — The UN Security Council Consolidated List
- OFAC SDN List — For transactions involving USD or US entities
- EU Sanctions List — For transactions with Europe
Any match — even a partial one — must be escalated and may become an LTKM.
Common LTKM Reporting Mistakes
| No | Mistake | Consequence | How to Fix It |
|---|---|---|---|
| 1 | Narrative too brief | PPATK returns the report | At least 3 paragraphs: identification, chronology, analysis |
| 2 | Incomplete customer data | Obstructs analysis | Ensure NIK, address, accounts, and CDD profile are complete |
| 3 | Late filing (>3 days) | Administrative sanction | Set a 1-day internal SLA for escalation to compliance |
| 4 | No supporting documents | Low quality | Attach statements, CDD/EDD forms, transaction evidence |
| 5 | Mixing opinion with fact | Credibility suffers | Separate transaction data from the suspicion analysis |
| 6 | Irrelevant indicators | Hard to prioritise | Pick the most specific indicator, not all of them |
LTKM Quality Control Checklist
Before submitting in goAML:
- Related party identity complete — Name, NIK, address, phone, occupation, source of funds
- Account numbers valid — Every account involved is listed
- Transaction detail accurate — Date, time, value, type, location
- Suspicion narrative adequate — At least 3 paragraphs
- Suspicion indicator selected — At least one from the PPATK list
- CDD profile attached — Including source of income
- Supporting documents attached — Statements, slips, EDD forms
- Reviewed by a supervisor — MLRO or head of compliance
- Deadline met — Within 3 working days
- No tipping off — The customer has not been informed
Master AML Reporting for Islamic Banking
Take AML/CFT for Islamic Banking to understand the typologies specific to Sharia products and how to report them.
FAQ
Does LTKM only apply to transactions above IDR 500 million?
No. LTKM has no monetary threshold. The IDR 500 million threshold applies to LTKT (cash reports). An IDR 10 million transaction showing a structuring pattern still has to be reported as an LTKM.
What is the deadline for filing an LTKM?
No later than 3 working days from the point the transaction is identified as suspicious. Late filing can draw a written warning, a fine, or ultimately revocation of the operating licence.
Can a compliance officer be sued over a false positive LTKM?
No. Article 29 of Law 8/2010 provides legal protection — a safe harbour provision — for Reporting Parties who report in good faith.
What happens after an LTKM is submitted?
PPATK validates completeness, analyses it against national databases, and where there is an indication of a criminal offence, passes the analysis to investigators (police, prosecutors, or the anti-corruption commission).
What is tipping off and what is the penalty?
Informing a customer that an LTKM has been filed carries up to 5 years' imprisonment and a fine of IDR 1 billion (Article 14, Law 8/2010).
How long must LTKM documents be retained?
Under Article 22 of Law 8/2010, all related documents (customer data, transaction records, CDD/EDD forms, copies of the LTKM) must be retained for 5 years from the end of the business relationship.
What is a PCO, and is one mandatory?
A PCO (PPATK Compliance Officer) is the designated liaison with PPATK. Appointing one is mandatory and must be notified to PPATK. The PCO is responsible for coordinating reporting and responding to requests for further information.
Can PPATK request additional information?
Yes. PPATK is empowered to request further information during its analysis. Failure to respond may be treated as obstruction and can attract sanctions.