Guide to choosing the right KBLI 2025 safely

Starting checklist

1. List the real operating activities, not just the company label.
2. Match them to the closest official KBLI description.
3. Check whether the code triggers a specific OSS risk path.

Validation before filing

• Compare similar codes.
• Check for additional sector licences.
• Reconfirm in OSS before submitting the NIB.

Risks of choosing the wrong code

• licensing mismatch
• tax or BPJS mismatch
• post-filing company data corrections

Why KBLI selection must start from the real operating activity

The most common mistake is choosing a code from the brand name, product label, or marketing language alone. KBLI is built around the underlying economic activity, not around the way the business is marketed. Two businesses that both call themselves a platform, studio, agency, or distributor may still belong to different codes if their operating model and revenue logic differ.

A safer review sequence

Start with the activities that actually generate revenue. Separate the core activity from the supporting ones and read the relevant section, division, and group before selecting the 5-digit code. That sequence forces the team to understand the classification context instead of choosing the first code that sounds similar.

Validation points after a code is selected

Once a candidate KBLI has been identified, re-check the OSS risk path, sector-licensing needs, payroll and BPJS implications, and the impact on tax records. If the structure involves foreign investors, add a foreign-ownership check before filing. A code that looks descriptively close is not always the safest one from a regulatory perspective.

How to use this page with the other layers

Open the section and division pages first, then move to the single-code page. After that, compare the result with the OSS layer, the linked KLU entry, the BPJS calculator, and the operating-region pages. The goal is not only to choose a code but to reduce mismatch risk across company records and licensing workflows.

Field checklist before the code is treated as final

Before a code is treated as final, the team should write down the activities it expects to carry out over the next twelve months. Separate revenue-generating work, supporting work, and occasional side activities. This matters because many companies select one code from the pitch deck or the legal-entity label and only later discover that the operating model is broader or narrower than the chosen description.

Examples of business models that often get misclassified

Software businesses often jump to a general programming code even though the real model also includes consulting, infrastructure support, systems integration, or data-service work. Restaurant businesses also look simple on paper but can move across restaurant service, food production, retail, cloud-kitchen operations, or ingredient distribution. If the operating model is not broken down first, the KBLI choice usually becomes soft as well.

Questions that should be answered before filing

• Does the main activity generate revenue from services, goods, licensing, or commissions?
• Does the business operate a physical site, warehouse, fleet, kitchen, studio, or fulfilment point?
• Does the model trigger standard certificates, local permits, or additional sector approvals?
• Does the structure involve foreign investors, import-export flows, or a PT PMA review that requires tighter screening?

How to read two similar candidates

When two codes sound close, do not start from the number. Start from the verb in the official description. Is the business producing, selling, managing, renting, developing, or distributing? In many cases, that seemingly small wording difference is exactly what separates the correct code from one that only sounds comfortable.

The impact of the wrong code on company records

A weak KBLI choice usually does not stop at OSS. It can affect the activity description in the deed, the NIB path, sector licensing, payroll controls, and even the way the company explains itself to investors or banks. That is why KBLI selection should be treated as business-structure design rather than as a minor form-filling step.

A more defensible internal workflow

Legal, finance, operations, and the founding team should review the code choice together before filing. One side explains the revenue model, another explains the operating process, and the candidate codes are then tested against the official descriptions. This seems slower up front, but it is materially cheaper than correcting the structure after the NIB or the company documents are already in circulation.

How this page is used in practice

In early reviews for digital-service businesses, we usually start from the section and division pages, then narrow the shortlist to three to five candidate KBLI codes before moving to a final code. Once that shortlist exists, we test the OSS path, the linked KLU layer, payroll exposure, and, where relevant, the PT PMA logic. That process is specifically designed to avoid choosing a code simply because the label feels familiar.

Sources

This portal is informational. Confirm the final obligation and competent authority before filing, licensing, payroll, tax, or investment decisions. Read methodology.