Choosing KBLI Business Codes for IT Consultants

Choose Indonesian KBLI business codes from the services you actually sell, then check the descriptions and requirements in OSS, Indonesia's Online Single Submission licensing system. Computer consulting, custom programming, data services, and equipment trading may need different codes. The lists below are research candidates, not a compulsory package for every consultancy or a guarantee of licensing and tender eligibility.

KBLI is the government's official list of business activity codes. Every Indonesian company picks a set of them for its deed of establishment, and that set follows the company everywhere: into the business registration number, into the online licensing system, into every tender document that asks what your company is allowed to do.

Why does the code list decide more than what the notary types?

Each activity has a risk profile that affects its licensing requirements. Check the activity scope as well as the code.

Government Regulation 28/2025 on risk-based business licensing sorts every code into four tiers. Low risk needs only a NIB — the business registration number that acts as your company's ID card. Medium-low risk needs a NIB plus a Standard Certificate you issue yourself by declaring that you meet the requirements. Medium-high risk needs a NIB plus a Standard Certificate that a ministry actually verifies before it becomes valid, which means waiting.

So two consultancies with identical offices and identical clients can sit in very different queues, purely because one of them put a heavier code in its deed.

The list also decides what you may bid on. Procurement packages name the KBLI codes a bidder must hold. A missing required code can fail the administrative check; follow the package's clarification and review procedures. The e-katalog system goes further and checks the codes on your registration against the product category you are applying to sell.

Codes are cheap while the deed is being drafted and expensive afterward. Adding one later means amending the deed at a notary, then re-registering the activity in the licensing system. Adding one now costs a line of text. That asymmetry is the whole reason to think about this before signing rather than after losing a bid.

What changed in KBLI 2025, and does it affect you?

The classification was rewritten. Regulation of Statistics Indonesia (BPS) No. 7/2025 brought KBLI 2025 into force on 18 December 2025, replacing KBLI 2020 and realigning the whole structure to ISIC Rev. 5 — the United Nations industry classification standard published in 2024 that most countries use as their base. The list shrank from 1,789 five-digit codes to 1,559, a net loss of 230.

Three dates matter for anyone registering now:

• 27 April 2026 — BPS published the official 2020-to-2025 conversion table and the government confirmed that KBLI 2025 does not require anyone to obtain new permits.
• 13–14 June 2026 — the OSS licensing system went down for maintenance to migrate.
• 15 June 2026 — OSS reopened running on KBLI 2025, converting existing registrations automatically where the scope of activity did not change.

For a new company, none of that is a burden. It is a trap only in one specific place: the notary's template. Plenty of drafts still carry KBLI 2020 numbering, and the conversion is not always one-to-one. Several 2020 codes were split into two or three 2025 codes, and a careless conversion carries over one fragment while dropping the rest — leaving you licensed for a slice of what you meant to do. Check every final number against the official migration table before the deed is signed. Resolve any one-to-many mappings with the notary before signing.

Which four candidate codes fit your services?

62209 may fit computer-consulting services. Confirm the activity scope, business scale, and requirements shown in OSS. A code number alone does not establish a universal risk grade, staffing requirement, or processing deadline. Save the result for the notary and licensing adviser.

62199 replaced 62019 in the renumbering, and that pair is worth memorising — it is the one you will keep seeing in tender documents. More on that below.

Which codes match your actual service lines?

Add these only where the service is real. Check the scope and obligations of every additional code; do not choose by its title alone.

The distinction inside 63102 catches people out. Deploying an application into a client's AWS account is consulting work under 62209 and 62199. Operating infrastructure that you own and bill for is a different business, with the verification queue that goes with it.

Niche codes exist for blockchain applications (62193), AI components built for other developers (62194), video games (62110, 58211, 58219), and VR/AR (62192). Note that an AI application built to a client's order is ordinary custom programming under 62199 — 62194 is for selling AI libraries and components as such.

Why take the trading codes if you only sell services?

Because sooner or later a client asks you to supply the hardware, and a consultancy holding only service codes has to refuse or subcontract.

If equipment procurement or trading is part of the services, research these candidate codes and check the requirements for the selected activity:

