Applying for a Business Identification Number, or NIB, is one of the central steps in Indonesia’s risk-based business licensing system. For a foreign-owned company, however, the process is not simply a matter of opening the Online Single Submission system, entering a company name and downloading a number. The information submitted through OSS connects the company’s legal profile, selected KBLI business activities, project locations, investment data and risk-based licensing route.
This guide explains how to apply for an NIB in Indonesia through OSS, what a foreign company should prepare, where application problems commonly begin and what to check after the NIB is issued. It is designed as a practical planning guide rather than a substitute for reviewing the requirements of a specific project.
Key Takeaways
- An NIB is evidence of business registration and the identity of a business actor in Indonesia’s OSS system; it is not automatically the final approval needed for every activity.
- A company should align its deed, corporate registry data, tax information, OSS account, KBLI codes, business locations and project data before submitting an NIB application.
- OSS uses the selected activity and project information to determine the risk-based licensing route and the documents or approvals that may follow.
- Low-risk activities generally rely on the NIB as the risk-based business licence, while other risk levels can require a Standard Certificate, licence, verification or supporting approval.
- Foreign ownership, spatial, environmental, building, product, import and sector requirements may still affect whether the company is ready to operate.
- The application should be treated as a controlled data exercise: review the draft, declarations and each activity’s status before issuing or relying on the NIB.
What Is an NIB?
NIB stands for Nomor Induk Berusaha, commonly translated as Business Identification Number. Under Indonesia’s current risk-based licensing framework, it serves as evidence that a business actor has been registered and as the business actor’s identity for conducting business activities. The current framework is principally governed by Government Regulation No. 28 of 2025 on Risk-Based Business Licensing, which replaced Government Regulation No. 5 of 2021.
The distinction between identity and operating readiness is essential. An NIB identifies the business actor and records its activities in OSS. The permissions required to begin and conduct a particular activity are determined through the risk-based route. Depending on the KBLI activity, business scale, location and project characteristics, OSS may show the NIB, a Standard Certificate, a licence, supporting business licences known as PB UMKU, or requirements connected with spatial use, environment, buildings or a sector authority.
For a broader explanation of how classification, registration and licensing fit together, see IndoGateway’s guide to NIB, OSS and KBLI in Indonesia.
Who Applies for an NIB Through OSS?
Business actors use the OSS system to obtain an NIB for activities covered by Indonesia’s risk-based licensing framework. For a foreign investor establishing an Indonesian limited liability company with foreign investment, commonly called a PT PMA, the applicant is the Indonesian company rather than an overseas shareholder acting in its own name. The company’s incorporation and corporate registry information therefore need to be in order before the OSS licensing workflow is completed.
The route can differ for other structures, such as a permanent establishment, representative office or a regulated sector entity. A foreign company should not assume that the same corporate form or account-registration path applies to every market-entry model. The appropriate applicant depends on the intended activity, legal presence and sector rules.
Companies that need help aligning incorporation and licensing can review IndoGateway’s Indonesia business setup solution and PT PMA company registration service.
What to Prepare Before Starting the NIB Application
Most avoidable problems arise before the applicant reaches the final issuance screen. The OSS application draws together information from several workstreams, so preparation should begin with a structured data review.
1. Confirm the company’s legal and registry data
Check the company’s legal name, legal form, registered address, deed information, corporate approvals or notifications, management and shareholder information against the records held by the relevant government systems. Inconsistent names, addresses or identifiers can interrupt account verification or cause the licensing profile to misrepresent the legal entity.
2. Establish and verify OSS access
The company needs the appropriate OSS access account and an email address that is actively monitored. Current official OSS guidance includes a dedicated non-micro and small business account-registration route for business entities. The authorized team should control the login, verification channel and recovery information, because the account will continue to be used for amendments, fulfilment, reporting and licence management.
3. Select the correct KBLI activities
Each intended business activity must be mapped to the most accurate Indonesian Standard Industrial Classification, or KBLI, code. The code should reflect what the company will actually do and earn revenue from, not merely a broad description that sounds convenient. The selected KBLI influences risk classification, licensing outputs, foreign ownership analysis and sector requirements. Review IndoGateway’s KBLI classification guide before filing.
4. Review foreign ownership and sector access
The fact that a code is available in OSS does not by itself prove that a proposed foreign shareholding structure is permitted or that no sector conditions apply. Ownership treatment can depend on the precise activity, scope, business model and applicable investment or sector rules. Complete this review before adding a KBLI to the corporate purpose and OSS profile. IndoGateway’s foreign ownership review service is intended for this type of activity-by-activity assessment.
5. Prepare project and location information
OSS may require information about the business location, land or premises, project type, investment components, workforce, products or services, production capacity and other activity-specific data. The exact fields depend on the applicant and activity. Use internally approved figures that can be reconciled with the company’s investment plan and supporting records rather than estimates entered only to move through the screen.
6. Identify linked approvals
Before filing, map whether the project may involve spatial conformity, environmental approval, building approval, industrial location, product registration, import arrangements, professional eligibility, foreign personnel or a sector regulator. Some of these items are integrated into OSS, while others may require verification or action through another authority’s system.
How to Apply for an NIB in Indonesia Through OSS
The screens and labels in OSS may be updated, and the path varies with applicant type and risk. The following sequence reflects the general workflow shown in current official OSS guidance for business licensing applications.
Step 1: Register or access the company’s OSS account
Go to the official OSS portal and use the account-registration path applicable to the business actor. For a non-UMK business entity, the registration flow requests the business-actor type, legal-entity type and company email before identity and profile verification. Use company-controlled contact details and ensure the person managing access is properly authorized.
Step 2: Review the business-actor profile
After signing in, review the data displayed for the legal entity. Confirm that names, identifiers, tax details, addresses, management and other imported or entered information are consistent with the underlying corporate records. If foundational corporate information is wrong, correct it through the appropriate source process rather than compensating with inconsistent licensing data.
Step 3: Start a new business licensing application
Use the business licensing management menu to begin a new application. Official OSS guidance shows the path through the business licensing menu, business management and new application functions. The exact interface wording may evolve, so follow the current labels shown in the authenticated account.
Step 4: Add the business field and KBLI
Select the KBLI code that matches the intended activity. Review the description and scope rather than relying only on the code title. Where the company has several activities, add each genuine activity with the correct project and location data. Do not add codes merely to preserve hypothetical future options without checking their effect on the company’s corporate purpose, ownership position and compliance obligations.
Step 5: Enter location, project and activity data
Complete the fields requested for the activity. These may cover location, project status, land area, workforce, investment components, products or services, capacity and other sector-specific details. OSS uses this information to determine the business scale, risk-based route and linked requirements. A material change to the project may therefore require an amendment rather than being handled as an informal operational change.
Step 6: Complete the required declarations and basic-requirement route
Read each declaration before accepting it. The system may present self-declarations or connect the application with spatial, environmental or other basic requirements. A declaration is a legal representation by the business actor, not a routine box to be checked without evidence. If the project data cannot support the statement, pause the application and resolve the underlying issue.
Step 7: Review the activity list and risk output
OSS displays the recorded activity, location, business data, scale, risk level, declarations and licensing status. Check the output for each activity. The risk classification determines the principal route: low-risk activities generally use the NIB; medium-low activities use the NIB and a self-declared Standard Certificate; medium-high activities require the NIB and a Standard Certificate that must be verified; high-risk activities require the NIB and a licence. Other approvals can also apply.
Step 8: Inspect the draft and issue the business licensing output
Review the draft NIB and the attached activity data carefully. Current OSS guidance shows a final disclaimer and issuance action after the draft is displayed. Issue the output only after confirming that the company, KBLI, location, scale, investment and declaration data are complete and accurate. Download and retain the NIB and related documents in the company’s controlled compliance records.
Step 9: Continue any fulfilment or verification process
Issuance of the NIB may be the beginning rather than the end of the route. Check whether a Standard Certificate remains unverified, a licence has not yet been issued, a basic requirement is pending or the activity must continue through a ministry or agency system. The official OSS guidance for medium-high and high-risk business-entity applications illustrates how fulfilment status can remain pending after the NIB appears.
What Happens After the NIB Is Issued?
First, read the NIB together with the activity-level status in OSS. A single company may hold several KBLI activities with different risk levels and different readiness states. One activity may be complete while another still requires verification, a licence or a supporting approval.
Second, complete the requirements associated with each activity. For medium-high risk activities, an unverified Standard Certificate should not be treated as authority to begin operational or commercial activity. For high-risk activities, the required licence must follow the applicable process. The company may also need PB UMKU approvals that support the main activity, depending on the sector and operating model.
Third, reconcile the licensing outputs with the broader launch plan. Premises, environmental, construction, import, product, workforce, immigration and tax workstreams should match the same legal entity, KBLI, address and commercial model. IndoGateway’s NIB and OSS business licensing service supports this integrated review.
NIB Application Checklist for Foreign Companies
| Workstream | Pre-filing check | Why it matters |
|---|---|---|
| Legal entity | Corporate name, form, deed and registry data are consistent | OSS identifies and validates the applicant through connected records |
| Access | Company-controlled email, authorized user and recovery details are available | The account remains essential for licence management and amendments |
| KBLI | Each code accurately describes a real revenue-generating activity | Classification affects risk, licensing and ownership analysis |
| Ownership | Foreign ownership and sector restrictions have been reviewed per activity | OSS availability alone is not a complete ownership opinion |
| Location | Address, land or premises data and intended use are documented | Spatial, environmental and building requirements can be location-dependent |
| Project data | Investment, workforce, products, services and capacity are internally approved | These inputs can affect scale, risk outputs and ongoing reporting |
| Declarations | Evidence supports each statement accepted in OSS | Self-declarations are substantive compliance representations |
| Post-NIB route | Every activity’s certificate, licence and supporting approvals are mapped | NIB issuance does not establish universal operating readiness |
Common NIB Application Mistakes
Selecting a broad but inaccurate KBLI code
A loosely related code can produce the wrong risk route, create a foreign-ownership problem or omit the licence actually needed. Start from the activity’s operational facts: what the company sells, who it serves, where it operates, whether it manufactures or imports, and how it earns revenue.
Treating the NIB as a universal operating licence
The NIB is sufficient as the risk-based business licence for low-risk activities, but that principle should not be generalized to every project. Review each activity’s OSS status and the requirements triggered by its risk classification.
Entering convenient rather than supportable project data
Investment, capacity, workforce and location inputs should match the company’s approved plan. Unsupported entries can create inconsistencies with corporate documents, investment reporting, sector filings and future amendments.
Ignoring pending verification
Seeing “NIB issued” does not resolve a Standard Certificate or licence whose status is still pending. Create a closing checklist for every activity and do not use the company-level NIB as a substitute for activity-level evidence.
Failing to update OSS when the business changes
New activities, changed locations, expanded facilities or altered project data may require updates and additional review. Licence management should remain part of the company’s change-control process after launch.
Frequently Asked Questions
1. Can a foreign company apply for an NIB before incorporating an Indonesian company?
Usually, a foreign investor using a PT PMA route completes the Indonesian company’s incorporation and corporate registration steps before finalizing its OSS business licensing profile. The applicant for the NIB is then the Indonesian legal entity. Other structures, such as a representative office or permanent establishment, can follow different rules and account paths. The correct sequence depends on the intended activity and legal presence, so the foreign investor should confirm the appropriate entity and applicant before beginning. An overseas parent company’s existence does not automatically create an Indonesian operating licence.
2. Is an NIB the same as an Indonesian business licence?
An NIB is the business actor’s registration evidence and identity in the OSS framework, but its licensing effect depends on the activity’s risk level. For a low-risk activity, the NIB generally serves as the risk-based business licence. Medium-risk activities involve a Standard Certificate, and high-risk activities involve a licence, with different fulfilment or verification requirements. Supporting approvals may also apply. The correct question is therefore not only whether the company has an NIB, but whether each KBLI activity has reached the status required before operational or commercial activity begins.
3. Which documents are needed for an NIB application in Indonesia?
The required information depends on the applicant, activity and project. A foreign-owned company should generally prepare consistent corporate registry and tax data, authorized OSS access, selected KBLI codes, location information, investment and workforce data, descriptions of products or services, capacity information where requested, and evidence supporting the declarations made in OSS. Spatial, environmental, building or sector documents may also become relevant. Because OSS draws information from connected systems, the team should first reconcile the source records rather than treat the application as an isolated form with a universal document list.
4. How long does it take to obtain an NIB through OSS?
There is no responsible universal timeline for the complete licensing outcome. The NIB itself may be generated after a complete and valid submission, but account verification, inconsistent source data, KBLI analysis, location requirements and system issues can affect the process. More importantly, NIB issuance may leave Standard Certificate verification, a licence, basic requirements or sector approvals outstanding. Companies should separate the administrative event of receiving an NIB from the time required to become operationally ready, then build a project schedule around every activity’s actual dependencies rather than a single headline estimate.
5. Can one company include several KBLI codes under one NIB?
A company can record multiple genuine business activities under its NIB, subject to its corporate purpose and the rules applicable to each activity. Each KBLI should match the actual operating model and be reviewed for foreign ownership, business scale, risk classification, sector conditions and location requirements. Activities under the same company can produce different licensing outputs and statuses. Adding numerous speculative codes can complicate compliance and reporting, so the better approach is to select activities that are commercially planned, legally supported and operationally understood, then manage additions through a controlled amendment process.
6. Does obtaining an NIB allow a company to import goods?
An NIB should not be treated as a universal conclusion that every company can import every product. Import activity depends on the company’s KBLI, importer role, intended use of the goods, customs and trade settings, product controls and other applicable requirements. Certain products or sectors may require registrations, approvals or restrictions beyond the company-level OSS record. The company should map the product, importer of record, ownership of the goods, distribution model and post-border obligations before shipment. This avoids confusing business registration with the complete legal and operational route for a specific import transaction.
7. What should a company do if its OSS data is different from its corporate documents?
The company should identify the authoritative source of the mismatch and correct the underlying record through the appropriate process before relying on the NIB application. Examples include differences in legal name, address, management, shareholders, tax information or business purpose. Entering alternative information merely to pass a screen can create a second inconsistency and make later amendments or regulatory checks more difficult. Keep evidence of corrections, confirm that connected systems have synchronized, and review the refreshed OSS profile. If the source or correction route is unclear, seek technical or regulatory assistance before issuing inaccurate licensing data.
8. What must be checked immediately after the NIB is issued?
Download the NIB and compare its company details, KBLI activities, locations and other recorded information with the approved application data. Then inspect each activity’s risk level, Standard Certificate or licence status, basic requirements, supporting PB UMKU approvals and any verification routed to another authority. Store the issued documents under controlled access and assign owners for outstanding steps. Finally, reconcile the OSS outputs with the company’s premises, environment, product, import, workforce, immigration, tax and reporting workstreams. The company should begin operations only when the requirements applicable to that specific activity and project have been satisfied.
Conclusion
A successful NIB application is the result of accurate preparation rather than rapid form completion. Foreign companies should align their corporate profile, choose defensible KBLI codes, verify ownership access, enter supportable project data and understand the risk-based outcome before issuing the NIB. After issuance, the decisive task is to close every activity-level certificate, licence and supporting approval required for the actual operating model.
Regulatory note: Indonesian investment, licensing, tax, immigration, product, environmental and operating requirements may change and may depend on the business activity, ownership structure, location, products and project circumstances. This article provides general information and is not project-specific legal, tax or regulatory advice. Applicable requirements should be verified before implementation.
Plan Your NIB and OSS Licensing Route
IndoGateway can help foreign companies connect entity setup, KBLI selection, OSS data, risk-based licensing and post-NIB approvals into one practical work plan. Contact IndoGateway to discuss the activities, location and operating model behind your Indonesia expansion.
