Intelligence Brief: With POJK No. 24/2025, OJK standardizes how banks classify and control inactive and dormant accounts. This is not a UX cleanup — it is a fraud and “mule account” response. Dormant money is now treated as a risk surface, not a forgotten balance.
01. Why This Exists: Dormant Accounts Became a Weapon
Indonesia’s fraud economy runs on accounts that aren’t actively monitored by their owners. If each bank defines inactivity differently, criminals exploit the gaps. POJK 24/2025 creates a single national language for account status — so enforcement becomes scalable.
ACTIVE
Accounts with qualifying activity (including certain non-cash actions like balance checks).
INACTIVE
Status change triggers notification + restrictions.
DORMANT
Long-term inactivity becomes a higher-control state.
02. The Mechanics: A Timeline of Account Status
| Clock | Status | Bank Action |
|---|---|---|
| Day 0–360 | Active | Normal features |
| Day 361+ | Inactive | Notify customer; restrict withdrawals; require reactivation request |
| Day 1801+ | Dormant | Higher-control handling; standardized governance expectations |
Customer Communication Becomes Mandatory
Banks must inform customers when an account transitions to inactive status through available channels. The industry implication is simple: status changes are now events — logged, notified, and defensible.
03. Startup Impact: KYC, Payroll, and Embedded Finance
-
///
Payroll & SME Banking Inactive account restrictions will surface as failed disbursements. Expect higher “account health” checks upstream.
-
///
Fraud Ops A standardized dormant definition makes mule-account detection easier — but pushes fraudsters to faster rotation.
-
///
Embedded Finance Fintechs relying on partner-bank accounts must align lifecycle rules, reactivation flows, and customer comms.
Analyst Outlook
"POJK 24/2025 is a quiet but powerful anti-fraud instrument. By standardizing account status nationally, OJK reduces ambiguity — and ambiguity is where scams live. Expect better controls, but also more friction in reactivation and payments unless UX is rebuilt."