KBLI 2025 scale restrictions in OSS and why PT PMAs feel the impact first

KBLI 2025 has been issued through BPS Regulation No. 7 of 2025 (Peraturan Badan Pusat Statistik Nomor 7 Tahun 2025) and is legally effective from promulgation in December 2025. The regulation requires every user of KBLI, including companies using OSS for licensing administration, to align existing KBLI usage within 6 (six) months from promulgation.

For many clients, the first practical friction appears as KBLI 2025 scale restrictions in OSS. OSS can block a KBLI selection where the KBLI is configured for specific business scales, and the entity’s profile sits outside those scales. PT PMA structures often meet this friction earlier because the OSS record and investment profile frequently place the entity into a large-scale category that OSS applies during licensing configuration.

This article explains KBLI 2025 scale restrictions in OSS through a client-operational lens and sets out an execution workflow for PT PMA KBLI selection in OSS, including how to plan a KBLI 2025 update for an existing NIB without destabilising downstream licences and corporate records.

What KBLI 2025 changes in practice

KBLI 2025 expands the classification structure to 22 categories (A–V) and updates the internal structure to reflect changes in economic activity captured by BPS.

The practical impact for operating businesses sits in three places:

• The activity description attached to a five-digit code can change.
• A single prior code can map into multiple KBLI 2025 options.
• Several prior codes can map into a single KBLI 2025 option.

Those shifts matter because OSS uses the five-digit KBLI as the unit for licensing configuration and compliance sequencing.

OSS treats the five-digit KBLI as the activity identifier that sets the licensing route and the compliance sequence for that activity. When KBLI 2025 splits or consolidates codes, the identifier attached to an NIB can change, and OSS applies a different configuration even where operations remain the same.

In practice, the five-digit KBLI drives six (six) OSS outcomes.

1. Risk level and licensing route
   Each five-digit KBLI carries a predefined risk profile that determines whether the activity sits under NIB only, NIB plus a Standard Certificate, NIB plus a Business Licence, plus any sector verification steps.
2. Sequencing of requirements and dependencies
   OSS presents requirements in a defined order. The five-digit KBLI influences which requirement appears first, which completion step unlocks the next step, and which authority validates the requirement.
3. Scope interpretation for the registered activity
   The activity description linked to a five-digit KBLI influences how OSS interprets alignment between the registered scope and day-to-day operations. This becomes sharper under KBLI 2025 for intermediary, platform, and multi-service models.
4. Linked approvals that sit behind the core OSS record
   Many activities carry approvals administered through sector standards and supervising authorities. The five-digit KBLI determines whether those approvals are triggered and how they are tracked through OSS.
5. Multi-activity exposure inside one entity
   Multi-activity businesses often carry several five-digit codes. Each code can carry its own risk pathway, scale settings, and verification steps. A single reclassified activity can therefore change the overall compliance workload.
6. Behaviour of split and merged codes
   A split pushes the business to select between narrower descriptions. A merger can introduce a revised risk profile and a revised set of completion requirements.

Practical implication: treat a KBLI 2025 update as a licensing design exercise, anchored in an activity map, with OSS pathway checks for each five-digit KBLI prior to OSS updates.

OSS risk-based licensing for KBLI codes and scale gating

OSS risk-based licensing for KBLI codes is anchored in the risk-based licensing framework set by Government Regulation No. 28 of 2025 on the administration of risk-based business licensing (Perizinan Berusaha Berbasis Risiko).

In that framework, the risk assessment and licensing setup are performed per KBLI five-digit activity. The annex methodology refers to determining both the risk level and the business scale ranking for each KBLI.

This is the operational trigger for KBLI 2025 scale restrictions in OSS:

• OSS can permit an activity only for certain scales (for example, micro, small, and medium).
• OSS can permit an activity for large scale under specific licensing paths or verification requirements.
• OSS can treat scale as a gate for the KBLI selection itself, or as a gate later in the licensing chain.

Where a business is registered as large scale in OSS, a KBLI configured for micro, small, or medium can become unavailable or can fail at a later licensing stage.

This is why OSS risk-based licensing for KBLI codes needs to be reviewed alongside KBLI 2025 mapping, rather than treated as a separate compliance task.

