Add a PT PMA KBLI Without Disrupting Existing Licenses

A PT PMA should add a KBLI through a separate change workstream that preserves existing OSS projects and licence evidence. Classify the new activity under KBLI 2025, screen foreign ownership and investment, confirm whether the deed must change, create the correct activity-location project, and obtain the required licence state before operating it. The official OSS guide is a workflow reference, not a substitute for the legal and licence impact review.

The team should inventory existing codes, locations, licence conditions, customers, and reporting before touching live data. Avoid replacing an existing activity, reusing the wrong project, or allowing the new code to inherit unsupported premises or scale assumptions. Define a filing window, screenshots and exports, acceptance tests, operating stop, and rollback or correction route so valid operations remain traceable throughout the update.

Pt pma kbli addition decision controls

Use the control, evidence, and release condition together; no single document should carry more meaning than it actually proves.

Key takeaways

• Approve only a genuine near-term activity with a documented boundary.
• Resolve structural dependencies before entering the activity in OSS.
• Use unique project identifiers and a no-change list for existing operations.
• Keep the new activity blocked until its complete licence state is effective.
• Release only from signed new-activity evidence and a successful continuity check.

In this article

• Approve the new KBLI
• Screen structural impacts
• Protect existing licences
• Create the new project
• Official References and Review Basis
• Regulatory Notes and Limitations
• Release and review
• Release the new PT PMA activity without rewriting the old licence history

Approve the new activity from KBLI 2025 facts

Before the next commitment, management should describe the new revenue model and select the current code with rejected alternatives. For approve the new activity from kbli 2025 facts, the classification must follow the real economic activity under current KBLI 2025 materials and then be tested against ownership, investment, location, and licensing consequences.

A future-looking label can be added without a real operating case or proper classification. A reviewer should trace operating narrative and kbli 2025 comparison to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For approve the new activity from kbli 2025 facts, a defensible review separates facts already evidenced, facts requested but not received, assumptions approved for planning, and conditions that still block release. It should connect operating narrative with kbli 2025 comparison, then show how rejected alternatives and launch and review triggers affect the next approval. Record the source for operating narrative, the reviewer of kbli 2025 comparison, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test approve the new activity from kbli 2025 facts through normal progress, delayed kbli 2025 comparison, and failure of rejected alternatives. The normal case confirms the intended order for operating narrative; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for launch and review triggers. Retain this stage-specific result with the final approval and review calendar.

• Operating narrative
• KBLI 2025 comparison
• Rejected alternatives
• Launch and review triggers

For approve the new activity from kbli 2025 facts, record both the accepted position and the rejected alternatives; this prevents a later portal edit or provider message from silently changing the decision.

Screen ownership, investment, deed, and tax impacts

The control file must show how the company will test the new code against foreign-investment conditions, investment plan, corporate purpose, capital, and tax model. For screen ownership, investment, deed, and tax impacts, the classification must follow the real economic activity under current KBLI 2025 materials and then be tested against ownership, investment, location, and licensing consequences.

A code can fit semantically while conflicting with ownership or the approved structure. A reviewer should trace perpres business-field screen and investment plan by code and location to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For screen ownership, investment, deed, and tax impacts, the practical deliverable is a version-controlled decision row that remains usable when the activity, location, counterparty, or responsible person changes. It should connect perpres business-field screen with investment plan by code and location, then show how deed-purpose review and tax and accounting impact affect the next approval. Record the source for perpres business-field screen, the reviewer of investment plan by code and location, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test screen ownership, investment, deed, and tax impacts through normal progress, delayed investment plan by code and location, and failure of deed-purpose review. The normal case confirms the intended order for perpres business-field screen; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for tax and accounting impact. Retain this stage-specific result with the final approval and review calendar.

• Perpres business-field screen
• Investment plan by code and location
• Deed-purpose review
• Tax and accounting impact

For screen ownership, investment, deed, and tax impacts, close the stage only when the authoritative record and the operating evidence agree, or when an unresolved difference has a named owner and stop condition. Where this stage changes another workstream, review Foreign Ownership Changes When a PT PMA Adds a New KBLI .

Protect existing projects and licence evidence

For PT PMA KBLI addition, export every existing activity, project, location, output, verification, and condition before filing. For protect existing projects and licence evidence, the classification must follow the real economic activity under current KBLI 2025 materials and then be tested against ownership, investment, location, and licensing consequences.

A mistaken replacement or location assignment can disturb licences that were not meant to change. A reviewer should trace existing project register and before-change oss exports to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For protect existing projects and licence evidence, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect existing project register with before-change oss exports, then show how no-change licence list and affected and unaffected customer map affect the next approval. Record the source for existing project register, the reviewer of before-change oss exports, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test protect existing projects and licence evidence through normal progress, delayed before-change oss exports, and failure of no-change licence list. The normal case confirms the intended order for existing project register; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for affected and unaffected customer map. Retain this stage-specific result with the final approval and review calendar.

