Indonesia KBLI Selection Memo: Evidence to Approve Codes Before Filing
Turn products, services, customers, delivery, assets, people, and locations into a documented KBLI 2025 decision with downstream impact checks.
A defensible KBLI selection memo begins with the real operating model and ends with an approved code, rejected alternatives, and downstream consequences. Use BPS KBLI 2025 materials and the official 2020–2025 correspondence table where legacy records are involved, then test foreign-investment conditions, project location, risk-based licences, investment planning, premises, tax, customs, employment, and banking before filing.
Do not choose a code from a keyword, competitor record, provider package, or expected customer label. The memo should describe what the company sells, to whom, how value is created and delivered, which assets and personnel are used, where each step occurs, and which regulated features apply. If one code cannot accurately cover the model, separate activities and identify the legal, operational, and investment consequences of each.
Kbli selection memo decision controls
Use the control, evidence, and release condition together; no single document should carry more meaning than it actually proves.
| Control stage | Question to resolve | Evidence anchor |
|---|---|---|
| Write the operating facts without KBLI language | document products, services, customers, pricing, delivery, assets, staff, suppliers, and locations in plain operational language | Product and service catalogue |
| Compare current KBLI 2025 candidates | match the facts to official descriptions, inclusions, exclusions, hierarchy, and 2020–2025 correspondence | Official KBLI descriptions |
| Record rejected codes and boundary cases | explain why plausible alternatives do not fit and identify any mixed or future activity outside the initial filing | Rejected-code rationale |
| Test ownership, investment, location, and licence effects | screen each selected code against foreign-ownership rules, investment calculation, OSS risk output, project location, premises, and sector approvals | Perpres investment-field screen |
| Approve and version-control the memo | obtain accountable legal, licensing, commercial, and executive approvals and link the memo to deed and OSS inputs | Named preparer and reviewers |
In this article
Key takeaways
- Freeze the factual narrative before comparing candidate codes.
- Approve only candidates that cover the material value-creating activity.
- Keep uncertain or future activity outside launch until separately approved.
- Resolve material downstream blockers before including the code in the filing set.
- File only the approved version and reopen it when the operating model changes.
Scope the KBLI selection memo before acting
Share the company facts, intended outcome, current records, and unresolved conditions so the KBLI selection memo review can be bounded.
Write the operating facts without KBLI language
Before the next commitment, management should document products, services, customers, pricing, delivery, assets, staff, suppliers, and locations in plain operational language. For write the operating facts without kbli language, the classification must follow the real economic activity under current KBLI 2025 materials and then be tested against ownership, investment, location, and licensing consequences.
Starting with code titles encourages the team to bend the facts around a preferred answer. A reviewer should trace product and service catalogue and customer and revenue model to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For write the operating facts without kbli language, 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 product and service catalogue with customer and revenue model, then show how process, assets, and people map and location and delivery flow affect the next approval. Record the source for product and service catalogue, the reviewer of customer and revenue model, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Control point
Freeze the factual narrative before comparing candidate codes.
- Product and service catalogue
- Customer and revenue model
- Process, assets, and people map
- Location and delivery flow
For write the operating facts without kbli language, record both the accepted position and the rejected alternatives; this prevents a later portal edit or provider message from silently changing the decision. For the adjacent control framework, compare Choosing KBLI Codes for PT PMA Registration .
Compare current KBLI 2025 candidates
The control file must show how the company will match the facts to official descriptions, inclusions, exclusions, hierarchy, and 2020–2025 correspondence. For compare current kbli 2025 candidates, the classification must follow the real economic activity under current KBLI 2025 materials and then be tested against ownership, investment, location, and licensing consequences.
Similar titles can represent different economic functions such as production, trade, agency, software, or consulting. A reviewer should trace official kbli descriptions and candidate comparison table to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For compare current kbli 2025 candidates, the practical deliverable is a version-controlled decision row that remains usable when the activity, location, counterparty, or responsible person changes. It should connect official kbli descriptions with candidate comparison table, then show how legacy-code correspondence and questions requiring authority confirmation affect the next approval. Record the source for official kbli descriptions, the reviewer of candidate comparison table, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Release test
Approve only candidates that cover the material value-creating activity.
- Official KBLI descriptions
- Candidate comparison table
- Legacy-code correspondence
- Questions requiring authority confirmation
For compare current kbli 2025 candidates, 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 How to Check Whether an Indonesia KBLI Allows 100% Foreign Ownership .
Test the KBLI selection memo evidence
Reconcile the authoritative, operational, contractual, tax, banking, and evidence fields that affect the KBLI selection memo decision.
Record rejected codes and boundary cases
For KBLI selection memo, explain why plausible alternatives do not fit and identify any mixed or future activity outside the initial filing. For record rejected codes and boundary cases, the classification must follow the real economic activity under current KBLI 2025 materials and then be tested against ownership, investment, location, and licensing consequences.
Without rejected alternatives, later teams may reintroduce a code based on the same superficial keyword. A reviewer should trace rejected-code rationale and mixed-activity boundary to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For record rejected codes and boundary cases, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect rejected-code rationale with mixed-activity boundary, then show how future expansion list and assumptions and review triggers affect the next approval. Record the source for rejected-code rationale, the reviewer of mixed-activity boundary, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Stop condition
Keep uncertain or future activity outside launch until separately approved.
- Rejected-code rationale
- Mixed-activity boundary
- Future expansion list
- Assumptions and review triggers
For record rejected codes and boundary cases, the output should name the owner, source evidence, unresolved condition, acceptance test, and the event that permits the next step.
Test ownership, investment, location, and licence effects
The responsible team should screen each selected code against foreign-ownership rules, investment calculation, OSS risk output, project location, premises, and sector approvals. For test ownership, investment, location, and licence effects, 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 semantically accurate code can still be unsuitable for the proposed structure or site. A reviewer should trace perpres investment-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 test ownership, investment, location, and licence effects, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect perpres investment-field screen with investment plan by code and location, then show how oss risk and licence output and site and sector conditions affect the next approval. Record the source for perpres investment-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.
Record standard
Resolve material downstream blockers before including the code in the filing set.
- Perpres investment-field screen
- Investment plan by code and location
- OSS risk and licence output
- Site and sector conditions
For test ownership, investment, location, and licence effects, preserve the source record, reviewer, date, exception, and approval so another team can reproduce the decision without relying on memory.
Approve and version-control the memo
A supportable decision begins when the company can obtain accountable legal, licensing, commercial, and executive approvals and link the memo to deed and OSS inputs. For approve and version-control the memo, the classification must follow the real economic activity under current KBLI 2025 materials and then be tested against ownership, investment, location, and licensing consequences.
Uncontrolled spreadsheets and chat messages cannot show which facts and code version were approved. A reviewer should trace named preparer and reviewers and approval date and code version to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For approve and version-control the memo, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect named preparer and reviewers with approval date and code version, then show how linked deed and oss fields and change and annual review triggers affect the next approval. Record the source for named preparer and reviewers, the reviewer of approval date and code version, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Decision rule
File only the approved version and reopen it when the operating model changes.
- Named preparer and reviewers
- Approval date and code version
- Linked deed and OSS fields
- Change and annual review triggers
For approve and version-control the memo, turn the result into a controlled work item with a responsible person, due date, evidence location, escalation path, and release condition.
Place the kbli selection memo decision inside HSJGlobal’s Indonesia company registration scope before executing documents, filings, or funding.
Regulatory Notes and Limitations
Indonesia KBLI Selection Memo: Evidence to Approve Codes Before Filing 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 Indonesia KBLI Selection Memo: Evidence to Approve Codes Before Filing, kBLI classification describes economic activity; it does not by itself prove foreign-ownership eligibility, premises suitability, or completion of every licence condition.
- For Indonesia KBLI Selection Memo: Evidence to Approve Codes Before Filing, kBLI 2025 and the official 2020–2025 correspondence table must be reviewed against the actual product, service, customer, delivery model, and location.
- For Indonesia KBLI Selection Memo: Evidence to Approve Codes Before Filing, changing an activity can affect investment, licensing, tax, customs, employment, environmental, building, and bank records, so each function should confirm its own field.
Official References and Review Basis
Primary materials for Indonesia KBLI Selection Memo: Evidence to Approve Codes Before Filing 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 Indonesia KBLI Selection Memo: Evidence to Approve Codes Before Filing.
- BPS KBLI 2020–2025 conversion table : Official correspondence table for reviewing changes between KBLI 2020 and KBLI 2025.
- BPS release on KBLI 2025 : Official explanation that KBLI 2025 was established by BPS Regulation No. 7 of 2025 and updates KBLI 2020.
- Online Single Submission portal : Official NIB, four-level risk classification, business licensing, KBLI, and support portal.
- 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.
Approve KBLI codes from a versioned operating-facts memo
The strongest KBLI decision can be reproduced from facts, official classification materials, rejected alternatives, and documented downstream tests. It does not depend on who remembers a provider conversation.
Attach the approved memo to incorporation or amendment instructions and reopen it before adding products, services, locations, or delivery methods.
Turn the KBLI selection memo into an approved next step
Create a sequenced action file with owners, evidence, exceptions, stop conditions, and an approved release point for KBLI selection memo.
Frequently asked questions
