A technology company registered its consulting arm as a supporting KBLI code alongside its primary software development classification, treating the distinction as a formality, a way to keep the paperwork simple while both business lines operated in practice. Within two years, the consulting arm was generating nearly as much revenue as the software business itself. When the company applied for a new license tied to that consulting activity, OSS flagged the application. A supporting code, by legal definition, cannot generate independent commercial revenue. What the company had actually been running was an unlicensed primary business activity wearing a supporting code’s paperwork.
That gap, between what most investors assume primary and secondary KBLI codes mean and what Indonesian regulation actually defines them as, is worth understanding before a single code gets selected, not after a license application exposes the mismatch.
Primary and Supporting Are Not Main and Extra, They Are a Legal Test
Most foreign investors read primary and supporting KBLI codes as a simple hierarchy, the main thing a company does and a list of smaller activities alongside it. Indonesian regulatory practice draws a sharper line than that. A primary code, kegiatan usaha utama, describes the core activity that actually generates commercial revenue and serves as the basis for the company’s risk classification under OSS RBA. A supporting code, kegiatan usaha pendukung, is defined more precisely under Article 35 of Minister of Investment and Downstreaming/BKPM Regulation No. 5 of 2025, which sets out seven specific conditions: it must support the primary activity, it can become a source of revenue, its license can be applied for after the primary activity’s license, it cannot duplicate the primary KBLI code, it can obtain operational legality even before the primary activity secures its own commercial permit, it must still satisfy applicable risk-based licensing requirements, and, critically, it is exempted from minimum investment validation and from mandatory inclusion in the Articles of Association only for as long as that activity has not yet generated revenue. This distinction is covered at the general classification level in XPND’s complete guide to KBLI codes and the site’s KBLI 2026 guide for foreign investors.
This is exactly the trap the technology company in the opening scenario fell into. The regulation does not prohibit a supporting activity from generating revenue outright. It ties the administrative convenience, no investment validation, no AoA listing requirement, specifically to the period before that revenue starts. The moment a supporting activity crosses into genuine commercial income, the exemptions built around its supporting status no longer apply, and Indonesian licensing practice expects the company to bring its records into alignment with that new reality.
The Moment a Supporting Activity Stops Being Supporting
This is not a hypothetical edge case. It is common enough that it has its own procedural pathway. When a supporting activity grows into a genuine, independently revenue generating line of business, the correct response is to formally elevate it to primary status through an Articles of Association amendment, ratified at an RUPS and registered through the standard notarial and AHU process, a sequence covered in XPND’s guide to calling and conducting an Extraordinary GMS. Treating this as an optional administrative cleanup rather than a required reclassification is precisely how a company ends up, years later, discovering that a meaningful share of its actual revenue was generated under a classification that never legally permitted it.
Single Purpose Codes Do Not Allow a Secondary Anything
A further complication sits underneath the primary and supporting distinction entirely. Under Article 10(1)(f) of Minister of Investment and Downstreaming/BKPM Regulation No. 5 of 2025, certain KBLI classifications are designated Single Purpose, meaning a company registered under one of these codes is legally prohibited from combining it with any other business activity whatsoever, supporting or otherwise. This is the current governing provision, having replaced the equivalent restriction that previously sat under BKPM Regulation No. 4 of 2021 before that regulation was revoked and consolidated into the current framework. The OSS RBA system flags this restriction directly when a Single Purpose code is selected. A company assuming it can always layer a supporting activity onto its primary classification needs to confirm the primary code itself does not fall into this restricted category first, since the standard primary and supporting structure simply does not apply to it.
Explore Our Services Regulatory Compliance in Indonesia
What Changed for Supporting Codes Since KBLI 2025
The compliance weight attached to supporting codes has increased recently. Before Minister of Investment and Downstreaming/BKPM Regulation No. 5 of 2025 took effect, OSS RBA allowed companies to register multiple KBLI codes without a firm distinction between primary and supporting activities in practice. Primary codes had to appear in a company’s Articles of Association under its stated purpose, while supporting codes only needed to be entered into OSS RBA, exempted from the AoA on the reasoning that they were not expected to generate revenue. Article 35 of the new regulation formalized that exemption as conditional rather than automatic, tying it specifically to the period before a supporting activity starts generating income, a shift covered in more depth in XPND’s guide to required documents for PT PMA incorporation. Getting this classification wrong under the current framework carries the same downstream consequences covered in XPND’s wrong KBLI code guide, licensing disruption, LKPM inconsistency, and a correction process that can run for weeks once the mismatch surfaces.
Why This Affects Capital Planning, Not Just Paperwork
The primary and supporting distinction is not confined to licensing terminology. It reaches directly into capital planning. A properly classified primary activity carries its own investment threshold and risk classification under OSS, a calculation covered in full in XPND’s PT PMA establishment cost breakdown. A company that quietly runs a genuinely commercial activity under a supporting code has not just misclassified a license. It has likely understated the investment commitment and risk profile that classification is actually supposed to reflect, a gap that tends to surface during exactly the kind of licensing review or capital verification the company least expects it during.
A Practical Sequence for Structuring Primary and Supporting Activities
Bringing the legal distinction, the reclassification trigger, and the Single Purpose restriction together, a grounded approach for a PT PMA looks like this.
- Confirm whether an activity generates independent commercial revenue before classifying it as supporting, since that revenue generation is the actual legal test, not how central the activity feels to the business
- Check whether the intended primary code falls under the Single Purpose category before assuming any supporting activity can be layered alongside it
- Monitor supporting activities that grow in scale over time, and treat crossing into genuine commercial revenue as a trigger for formal reclassification rather than a milestone to note informally
- Ensure both primary and supporting classifications are properly reflected in the Articles of Association under the current KBLI 2025 requirements, not just entered into OSS RBA
- Revisit capital and risk classification calculations whenever a supporting activity is reclassified as primary, since the investment threshold attached to that activity changes the moment its status does
None of these steps are unusual individually. What causes the most damage is treating the primary and supporting distinction as a formality decided once at incorporation, when it is actually a classification that needs to be revisited every time a business line’s actual commercial weight changes.
XPND’s regulatory compliance team works with PT PMA clients to map business activities against the correct primary and supporting classification from the outset, and to catch the moment a supporting activity has quietly become a commercial one before a license application or an audit catches it first. A KBLI code is not just a label attached to a business activity. It is a legal claim about what that activity is actually allowed to do, and the gap between the two only becomes expensive once someone outside the company is the one who notices it.