• 46511 — wholesale of computers and peripherals. The general B2B procurement umbrella.
• 46512 — wholesale of software. Read the 2025 scope carefully: it narrowed to software on physical media with a perpetual licence. Digital licences and subscriptions now belong to 58290.
• 47401 / 47403 — the retail counterparts, for computers and software. Government software packages often name one of these as an acceptable alternative to a programming code.
• 73100 — advertising, if you run digital marketing campaigns for clients.
• 72102 — engineering and technology R&D, if you do prototyping. Check the activity scope and risk profile in OSS rather than inferring permit requirements from the term R&D.

There is a practical wrinkle in public procurement worth knowing before you read your first tender document. Many packages still specify KBLI 2020 codes — you will see requirements written as "NIB with KBLI 62019 or 46512/47413". The official 2025 equivalents are 62199 and 47403 respectively, both already in the lists above, but a registration issued under the new numbering does not automatically satisfy every package requirement. Ask the procurement team to confirm the accepted equivalents in writing. Bring the conversion table to the clarification meeting rather than arguing from memory.

Government IT work may use direct procurement, e-katalog, or tender procedures according to the package. E-katalog checks the codes on your registration against the product category automatically when you apply as a supplier, which makes holding the right trading code a precondition rather than a formality.

What does an IoT line add?

The anchor is 62204: designing integrated systems to order, including hardware modification such as sensors and microcontrollers. The software, firmware, and dashboards around it are already covered by 62199. What you add beyond that depends on how you make money from the devices:

For own-brand equipment assembled by a contractor, check whether the BPS description classifies your role as manufacturing. Code 26513 is a candidate to research for measuring equipment; the product name and who solders it are not enough to determine the final code.

Check installation requirements. Codes 43213 and 43212 may be relevant to building electronics or telecommunications installation. Installation work can bring construction-sector requirements. Do not assume an IT-service code substitutes for those permissions; check the work package with OSS and the competent authority before starting.

Which codes look right but are traps?

Three of them, and all three are tempting because the titles read like consulting work.

62202 (digital identity) and 62203 (electronic certificates). Distinguish operating identity systems or issuing certificates from consulting about them. Check activity boundaries, eligible business scale, and the OSS requirements; do not select a code merely because the work touches digital identity.

61201 (telecommunications service resale). Research this if you actually resell telecommunications services. Confirm the role, provider relationship, and licensing requirements. Connecting a client’s network alone does not automatically require this code.

Check electronic-commerce requirements. Selling software or SaaS through your own platform needs an assessment of the business role and transaction model. A payment button alone does not establish a universal SIUPMSE requirement. Check the applicable OSS activity and trade rules before accepting transactions.

The same principle applies to intellectual property in your contracts: what you declare you do should match what you actually deliver and what you actually own. Mismatches between the registered scope, the contract, and the delivered work are the ones that surface during an audit or a dispute, which is the theme of who owns the code when a freelancer builds it. The equivalent problem on the supplier side — vendor SDKs shipped with no licence text at all — shows up in hardware integration contracts.

What happens after the deed is signed?

Use a checklist rather than assuming one schedule applies to every business:

1. Match the deed, NIB, and OSS activity descriptions. Check code conversion as well as the services actually offered.
2. Record the permits required for each activity. Prepare Standard Certificates or other permissions where required; NIB alone is not always sufficient.
3. Prepare the evidence the activity requires. This may include technical staffing, business processes, and equipment documentation.
4. Confirm capital and beneficial-owner filings with the notary. Agree on the documents, responsible person, and deadlines applicable to your entity.
5. Check LKPM reporting. Frequency and exemptions depend on business scale and status; do not assume every consultancy must file quarterly.

The list is a promise, not a formality

The code list should describe the services the company plans to provide. Missing codes may limit activities; irrelevant additions can create obligations the business does not need.

Start from the services you plan to sell and the candidate codes that fit. Check BPS descriptions and the actual OSS requirements, then agree on the codes and follow-up permits with your notary before signing.

This article is a research guide based on KBLI 2025 and the current OSS risk-based licensing profiles. Licensing requirements change, and profiles for individual codes are adjusted from time to time — verify each final code in OSS and against the BPS migration table before signing anything.