Apply for NIB via Indonesia OSS System Guide
An NIB application is complete only when the entity, activity, location, risk result, declarations, investment data, permissions, and issued documents match the operating plan.
To apply for an NIB, use the official OSS account for the correct legal entity, verify the entity and authorized-user data, add the real business location and activities using current KBLI codes, complete project, investment, product or service, workforce, spatial and environmental information as applicable, review the risk result and declarations, then issue and download the NIB and every related output. Reconcile the issued record to the approved application before using it with banks, tax offices, customers, landlords, customs, or sector authorities.
Before submission, have a second authorized reviewer confirm the legal entity, user authority, KBLI codes, locations, project data, investment figures, workforce data, declarations, and supporting evidence. After issuance, use the NIB status explanation to verify what the document confirms, then record every standard certificate, sector approval, verification, or operating condition that remains outstanding. Do not treat issuance alone as permission for an activity that still has unmet requirements.
Key takeaways
- Use only the official OSS domain and keep company-controlled credentials, recovery contacts, and submission evidence.
- Approve KBLI, location, investment, workforce, product, environmental, and project data before entry.
- Read the risk result and every declaration; an NIB is not a universal substitute for certificates, licenses, verification, or PB UMKU.
- Download, reconcile, and archive every issued output and unresolved requirement before operational reliance.
Prepare the OSS application
Reconcile entity, authority, activity, KBLI, location, project, investment, workforce, and evidence before entry.
In this article
Prepare OSS access and the legal-entity record
Before application entry, confirm the exact entity, deed and AHU record, taxpayer identity, directors and authorized representatives, shareholders and beneficial owners, registered address, email and telephone, foreign shareholder documents, and user who will control OSS. Record company-owned recovery channels and a backup authorized user. If an agent prepares data, management should approve the exact application and retain access; no provider should be the sole holder of credentials, one-time codes, or issued documents.
OSS is Indonesia's official electronic risk-based licensing system. Reach it through the official OSS portal rather than a link supplied in a message or advertisement. The official portal describes NIB as the formal business identity, but the application and later operating permissions still depend on correct entity and project data. Verify any unusual request through official support channels.
Create an application authority memo listing the legal applicant, responsible director, preparer, reviewer, submitter, access roles, recovery contacts, permitted changes, and evidence location. Freeze a corporate data sheet and compare it with the live OSS profile before adding a project. Stop if legal name, taxpayer identity, directors, address, ownership, or authority is wrong; determine the proper upstream correction rather than typing inconsistent project data around it.
| Readiness item | Evidence | Do not proceed when |
|---|---|---|
| Entity identity | Deed, AHU, taxpayer and current corporate profile | Names, numbers or legal status conflict |
| Authority | Director approval, user role and controlled mandate | Submitter cannot prove authority |
| Account control | Company email, phone, recovery and backup access | Agent controls the only credential path |
| Data snapshot | Approved master data and version date | Team is entering from unreviewed chats or drafts |
Approve NIB project, KBLI, location, and investment data
Build the project data outside OSS. For each activity, record current KBLI and scope, project name, business and operating address, coordinates and land or premises basis, sector, products or services, expected capacity, workforce, investment plan and category, equipment, construction or operating stage, environmental parameters, existing approvals, and launch date. Reconcile those fields to the deed, shareholder plan, leases, contracts, budget and the activity map approved by management.
The current OSS KBLI 2025 conversion guide instructs users to select the correct activity, scope and location and continue through NIB issuance. Use the current classification even if a historic proposal cites KBLI 2020. The KBLI decision should already have passed ownership and sector review; OSS data entry is not the moment to guess what the company does.
Run a cross-field challenge. Does the activity fit the location and premises? Does the location fit spatial and environmental requirements? Does investment data belong to this project without duplication? Do products, capacity, workforce and operating stage tell a coherent story? Does the bank and tax narrative match? If the system generates an unexpected risk or permission route, stop and recheck source data and current rules rather than changing facts to obtain a preferred output.
Activity
Current KBLI, official scope, real deliverable, foreign-investment analysis and sector conditions.
Location
Address, coordinates, lease or title, zoning or spatial route, building and environmental suitability.
Project
Investment plan, assets, workforce, products, capacity, stage, schedule and evidence without duplicate allocation.
Test the NIB permission path
Review risk, declarations, certificates, licenses, verification, PB UMKU, premises, and sector dependencies.
Review OSS risk results, requirements, and declarations
Treat the system result as a decision pack. Record the risk level, NIB function, standard certificate or license, whether verification is pending, basic requirements, environmental document, spatial or building dependency, PB UMKU, sector approvals, self-declarations, technical standards, inspection or evidence, and the point at which the activity may lawfully operate. Read every declaration and confirm the company can comply before checking it. A click can create an enforceable representation even when no file is uploaded at that moment.
PP 28 of 2025 is the current risk-based licensing framework and replaced PP 5 of 2021. Its official BPK record distinguishes risk-based business licensing and includes NIB, certificates, licenses, basic requirements, PB UMKU, supervision and sanctions within the broader framework. The exact permission output depends on the activity and facts; an NIB alone must not be described as full operational approval for every risk level or sector.
Create a requirement tracker from every generated output and portal status. Assign owner, authority, document, dependency, submission route, verification, inspection, expiry or renewal, operating condition, evidence and deadline. Use the Indonesia business license guide to connect NIB issuance with later permissions. Do not sign a customer contract or open a site merely because the NIB PDF exists.
Risk result
Record inputs, generated level, applicable standard or license, verification and operating consequence.
Declaration
Identify factual basis, control owner, ongoing standard, evidence and escalation trigger before acceptance.
Dependency
Track spatial, environmental, building, sector, PB UMKU, inspection and professional conditions separately.
Issue, reconcile, and control the NIB outputs
Before clicking the final issuance action, compare the draft NIB and related outputs with the approved application pack. Check legal name, NIB data, taxpayer identity where shown, address and locations, KBLI codes and scopes, projects, risk results, statements, certificate or license status, dates, and identifiers. Use an authorized maker-reviewer-approver record. Immediately download every output and preserve the final application version, issuance evidence, and unresolved requirement tracker.
BKPM's official NIB issuance service standard states that NIB issuance through OSS is not charged a fee. This does not mean the entire licensing project has no cost: sector charges, PNBP, environmental or technical work, premises, certification, professional services and third-party evidence can be separate. Reject any invoice that labels a private service fee as an official NIB fee without a verified legal basis and payee.
Reconcile the issued NIB to deed and AHU data, tax setup, bank KYC, leases, contracts, invoices, customs or import plans, staffing, website claims, and the license tracker. Correct errors through the current official process and preserve old and new versions. Set a change trigger for KBLI, address, shareholder, director, capital, project, product, location or operating-model changes. The NIB is a controlled corporate record, not a PDF to circulate without version and access management.
Issuance pack
Approved inputs, draft review, final NIB, statements, certificates or licenses, receipt or status and requirement tracker.
Cost control
Separate no-fee NIB issuance from legitimate government, sector, technical, premises and professional costs.
Record control
Current version, secure access, permitted disclosure, downstream updates, change triggers and superseded-document archive.
Official references and review basis
The following primary sources were checked on August 1, 2026. They establish the regulatory or service boundary used in this article; bank, tax office, OSS, AHU, and immigration decisions can still depend on the current record and the facts of a particular application.
- OSS — Official portal — Primary official domain for Indonesia's electronic risk-based licensing system.
- OSS — NIB creation guide — Current official NIB guide context; verify live navigation and transitional instructions.
- BKPM — NIB issuance service standard — Official service standard stating that OSS NIB issuance is not charged.
- BPK — PP 28 of 2025 — Current risk-based licensing framework.
- BPK — Permeninves/BKPM 5 of 2025 — Current OSS licensing procedure and supervision framework.
The release gate for an OSS NIB application
Release the application only when company identity and authority are correct, the current KBLI and real activity match, location and project data are evidenced, investment and workforce figures are approved, risk results and declarations are understood, and every post-NIB permission and verification dependency has an owner. Issue through the official system and retain the exact output pack.
Do not represent the company as fully licensed from the NIB alone. Reconcile the issued record with corporate, tax, bank, contract, premises and operating data and escalate unexpected risk results or permissions. Use the Indonesia company registration framework to position NIB inside the full launch sequence.
Reconcile the issued NIB
Check every output against corporate, tax, bank, contract, address, project, and operating records.
Frequently asked questions