KBLI 2025 business scale classification and why it impacts PT PMAs

KBLI 2025 business scale classification becomes operational when it interacts with OSS configuration. The KBLI itself is a classification standard issued by BPS, and OSS uses that standard as an administrative anchor for licensing and reporting.

For PT PMA clients, PT PMA KBLI selection in OSS often carries additional complexity because business fields can also sit within investment regime settings under the Investment Business Fields framework (Perpres 10/2021 as amended by Perpres 49/2021).

KBLI 2025 scale restrictions in OSS: typical triggers

Most blocks linked to KBLI 2025 scale restrictions in OSS arise from one of the following four conditions:

1. The KBLI is configured for micro, small, or medium scales, and the entity is recorded as large scale.
2. The KBLI maps into a different sector cluster under KBLI 2025, changing the licensing pathway and the scale settings applied during that pathway.
3. The KBLI connects to sector standards that introduce scale-linked facility, staffing, reporting, or verification requirements.
4. The KBLI sits within an investment field configuration that introduces ownership conditions or activity conditions that interact with the chosen entity type.

Each trigger requires a different remediation path. A single “change the code in OSS” approach frequently causes secondary issues in deeds, commercial contracts, and operational licensing completeness.

PT PMA KBLI selection in OSS: a diagnostic workflow

The fastest route to stabilise PT PMA KBLI selection in OSS is a structured diagnostic and sequencing process. The steps below also form the backbone of a controlled KBLI 2025 update for an existing NIB.

Step 1: Build the activity map

Document each revenue-generating and compliance-relevant activity, including operational delivery and supporting functions. Use four or more activity layers per business where relevant, for example:

• core service delivery
• sales and distribution method
• facility operation and customer access model
• platform or intermediary functionality
• supporting services delivered to related entities

Step 2: Map KBLI 2020 to KBLI 2025 options

Use the KBLI 2025 activity descriptions to select the closest match for each activity the business actually performs. KBLI 2025 introduces greater specificity, so one KBLI 2020 code can map into several plausible KBLI 2025 candidates, and selection needs to follow the operating model rather than legacy code habits.

A workable mapping approach is:

• Start from an activity map, then match each activity line to the KBLI 2025 wording, including the boundaries of what the description covers and what it excludes.
• Where multiple candidates appear, separate principal activity from supporting activities and map them independently, rather than forcing one umbrella code to cover the entire model.
• Record the basis for each selection in a short narrative that links the chosen KBLI to real operational evidence such as revenue streams, contracts, service delivery steps, and staffing. This narrative becomes the reference point when updating OSS records and when aligning corporate documents.
• Flag activities that sit close to regulated or supervised sectors, because KBLI 2025 introduces new and refined classifications for platform intermediation, digital content, energy and sustainability-linked activity, and other areas that can trigger additional licensing dependencies.
• Confirm the final shortlist by checking how each candidate code behaves inside OSS, including risk pathway and scale eligibility, before any updates are submitted.

How TraceWorthy supports this step
TraceWorthy can complete the KBLI mapping as a controlled work product rather than an informal code swap. The output is designed for implementation, including:

• a KBLI 2020 to KBLI 2025 mapping table tied to an activity map, with the rationale for each selection
• a short activity narrative suitable for OSS updates and internal governance records
• identification of multi-code stacks where one business model legitimately requires multiple five-digit codes
• early flags for scale gating, sector approvals, and foreign investment conditions that can affect PT PMA structures
• an implementation sequence covering OSS updates and any related deed or licence alignment work

This turns mapping into an execution-ready input for the KBLI 2025 update process, with reduced rework risk once the OSS changes begin.

Step 3: Validate OSS risk-based licensing for KBLI codes

For each candidate KBLI, verify:

• the risk level configuration in OSS
• the business scale configuration applied to the KBLI
• the licensing type outcomes and completion requirements
• any sector-standard dependencies tied to that KBLI

This step is where OSS risk-based licensing for KBLI codes either confirms the selection or signals a scale gate.

Step 4: Validate KBLI 2025 business scale classification against the entity profile

This step confirms whether the entity’s OSS profile will be treated as micro, small, medium, or large when OSS applies licensing rules to the selected KBLI set. The purpose is to identify scale mismatches early, because scale is frequently applied as a gate in OSS for certain activities.

