How to Choose KBLI Codes for PT PMA Setup Guide

The right KBLI is the code whose official scope matches what the PT PMA will actually sell, deliver, locate, staff, invoice, and license—not the broadest label in a search result.

Choose KBLI codes for a PT PMA by writing an activity-and-revenue map first, then matching each distinct activity to the current official KBLI description and scope. For every candidate code, test foreign-investment access, reserved or partnership conditions, risk level, location and spatial requirements, sector license and PB UMKU dependencies, investment and capital implications, staffing, tax and customs consequences, and the evidence the company can produce. Only then approve the code set for the deed and OSS application.

Use the Indonesia KBLI directory to identify possible codes, but approve none until the activity map, foreign-investment conditions, risk level, location, licensing, capital, tax, customs, staffing, and evidence tests are complete. Record why each code is included or rejected, identify any activity that must be separated or conditioned, and obtain current sector-specific advice when the official description does not clearly match the planned revenue and operating model.

In this article

• Write the PT PMA activity map before searching KBLI
• Match each activity to KBLI 2025 scope
• Test foreign-investment and license effects by KBLI
• Approve a defensible KBLI set for deed and OSS
• Official references and review basis
• The approval test for a PT PMA KBLI set

Key takeaways

• Describe activities in operational verbs, customers, deliverables, locations, channels, and revenue flows before searching codes.
• Use the current OSS KBLI 2025 information and preserve the exact description and scope checked.
• Test ownership, risk, sector, premises, PB UMKU, capital, tax, customs, and staffing consequences by code and project.
• Reject decorative codes that the company cannot support with contracts, people, premises, systems, and permits.

Write the PT PMA activity map before searching KBLI

Interview commercial, operations, product, finance, and legal owners and describe each activity without code language. Record what is sold, who the customer is, whether the company manufactures, imports, distributes, hosts, consults, licenses intellectual property, operates a platform, holds inventory, employs regulated professionals, or receives commission, where the work occurs, who performs it, what the customer receives, how the company invoices, and what happens during the first twelve months. Separate current launch activities from later options.

KBLI is a classification system, while OSS uses the selected business activity with location and other data to determine the licensing route. The official OSS KBLI page now identifies KBLI 2025. That is why an old adviser checklist, a competitor's NIB, or a KBLI 2020 label should not be copied without checking the current classification and transition position. Preserve the official page or record checked and the date.

Turn the interview into an activity matrix with one row per revenue or regulated activity. Add product or service, customer, contract promise, delivery evidence, location, facility, staff or professional role, equipment, supplier and subcontractor, payment flow, tax invoice, import or export, data or platform element, expected start date, and owner. If two teams describe the activity differently, resolve the commercial facts before debating codes. The code decision cannot repair an unclear business model.

Match each activity to KBLI 2025 scope

Search the current official KBLI material using the operational nouns and verbs from the activity map. Read the full description, inclusions, exclusions, scope options, and any linked licensing information; do not select from the code title alone. Where one old code maps to several new codes or several old codes map to one, document why the chosen KBLI 2025 scope fits the real activity. Keep rejected candidates and reasons so a later reviewer can see that the answer was deliberate.

OSS has issued a current KBLI 2020-to-2025 conversion guide . It shows that conversion can be one-to-one, one-to-many, or many-to-one and tells users to choose the correct activity, scope, and location before continuing to NIB issuance. Treat conversion as a substantive mapping exercise, not a mechanical rename.

Build a decision note for every selected code: current code and label, full scope excerpt paraphrased in the company's words, matched activity, excluded activities, customer and deliverable, location, launch date, source URL, access date, reviewer, and uncertainty. If the planned service bundles several activities, decide whether the company needs multiple codes, a different lead code, separate contracts, subcontracting, or a narrower launch. Do not add a broad code merely to look flexible.

Test foreign-investment and license effects by KBLI

For every candidate code, run a separate access and licensing test. Check whether the activity is open to foreign investment, subject to a foreign ownership limit, reserved or allocated to cooperatives or UMKM, requires partnership, is closed, or is affected by a sector-specific rule. Then identify the OSS risk level, NIB role, standard certificate or license, verification, PB UMKU, technical approval, professional requirement, product approval, environmental and spatial condition, and competent authority.

The investment-field framework is contained in Presidential Regulation 10 of 2021 as amended by Presidential Regulation 49 of 2021. The official BPK record for the amendment explains that commercial fields are generally open except closed or central-government-only activities, while schedules and conditions still matter. PP 28 of 2025 now governs risk-based licensing. These high-level rules do not replace a current code, sector, location, shareholder, and project analysis.

Create a license path card for each code and location. List the risk result, NIB, certificate or license, verification, PB UMKU, sector and local authority, spatial and environmental prerequisites, premises type, documents, inspection or technical evidence, dependency, owner, and earliest lawful operating gate. Compare the result with the foreign-ownership verification guide . Stop the setup if the shareholder plan, premises, or launch date assumes a permission the current activity cannot obtain.

Approve a defensible KBLI set for deed and OSS

Before incorporation or amendment, reconcile the proposed code set with the deed's purposes, shareholder and ownership analysis, OSS project plan, location, investment and capital schedule, operating budget, staffing, contracts, invoice descriptions, tax and customs registrations, bank KYC narrative, website claims, and implementation calendar. One code may affect several downstream records, and a mismatch discovered after contracts are signed can require more than a simple portal edit.

PP 28 of 2025 defines risk-based business licensing and requires business operators to hold the permissions applicable to their activities. Review the current official risk-based licensing record . OSS acceptance of a code or issuance of an NIB should not be represented as proof that every certificate, verification, sector approval, site condition, or operating requirement is complete.

Hold a board or authorized management approval with the activity map, selected and rejected codes, ownership analysis, license paths, location results, investment and staffing effects, adviser assumptions, unresolved items, and change triggers. Assign a pre-contract check so sales and operations cannot launch an unapproved activity. If a mismatch is already present, use the PT PMA KBLI correction sequence rather than disguising the activity under an adjacent code.

Official references and review basis

The following primary sources were checked on August 1, 2026. They establish the regulatory or service boundary used in this article; bank, tax office, OSS, AHU, and immigration decisions can still depend on the current record and the facts of a particular application.

• OSS — KBLI 2025 — Primary current classification page for KBLI 2025.
• OSS — KBLI 2020-to-2025 conversion guide — Official guide showing one-to-one, one-to-many and many-to-one conversion workflows.
• BPK — Presidential Regulation 49 of 2021 — Official record amending the investment business-field framework.
• BPK — PP 28 of 2025 — Current risk-based licensing framework.
• BPK — Permeninves/BKPM 5 of 2025 — Current OSS licensing procedure and supervision framework.

The approval test for a PT PMA KBLI set

Approve only codes that match a documented launch activity, use the current KBLI version, pass foreign-investment and sector checks, produce a feasible risk-based license path, fit the real location, and reconcile with the deed, contracts, staffing, investment plan, tax, customs, banking, and operating evidence. More codes do not create more legal flexibility when the underlying activities are unsupported.

Keep a rejected-code record and a future-activity gate. Escalate ambiguous scope, foreign ownership, UMKM reservation, sector licensing, location, or capital effects to qualified Indonesian advisers before filing. Use the Indonesia company registration framework to sequence the approved code set with the rest of setup.

Related insights

• Indonesia KBLI directory
• Foreign ownership check by KBLI
• PT PMA KBLI correction sequence
• Capital requirements by KBLI