Foreign-owned companies often expect Indonesia’s Online Single Submission system to work like a single online application. In practice, OSS is the delivery layer for a connected licensing framework. The result depends on whether corporate records, business activities, foreign-investment eligibility, project locations, risk classifications and sector requirements all agree.
When they do not, a company may see missing activities, incomplete licence outputs, validation messages or an NIB that does not yet establish operating readiness. This guide explains the most common OSS licensing problems for foreign-owned companies, how to diagnose them and when the issue requires more than a technical correction.
Key Takeaways
- OSS does not replace corporate, investment, spatial, environmental or sector rules; it connects them through a risk-based licensing process.
- An NIB is a business identity, but it is not universal proof that every listed activity may begin commercial operations.
- Most persistent problems trace back to mismatched entity data, an unsuitable KBLI, foreign-ownership restrictions, an incomplete project record or an unfinished verification step.
- Correct the underlying record in the authoritative system first. Re-entering the same inconsistent information in OSS rarely resolves a substantive problem.
- Review each KBLI and project location separately because one company can receive different risk levels and licensing outputs across its activities.
- Before launch, compare the downloaded OSS documents with the company’s real activities, premises, products and supporting approvals.
Why OSS Licensing Problems Are Different for Foreign-Owned Companies
A foreign-owned Indonesian limited liability company, commonly called a PT PMA, sits at the intersection of company law, investment rules and sector regulation. The official OSS portal processes risk-based business licensing, while corporate information originates in the Ministry of Law’s administration system and activity classifications follow the official KBLI framework.
Government Regulation No. 28 of 2025 defines the current risk-based licensing framework and covers basic requirements, business licensing, supporting business licences, OSS services, supervision and sanctions. It replaced Government Regulation No. 5 of 2021. The practical implication is important: a screen-level error can reflect a legal or data dependency outside OSS rather than a website malfunction.
Foreign ownership adds another checkpoint. A commercially available activity is not automatically available to every foreign ownership structure on identical terms. The selected KBLI must be assessed against the applicable investment-business-field and sector rules. IndoGateway’s foreign ownership overview provides a useful starting point, but the final conclusion should be made for the exact activity and project.
Common OSS Issues at a Glance
| Issue | Typical symptom | First point to check |
|---|---|---|
| Corporate data mismatch | Entity information is missing, outdated or cannot be validated | Latest approved corporate record and responsible user’s access |
| Incorrect KBLI | The activity description or licence route does not match operations | Revenue activity, operating model and official KBLI description |
| Foreign-investment incompatibility | An activity cannot be selected or needs a different structure | Current investment and sector rules for that KBLI |
| Incomplete risk-based output | NIB is issued, but a Standard Certificate or licence is not effective | Risk level, status and outstanding fulfilment requirements |
| Location dependency | Spatial, environmental or site fields block progress | Project address, land/building basis and required basic approvals |
| Missing supporting licence | Main business licence exists, but a regulated function remains unavailable | Applicable PB-UMKU, product, import or sector approval |
| Project-data inconsistency | Risk validation or application routing produces an unexpected result | Investment plan, scale, capacity, products and activity description |
| Transition or amendment issue | Old and new records do not align | Applicable OSS change process and KBLI conversion pathway |
1. Corporate Data in OSS Does Not Match the Legal Entity Record
OSS depends on authoritative corporate data. A change to the company name, address, management, shareholders, capital or stated business purposes may first need to be completed through the appropriate corporate process and recorded in the Ministry of Law system. The OSS record can then follow the approved source data through the applicable synchronization or change workflow.
Start with the latest deed, Ministry approval or notification, tax identification information and the exact spelling used for the company and its officers. Do not create a second account or alter unrelated fields simply to bypass a validation message. The Ministry of Law’s corporate administration FAQ confirms that foreign shareholders can make a company a PT PMA and explains that changes to a company’s purposes require the appropriate corporate action.
2. The Selected KBLI Does Not Describe the Real Business
KBLI is not a marketing label. It is the official classification used to identify the economic activity that drives licensing analysis. A broad commercial description such as consulting, technology, distribution or manufacturing may map to several different codes, each with its own scope and potential licensing consequences.
Map each revenue-generating and operational activity before selecting a code. Review what the company will sell, who will buy it, where the work occurs, whether goods are imported or produced, whether a digital platform intermediates transactions and whether the company acts as principal, agent or service provider. Then compare that operating model with the official description, inclusions and exclusions.
BPS issued KBLI 2025 through Regulation No. 7 of 2025, with targeted descriptive changes under BPS Regulation No. 6 of 2026. Official implementation guidance also introduced conversion arrangements. Use the current directory and conversion references, but do not treat an automated mapping as proof that the activity scope, foreign-ownership position and licence route are correct. IndoGateway’s KBLI selection guide explains the operational questions to resolve before filing.
3. The Activity Has Not Been Checked for Foreign-Investment Eligibility
An OSS account may accept corporate information while a specific activity still requires a foreign-investment review. Presidential Regulation No. 10 of 2021, as amended by Presidential Regulation No. 49 of 2021, provides the investment-business-field framework, but sector rules and the exact activity remain material.
Check eligibility for every proposed KBLI rather than applying a single conclusion to the entire company. Also confirm whether the planned ownership, business scale, operating role and any sector-specific conditions are compatible. A related activity can have a different investment treatment even when it appears commercially similar.
If the structure and activity do not align, the answer is not to choose a loosely related code. That can create a larger compliance problem by making the legal documents, actual operations and OSS record inconsistent. Resolve the activity and ownership analysis before finalizing the corporate purposes and licence application.
4. The Company Treats the NIB as the Final Operating Licence
The NIB is a core business identity in OSS, but the required licensing output depends on the risk level of each activity. Under the risk-based framework, low-risk activities generally rely on the NIB, while medium-risk activities involve a Standard Certificate and high-risk activities involve a licence. The exact status and fulfilment route must be checked in the company’s OSS record.
A document may be generated before all substantive requirements have been completed. For medium-high and high-risk activities, the official OSS guidance directs companies to a fulfilment process for standards or licence requirements. Read the status wording, not only the document title. Pending verification, unfulfilled requirements or an ineffective output can mean that commercial operation should wait.
5. Location, Spatial or Environmental Inputs Are Incomplete
OSS licensing is project-specific. The same KBLI can follow a different practical route when the location, land status, building use, industrial-estate position, production process or environmental impact changes. A head-office address should not automatically be reused as the operational site if the project takes place elsewhere.
Confirm the complete address, coordinates where required, control of the premises, zoning or spatial position, building use and environmental pathway. A data-entry correction cannot cure an unsuitable site or missing project approval. Manufacturing and industrial projects deserve a joined-up review of business licensing, spatial compatibility, environmental approval, construction readiness and sector standards. IndoGateway’s environmental approval guide and industrial business licensing service provide further context.
6. The Main Licence Exists, but Supporting Approvals Are Missing
OSS distinguishes the main business licence from licences supporting business activities, commonly called PB-UMKU. Depending on the activity, product and operating model, a company may also need approvals connected with imports, product registration, standards, distribution, employment, immigration or sector supervision.
Do not assume that every dependency appears automatically or becomes effective at the same time. Build an approval matrix for each activity that identifies the main OSS output, supporting licences, issuing authority, prerequisite and operating milestone. For example, an importer may need to coordinate its business activity with customs and product rules, while a manufacturer may face site, environmental, industrial and product workstreams.
The official OSS PB-UMKU guidance is the correct starting point for the system process. For an integrated internal review, use the Indonesia licence checker and verify conclusions against current official requirements.
7. Investment, Capacity, Product or Project Data Is Inconsistent
OSS uses project data to route an application. Inconsistent entries can produce unexpected scale validation, risk analysis or licence requirements. Common examples include an activity description that conflicts with the selected KBLI, capacity expressed in the wrong unit, products that do not match the business line, or an investment plan that is not coordinated with the company’s actual project.
Prepare one controlled project-data sheet before entering information. It should cover the entity, KBLI, activity description, location, land and building use, products or services, capacity, planned investment, workforce and expected operating model. The finance, legal, operations and licensing teams should work from the same version.
When a substantive project field changes, use the official change route and determine whether the change triggers renewed fulfilment or verification. OSS guidance for business-data changes distinguishes fields that may require verification from administrative updates that may not. Preserve the old documents, submission receipts and an explanation of what changed.
8. A KBLI Transition or Company Amendment Has Not Been Handled Correctly
KBLI 2025 implementation created a transition question for existing companies. BPS guidance states that the new classification does not, by itself, require businesses to obtain new licences. Where there is no substantive business change, conversion can be handled through the government implementation mechanism; a substantive change to the company’s purposes or activity scope may require corporate and OSS action.
Separate a classification conversion from a genuine expansion. If the company is adding a new service, product line, manufacturing process or commercial role, analyze the new activity on its own merits. Check corporate purposes, foreign-investment eligibility, risk, location and supporting approvals before changing OSS. The official BPS conversion-table announcement is a useful reference, while IndoGateway’s guide to changing KBLI codes explains the decision path.
9. Account Access or a Technical Validation Error Blocks the Process
Some cases are genuinely technical: an inactive email address, unavailable one-time password, incorrect access role, browser-session problem or data synchronization delay can block progress. Use the official OSS access and account-recovery guidance, capture the full message, and record the time, user, menu path and activity affected.
Before escalating, confirm that the problem persists with the correct authorized account and that the underlying entity data is current. Avoid repeatedly submitting variations of regulated facts simply to make the screen advance. If the issue appears to be synchronization between systems, retain proof of the approved source record and use the official OSS support channels shown on the portal.
A Practical OSS Troubleshooting Process
- Freeze the facts. Record the exact error, affected KBLI, project location, licence status and last successful step.
- Classify the problem. Decide whether it concerns access, corporate data, activity classification, ownership, project data, location, risk output or a supporting approval.
- Identify the authoritative record. Determine whether the correction belongs in the corporate administration system, OSS, tax record or a sector authority’s process.
- Check the current legal route. Review Government Regulation No. 28 of 2025, the applicable OSS guidance, the current KBLI and relevant investment or sector rules.
- Correct the source first. Complete any required corporate or project amendment before attempting downstream synchronization.
- Reprocess only the affected activity. Avoid changing unrelated licences or entity data.
- Download and compare outputs. Verify names, addresses, KBLI codes, locations, statuses and outstanding obligations.
- Run an operating-readiness review. Confirm supporting approvals and implementation conditions before launch.
Documents and Information to Prepare Before Troubleshooting
- Latest deed and Ministry of Law approval or notification
- Company tax identification and registered address records
- Shareholder, director and commissioner information
- Proposed and existing KBLI list with plain-English activity descriptions
- Project addresses, premises documents and site-use information
- Products, services, capacity and operating-process summary
- Investment plan and project schedule used in the application
- Existing NIB, Standard Certificates, licences and PB-UMKU documents
- Environmental, spatial, construction, product, import or sector approvals where relevant
- Screenshots, submission receipts and correspondence relating to the error
How to Decide Whether the Company Is Ready to Operate
Use a three-part test. First, confirm corporate authority: the company’s approved purposes and governance must support the activity. Second, confirm licensing effectiveness: the correct activity and location must have the required risk-based output and completed fulfilment status. Third, confirm operational dependencies: premises, environmental, product, import, workforce and sector approvals must be ready where applicable.
If any part remains unclear, treat the company as not yet cleared for that activity and obtain a focused review. This does not mean every unresolved dashboard item prevents every operation. It means the decision should be made for the particular KBLI, location and commercial step, using the underlying requirements rather than a general impression that the OSS profile looks complete.
Frequently Asked Questions
1. Can a foreign-owned company obtain an NIB through OSS?
Yes. An Indonesian foreign-investment company can obtain an NIB through OSS after the legal entity and required data are properly established and validated. However, the NIB identifies the business and forms part of the licensing process; it does not automatically confirm that every activity is open to the proposed foreign ownership or that all operating conditions are complete. Each KBLI should be checked for investment eligibility, risk level, location dependencies and supporting approvals. The appropriate sequence also depends on the company’s legal form, corporate record and actual project.
2. Why does OSS show company information that is different from the latest deed?
The difference may arise because the corporate amendment has not been completed in the authoritative corporate system, has not synchronized, or requires a specific OSS change workflow. Compare the latest deed with the Ministry approval or notification and confirm that names, officers, shareholders, address and business purposes are correctly recorded at source. Then use the relevant OSS update process. Do not overwrite unrelated information to force a match. If the authoritative record is correct but OSS remains outdated, document the discrepancy and escalate it through official OSS support with supporting evidence.
3. Does an issued NIB mean a PT PMA can immediately start operating?
Not necessarily. Whether operations may begin depends on the risk-based licensing output for the specific activity and whether any required standards, licence verification, basic requirements or supporting approvals have been completed. A low-risk activity may have a simpler route, while medium-high or high-risk activities can require additional fulfilment before the relevant output becomes effective. Product registration, import, environmental, construction, workforce or sector approvals may also be separate dependencies. Review the status of each KBLI and project location rather than treating the NIB as universal operating clearance.
4. What should a company do if the wrong KBLI was selected?
First determine whether the problem is a classification error or a substantive change in the business. Map the actual products, services, customers, revenue model and operating process to the current KBLI descriptions. Then check corporate purposes, foreign-investment eligibility, risk classification and supporting requirements for the correct code. A company amendment may be required if the activity is outside the approved corporate scope. Use the formal OSS change pathway and assess any effect on existing licences. Do not simply add a convenient code without reviewing its legal and operational consequences.
5. Why is a Standard Certificate shown as unverified or incomplete?
The status may indicate that the activity requires fulfilment of business standards, submission of supporting documents or verification by the responsible authority before the certificate is effective for the intended operation. Check the activity’s risk level, the exact status language, outstanding requirements and the responsible authority displayed in OSS. Also confirm that project location and basic approvals are complete. The remedy depends on the missing substantive requirement, not merely on downloading the certificate again. Keep evidence of submissions and follow the official process for the affected KBLI and project.
6. Can one PT PMA use OSS for several KBLI activities and locations?
Yes, one company and NIB can cover more than one business activity, but each activity and project location must be assessed separately. Different KBLIs can have different foreign-ownership positions, risk levels, licensing outputs, authorities and supporting approvals. A new location can also introduce spatial, environmental, building or regional dependencies that do not apply at the head office. Maintain an activity-location matrix showing the corporate basis, investment eligibility, OSS status and supporting requirements for every combination. This makes gaps visible and reduces the risk of assuming one completed licence covers the entire business.
7. How should an existing company handle the transition to KBLI 2025?
Start by distinguishing a classification conversion from a change in actual business. Official BPS implementation information states that KBLI 2025 does not, by itself, require businesses to obtain new licences, and conversion mechanisms have been prepared. If the company’s activity is unchanged, review the official mapping and confirm how its records are converted. If the company is changing its purposes, products, services or operating model, treat that as a substantive amendment and reassess corporate documents, foreign-investment eligibility and licensing. Preserve prior licences and document the basis for any update.
8. When should a foreign company seek professional help with OSS?
Specialist review is advisable when the issue affects foreign-ownership eligibility, corporate purposes, a medium-high or high-risk licence, land or environmental approval, regulated products, imports, manufacturing, construction, or the legal ability to operate. It is also useful when government systems show conflicting records or an amendment may affect existing licences. Prepare a concise evidence pack before seeking help: the exact error, company documents, KBLI and location list, OSS outputs, project facts and prior correspondence. A focused review is faster and more reliable than repeatedly changing data without a diagnosis.
Conclusion
OSS problems become manageable when the company stops treating them as isolated screen errors. The correct diagnosis starts with the legal entity, then moves through KBLI selection, foreign-investment eligibility, project data, location, risk-based outputs and supporting approvals. Aligning those layers is more important than completing fields quickly.
For a foreign-owned company, the safest outcome is a reconciled record: the deed, Ministry data, OSS profile, issued documents and real operating model should all tell the same story. That alignment supports licensing, future amendments, supervision and day-to-day compliance.
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.
Resolve Your OSS Licensing Issues with a Structured Review
IndoGateway can help your team reconcile corporate data, KBLI activities, OSS outputs and the supporting approvals connected with your Indonesia project. Start with a documented review of the exact activity, ownership structure, location and operating model.
Contact IndoGateway to discuss an OSS licensing assessment for your foreign-owned company.
