When an Indonesian company changes what it sells, produces, distributes, or delivers, updating a marketing description is not enough. The company may need to align its corporate purpose, KBLI classification, OSS project data, risk-based business licensing, site approvals, and supporting sector permits. The practical challenge is identifying which records are affected before the new activity starts.
This guide explains how to approach a business license amendment in Indonesia when activities change. It is written for foreign-owned companies and regional teams that need a controlled, evidence-based amendment process rather than a rushed OSS edit.
Key Takeaways
- A change in commercial activity should first be translated into the correct KBLI scope; the product name or internal business-unit label is not the licensing classification.
- An OSS data update, a new business activity, and a corporate deed amendment are different workstreams, although one project may require all three.
- Each added activity can have its own risk level, business license, Standard Certificate, basic requirements, and sector-specific supporting approvals.
- The NIB is an important business identity, but it should not be treated as automatic evidence that every amended activity is ready for commercial operation.
- Foreign ownership, project location, products, facilities, import functions, workforce, and sector rules should be checked before the company commits to the change.
- A defensible amendment file records the old position, the intended new operating model, the approvals affected, and the evidence that each requirement has been completed.
What Counts as a Business Activity Change?
A business activity change is broader than a formal change of company name or address. It can occur when a company begins manufacturing goods that it previously imported, starts selling directly instead of supplying through a distributor, adds installation or maintenance services, opens a new operating location, introduces a digital marketplace function, or expands from advisory work into a separately regulated professional service.
The first question is not simply, “Which field should we edit in OSS?” It is, “What will the company actually do, for whom, with which assets, at which location, and under which commercial model?” Those facts determine whether the existing KBLI description still covers the activity or whether a new classification and licensing route should be assessed.
Indonesia’s current risk-based licensing framework is governed at a high level by Government Regulation No. 28 of 2025. The framework evaluates licensing by business activity and risk. This activity-level approach is why a company can hold one NIB while different activities under that company follow different licensing paths.
Three Amendment Routes That Companies Often Confuse
1. Updating Data for an Existing Activity
An existing licensed activity may continue, but project information may change. Examples include the project name, operating status, investment data, workforce data, or other fields made available in the relevant OSS amendment workflow. The current OSS guide to changing business data shows users selecting the relevant business activity and location before reviewing and saving amended information.
This route should not be used to disguise a materially different activity as a minor data correction. If the revenue model, goods, services, production process, customer role, or regulated function changes, the company should reassess the KBLI and licensing position rather than assuming that an existing project record remains sufficient.
2. Adding, Replacing, or Reclassifying a KBLI Activity
A company may need to add a new KBLI when the intended activity is outside the existing scope. The assessment should use the wording and coverage of the classification, not only the five-digit code or title. Indonesia’s move from KBLI 2020 to KBLI 2025 also means that a historical code may be unchanged, renumbered, split, combined, or reorganized. The official OSS KBLI conversion guidance expressly treats the conversion information as a reference rather than a legal decision and tells users to inspect the applicable activity description.
Adding an activity can trigger a fresh risk-based licensing output for that activity. Depending on its assigned risk and applicable standards, the route may involve an NIB, a Standard Certificate, a business license, verification, basic requirements, or supporting approvals. The exact output should be confirmed using the current OSS record and sector rules for the selected activity and project facts.
3. Amending Corporate Records
If the new activity is not covered by the company’s approved purposes and objectives, an OSS change may need to be preceded or accompanied by a corporate amendment. The required corporate action depends on the existing deed, articles, shareholder approvals, and the nature of the change. Data consistency matters because OSS relies on connected business-entity information and because regulators, banks, counterparties, auditors, and tender authorities may compare the corporate and licensing records.
Companies should therefore review the latest deed and Ministry of Law record before modifying activities in OSS. A notarial or corporate step should not be assumed in every case, but it should be resolved where the approved corporate scope does not support the intended activity.
When Is a Business License Amendment in Indonesia Likely to Be Needed?
An amendment assessment is appropriate whenever a change could affect the legal description, risk profile, location, or regulatory dependencies of the business. Common triggers include:
- adding manufacturing to an import or distribution company;
- moving from wholesale to retail, direct-to-consumer, or marketplace operations;
- adding installation, maintenance, testing, construction, or technical services;
- expanding into a regulated product category or professional service;
- opening a factory, warehouse, restaurant, office, or other operating site;
- changing a production process, capacity, land footprint, or environmental profile;
- adding import, export, logistics, payment, electronic-system, or digital intermediation functions;
- changing from a supporting activity to a revenue-generating line of business; or
- converting an old KBLI reference where the new classification changes the applicable scope.
A change does not always mean the old license should be replaced. One activity may remain active while another is added. In other cases, a discontinued activity may require a separate cancellation or revocation workflow rather than merely disappearing from an edited description. The appropriate treatment depends on the company’s intended portfolio and the status of each existing approval.
How to Amend Business Licenses When Activities Change
Step 1: Write the New Operating Model in Plain Language
Document the goods or services, revenue flow, contractual role, customers, suppliers, inventory ownership, production steps, digital functions, locations, equipment, employees, imported inputs, and supporting services. This operating narrative becomes the basis for classification and prevents a code from being selected only because its title sounds convenient.
Step 2: Map the Model to KBLI 2025
Compare the activity against the official KBLI wording and the current OSS directory. Review inclusions, exclusions, and adjacent codes. Where an old code is involved, use the official KBLI 2020-to-2025 conversion tool as a starting point, then validate the substantive scope. A split or reorganized code may require the company to choose among several new activities rather than perform a mechanical one-for-one replacement.
Step 3: Check Foreign-Investment Eligibility
For a PT PMA, the ownership analysis should be completed for each proposed activity before the amendment is filed. Eligibility may depend on the precise KBLI, investor profile, sector, business scale, partnership conditions, or other rules. Do not assume that an activity is open to foreign investment because another activity in the same company is permitted.
Step 4: Align the Corporate Scope
Compare the proposed activity with the company’s deed, articles, Ministry of Law data, tax profile, and internal approvals. Determine whether a shareholder resolution, notarial amendment, Ministry of Law filing, or other corporate update is required. Sequence this work so the source corporate data and the OSS filing do not contradict one another.
Step 5: Review Location and Basic Requirements
Assess the new activity at its actual site. Spatial-use conformity, environmental documents, building approvals, land or tenancy evidence, and sector-specific facility conditions may be relevant. An activity that is valid in principle can still face a location or facility barrier. For practical scoping, IndoGateway’s Indonesia licence checker can help organize the questions that need formal verification.
Step 6: Submit the Correct OSS Change
Use the current OSS menu for the relevant action, such as changing business data or managing the company’s business activities. Select the correct activity and location, review old and new data, complete the declarations, and retain the transaction evidence. Interface labels and available fields can change, so teams should follow the live OSS guidance rather than an outdated screenshot or internal checklist.
Step 7: Complete Activity-Level Outputs and Supporting Approvals
After the OSS change, review the result for every affected activity. The official PB UMKU directory illustrates the wide range of supporting approvals connected to specific sectors and activities. Product registrations, import permissions, professional authorizations, technical certificates, environmental approvals, or other sector processes may sit alongside the main risk-based license.
Step 8: Verify Operational Readiness Before Launch
Do not stop when an updated NIB can be downloaded. Confirm that every required certificate or license has the correct status, any verification is complete, basic requirements are satisfied, and operational evidence is available. Update contracts, invoices, standard operating procedures, websites, labels, tax configurations, customs arrangements, employment plans, and compliance calendars where the new activity affects them.
What Happens to the Existing NIB?
A company should not assume that every activity amendment creates an entirely new business identity. The practical OSS result depends on the type of change and the existing entity record. The NIB remains central to the business identity, while individual activities and their licensing outputs can be added, changed, verified, or discontinued within the wider record.
The safer control is to compare the updated documents with the pre-amendment set. Check the company name and identity, listed KBLI activities, project locations, risk outputs, license statuses, and supporting approvals. If the amendment changes importer, customs, product, facility, or sector functions, confirm whether separate systems or registrations must also be updated.
Why Amending OSS Alone May Not Be Enough
OSS is the central electronic licensing system, but a business change can reach beyond the OSS record. A manufacturing expansion can affect industrial, environmental, building, product, and import workstreams. A new e-commerce function can affect electronic-system, trade, consumer, payment, and data obligations. A regulated professional service can depend on individual qualifications, sector registration, or organizational approvals.
This is why the licensing amendment should be managed as a cross-functional project. Legal, tax, finance, operations, property, HR, customs, product, IT, and compliance teams should work from the same activity description. IndoGateway’s NIB and OSS business licensing service and sector licence support cover these connected workstreams.
Common Amendment Mistakes
- Selecting a code by title only. A familiar label may not cover the actual product, service, customer role, or production process.
- Treating a data correction as a new-activity approval. Editing an existing project record does not necessarily authorize a materially different activity.
- Ignoring corporate documents. An OSS record that is broader than the approved corporate purpose creates an avoidable consistency problem.
- Assuming one risk outcome applies to the whole company. Risk-based licensing is activity-specific, and different sites or functions can produce different requirements.
- Forgetting foreign-ownership review. A PT PMA must assess the proposed activity on its own facts before adding it.
- Launching after NIB update alone. Supporting approvals, verification, location requirements, and sector conditions may still be outstanding.
- Deleting historical evidence. Keep the old licenses, amendment submissions, updated outputs, approvals, and internal decision record together.
A Practical Pre-Filing Checklist
| Workstream | Question to Resolve | Evidence to Retain |
|---|---|---|
| Operating model | What exactly will the company do differently? | Approved activity narrative and process map |
| KBLI | Which current classification covers each revenue activity? | Code analysis, scope wording, and conversion notes |
| Investment | Is each activity compatible with the ownership and investor profile? | Current activity-specific eligibility review |
| Corporate | Does the approved corporate purpose cover the activity? | Deed, resolutions, notarial documents, and official record |
| Location | Can the activity operate at the proposed site? | Spatial, environmental, building, and premises documents |
| OSS licensing | What output and status apply to each activity? | NIB, certificates, licenses, submissions, and status records |
| Sector approvals | Are PB UMKU, product, import, technical, or professional approvals needed? | Issued approvals and verification evidence |
| Operations | Are systems, contracts, tax, workforce, and compliance controls aligned? | Launch checklist and accountable owners |
Frequently Asked Questions
1. Can a company add a new business activity to its existing NIB?
A company can generally manage more than one business activity within its OSS record, but adding an activity is not merely an administrative label change. The proposed activity should be mapped to the correct current KBLI, checked against the company’s corporate purpose and foreign-investment position, and processed through the applicable OSS route. The added activity may generate its own risk-based license, Standard Certificate, verification requirement, basic requirements, or supporting approvals. Operational launch should wait until the complete activity-level output has been reviewed.
2. Does changing a KBLI code always require a deed amendment?
No universal answer applies. A corporate amendment may be required when the intended activity is outside the purposes and objectives already approved in the company’s deed and official entity record. A code conversion or data alignment may present a different situation if the substantive activity remains within the approved scope. The company should compare the old and new KBLI descriptions with its latest deed, articles, and Ministry of Law data. The notary and regulatory team should resolve the corporate sequence before inconsistent OSS data is filed.
3. Can the company start the new activity as soon as OSS shows the updated NIB?
Not necessarily. An updated NIB confirms an important part of the business record, but operating readiness depends on the output for the specific activity. A medium-risk activity may involve a Standard Certificate and, where applicable, verification; a high-risk activity may require a license. Basic requirements, location conditions, environmental or building matters, product approvals, PB UMKU, import permissions, or professional authorizations may also apply. The company should review the status and evidence for every requirement before beginning commercial operations or signing launch commitments.
4. What if the company changes from trading to manufacturing?
Moving from trading to manufacturing is usually a material operating-model change and should be assessed as more than an OSS data edit. Manufacturing classification depends on the actual transformation process and products, while the project may introduce industrial, location, environmental, building, machinery, workforce, raw-material, import, and product-compliance issues. Foreign-investment eligibility and corporate scope should also be checked for the manufacturing activity. The company should map the factory project comprehensively, obtain the applicable activity-level outputs, and verify site readiness before production begins.
5. How should a company handle the KBLI 2020-to-2025 transition during an amendment?
Start with the official OSS conversion tool, but do not treat its mapping as the final legal conclusion. A code may remain the same, change one-to-one, split, merge, or be reorganized. Read the current KBLI 2025 scope for the company’s actual goods, services, and operating role, then compare it with the historical activity and corporate documents. If a former code splits into several new codes, the company may need to identify which current activities genuinely apply and evaluate the licensing consequences of each selection.
6. Will adding an activity change the licenses for existing activities?
It may or may not. Existing activities can remain valid while a new activity receives a separate licensing output, but the broader project should be reviewed for shared locations, facilities, environmental impacts, products, supporting approvals, and corporate data. A change to the site, production process, scale, or operating model can affect more than the newly added code. Preserve the existing approvals, compare them with the updated OSS record, and identify whether any consequential updates are required rather than assuming that all prior licenses automatically change or remain untouched.
7. How long does a business license amendment take in Indonesia?
There is no reliable universal timeline. The duration depends on the type of amendment, quality and consistency of source data, corporate approvals, KBLI analysis, OSS risk output, location, basic requirements, sector verification, supporting approvals, and government review. A simple permitted data update is different from adding a manufacturing project or regulated service. Planning should use a dependency-based schedule with separate owners for corporate, OSS, property, environmental, technical, product, import, and sector tasks rather than promising one standard completion period to management.
8. What records should be kept after the amendment is completed?
Keep the pre-amendment licenses, approved operating-model description, KBLI analysis, ownership review, corporate resolutions and deeds, Ministry of Law evidence, OSS submissions, declarations, updated NIB, activity-level certificates or licenses, verification records, basic-requirement documents, PB UMKU and sector approvals, and internal launch authorization. Also retain screenshots or receipts showing key submission statuses where appropriate. A consolidated record helps management demonstrate why the classification was selected, confirm what remains pending, support audits, and prevent later teams from relying on an incomplete document set.
Conclusion
A business license amendment in Indonesia should begin with the changed operating facts, not with an OSS menu. Define the new activity, map it to KBLI 2025, confirm foreign-investment and corporate alignment, evaluate the site, submit the correct OSS change, and complete every activity-specific and supporting approval. This sequence reduces the risk of a company appearing updated on paper while remaining unready to operate.
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 License Amendment with IndoGateway
IndoGateway can help your team translate an activity change into a coordinated corporate, KBLI, OSS, location, and sector-licensing work plan. Contact IndoGateway to review the intended operating model and identify the approvals that should be resolved before launch.
