NIB and OSS Business Registration in Indonesia

What an NIB proves—and what it does not authorize

A founder receives an NIB from OSS and forwards the PDF to a prospective customer. The company exists, the number is genuine, and the first agreement is ready. That still leaves a question worth settling before services begin: is this particular business activity cleared to operate?

Nomor Induk Berusaha (NIB) is Indonesia’s business identification number, obtained through the national Online Single Submission (OSS) system. A PT PMA acquires its corporate status through the separate incorporation process recorded with the Ministry of Law’s AHU administration. OSS handles business licensing. For an activity classified as low risk, the NIB itself may provide the relevant business authorization, provided other applicable requirements are met. More demanding activities can require further approvals.

Consider a foreign-owned company planning both advisory work and guest accommodation. It has one corporate identity, yet these activities may have different licensing conditions and statuses. Approval for one does not extend to the other. The distinction applies throughout Indonesia; operating in Bali adds location-specific questions but does not create a separate Balinese NIB.

Before applying: reconcile company records and account access

The easiest OSS applications are often the ones where the incorporation record has already been reconciled. A company’s current paperwork, its AHU entry and the details an adviser intends to submit should tell the same story. A small inconsistency can block progress or produce a license that does not accurately reflect the operator.

For an existing PT PMA, six groups of information deserve attention: the registered legal name and entity type; the deed, AHU approval and recorded amendments; tax identification where applicable; directors and authorized signatories; the registered domicile alongside actual operating sites; and the activities described in the corporate documents. A change of director recorded by the notary, for example, may affect who can legitimately act for the company. An address on the deed may also be entirely different from the premises where customers will be served.

The person filing must have proper authority, whether as a director or a duly authorized representative. An agent can assist with the process, but an agent-owned email account should never become the company’s only way to receive notices, retrieve attachments or update business details. Retaining corporate access also matters long after the initial NIB is issued. The business will need to respond to additional verification requests and may later have to change its activities or locations.

Where the OSS profile differs from AHU, the correction route depends on the source of the error. Companies still incorporating a PT PMA before filing in OSS must complete that corporate process first; the licensing form cannot replace it. Changes to that record and technical synchronization failures have different official correction routes. Submitting an inaccurate workaround can turn a temporary portal problem into a lasting compliance problem.

How KBLI codes and risk levels shape the OSS requirements

KBLI is the classification that tells Indonesian licensing authorities what the company proposes to do. It is tempting to select the easiest-looking description and move on. That shortcut is especially risky when the intended services, customer contracts or premises do not match the category on the filing.

Imagine an advisory business using a rented office in Denpasar. Its licensing questions concern the actual scope of advice, the chosen activity classification, foreign-investment eligibility and its operating location. A café or short-stay accommodation operator has a different set of practical obligations because people will be eating or staying on the premises. The words “consultancy”, “café” and “villa” do not, by themselves, determine a reliable risk band. The live OSS entry and the relevant sector and operating conditions do.

Indonesia applies four levels: low, medium-low, medium-high and high risk. These are regulatory classifications, not judgments about commercial success. The classification determines whether an NIB is sufficient for business licensing or whether the activity also needs a declaration-based Standard Certificate, a verified certificate or a separate license. A PT PMA with several activities may therefore have several distinct licensing outcomes attached to the same business identity. This is why an activity-by-activity review is more informative than the NIB cover page.

KBLI 2025 is now available in the official OSS directory. For an older project, choosing a KBLI 2025 activity code also means understanding the official conversion rules. That is not a compulsory relicensing exercise for every existing operator. In an April 2026 clarification, Statistics Indonesia and the responsible ministries stated that a code conversion without a substantive change of business does not, by itself, require new licenses. A real change to the objects or scope of a business is different and may require AHU and OSS amendments. Foreign-ownership restrictions also remain a separate test: adding a KBLI code cannot override them.

Applying for an NIB through the OSS portal

The OSS workflow is easier to understand as licensing for actual business activities and sites. It is not simply a form that produces a registration number. The company needs lawful access to its account, a consistent corporate record and a clear description of what it intends to operate. An existing NIB usually calls for the relevant amendment or additional activity procedure, not an unnecessary second identity for the same company.

An authorized applicant signs in through the official portal and selects the route appropriate to the entity and application. For a PT PMA, the corporate profile should correspond with its current AHU record. The filing then moves to activity details: the correct KBLI classification, each operating location and the project information OSS requires. A head-office address may be suitable for administration but cannot simply stand in for a kitchen, guest property or warehouse. The location entered should describe the operation that will actually take place.

OSS applies the relevant basic-requirement checks and risk-based licensing conditions. Depending on the activity and site, this may involve spatial conformity, environmental requirements, building documentation, declarations or verification by a competent authority. The application route differs between risk bands and business circumstances. Older projects undergoing transition can also follow a route that looks different from a fresh application, so a screenshot from another operator is an unreliable guide to the current filing.

A final review should cover more than spelling and registration numbers. The declaration needs to describe the real operation and the commitments the business can genuinely meet. If a supporting condition has not been fulfilled, checking a box does not cure that deficiency. A business planning several activities should inspect the resulting permissions separately, since their statuses can diverge even when they were entered during the same working session.

Once OSS has processed the submission, retain the NIB, the activity-level outputs, the application reference and date, any Standard Certificates, statements made and outstanding approval requirements. Some files will show a completed authorization while others may identify further verification or an unissued license. Those differences matter when a potential customer asks whether work can start. Portal labels and screen sequences change; the official guides for low/medium-low and medium-high/high risk are better references for the current interface than a fixed set of button names published years earlier.

