A technology company operating in Jakarta had been running its software development operations under KBLI 62010 for three years. When they applied to add a new business line involving data analytics services, the OSS RBA system flagged an inconsistency. Their actual primary activity, which involved developing and licensing software products to third parties, fell under KBLI 58200, not 62010. The wrong code had been selected at incorporation. Three years of LKPM reports had been filed under a classification that did not accurately describe their operations. The correction process took eleven weeks, required a notarial deed amendment, and temporarily blocked their ability to process the new license application.

The KBLI code is not administrative background information. It is the foundation on which every license, every LKPM report, every investment threshold calculation, and every OSS RBA interaction sits. When it is wrong, the consequences compound quietly over time until they surface at the moment the company needs to move quickly.

Why KBLI Errors Are More Common Than They Appear

KBLI errors occur in three typical situations, and none of them involve deliberate misrepresentation.

Selection error at incorporation

The process of choosing a KBLI code at the time of company establishment is often treated as a procedural formality rather than a strategic decision. Notaries typically offer a list of codes for the client to choose from, and investors who are unfamiliar with the classification system select the code that sounds closest to their intended activity. The five-digit codes are nuanced, and the difference between related codes is not always obvious from a plain-language description. Under the Business Identification Number (Nomor Induk Berusaha or NIB) system through OSS RBA, a wrong selection at this stage propagates through every subsequent licensing and reporting step.

Migration error under KBLI 2025

BPS Regulation No. 7 of 2025 introduced the KBLI 2025 framework, which restructured several categories from the previous KBLI 2020 system. Category J, which previously covered all Information and Communication activities, was split into two separate categories. Several codes were consolidated, others were subdivided. The mandatory compliance deadline for all existing companies to realign their KBLI classifications with the new framework was June 18, 2026. Companies that migrated their codes without careful review may have selected a 2025 equivalent that does not precisely match their actual business activity.

Activity drift

A company incorporated under a specific KBLI code gradually expands its activities beyond the scope of that code without formally updating its registration. The OSS RBA system cross-references actual activity descriptions in LKPM reports against the registered KBLI. Over time, the discrepancy between what the company reports as its activities and what its KBLI code permits creates a compliance exposure that auditors and inspectors identify during field checks.

What the KBLI Code Actually Governs

Understanding why a wrong KBLI code causes problems requires understanding the range of decisions that flow from it.

Risk level classification. Each KBLI code in the OSS RBA system carries one of four risk levels: low, medium-low, medium-high, or high. The risk level determines which licenses a company must obtain before commencing operations, how frequently it is subject to post-licensing supervision, and whether it needs to complete an Environmental Impact Assessment (Analisis Mengenai Dampak Lingkungan or AMDAL). A company operating under a lower-risk KBLI than its actual activity warrants is effectively operating without the licenses its real activity requires.

Foreign ownership limits. Under the Positive Investment List (Daftar Prioritas Investasi or DPI), the maximum permitted foreign ownership percentage varies by KBLI code. Some codes allow 100 percent foreign ownership. Others are restricted or closed to foreign investment entirely. A PT PMA that has registered under a KBLI code with a higher foreign ownership ceiling than its actual activity permits may be in violation of sectoral ownership restrictions without being aware of it.

Investment threshold and LKPM reporting. The IDR 10 billion total investment value requirement applies per five-digit KBLI code per project location. A company that registers multiple KBLI codes must meet the investment threshold for each code it operates under. LKPM reports filed under the wrong code misrepresent the company’s investment realization to the Ministry of Investment (Kementerian Investasi dan Hilirisasi or BKPM), which monitors compliance through quarterly reports submitted through OSS RBA.

Investor KITAS eligibility. The immigration authority cross-references a PT PMA shareholder’s KBLI classification when assessing Investor KITAS eligibility. A mismatch between the registered code and the actual business activity can create a verification problem during the BKPM recommendation stage of the application process.

Tax treatment. Certain KBLI codes qualify for specific tax incentives including tax holidays, tax allowances, and gross income reduction facilities. A company that operates under the wrong code may be ineligible for incentives it would otherwise qualify for, or may have claimed incentives it was not entitled to.

The Consequences of Operating Under the Wrong KBLI Code

The severity of the consequences depends on how long the error has been in place, how materially it misrepresents the company’s actual activities, and when it is detected.

License invalidity

Under Government Regulation (Peraturan Pemerintah or PP) No. 5 of 2021 on Risk-Based Business Licensing, a business license is tied directly to the KBLI code under which it was issued. If the company’s actual activity falls under a different code, the license issued under the wrong code does not legally cover those activities. The company is technically operating without a valid license for its actual business, regardless of whether a license physically exists in the OSS system.

LKPM sanctions

Inaccurate LKPM reporting resulting from a wrong KBLI code can trigger administrative sanctions under BKPM Regulation No. 5 of 2025. Sanctions range from written warnings to suspension of business licenses. For PT PMA entities, four consecutive quarters of zero or inconsistent investment realization reporting can result in NIB deletion proceedings.

OSS RBA system flags

The OSS RBA system conducts automated cross-checks between a company’s registered KBLI, its LKPM activity reports, and tax data from the Directorate General of Taxes (Direktorat Jenderal Pajak or DJP). Discrepancies trigger system flags that can block license renewals, restrict permit amendments, and prevent new license applications from being processed until the inconsistency is resolved.

