KBLI 2025 SDPPI Certification: Indonesia's June Deadline

Indonesia's KBLI 2025 Is Now Mandatory and It Can Block Your SDPPI Certification

Indonesia has switched to a new national business-classification standard, and the change reaches further than corporate registration alone. Since 18 June 2026, the 2025 Indonesian Standard Industrial Classification (KBLI 2025) is the only classification accepted across the Online Single Submission (OSS) system.

For the wireless and telecommunications industry, that single administrative change has a direct downstream effect: a company cannot generate the business licence needed to open a DJID/SDPPI certification application unless its KBLI codes have already been migrated to the 2025 framework.

If your Indonesian importer, distributor, or appointed certificate holder is still registered under KBLI 2020 codes, new type approval filings can stall before they begin.

What Actually Changed

The 2025 classification was introduced by BPS Regulation No. 7 of 2025 on the Indonesian Standard Industrial Classification, issued by Statistics Indonesia (Badan Pusat Statistik, BPS). The regulation was promulgated and came into force on 18 December 2025, repealing the previous KBLI 2020 framework (BPS Regulation No. 2 of 2020). BPS published the accompanying KBLI 2025 catalogue on its official portal on 24 December 2025.

The regulation set a six month transition window. Under Article 5, every KBLI user must align its registered classification with KBLI 2025 within six months of promulgation, no later than 18 June 2026. That deadline is the point at which the transition closes and the new codes become operationally mandatory across OSS and connected government systems.

Key structural changes in KBLI 2025 include:

• Alignment with ISIC Revision 5, the latest United Nations international classification standard.

• Expansion from 21 to 22 business categories, driven largely by splitting the former "Information and Communication" category into a media/content category and a separate technology-and-telecommunications category.

• Renumbering, splitting, and consolidation of many individual codes, so a business may keep the same activity but receive a different code number.

  
  

For most companies the migration is administrative but it is not optional, and for regulated activities such as telecom equipment certification it sits directly in the critical path.

How the KBLI 2025 SDPPI Certification Link Works

DJID/SDPPI type approval in Indonesia is initiated through the OSS portal, not directly on the certification system. The sequence is:

1. The applicant (a local Indonesian entity acting as certificate holder) logs in to OSS and starts a PB-UMKU application, Perizinan Berusaha Untuk Menunjang Kegiatan Usaha, the supporting business licence.

2. During that step, the entity selects the KBLI code that matches the business scope for the product.

3. The applicant requests the licence type "Certificate for Telecommunication Equipment and/or Devices," then is redirected into the DJID/SDPPI e-certification system.

4. The issued PB-UMKU acts as the submission ticket that opens an application slot on the DJID portal. No PB-UMKU means no slot, and no slot means the certification application cannot proceed.

   
   

Here is the chokepoint: a PB-UMKU cannot be generated on legacy KBLI 2020 codes once the transition closes. If the certificate holder's OSS profile still carries 2020 codes, the system will not let it create the PB-UMKU, and the DJID/SDPPI filing is blocked at the very first step. The product, the test reports, and the technical file are irrelevant until the underlying KBLI is current.

What This Means for Manufacturers

For a foreign manufacturer, the exposure is indirect but real: your Indonesian market access depends on a local entity whose OSS/KBLI status you do not control directly.

• Your certificate holder is the single point of failure. SDPPI/DJID applications must be filed by a local Indonesian company holding a valid NIB. If that partner has not migrated to KBLI 2025, your filings are blocked even if every technical document is ready.

• The problem is invisible until you file. A certificate holder can appear fully operational and only discover the block when it tries to create a new PB-UMKU. Projects with tight launch windows are most at risk.

• New entities have no grace period. Companies registering in 2026 must use KBLI 2025 from the outset; there is no transition cushion for fresh OSS profiles.

• A code may move even if the activity does not. Because many codes were renumbered or split, the relevant telecom related KBLI for your product scope may now carry a different number, worth confirming, not assuming.

  
  

Certification Impact Summary

Area	Before (KBLI 2020)	After (KBLI 2025, from 18 Jun 2026)	Action trigger
OSS / NIB profile	KBLI 2020 codes accepted	Only KBLI 2025 codes accepted	Migrate codes in OSS
PB-UMKU creation	Possible on 2020 codes	Blocked until codes are migrated	Verify certificate holder's KBLI
DJID/SDPPI application slot	Opened via PB-UMKU ticket	No PB-UMKU = no slot	Confirm PB-UMKU can be generated
Telecom-related KBLI code	Existing number	May be renumbered/split	Re-confirm correct code for product scope
New local entities	Transition period applied	No transition — 2025 from day one	Use KBLI 2025 immediately
Existing valid certificates	Valid	Remain valid (not auto-revoked)	No action for issued certificates

Timeline + Required Actions

Regulatory timeline

• 17–18 December 2025 — BPS Regulation No. 7 of 2025 enacted and in force; KBLI 2020 repealed.

• 24 December 2025 — BPS publishes the KBLI 2025 catalogue on its official portal.

• April 2026 — BPS / BKPM / Ministry of Law guidance and a KBLI 2020→2025 conversion table issued to support OSS migration.

• 18 June 2026 — End of the six-month transition. KBLI 2025 becomes operationally mandatory across OSS; legacy codes can no longer support new PB-UMKU filings.

  
  

Required actions for manufacturers and certificate holders

1. Immediately confirm your certificate holder's KBLI status. Ask the local importer/distributor whether its OSS profile has been converted to KBLI 2025.

2. Verify a PB-UMKU can actually be created. A profile that "looks" updated should still be tested by attempting (or confirming the ability to open) a new PB-UMKU for telecom-device certification.

3. Re-check the correct KBLI code for the product's business scope, since codes may have been renumbered or split.

4. Use the BPS conversion table to map any legacy codes and identify required OSS amendments.

5. Escalate stalled migrations — KBLI changes can require notarial/legal updates to corporate data, which take time. Start now to avoid certification delays.

6. For new market entrants, ensure KBLI 2025 codes are selected from the first OSS registration; there is no transition cushion.