Choosing a KBLI code is not a naming exercise. It is a licensing design decision that connects what an Indonesian company actually does with its OSS profile, risk classification, business licensing, foreign-ownership review, location requirements, and sector-specific approvals. A code that sounds broadly relevant can still be wrong if its detailed description, exclusions, business scale, or regulated scope does not match the operating model.
For foreign investors, the practical goal is to select a defensible set of KBLI 2025 activities before incorporation and OSS filing, while leaving enough room for the company’s genuine near-term operations. This guide explains how to review KBLI Indonesia classifications systematically and where specialist verification is essential.
Key Takeaways
- KBLI 2025 is Indonesia’s current standard classification of economic activities and is now reflected in the OSS licensing environment.
- Start with the company’s actual revenue-generating activities, operating process, customers, products, facilities, and transaction flow, not with a preferred code title.
- Read the full description, included activities, exclusions, scope options, risk information, and supporting-license requirements shown for each candidate code.
- A KBLI conversion from 2020 to 2025 may be unchanged, changed, split, merged, or restructured. A conversion result is a starting point, not proof that the new code fits.
- Foreign ownership, investment structure, location, product regulation, environmental obligations, workforce, import activity, and sector approvals may change the practical licensing route.
- Record why each code was selected and validate the complete code combination before incorporation, amendment, or OSS submission.
What Is KBLI 2025?
KBLI stands for Klasifikasi Baku Lapangan Usaha Indonesia, Indonesia’s standard classification of economic activities. The Central Statistics Agency (BPS) describes KBLI as a standard used to group economic activities according to shared characteristics. BPS Regulation No. 7 of 2025 established KBLI 2025 and replaced the previous 2020 classification.
The classification serves a statistical purpose, but businesses encounter it operationally because OSS uses KBLI activities to connect a project with risk-based business licensing. The selected code helps determine the regulatory path displayed in the system, including the relevant scope, risk level, business scale, basic requirements, business licence, standards, and supporting licences that may apply.
A five-digit KBLI code describes a specific class of economic activity. The title is useful for discovery, but the description and exclusions are more important. Two activities that sound commercially similar may fall into different codes because one concerns manufacturing and the other wholesale, retail, software operation, professional services, repair, or intermediary activity.
Businesses should therefore treat the KBLI as a structured description of how the company earns revenue and performs its work. IndoGateway’s NIB and OSS business licensing service can support the classification and filing workstream when a project involves multiple activities or regulated dependencies.
Why KBLI Selection Matters to a Foreign Business
A selected KBLI code can influence much more than the wording in a company profile. In a foreign-investment project, it can affect whether the planned activity is consistent with the company’s constitutional documents, whether the activity is available to foreign investment, how OSS classifies the risk, which authority or sector is involved, and what evidence may be required before commercial operations begin.
The effect is project-specific. A company that imports equipment, assembles products, operates a digital platform, stores inventory, provides after-sales service, and sells to Indonesian customers may need to analyze several distinct activity streams. Using one broad commercial description may conceal licensing obligations; adding every remotely related code may create unnecessary compliance commitments and confuse the company’s primary purpose.
| Decision area | Question to test | Why it matters |
|---|---|---|
| Core activity | What product or service creates revenue? | Identifies the activity that should anchor the classification. |
| Operating process | Does the company manufacture, trade, distribute, operate, advise, repair, or intermediate? | Commercially related functions can belong to different KBLI classes. |
| Customer and channel | Is the sale wholesale, retail, online, business-to-business, or platform-mediated? | The route to market may change the relevant classification or supporting obligations. |
| Foreign investment | Is the activity open to the proposed foreign ownership and structure? | Ownership treatment must be checked against the specific activity and sector. |
| Risk and licences | What risk level, standards, permits, or PB-UMKU appear for the precise scope? | An NIB may not by itself establish operating readiness for every activity. |
| Site and product | Does the model involve land, construction, environment, imports, or regulated goods? | Parallel approval workstreams may be necessary. |
Seven Checks to Complete Before Selecting a KBLI Activity
1. Describe the Real Activity in Operational Language
Begin without using regulatory labels. Write a plain-language description of what the Indonesian entity will do from purchase or production through delivery and payment. Identify what it buys, makes, stores, imports, markets, sells, installs, maintains, licenses, or operates. Note whether it owns goods, acts as an agent, facilitates third-party transactions, or provides professional expertise.
This exercise prevents the team from selecting a code simply because its title resembles a marketing description. It also exposes supporting functions that may be incidental to the main activity rather than separate businesses. The distinction matters because not every internal function needs its own KBLI code, while a separately monetized service may need independent treatment.
2. Read the Full Description and Exclusions
Search the official OSS KBLI directory by activity terms and candidate codes. Read the complete description rather than stopping at the title. Pay particular attention to examples, included activities, exclusions, cross-references, and the position of the code within the broader category and group.
An exclusion can be decisive. For example, a code may cover operation of a service but exclude software development, product manufacturing, financial activity, or transportation. When a proposed business combines several roles, compare each role with the wording of each code instead of assuming that one label covers the entire value chain.
3. Select the Correct Scope Within the Code
The OSS detail page may show more than one scope under a single KBLI code. Scopes can differ by sector, business model, product, scale, or regulated function. They may carry different risk classifications or obligations. The code alone is therefore not always the end of the classification analysis.
Record the intended scope alongside the code. If the team cannot identify which scope describes the project, treat that uncertainty as a review issue before filing. A technically correct code paired with the wrong scope can still produce an unsuitable licensing path.
4. Check the Risk-Based Licensing Result
Indonesia’s risk-based licensing system uses the characteristics of the business activity to determine the applicable licensing route. The OSS portal describes four risk levels, while Government Regulation No. 28 of 2025 provides the current overarching framework for risk-based business licensing.
Do not infer a risk level from the general nature of an industry. Review the result for the exact KBLI, scope, scale, and project characteristics. The output may distinguish between an NIB, standard certification, a licence, or other fulfilment and verification steps. Supporting business licences, known as PB-UMKU, can also appear for particular operational needs. IndoGateway’s guide to Indonesia’s four risk-based licensing levels provides additional context, but the current OSS result should be checked for the project.
5. Review Foreign-Ownership and Investment Conditions
Foreign ownership is not determined by the English description of a business alone. It should be reviewed against the exact activity, relevant investment rules, sector regulations, and the proposed shareholder structure. Some activities may be open, reserved, restricted, subject to conditions, or governed through a sector-specific framework.
Complete this review before finalizing a PT PMA’s business purposes or assuming that a code can be added later without structural consequences. The analysis should also consider whether the activity belongs in the foreign-owned operating company, another licensed Indonesian entity, or a contractual relationship with a qualified local provider. See IndoGateway’s overview of foreign ownership review in Indonesia for the questions that commonly require verification.
6. Identify Connected Approvals and Operational Dependencies
A KBLI activity does not replace product, facility, import, workforce, tax, environmental, building, or sector compliance. A trading activity may still require importer arrangements and product approvals. Manufacturing may involve industrial, environmental, spatial, building, machinery, and workforce workstreams. A digital business may face electronic-system or sector rules in addition to OSS licensing.
Build a dependency map for every candidate code. List the project location, property status, equipment, products, raw materials, imports, foreign personnel, customer channel, and technical standards. Then identify which approvals must be obtained before setup, construction, import, production, distribution, or sale. The Indonesia Licence Checker can help frame the initial review, while regulated projects should be verified with the competent authorities and qualified advisers.
7. Test the Complete Combination of Codes
Many businesses legitimately perform more than one economic activity, but a list of individually plausible codes is not automatically coherent. Review the portfolio as a whole. Confirm which activity is primary, which activities generate separate revenue, which are supporting functions, and whether the company can meet the licensing and investment requirements associated with each selected code.
The combination should align with the deed, OSS project data, facilities, commercial contracts, accounting, invoicing, reporting, and actual operations. Avoid adding speculative codes merely to preserve theoretical flexibility. A focused, documented scope is generally easier to govern than a large list that nobody has evaluated operationally.
How to Handle the Transition from KBLI 2020 to KBLI 2025
Existing businesses should not assume that an old code maps automatically to an identical new activity. The official OSS conversion guide identifies five conversion patterns: unchanged one-to-one, changed one-to-one, split into several codes, merged into one code, and restructured across several codes.
Even an unchanged number may contain adjusted wording in its title or description. A split may require the business to choose among narrower codes based on what it actually does. A merger can bring activities together under a new description. A restructured mapping requires a fresh comparison rather than mechanical replacement.
- Inventory the company’s existing KBLI codes, NIB, licences, projects, and outstanding OSS applications.
- Use the official OSS conversion tool to identify the relevant 2025 candidates and conversion type.
- Read every candidate’s current description, exclusions, scope, risk data, and obligations.
- Compare the candidates with current operations, not only the activities described when the company was established.
- Check whether licences, standards, spatial data, products, facilities, and sector approvals remain aligned.
- Plan any corporate-document and OSS amendments in the correct sequence, preserving records of the basis for the change.
The OSS guide expressly cautions that a conversion result does not automatically establish that every new code fits a business. This is particularly important for projects already in process, legacy licences, and activities whose scope changed. Review transition cases individually before editing live OSS data.
A Practical KBLI Selection Workflow
- Build an activity inventory. Interview commercial, operations, product, supply-chain, finance, and legal stakeholders. Capture present and near-term activities separately.
- Draw the transaction flow. Show who owns the product, signs the customer contract, issues the invoice, receives payment, operates the platform, holds inventory, and bears technical responsibility.
- Create a candidate list. Search official KBLI descriptions using multiple Indonesian and English activity terms. Include alternative codes for comparison.
- Eliminate poor matches. Use descriptions, exclusions, and hierarchy to remove codes that describe a different function, channel, product, or industry.
- Review regulatory effects. For each remaining code and scope, check risk, licence output, standards, PB-UMKU, foreign-investment treatment, sector authority, and location or product dependencies.
- Reconcile the corporate documents. Ensure the proposed activities align with the deed and corporate purpose. Coordinate amendments before relying on a new OSS profile.
- Approve and document. Prepare a short classification memo recording facts, selected codes, alternatives rejected, dependencies, sources, and open conditions.
- Monitor change. Revisit the classification before launching a new product, channel, facility, revenue line, import model, acquisition, or material operational change.
This workflow gives management an auditable basis for its decision. It also makes later amendments easier because the company can distinguish a genuine change in activity from a correction to old data.
Common KBLI Selection Mistakes
- Choosing by title alone: the detailed description or exclusion may contradict the initial impression.
- Using a code because a competitor uses it: another company may have a different product, transaction role, ownership, scale, site, or legacy licence.
- Confusing a business model with a channel: selling online does not necessarily replace the classification of the underlying product or service.
- Treating trading as manufacturing: owning a brand, specifying products, importing, assembling, and manufacturing are distinct factual functions.
- Ignoring scope-level differences: one code can present several regulatory scopes with different consequences.
- Assuming the NIB completes all licensing: higher-risk activities or supporting operations may require further fulfilment, verification, licences, or standards.
- Adding excessive future activities: speculative codes can create governance and compliance work without supporting an approved operating plan.
- Forgetting non-OSS workstreams: product registration, import, land, building, environment, sector, immigration, and tax requirements may sit alongside business licensing.
Questions Management Should Answer Before Filing
- What will the Indonesian entity sell, and what will appear on its invoices?
- Will it manufacture, assemble, package, import, distribute, retail, license, operate, repair, or advise?
- Will it act as principal, reseller, agent, marketplace, contractor, or service provider?
- Which activities begin immediately, and which are only future possibilities?
- Where will each activity occur, and what property, equipment, environmental, or building conditions apply?
- Are the products or services regulated by a technical or sector authority?
- Does the proposed foreign ownership fit every selected activity?
- Which OSS licences, standards, and supporting licences must be effective before revenue begins?
- Do the deed, contracts, transfer-pricing model, invoices, staffing, and reporting support the same operational story?
If the answers are inconsistent, pause the filing and resolve the operating model first. Classification quality depends on business facts; it cannot compensate for a structure that has not been agreed internally.
When Specialist Verification Is Especially Important
Obtain targeted regulatory review when the candidate activity is subject to foreign-ownership conditions, a sector regulator, product registration, import controls, professional or technical qualifications, environmental approval, spatial or construction requirements, regulated infrastructure, financial services, telecommunications, healthcare, energy, mining, construction, transport, education, food, cosmetics, medical devices, or other sensitive operations.
Verification is also appropriate when an existing company is converting legacy codes, an OSS mapping produces several plausible options, a code has multiple scopes, licences appear inconsistent with actual operations, or a proposed amendment could affect contracts, tax, incentives, reporting, or sector approvals. Government Regulation No. 28 of 2025 and Investment Ministry/BKPM Regulation No. 5 of 2025 provide the current general framework, but the correct result still depends on the facts and applicable sector rules.
Conclusion
Good KBLI selection begins with a precise operating model and ends with a documented regulatory review. The code title is only an entry point. Businesses should confirm the full KBLI 2025 description, exclusions, scope, risk-based licensing output, foreign-investment treatment, project location, product and facility requirements, and the relationship between all selected activities.
For an existing business, conversion from KBLI 2020 should be treated as a substantive review rather than an administrative rename. For a new foreign-owned company, classification should be resolved before the deed and OSS data lock the project into an avoidable amendment cycle.
Plan Your KBLI and OSS Licensing Route
IndoGateway can help foreign investors translate an operating model into a coordinated Indonesia setup and licensing plan, including KBLI review, PT PMA alignment, NIB and OSS processing, and connected product, import, location, workforce, and compliance workstreams. Contact IndoGateway to review your proposed activities before filing or amending the company’s business scope.
Frequently Asked Questions
1. What is a KBLI code in Indonesia?
A KBLI code is an official classification used to identify a particular type of economic activity in Indonesia. Businesses encounter it during company setup and OSS licensing because the selected activity connects the project with scopes, risk information, and potential licensing obligations. A five-digit code should be selected by comparing the company’s actual operating and revenue model with the full official description, inclusions, exclusions, and hierarchy. The title alone is not enough, and the appropriate code may depend on whether the company manufactures, trades, intermediates, operates, repairs, or provides services.
2. Is KBLI 2025 different from KBLI 2020?
Yes. KBLI 2025 updates the previous classification to reflect changes in economic activity, including newer and more detailed business models. The official OSS conversion framework shows that a 2020 code may remain unchanged, change one-to-one, split into several codes, merge with other codes, or be restructured. Even where the number remains the same, wording may have changed. Existing companies should therefore review the new description and scope against current operations rather than treating conversion as an automatic code substitution. Legacy licences and unfinished OSS projects may also require case-specific transition analysis.
3. How do I choose the right KBLI code for a PT PMA?
Start by documenting what the PT PMA will actually sell, how it will deliver the product or service, who owns inventory or intellectual property, who contracts with customers, and which activities create revenue. Search official KBLI 2025 descriptions for several candidate codes, then compare their descriptions, exclusions, scopes, risk outputs, and supporting obligations. Separately verify foreign-investment treatment and sector conditions for every candidate. Finally, reconcile the selected portfolio with the deed, proposed facilities, contracts, staffing, import model, and launch sequence. Specialist review is prudent where ownership or sector rules are unclear.
4. Can an Indonesian company use more than one KBLI code?
An Indonesian company can generally register more than one business activity when those activities genuinely form part of its approved business plan and satisfy the applicable requirements. However, each code should be independently justified and the combination should make operational sense. Management should distinguish primary revenue activities from incidental internal functions and speculative future plans. Every additional code may introduce risk, licensing, reporting, ownership, facility, or sector implications. For a PT PMA, the full combination should also be checked against foreign-investment rules and the company’s constitutional documents before inclusion or amendment.
5. Does selecting a KBLI code automatically give the company permission to operate?
No. Selecting a KBLI code identifies the business activity; it does not by itself complete every approval needed to operate. OSS uses activity and project data to determine a risk-based licensing route, which may involve an NIB, standard certification, a business licence, verification, or other fulfilment. Supporting licences and non-OSS approvals may also apply to products, imports, facilities, environment, construction, workforce, or a regulated sector. Operating readiness should therefore be assessed against the effective status and conditions of all relevant approvals, not merely the presence of a code on the company profile.
6. Can I rely on the OSS KBLI conversion result without further review?
No. The official OSS guidance states that conversion information helps users understand the relationship between KBLI 2020 and KBLI 2025, but it does not automatically mean every resulting code fits the business. This is particularly important when an old code splits into several new activities or several codes are restructured. Review the current description, exclusions, scope, risk, and obligations for every result, then compare them with current operations and licences. Preserve a written record of the analysis before changing company or project data, especially where legacy approvals remain active.
7. Does the KBLI code determine foreign ownership limits?
The exact business activity is a central input to foreign-ownership analysis, but the code should not be used in isolation as a definitive ownership answer. The result can depend on the activity’s scope, applicable investment framework, sector-specific rules, licensing authority, and proposed shareholder or operating structure. A broadly similar commercial activity may have different treatment when performed through another sector or regulated model. Foreign investors should verify each selected activity against current official rules before incorporation or amendment and should avoid assuming that a code used by another company produces the same ownership outcome.
8. When should a company review or change its KBLI codes?
A company should review its KBLI portfolio when it introduces a new product or service, changes its transaction role, begins manufacturing or importing, opens a different type of facility, launches a platform or sales channel, acquires another business, converts from KBLI 2020, or discovers that registered activities no longer match operations. Review should occur before the operational change so that corporate documents, OSS licensing, contracts, product approvals, location requirements, and reporting can be sequenced correctly. A change should not be filed as a standalone data edit without assessing its connected legal and regulatory effects.
