Skip to main content
DTI

DTI PROPRIETARY · INTEGRATED CONGLOMERATION REPORTING

A platform that helps financial groups organize data, validation, and reporting more systematically.

PIKK helps financial holdings collect data, run validation, monitor reporting status, and strengthen cross-entity governance.

Discuss your deployment

Free initial consultation — we'll map your needs, integration, and compliance.

Are you inquiring for an organization or yourself?*

Reply within 1 business day · Your data is protected (UU PDP)

ABOUT PIKK REPORTING

Built for the OJK conglomerate reporting framework.

Indonesian financial conglomerates (Konglomerasi Keuangan) operate under one of Southeast Asia’s most demanding regulatory frameworks. UU P2SK No. 4/2023 placed financial conglomerates under integrated OJK supervision, and POJK 30/2024 mandates consolidated reporting by the conglomerate’s parent entity — the PIKK (Perusahaan Induk Konglomerasi Keuangan) — pulling data from multifinance, insurance, digital banking, venture capital, pension funds, and securities across quarterly, semester, annual, and incidental cycles.

PIKK Reporting is DTI’s proprietary platform for integrated conglomeration reporting: it consolidates multi-entity data, validates it against OJK rules, and generates submission-ready PIKK reports — backed by an Early Warning dashboard and a Knowledge & Information Catalogue for governance, audit, and risk documents.

Engineered in Jakarta with direct access to evolving POJK requirements, PIKK is purpose-built for Indonesia’s regulatory reality — not adapted from generic global tools. Submission to OJK runs through the official SILARAS Web and APOLO Web channels. Deployed with a major Indonesian financial conglomerate (named reference available under NDA).

CAPABILITIES

Built for the full PIKK reporting workflow

PIKK helps financial holdings organize data collection, validation, approval, monitoring, and governance documentation in one workflow.

01

Multi-entity consolidation

Consolidate data across the conglomerate’s subsidiaries — multifinance, insurance, digital banking, venture capital, pension funds, securities — with automated mapping and reconciliation.

02

Configurable rule engine

Regulation rules are configured in-app and regenerated when OJK updates requirements — without redeploying the application.

03

XBRL + two-level validation

XBRL output with validation at both member-entity (Anggota) and parent (Induk) levels before submission to OJK.

04

Multi-input & dual submission

Three input methods (HTML form, Excel, PDF); OJK-ready TXT/PDF plus internal XLS/CSV output; dual submission via SILARAS Web (per-entity) and APOLO Web (consolidated PIKK).

05

Early-warning dashboard

Grafana-powered monitoring with early-warning signals — forward-looking risk insight for holding management, not just hindsight reporting.

06

Knowledge & Information Catalogue

A centralized repository for regulatory, audit, risk, and internal documents — serving 8 functional domains: Compliance, Legal, Risk, Internal Audit, Finance, Corporate Planning, IT, and HC&GS.

STANDARDS & FRAMEWORK

Anchored in the OJK reporting framework

UU P2SK 4/2023
Integrated FC supervision
POJK 30/2024
Conglomerate (PIKK) reporting
SILARAS · APOLO
OJK submission platforms
PSrE — Tilaka
Sister-company e-signing

FAQ

Common questions

Who must submit PIKK reports under POJK 30/2024?

The conglomerate’s parent entity — the PIKK (Perusahaan Induk Konglomerasi Keuangan). Under UU P2SK 4/2023, financial conglomerates fall under integrated OJK supervision, and the PIKK consolidates data from its member entities (multifinance, insurance, digital banking, venture capital, pension funds, securities) into one submission.

What reporting cycles does POJK 30/2024 require?

Quarterly, semester, annual, and incidental reports. PIKK Reporting tracks all cycles with status monitoring and early-warning signals so deadlines are visible to the holding — not discovered late by each entity.

What is XBRL and why does it matter?

XBRL (eXtensible Business Reporting Language) is the structured data format used for regulator submissions. PIKK generates XBRL output and validates it twice — at the member-entity (Anggota) level, then at the parent (Induk) level — before anything is submitted to OJK.

How does submission to OJK actually work?

Through OJK’s official channels: SILARAS Web for per-entity reports and APOLO Web for the consolidated PIKK submission. PIKK Reporting produces submission-ready outputs for both, plus internal XLS/CSV for reconciliation.

Has PIKK Reporting been used in production?

Yes — it is deployed with a major Indonesian financial conglomerate. A named reference is available under NDA.

How do we get pricing?

Scope depends on the number of member entities, report types, and integration needs. Request a proposal and DTI will map your conglomerate structure to an implementation plan and quotation.

READY TO DEPLOY PIKK REPORTING?

Sandbox access and a tailored walkthrough.

Schedule a PIKK discussion to map entities, data sources, approval workflows, and reporting requirements.

Chat via WhatsApp