Indonesia’s Online Single Submission system is the main digital gateway for risk-based business licensing. For a foreign business, however, using OSS successfully is not simply a matter of completing an online form. The output depends on whether the legal entity, ownership structure, business classification, project location and operating model have been mapped correctly before the application begins.
This guide explains what foreign investors and foreign-owned companies should know about OSS, how the system connects KBLI activities to the NIB and further approvals, and how to prepare data that can support real operating readiness.
Key Takeaways
- OSS is the electronic licensing system; it does not replace the need to establish the correct legal presence or satisfy sector-specific rules.
- A Nomor Induk Berusaha (NIB) is the business identification number issued through OSS, but an NIB alone does not prove that every planned activity is ready to operate.
- Each selected KBLI activity is assessed through the risk-based licensing framework, which can produce different requirements for different activities and locations.
- Foreign ownership, project scale, location, products, facilities and supporting activities can affect the licensing route beyond the basic OSS registration.
- The most efficient preparation starts with an activity-and-location map, not with data entry in the portal.
What Is Online Single Submission in Indonesia?
Online Single Submission, commonly shortened to OSS, is Indonesia’s electronically integrated system for business licensing. The official OSS portal is used by business actors to register, submit project and activity data, obtain licensing outputs, manage changes and access related services. It also connects licensing workflows involving central ministries, agencies and regional authorities.
The current risk-based framework is established by Government Regulation No. 28 of 2025. That regulation replaced Government Regulation No. 5 of 2021 and covers basic requirements, business licensing, supporting business licences known as PB UMKU, OSS system services, supervision and sanctions. It defines risk-based licensing as an approach based on the risk analysis of each business activity.
That last point is crucial. OSS is not one generic licence application. It is a system that processes the facts attached to a specific business actor, activity and project. Two companies that appear commercially similar may receive different requirements because their KBLI codes, locations, products, facilities or operating methods differ.
Why OSS Matters to Foreign Businesses
For many foreign investors, OSS sits between corporate establishment and commercial operation. A PT PMA may already have a deed of establishment and Ministry of Law approval, yet it still needs to ensure that its intended activities are properly reflected in OSS and that the corresponding licensing requirements are fulfilled.
OSS matters because the information entered into the system can shape several downstream workstreams:
- the activities shown under the company’s NIB;
- the risk level applied to each activity;
- whether a standard certificate or further business licence is required;
- which basic requirements must be addressed for the project location;
- whether supporting licences or PB UMKU are needed;
- which authority may verify, approve or supervise the activity; and
- how the company demonstrates licensing status to banks, customers, landlords, vendors or regulators.
Foreign businesses should therefore treat the OSS record as operational master data. It needs to align with the company’s constitutional documents, shareholder and management information, tax profile, project plan and actual activities. A mismatch can create complications when the business later adds a location, imports equipment, registers a product, hires personnel or undergoes regulatory supervision.
How OSS, KBLI and the NIB Work Together
Three concepts are often mixed together: OSS, KBLI and NIB. They serve different functions.
| Element | Practical function | Key planning question |
|---|---|---|
| OSS | The electronic system used to submit, process and manage business licensing information. | Are the company and project data accurate and complete? |
| KBLI | Indonesia’s official classification of economic activities. | Which code and description accurately cover what the business will actually do? |
| NIB | The official business identification number issued through OSS. | Do the activities and project records attached to the NIB match the intended operations? |
| Business licensing outputs | The risk-dependent legalities and requirements associated with the activity. | What must be issued, verified or fulfilled before this activity may operate? |
| PB UMKU | Licensing used to support certain business activities. | Does the operating model require additional supporting approvals? |
Indonesia published KBLI 2025 through BPS Regulation No. 7 of 2025. The BPS conversion-table announcement explains that mappings from KBLI 2020 to KBLI 2025 may be one-to-one, one-to-many or many-to-one. This means an existing activity should not be remapped merely by matching a familiar label. The scope and description must be checked against the business model.
The company should also distinguish a broad commercial description from the regulated activity. For example, saying that a business provides “technology services” may be too vague to identify the correct classification. The team should document what it delivers, to whom, through what channel, whether it develops or resells products, whether it imports, and where the work occurs.
The Four Risk Levels in OSS
The official OSS portal states that Indonesia’s risk-based business licensing system groups businesses into four levels. At a high level, these are low risk, medium-low risk, medium-high risk and high risk. The licensing consequence generally becomes more demanding as the assessed risk increases, but the exact output must be confirmed for the relevant KBLI and project data.
| Risk level | General licensing pattern | What the business should verify |
|---|---|---|
| Low | The NIB generally functions as the business licence for the activity. | Whether basic, sectoral, product, location or supporting requirements still apply. |
| Medium-low | The NIB and a standard certificate based on the business actor’s statement generally form the licensing basis. | The standards declared, timing of fulfilment and supervision obligations. |
| Medium-high | The NIB and a standard certificate subject to verification generally apply. | What evidence is required, which authority verifies it and when operations may begin. |
| High | The NIB and a business licence generally apply, with applicable standards or conditions. | Approval dependencies, technical standards and any prerequisites tied to the project. |
This table is a planning summary, not an activity-specific conclusion. The applicable approvals may depend on the selected KBLI, project location, risk classification, operating model, products and facilities. Companies should use the actual OSS output and current sector rules for implementation.
Foreign investors can explore this framework further in IndoGateway’s guide to Indonesia’s four risk-based licensing levels and the practical overview of how NIB, OSS and KBLI connect.
What to Prepare Before Using OSS
Preparation should be organized around the project, not only the portal fields. A useful pre-OSS pack normally covers the following areas.
1. Confirm the legal applicant
Determine whether the applicant is an Indonesian legal entity, a qualifying foreign business presence or another recognized form. A foreign group should not assume that its overseas parent can use the same route as a PT PMA. The correct presence depends on the activity and relevant sector framework. For an operating foreign-owned company, review the steps in IndoGateway’s PT PMA setup guide.
2. Map every revenue-generating and supporting activity
List what the company will sell, manufacture, distribute, provide, license or operate. Separate principal activities from supporting functions. Then assess the closest KBLI descriptions, their boundaries and their compatibility with the company’s corporate purposes and foreign ownership position.
3. Map each project location
An office, warehouse, store, factory, data facility and project site may raise different questions. Location can affect spatial, environmental, building, industrial-estate and regional workflows. Avoid treating a registered office address as a complete description of the physical operating footprint.
4. Reconcile corporate data
Names, identification details, management positions, shareholders, capital data, addresses and contact information should be consistent across the supporting corporate records and connected government systems. If upstream data is outdated or incomplete, correct the authoritative record before relying on repeated manual entry.
5. Identify product and sector overlays
OSS business licensing does not necessarily complete product registration, import controls, sector accreditation, professional certification or facility approvals. A food, medical-device, construction, energy, transport, digital or industrial project may have separate technical workstreams. These should be identified early so that the NIB is not mistaken for the final operational approval.
A Practical OSS Workflow for Foreign-Owned Companies
- Define the operating model. Record the products, services, customers, transaction flow, facilities, imports, workforce and locations that the Indonesian business will use.
- Validate the legal structure. Confirm that the intended entity or foreign business presence is appropriate for the activities and ownership arrangement.
- Select and verify KBLI activities. Match the real scope of work to the current classifications and review foreign investment and sector implications.
- Prepare consistent master data. Reconcile corporate, tax, management, shareholder, address and contact information.
- Register or access the correct OSS account. Use the official non-UMK or other applicable workflow and maintain control of the registered email and authorized access.
- Complete business and project records. Enter the selected activity, location, investment and operational information accurately for each project.
- Review system-generated requirements. Examine the risk level, basic requirements, licensing output, standard certificate, licence and PB UMKU pathways shown for each activity.
- Fulfil verification and technical steps. Submit supporting evidence and coordinate with the competent authority where verification or approval is required.
- Check operating readiness. Confirm that sector, product, import, environmental, building, workforce and other dependencies have been addressed before launch.
- Maintain the OSS record. Update data when the company changes activities, locations, corporate information or project characteristics, and monitor ongoing reporting and supervision obligations.
The portal provides official guidance for business actors, including non-UMK OSS access registration. Screens and process labels can change, so teams should use the current portal guide rather than relying on an old screenshot or a saved checklist.
Common OSS Problems Foreign Businesses Encounter
Choosing a KBLI code from a short label
A short label can hide exclusions or a narrower scope. Read the classification description and assess whether the activity includes development, manufacturing, wholesale, retail, intermediation or professional services. One commercial offering can involve several legally distinct activities.
Assuming the NIB is the final licence
The NIB is central, but it is not a universal certificate of operating readiness. The company must review the licensing status of every activity and any additional basic, technical, product or supporting requirements.
Inconsistent corporate information
Differences between OSS and upstream records can interrupt the workflow or produce unreliable documentation. Changes to shareholders, management, addresses or corporate purposes should be handled in the proper sequence.
Using one project record for a more complex footprint
A company may have several locations or activities with different risk and approval implications. Project records should reflect how and where the business actually operates.
Losing control of access credentials
The OSS account contains sensitive corporate information and can be used for consequential licensing actions. The registered email, responsible person, delegated access and internal approval process should be controlled and documented.
Ignoring post-issuance obligations
Licensing is not finished when a document is downloaded. Businesses should review conditions, standards, reporting, supervision and change-management duties. Where applicable, investment activity reporting may form part of the compliance calendar; see IndoGateway’s overview of LKPM investment reporting support.
How to Check Whether an OSS Record Is Operationally Reliable
A useful quality-control review asks more than whether the NIB exists. The team should be able to answer these questions:
- Does the legal entity in OSS match the entity that will sign contracts and receive revenue?
- Do the KBLI activities cover the actual products, services and transaction flows?
- Are all material project locations recorded appropriately?
- Has each activity’s risk-based licensing output been reviewed separately?
- Are required standard certificates, licences or verifications in the correct status?
- Have basic requirements and sector or product dependencies been checked?
- Are ownership, capital, management and contact records consistent with authoritative documents?
- Does the compliance calendar include reporting, renewal, supervision and change events?
This review is especially valuable before signing a lease, importing machinery, beginning construction, onboarding employees or committing to a customer launch date. OSS should be assessed as one connected part of the operating model, not as an isolated administrative task.
Frequently Asked Questions
1. What is Indonesia’s Online Single Submission system?
Indonesia’s Online Single Submission system is the official electronic platform for integrated business licensing. A business actor uses OSS to manage identity, activity, project and location data and to obtain or process risk-based licensing outputs. The system connects workflows involving central and regional authorities, but it does not remove the substantive requirements imposed by the applicable regulations. For a foreign business, OSS should be understood as the licensing transaction layer: the result still depends on the correct legal entity, KBLI classification, ownership position, project facts and any sector-specific rules.
2. Can a foreign company register directly in OSS?
A foreign business may use an OSS route when its recognized legal form and activity are eligible for that route, but foreign status alone does not establish eligibility. Many operating investments use an Indonesian foreign-owned limited liability company, or PT PMA, while certain representative offices or foreign business entities may follow specialized pathways. The appropriate applicant depends on the activity, commercial presence and sector. The business should establish the legal route first, then register or access the matching OSS profile. It should not assume an overseas parent can substitute for a locally required operating entity.
3. Is an NIB enough for a foreign-owned company to start operating?
No, an NIB should not automatically be treated as complete operating permission for every activity. It is the company’s business identification number and can function as the business licence for a low-risk activity, but other activities may require a standard certificate, verification or a business licence. Basic requirements, PB UMKU, product registrations, import controls, environmental approvals, building matters or sector-specific permissions may also be relevant. The company should review each KBLI activity and project location individually and confirm the status and conditions of every applicable output before commencing the regulated operation.
4. How does OSS determine the risk level of a business?
OSS applies Indonesia’s risk-based licensing framework to the selected business activity and the project information submitted. The framework groups activities into low, medium-low, medium-high and high-risk levels, with different general licensing consequences. A company should not select its own preferred risk tier or infer it only from company size. The output is tied to the applicable activity and parameters in the regulatory framework. Because location, scale, product, facility or operating details may be material, the business should verify the actual OSS result rather than relying on a generic industry summary.
5. How should a foreign investor select KBLI codes for OSS?
The investor should start with a written description of the actual operating model, then compare that description with the scope of the current KBLI classifications. It should distinguish manufacturing, distribution, retail, intermediation, digital delivery, consulting and supporting activities rather than choosing a broad label that merely sounds familiar. The team should also review whether each activity is consistent with the entity’s corporate purposes and the applicable foreign investment and sector rules. With KBLI 2025 implementation, existing mappings may not always be one-to-one, so the official descriptions and conversion information deserve careful review.
6. What information commonly causes problems in an OSS application?
Problems often arise when corporate records and OSS data do not agree, or when the project has not been defined precisely enough. Common pressure points include the company name, shareholder and management details, addresses, contact email, business purposes, KBLI selections, project locations and investment information. A technically accepted entry can still be operationally wrong if it describes a different activity or location from the real business. The safest approach is to create a reconciled master-data pack and assign internal owners to verify corporate, tax, operational and licensing information before submission.
7. Can a company add or change activities after obtaining an NIB?
A company can generally manage changes through the relevant corporate and OSS processes, but the correct sequence depends on what is changing. Adding an activity may first require an amendment to the company’s stated purposes, a review of foreign ownership eligibility and a reassessment of project or location requirements. A KBLI change can also generate a different risk classification or new licensing outputs. The company should preserve the validity of existing operations while assessing the change, update authoritative upstream records where necessary, and review the resulting OSS status before launching the new activity.
8. How long does an OSS licensing process take?
There is no reliable universal timeline for OSS licensing. Account access and a straightforward low-risk registration may move differently from a project requiring verified standards, technical review, spatial or environmental steps, sector approval or coordination across authorities. Timing can also be affected by data inconsistencies, incomplete evidence and changes to the project scope. A foreign business should build its schedule from the actual KBLI activities, risk levels, locations and approval dependencies. It is more useful to track each prerequisite and responsible authority than to rely on a single headline estimate for the entire licensing process.
Conclusion
Indonesia’s OSS system can make licensing more integrated, but it cannot compensate for an unclear business model or inaccurate project data. Foreign businesses get the best result when they define their activities and locations first, validate the legal and ownership structure, select KBLI codes carefully, reconcile master data and then examine every risk-based output generated by the system.
The practical objective is not merely to obtain an NIB. It is to build a licensing record that accurately supports the company’s contracts, facilities, people, products and launch plan, with a clear path for further approvals and ongoing compliance.
Plan Your OSS Licensing Route with IndoGateway
IndoGateway helps foreign investors connect company setup, KBLI selection, OSS licensing and related operational workstreams. Before submitting data or committing to a launch schedule, contact IndoGateway to map the activities, locations and approvals relevant to your Indonesia project.