• Existing project register
• Before-change OSS exports
• No-change licence list
• Affected and unaffected customer map

For protect existing projects and licence evidence, the output should name the owner, source evidence, unresolved condition, acceptance test, and the event that permits the next step. For the adjacent control framework, compare Adding Business Activities to a PT PMA .

Create and license the new activity-location project

The responsible team should enter the approved code, location, scale, investment, and required data, then complete its licence and supporting approvals. For create and license the new activity-location project, the classification must follow the real economic activity under current KBLI 2025 materials and then be tested against ownership, investment, location, and licensing consequences.

A newly visible code does not mean the project is verified or operational. A reviewer should trace oss submission evidence and risk and licence output to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For create and license the new activity-location project, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect oss submission evidence with risk and licence output, then show how premises and supporting approvals and verification and condition register affect the next approval. Record the source for oss submission evidence, the reviewer of risk and licence output, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test create and license the new activity-location project through normal progress, delayed risk and licence output, and failure of premises and supporting approvals. The normal case confirms the intended order for oss submission evidence; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for verification and condition register. Retain this stage-specific result with the final approval and review calendar.

• OSS submission evidence
• Risk and licence output
• Premises and supporting approvals
• Verification and condition register

For create and license the new activity-location project, preserve the source record, reviewer, date, exception, and approval so another team can reproduce the decision without relying on memory.

Official References and Review Basis

Primary materials for Add a PT PMA KBLI Without Disrupting Existing Licenses were checked on August 4, 2026 and support this page's framework; they do not replace a matter-specific legal, tax, licensing, accounting, security, premises, or bank review of Add a PT PMA KBLI Without Disrupting Existing Licenses.

• OSS guide to adding a business field and mapping a location : Official workflow reference for adding an activity and using the location map.
• BPS KBLI 2020–2025 conversion table : Official correspondence table for reviewing changes between KBLI 2020 and KBLI 2025.
• Presidential Regulation No. 10 of 2021 : Investment business-field framework, as amended.
• Presidential Regulation No. 49 of 2021 : Current amendment to the investment business-field framework.
• Government Regulation No. 28 of 2025 : Current risk-based business licensing framework; it revoked Government Regulation No. 5 of 2021.
• Ministry of Investment and Downstream Industry/BKPM Regulation No. 5 of 2025 : Current OSS procedures, investment facilities, supervision, and reporting framework.

Regulatory Notes and Limitations

Add a PT PMA KBLI Without Disrupting Existing Licenses provides a decision and evidence framework, not a universal legal opinion. Review the current official output and company-specific facts before filing, contracting, paying, or operating.

• For Add a PT PMA KBLI Without Disrupting Existing Licenses, kBLI classification describes economic activity; it does not by itself prove foreign-ownership eligibility, premises suitability, or completion of every licence condition.
• For Add a PT PMA KBLI Without Disrupting Existing Licenses, kBLI 2025 and the official 2020–2025 correspondence table must be reviewed against the actual product, service, customer, delivery model, and location.
• For Add a PT PMA KBLI Without Disrupting Existing Licenses, changing an activity can affect investment, licensing, tax, customs, employment, environmental, building, and bank records, so each function should confirm its own field.

Release the new activity and review continuity

A supportable decision begins when the company can reconcile final records, update tax, bank, contracts, reporting, and operating instructions, and sample existing licences after cutover. For release the new activity and review continuity, the classification must follow the real economic activity under current KBLI 2025 materials and then be tested against ownership, investment, location, and licensing consequences.

The new code may be correct while downstream systems or old projects were inadvertently changed. A reviewer should trace final activity and project exports and dependent update acceptances to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For release the new activity and review continuity, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect final activity and project exports with dependent update acceptances, then show how operating release memo and post-cutover sample review affect the next approval. Record the source for final activity and project exports, the reviewer of dependent update acceptances, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test release the new activity and review continuity through normal progress, delayed dependent update acceptances, and failure of operating release memo. The normal case confirms the intended order for final activity and project exports; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for post-cutover sample review. Retain this stage-specific result with the final approval and review calendar.

• Final activity and project exports
• Dependent update acceptances
• Operating release memo
• Post-cutover sample review

For release the new activity and review continuity, turn the result into a controlled work item with a responsible person, due date, evidence location, escalation path, and release condition.

Use the Indonesia company registration service scope to coordinate each deed, OSS, licensing, banking, or post-registration dependency identified for pt pma kbli addition.

Release the new PT PMA activity without rewriting the old licence history

Treat the added KBLI as a controlled new project with its own facts, ownership screen, investment logic, location, licence state, and operating release. Preserve existing records as the baseline.

After cutover, verify both the new activity and a sample of unaffected projects so a successful addition does not hide damage to valid licences.

Related insights

• Adding Business Activities to a PT PMA
• Foreign Ownership Changes When a PT PMA Adds a New KBLI
• PT PMA License Condition Tracker After Registration