Field inspection exposure

PP No. 28 of 2025 strengthened the post-licensing supervision framework by mandating regular field inspections for medium and high-risk business classifications. Companies whose actual activities are inconsistent with their registered KBLI face heightened exposure during these inspections. Inspectors from the relevant technical ministry or local government office assess whether the company’s operations match its registered classification. A mismatch is recorded as a compliance violation.

Bank account and financial implications

Corporate bank accounts in Indonesia are opened against the company’s NIB and KBLI classification. Some banks conduct periodic compliance checks against OSS data. A KBLI mismatch that surfaces during a bank review can affect credit facilities, transaction processing, and account standing.

How to Detect Whether Your KBLI Code Is Correct

Companies that want to assess their current KBLI compliance should work through three verification steps.

The first is an activity-to-code comparison. The starting point is a plain-language description of the company’s actual primary business activity, written without reference to any existing KBLI code. This description is then matched against the BPS KBLI 2025 classification framework to identify which five-digit code most precisely corresponds to the activity. Where the company operates multiple distinct activities, each one requires its own code assessment.

The second is an OSS data review. The company’s current KBLI registration in the OSS RBA system should be compared against the result of the activity-to-code comparison. The OSS RBA portal at oss.go.id provides access to the company’s current NIB data including registered KBLI codes. Any difference between the registered code and the correct code for the actual activity identifies the scope of the correction required.

The third is a Positive Investment List check. For PT PMA entities, the identified correct code should be cross-referenced against the DPI to confirm the foreign ownership percentage permitted under that code. If the correct code carries a lower foreign ownership ceiling than the current code, the shareholding structure may also require adjustment before the KBLI correction is processed.

How to Correct a Wrong KBLI Code

The correction process for a wrong KBLI code in Indonesia involves two parallel tracks: the corporate documentation track and the OSS RBA system track.

Corporate documentation. A KBLI change requires a formal amendment to the company’s Articles of Association (Anggaran Dasar) through a notarial deed. This deed must be submitted to the Ministry of Law’s Legal Entity Administration System (Sistem Administrasi Badan Hukum or SABH) within 30 days of execution, in accordance with Minister of Law Regulation (Peraturan Menteri Hukum or Permenkum) No. 49 of 2025. Failure to submit within this window results in the amendment being rejected and the process needing to restart.

OSS RBA system update. Once the notarial deed amendment has been processed and confirmed through SABH, the new KBLI data is reflected in the Ministry of Law’s AHU system. This data is then synchronized with the OSS RBA system. The company must log into OSS RBA to verify the updated KBLI data has been correctly reflected in the NIB record and update any associated business licenses to reflect the new classification.

License reissuance. Where the correct KBLI carries a higher risk level than the previous code, new or upgraded licenses will need to be obtained under the corrected classification before the company can continue operations under that code. The license application process follows the standard OSS RBA pathway for the new risk level.

LKPM correction. LKPM reports filed under the wrong KBLI code may need to be reviewed and corrected through the OSS RBA investment activity report system. Companies with significant reporting history under an incorrect code should assess whether historical reports need to be amended and consult with BKPM’s investment monitoring division on the appropriate correction procedure.

The total timeline for a straightforward KBLI correction typically runs four to eight weeks from the notarial deed execution to confirmed OSS RBA data synchronization. Cases involving license reissuance, DPI compliance reviews, or historical LKPM corrections extend this timeline.

The KBLI 2025 Transition as an Opportunity to Correct Existing Errors

The mandatory KBLI 2025 realignment deadline of June 18, 2026 created both a compliance obligation and a correction opportunity. Companies required to migrate their codes from the KBLI 2020 framework to KBLI 2025 had a legitimate basis to review and correct their classifications as part of the migration process.

For companies that completed their KBLI 2025 migration without conducting a thorough activity-to-code review, there is still time to assess whether the migrated code accurately reflects actual business activity. The KBLI 2026 guidance published by BKPM provides updated sector-specific guidance on code selection that was not available at the time of the original KBLI 2025 release. A detailed breakdown of the current classification framework is available in the KBLI 2026 guide for foreign investors.

For companies that have not yet completed their KBLI 2025 migration, this is a compliance obligation that needs to be addressed immediately. The selection methodology for identifying the right five-digit code is covered in the guide on how to choose the correct KBLI.

One Problem That Compounds Before It Gets Fixed

The reason KBLI errors tend to be caught late is that they rarely announce themselves. The wrong code allows a company to operate, file LKPM reports, and renew licenses for months or years before the inconsistency surfaces in a system check, an inspection, or a new application that triggers cross-referencing. By the time the problem is visible, there is usually a backlog of inaccurate reporting to address alongside the correction itself.

XPND works with PT PMA companies on exactly this kind of diagnostic. Before any amendment is filed, the team maps the company’s actual activities against the current KBLI 2025 framework, checks the DPI implications of the correct code, reviews historical LKPM reports for inconsistencies that will need to be addressed, and confirms whether any licenses require reissuance under the corrected classification. The point is to understand the full scope of what needs to be corrected before the notarial process begins, not discover additional problems partway through it.

If your company has been operating under the same KBLI code since incorporation without a formal review, or if your KBLI 2025 migration was completed quickly under deadline pressure, the starting point is a straightforward classification audit. Reach out to info@xpnd.co.id to get that process started.