Search KBLI by Business Activity Name: Find Candidate Codes and Check Their Scope

Write the activity before choosing the search terms

Create a short activity statement with a verb, an output, the customer and the delivery arrangement. Explain whether the Indonesian entity makes goods, resells them, supplies a service, licenses an asset or facilitates another party’s transaction. This is a classification exercise; a company name and a marketing slogan rarely describe those distinctions precisely enough.

Use a separate line for each commercially distinct activity. A business developing software for clients and selling its own subscription product should describe both revenue streams before deciding whether the same classification covers them. Do not assume that a code associated with “online” covers every product sold through a website.

Search the activity you perform, not the category you hope to qualify for. Identify who contracts with customers, who owns the stock or intellectual property, and what is delivered. If those facts are still undecided, mark the search as preliminary. Choosing an appealing code cannot resolve an unfinished business model.

• Replace a broad industry word with the actual action: grow, manufacture, wholesale, repair or advise.
• Add the object of the action and the customer type where they change the scope.
• Record whether the activity is performed for the company itself or for third parties.
• Keep possible future activities outside the initial shortlist unless they are part of a defined launch plan.

Run the official search and save the candidate evidence

Open the OSS activity-name and code search . The page accepts an activity name or KBLI code and provides conversion-type filters. Search the core activity term first, then a narrower output term. If an English expression gives weak results, use the relevant Indonesian activity wording and keep a note of what it means in your business.

Capture each plausible result in a candidate register. Store the code as text so leading zeroes survive. Keep the displayed title, classification version, source link, retrieval date and the reason it might fit. Do not enter a code into the deed instruction merely because it is the first search result.

1. Search the principal verb or output and collect a small set of plausible candidates.
2. Open a candidate rather than relying on its abbreviated result label.
3. Read its description, inclusions, exclusions and displayed scopes where available.
4. Compare the actual planned activity against those boundaries.
5. Record a fit decision and the evidence still needed before filing.

A reproducible search note might say “searched the Indonesian term for the production activity; excluded candidates concerned only with resale.” That note explains the selection logic without copying a directory. If nothing fits, revise the factual description or obtain classification clarification; do not force a match merely to finish a portal screen.

Compare code scope with the proposed contract

Use the following worksheet to make the scope comparison explicit. The tests are editorial decision aids, not an official scoring system. A single material exclusion is more important than several matching keywords, so do not add up ticks and interpret a high total as approval.

For a verified navigation example, the official conversion record for 01111 identifies Pertanian Jagung, or maize farming, in both versions. That demonstrates how to inspect a specific code relationship. It does not establish the right code for maize trading, processing, freight or every business that mentions maize.

The contrast is useful: a shared product word can connect different economic activities. Product similarity does not establish activity equivalence . Record why a farming candidate was rejected if the entity will instead buy and resell crops. This produces a usable audit trail without asserting an unverified replacement code.

Check what changed between KBLI versions

The OSS conversion guide distinguishes unchanged and changed one-to-one relationships, splits, mergers and restructuring. It also warns that a conversion reference is not a legal decision. Treat conversion as a relationship to investigate, rather than a command to select every new code displayed.

For an unchanged number, compare the wording and detailed scope. For a split, identify which new activity descriptions reflect the actual business. For a merger, verify that the consolidated description still covers the existing activity. For restructuring, retain the before-and-after rationale so the team can explain which activities were carried forward.

Maintain two separate columns: the classification currently shown in the existing records and the candidate classification supported by the present business description. Do not erase the old version from the working file. Losing that history makes it harder to explain why an existing licence and a new instruction display different codes.

If the business itself is changing, distinguish the change from a purely classificatory conversion. The review of activity additions and OSS updates becomes relevant when the proposed scope extends beyond the existing company purpose or permissions. Document the proposed activity first, then identify the corporate and licensing records affected.

Keep classification separate from permission to operate

A candidate that describes the activity correctly still needs the applicable ownership, investment, location and licensing assessment. These are separate questions. A code search cannot by itself prove that a foreign shareholder may own a particular percentage, that a virtual address is acceptable or that all operating conditions are satisfied.

When preparing Indonesia company registration requirements , carry the approved activity description into the entity instruction and the subsequent licensing review. The same commercial facts should inform both, but a completed incorporation record does not replace the activity-specific permission analysis.

Use a release sheet with separate conclusions: classification fit; foreign investment access; proposed premises; and the identified licensing workstream. Record the source and reviewer for each conclusion. If the person selecting the code has only completed the first task, label the other tasks as open rather than presenting a green “KBLI approved” badge.

Where the search interface or a detail page cannot be loaded, retain the source URL and mark the affected field as unverified. Resume from that evidence gap. A cached screenshot may explain an earlier instruction, but it should not be treated as proof of what the current system now displays.

Release a KBLI shortlist with a reason for every selection

Choose a code only when its current description and scope match the documented activity, and when separate permission questions have been allocated and resolved to the degree needed for the next filing. Keep rejected alternatives and their reasons in the working register; they explain why a nearby label was not selected.

The deliverable is a concise, dated instruction: activity statement, selected code and version, scope evidence, reason for fit, unresolved conditions and the person approving release. A shortlist becomes a filing instruction only after its material boundaries are checked. Escalate a genuine scope conflict rather than adding unrelated codes to conceal it.