In practice, the validation involves:

• confirming the entity’s current scale status in OSS and the inputs that drive it, including capital profile, investment positioning, and the way the business has been registered across its activity lines
• checking whether each proposed five-digit KBLI is configured in OSS for the entity’s scale category, since some activities are configured for micro, small, or medium outcomes and can be blocked for a large-scale entity
• testing the interaction between scale and risk pathway, because the same business activity can carry different completion requirements depending on scale, including facility standards, staffing standards, document evidence, and verification steps
• checking whether the scale outcome causes downstream licensing steps to become unavailable or incomplete, even where the KBLI selection itself appears to be accepted during the initial OSS entry stage
• documenting the scale-risk exposure per activity line so the KBLI set can be finalised based on licensing feasibility rather than only on activity description matching

TraceWorthy’s role at this step is to run the scale and pathway checks as part of a controlled implementation plan, so clients do not discover scale gating late in the licensing process after corporate documents and operational plans have already been set.

Step 5: Confirm investment field conditions relevant to the KBLI set

For PT PMA structures, each KBLI selection also needs an investment regime check. Indonesia treats certain business fields as open, open with conditions, reserved, or otherwise subject to requirements, and those conditions can affect whether a PT PMA can register and operate the activity as described.

In practice, this step involves:

• checking whether any KBLI in the proposed set sits in a business field that carries foreign ownership conditions, partnership requirements, location restrictions, special licences, or other activity-specific requirements
• confirming whether any KBLI is allocated to micro, small, or medium enterprises, or to cooperatives, because that allocation can create a structural mismatch for a PT PMA
• validating that the chosen KBLI descriptions align with the operational model described in corporate and commercial documentation, since OSS and other systems can cross-check the business field description against the registered activity
• identifying whether the investment conditions change the most sensible entity architecture, for example separating an operational activity from supporting activities such as management services, technology services, or IP licensing within a group structure

TraceWorthy’s role at this step is to connect the legal investment setting to the practical OSS and corporate sequencing, so the final KBLI set is workable for registration, licensing completion, and ongoing operation.

Step 6: Execute the KBLI 2025 update for an existing NIB with sequencing controls

A KBLI 2025 update for an existing NIB should follow a controlled sequence:

• prepare the final KBLI set and activity narrative
• identify dependent licences and certificates linked to each KBLI
• align corporate documents where the deed, articles, or corporate profile embed business activities
• update OSS records, then complete downstream licensing steps
• align internal policies and employee documentation where regulatory standards require documented procedures
• record evidence of completion and keep a change register for future audits

This sequencing prevents rework and reduces the probability of partial licensing completeness.

KBLI 2025 update for an existing NIB: why timing matters

---

Five client examples: where scale restrictions surface

The examples below show how KBLI 2025 scale restrictions in OSS can surface in real operating models and how TraceWorthy approaches PT PMA KBLI selection in OSS.

1) Padel facilities and club operators

Padel operators frequently run multi-activity models: venue operation, coaching delivery, membership systems, event hosting, retail sales, and food and beverage operations. A single code selection rarely reflects the entire operating footprint.

Where KBLI 2025 scale restrictions in OSS appear, the root cause is often a mismatch between a facility-operation KBLI and an entity scale outcome in OSS. The remediation approach begins with OSS risk-based licensing for KBLI codes review across each activity layer, then redesign of the KBLI set so each code aligns to a real operational function. This process stabilises PT PMA KBLI selection in OSS and supports a controlled KBLI 2025 update for an existing NIB.

2) Owned or leased real estate operations (including KBLI 68111)

Real estate operators using KBLI 68111 often carry supporting activities that sit outside property operation, including managed services, leasing administration, maintenance services, and short-stay style activity delivered through third parties.

Scale gating issues can arise where a property entity carries a large-scale profile and selects an activity configured for a different scale outcome in OSS. A clean solution requires KBLI 2025 business scale classification review, then OSS risk-based licensing for KBLI codes confirmation, then execution of a KBLI 2025 update for an existing NIB that aligns deeds, OSS, and dependent licences.