When an NIB is enough—and when a license still needs approval

An issued NIB can mean different things for different activities. For low-risk business licensing, it commonly serves as the operative authorization, subject to the requirements that still apply to the location and service. Medium-low risk adds a Standard Certificate based on the operator’s declaration that the relevant standards will be met. Neither category should be treated as an exemption from continuing compliance.

Medium-high risk introduces a distinction founders sometimes miss. OSS may issue an unverified Standard Certificate, providing a basis for preparatory activity. Commercial operations require verification of the relevant standards by the competent authority. For high-risk activities, the business needs an issued license, known as an Izin, and sometimes additional sector requirements. The comparison matrix sets out these different documents and operating conditions without assigning a risk classification to a particular café, consultancy or accommodation business.

The practical test comes when money or customers are involved. Leasing premises for fit-out is not the same act as serving guests or delivering a paid service. A business that has permission to prepare cannot assume that sending invoices or taking advance payments turns that permission into authorization to operate. Contractual commitments made before opening also deserve scrutiny: what the business promises to do may itself expose a licensing gap.

For a company with multiple KBLI activities, the question is therefore answered one line at a time. The status of a verified activity does not cure an unverified certificate or missing license elsewhere in the same OSS account.

Business premises and location approvals are separate checks

A Bali address accepted by OSS is not proof that the property can lawfully accommodate the proposed operation. Selecting the right registered address for a Bali company does not settle which activities its customer-facing premises can legally accommodate. When the business changes from desk-based services to hospitality, food preparation or warehousing, the premises can become the decisive licensing issue.

Indonesia’s basic requirements can involve spatial conformity (KKPR), environmental approval, building approval (PBG) and a certificate of building fitness or occupancy (SLF), according to the applicable circumstances. There is an important distinction for tenants in shared office or commercial buildings: some requirements may be held by the building owner or manager and used through the permitted procedure. A tenant should understand whether those documents cover the relevant area and use. A generic assurance that “the building has papers” does not answer that question.

For a proposed guest property in the Canggu area, the specific plot, local spatial plan and authorized building use deserve separate attention. Local planning conditions in Bali sit alongside the national OSS framework. A virtual office address does not resolve the legality of a physical restaurant or villa operation, even if the portal accepts that address for another purpose. This matters particularly before the business commits to a long lease, construction work or equipment that cannot easily be moved.

Sector-specific permissions may add another layer. Their relevance has to be established from the actual activity, not from a general assumption that all businesses on Bali require the same package of permits.

After the NIB is issued: verify every activity, not just the PDF

Keep the full OSS record once the NIB has been issued. A single PDF makes a useful reference, but it says little about the detailed permissions attached to each activity and location. The same account may contain an operative approval, an unverified certificate and another application awaiting a sector decision.

For each KBLI entry, the company should be able to trace the relevant project address, risk band, document, current status and any outstanding condition. Where supplementary business permits (PB UMKU) apply, they need their own evidence. The scope and terms of an issued license also matter: a correct number attached to the wrong location or activity does not provide comfort about the operation the company actually intends to run.

A saved status record, dated copies of the attachments and a named person responsible for follow-up help prevent misunderstanding. Take a business that can already perform office-based services but is still waiting on approvals for guest accommodation. Both activities may appear in the account, yet the company should not describe both as ready to trade. After an authority verifies a standard or issues a permit, the record should be updated and the new output retained.

Tax registration, employment compliance and LKPM investment reporting after registration, where applicable, follow their own rules beyond OSS licensing. This account of NIB is a guide to the national framework, not a determination for a particular company. Actual commercial readiness must be judged from the current OSS activity record, the issued permissions and the premises; unresolved legal questions call for independent Indonesian advice before operations begin.

Fixing OSS mismatches and incomplete licensing statuses

An incomplete OSS application is not a single kind of failure. The next action depends on what the system is waiting for, where the inconsistent data originated and whether the application belongs to the current or a transitional workflow. Save the application reference and the precise status before trying to change anything. An agent’s statement that the process is “almost finished” is not a substitute for that record.

One common mismatch comes from AHU. An older company name, an unrecorded change of management or an amendment that has not synchronized can leave the licensing profile out of step with the legal entity. The corporate documents and underlying registry entry establish what should be corrected. A substantive company change goes through the appropriate corporate route; an import or synchronization problem belongs with the relevant official service. Entering knowingly inaccurate details to advance the form creates a new problem.

The activity classification can also be wrong. Sometimes this is a conversion issue arising from the transition to KBLI 2025; sometimes the proposed business genuinely extends beyond the company’s original scope. The distinction changes the remedy. An unchanged activity may qualify for the official mapping or automatic conversion process, while a new activity can require corporate and licensing amendments. Filing a convenient but unrelated KBLI is not a legitimate workaround.

A pending site approval is a different problem. The project may be waiting for spatial conformity or another premises-related requirement. Its location record, any issued documents and the authority responsible for the outstanding decision should be reviewed together. An unverified Standard Certificate under a medium-high-risk classification is more specific still: it allows preparation under the applicable framework, not unrestricted commercial service. The status must be resolved through the stated verification process.

Finally, an older OSS project may require the official transition route instead of a fresh submission. Recreating the project without understanding where earlier approvals sit can make the record harder to reconcile. When contacting OSS support or the competent sector authority, the useful evidence is the project number, screenshots showing the current status, the list of outstanding requirements and the previously issued documents. Preserve the support reference as part of the company’s licensing history.