A PT PMA registered for software development quietly started generating real revenue from a consulting service it had begun offering clients almost as an afterthought, treating the new income stream as a natural extension of the existing business rather than a distinct activity requiring its own registration. Nobody flagged it internally, since the work felt closely related to what the company was already licensed to do. An LKPM review eighteen months later flagged it immediately. The company had been operating an entirely unlicensed business line for a year and a half, generating income under a KBLI code that had nothing to do with consulting services at all.

That gap, between activities that feel like a natural extension of an existing business and activities that legally require their own registered code, is exactly where adding a KBLI stops being optional and starts being a compliance requirement.

Why Adding a KBLI Is Not One Step, It Is a Sequence

Expanding a PT PMA’s registered activities touches several interconnected systems at once, the Articles of Association, the company’s capital structure, its risk classification under OSS, and, where foreign staff are involved, its immigration sponsorship position. Treating this as a single form submission rather than a sequence of dependent steps is how companies end up with a technically updated NIB sitting on top of capital or documentation that was never actually brought into alignment.

Step 1: Confirm Whether the New Activity Actually Needs a New Code

Not every new activity requires the same treatment. If the activity genuinely supports the company’s existing primary business without generating independent commercial revenue, it may qualify as a supporting classification rather than requiring the fuller registration process a primary activity demands, a distinction covered in detail in XPND’s guide to primary versus secondary KBLI codes in Indonesia. The moment that supporting activity starts generating its own revenue, as it did in the scenario above, it no longer qualifies for that lighter treatment and needs to be registered and capitalized as its own primary classification instead.

Step 2: Amend the Articles of Association If the New Code Requires It

Where the new activity needs to be registered as a primary classification, the company’s Articles of Association typically need to be amended to reflect the expanded scope of business, a decision requiring formal shareholder approval. That approval process runs through the same RUPS-LB mechanics covered in XPND’s guide to calling and conducting an Extraordinary GMS, including the notice period, quorum requirements, and the notarization and AHU registration sequence that follows once the resolution passes.

Step 3: Recalculate Capital Against the New Combined Code Count

Each five digit KBLI code carries its own capital obligation, and adding a code changes the company’s total capital position rather than simply adding a line item to an existing structure. Under current BKPM regulation, a PT PMA holding three KBLI codes needs paid-up capital of at least IDR 2.5 billion per code, combined, alongside a total investment plan exceeding IDR 10 billion per code, a calculation explained precisely in XPND’s guide to BKPM Regulation 5/2025. A company adding a fourth code without recalculating its capital position against this per code requirement is updating its licensing record while leaving its actual capital structure out of alignment with what that record now claims.

Worth flagging separately, the OSS system itself has been reported to apply its own validation check at the point of a KBLI change, blocking the update where a PT PMA’s recorded paid-up capital has not reached IDR 10 billion, a figure that reflects the older capital threshold rather than the current reduced requirement. Whether this is a system level check that has not fully caught up to the current regulation or a scenario tied to a specific sectoral exception is worth confirming directly with OSS before assuming the change will process smoothly purely because the company satisfies the current legal minimum.

Step 4: Reassess Risk Classification for the New Activity Specifically

Every KBLI code carries its own risk classification under the OSS RBA system, and that classification can differ meaningfully from the codes a company already holds. A company operating comfortably under low risk classifications for its existing activities can find that a newly added code sits in a medium high or high risk tier, triggering licensing requirements, environmental permits, or sector specific approvals that its existing operations never needed. Confirming the new activity’s actual risk classification before assuming the addition will process as smoothly as the company’s original registration avoids discovering this gap only once the new license application stalls.

Step 5: Update the NIB and Verify Foreign Worker Consistency

The final step updates the company’s Business Identification Number itself to reflect the new activity, since operating outside registered KBLI codes is a compliance breach regardless of whether the underlying activity would otherwise be permitted, a principle explained in XPND’s NIB guide. For companies employing foreign staff in roles tied to the new activity, this step carries an additional dependency. A foreign worker’s RPTKA authorization has to align with the company’s registered KBLI codes, and a specialist brought in for an activity the company has not yet formally added cannot be sponsored for that role, a consistency requirement covered in XPND’s KBLI 2026 guide for foreign investors.

A Practical Sequence for Adding a KBLI to an Existing PT PMA

Bringing these five steps together, a grounded approach for a PT PMA expanding its registered activities looks like this.

  • Confirm whether the new activity genuinely qualifies as a supporting classification or has already crossed into generating independent commercial revenue that requires primary registration
  • Secure RUPS-LB approval and complete the Articles of Association amendment before proceeding to any capital or NIB update
  • Recalculate the company’s total paid-up capital and investment plan against the new combined KBLI count, not just the single new code being added
  • Confirm the new activity’s specific OSS risk classification before assuming it will inherit the licensing treatment of the company’s existing codes
  • Update the NIB and verify that any foreign staff tied to the new activity have RPTKA authorization consistent with the newly registered code

None of these steps are unusual individually. What causes real exposure is treating a new activity as an informal extension of the existing business for months or years before anyone actually runs it through this sequence, by which point the gap has already generated real revenue under a license that never covered it.

XPND’s business licensing team manages this expansion sequence for PT PMA clients directly, confirming whether a new activity actually needs its own classification before revenue accumulates under the wrong code, and coordinating the capital, documentation, and NIB updates so the company’s licensing record reflects what it is actually doing. A business that has genuinely grown beyond its original registration is not a compliance problem waiting to happen. A business that grew without ever updating that registration is.