KBLI 2025 leaves the daily rental position unchanged. OSS and investment-field settings continue to treat short-stay, daily rental activity as an accommodation business line linked to hotel-classified operations and the associated licensing chain. A PT PMA recorded as a large-scale enterprise generally cannot participate in daily rental activity through a property operation code such as KBLI 68111, and the workable route relies on hotel classification alignment rather than a real estate leasing classification.

3) E-commerce fashion merchants

Online fashion merchants can operate as principal sellers, marketplace intermediaries, logistics coordinators, or brand-led sellers using outsourced manufacturing. KBLI 2025’s increased specificity increases the importance of correct activity description matching, and scale gating can arise where a marketplace or intermediary feature maps to a KBLI configured for a specific scale profile.

TraceWorthy’s approach runs PT PMA KBLI selection in OSS through an activity map that captures the sales model, payment flows, fulfilment model, and supplier management. The KBLI set is then validated through OSS risk-based licensing for KBLI codes, then implemented via a KBLI 2025 update for an existing NIB.

4) Energy saving systems and technology

Energy efficiency businesses often mix technology, installation, maintenance, monitoring, and performance-linked contracting. KBLI 2025 highlights newer and evolving sectors, which increases the likelihood of a mapping shift from KBLI 2020 descriptions.

Scale gating can surface where installation and supporting services are configured for scale-linked standards. The remediation is driven by KBLI 2025 business scale classification confirmation, then OSS risk-based licensing for KBLI codes validation across equipment supply, service delivery, and technology components. This sequencing supports a stable KBLI 2025 update for an existing NIB.

5) Influencer and vendor platform businesses

Platforms frequently operate as intermediaries: matching, campaign management, payment processing, content review, analytics, and brand services. KBLI 2025 shifts the classification logic toward business model specificity, which makes misalignment and scale gating more common where a platform selects a code that OSS configures for a different scale outcome.

TraceWorthy’s approach keeps PT PMA KBLI selection in OSS aligned to the real model by separating intermediary functions, agency-style services, content production functions, and technology operations, then validating each through OSS risk-based licensing for KBLI codes. The final step is a controlled KBLI 2025 update for an existing NIB with licensing dependency tracking.

A practical implementation package for clients

A TraceWorthy KBLI 2025 workstream is designed to deliver measurable outputs that clients can use with internal teams, notaries, and operational managers:

• a KBLI mapping table from current OSS codes to KBLI 2025 selections with activity narrative
• a scale and licensing pathway register based on OSS risk-based licensing for KBLI codes
• a dependency list covering certificates, sector standards, operational requirements, and corporate document touchpoints
• an execution sequence for the KBLI 2025 update for an existing NIB, including evidence tracking for completion
• a remediation plan for KBLI 2025 scale restrictions in OSS where an entity profile blocks a selected activity

Many PT PMA owners use the KBLI 2025 workstream as the trigger for a broader compliance reset. TraceWorthy can run a comprehensive Business Health Check alongside the KBLI review and remediation process to identify non-compliances that have accumulated through regulatory changes and day-to-day operational drift. This combined approach allows the KBLI mapping, OSS updates, licensing dependency checks, and corporate document alignment to run in parallel with a structured review of governance, licensing completeness, employment documentation, payroll settings, and other compliance obligations that often remain unnoticed until an inspection, a transaction, or a banking requirement forces disclosure.

Summary

KBLI 2025 increases specificity in activity descriptions and OSS applies licensing configuration per five-digit KBLI, including risk pathway and business scale settings. KBLI 2025 scale restrictions in OSS arise where an activity is configured for a different scale category than the entity profile applied in OSS, and PT PMA structures often meet this friction early. A controlled KBLI 2025 update for an existing NIB requires an activity map, a multi-code stack design where the operating model requires it, and validation of OSS risk pathways and scale eligibility per code, alongside a review of investment field conditions that affect foreign ownership settings. For property businesses, daily rental activity remains aligned to hotel-classified accommodation pathways rather than a real estate leasing classification, so code selection needs to reflect that operational and licensing reality. Where owners want a wider compliance reset, the KBLI review can run alongside a TraceWorthy Business Health Check to identify and remediate compliance gaps arising from regulatory change and operational drift.

---