Post-NIB operating gate
Indonesia PB UMKU and Prerequisite Gap Audit After NIB
The NIB identifies the business, but each activity can still depend on risk-level verification, prerequisites, sector standards and supporting licences before operation.
The most common Indonesia business licence mistake is treating NIB issuance as confirmation that every listed activity may operate immediately. Under the current risk-based system, each KBLI and project location can have its own risk level, prerequisites, standard certificate, licence, verification status, sector standards and supporting business licence, often called PB UMKU. A company can therefore hold a valid NIB while one activity is verified, another is conditional and a third has not completed its supporting approval. After NIB issuance, open the live OSS activity dashboard and build a line-by-line permission register showing the exact activity, location, risk classification, issued output, verification state, unmet commitment, authority, expiry or reporting duty and lawful operating condition. Verify the result against current Government Regulation No. 28 of 2025 and sector rules before signing customers, invoicing or starting the regulated activity.
Key takeaways
- Verify every KBLI and project location separately after NIB issuance.
- Record the exact status and operating condition, not only the document title.
- Check spatial, environmental and building prerequisites where the activity requires them.
- Inventory PB UMKU and product or professional approvals outside the core licence.
- Reverify after changes in activity, capacity, location, product or sector standard.
Read the permission at activity level
The label shown in OSS must be read together with status, prerequisites and sector conditions. Use the strictest unresolved operating gate for that activity.
Low risk
NIB may be the business licence
Confirm the activity, location and any supporting requirements still apply.
Medium-low risk
NIB plus standard certificate
Check the certificate and self-declared standards for the precise activity.
Medium-high risk
Verified standard certificate
Do not confuse submission or unverified status with operational verification.
High risk
NIB plus licence
The licence and prerequisites must reach the required effective status before operation.
Evidence basis: Government Regulation No. 28 of 2025 · BKPM Regulation No. 5 of 2025
Verify what the NIB does not show
Open every activity record and identify its status, prerequisites, verification and supporting licences.
Government Regulation No. 28 of 2025 replaced the 2021 risk-based licensing regulation and now governs basic requirements, business licences, supporting licences, OSS, supervision and sanctions. Providers and internal checklists should therefore cite the current rule and current sector implementation, not an old status description copied from a prior project.
Use a detailed business licence requirements matrix to connect the legal output to the real operating step. For example, the right to maintain a corporate address does not prove the right to manufacture, serve food, import a product or employ a regulated professional at that location.
Verify every OSS activity, project and status
One NIB can contain several activities and locations. Open each project record and retain the live status and underlying output.
NIB-only review
The warning sign appears when the team checks the front page but never opens individual activity records. Verify it with OSS project list, five-digit KBLI, location and activity outputs. The responsible person should verify each activity and save the status evidence; otherwise, a conditional activity is treated as fully licensed.
Certificate title accepted
Treat a standard certificate exists but required verification is incomplete as a decision gate, not an administrative detail. Keep certificate number, status, verification record and sector standard in the transaction file, then confirm the operating condition with the applicable authority or rule. This reduces the chance that medium-high-risk activity begins before verification.
Wrong project location
A reliable check starts with project identifier, address, map, lease and activity record. It should resolve whether the licence output belongs to another branch, parcel or city. Where the records do not reconcile, correct or obtain the location-specific permission; proceeding without that step can mean the company operates at a site outside the approved project.
Old output reused
a PDF from before an amendment is circulated as current The evidence that matters is live OSS export, issue date, amendment history and revoked or superseded status. control document versions and withdraw obsolete copies If that control is skipped, customers and inspectors receive misleading evidence.
Check prerequisites and supporting licences beyond the NIB
An activity can depend on site, environmental, building, product, professional or operational permissions that are not captured by saying the company has an NIB.
Spatial requirement unfinished
Treat the project location has not completed the applicable conformity route as a decision gate, not an administrative detail. Keep KKPR or spatial output, parcel and activity coordinates in the transaction file, then complete the basic requirement before the operating gate. This reduces the chance that the licence chain lacks a location foundation.
Environment treated as later
A reliable check starts with process, capacity, waste and current environmental approval. It should resolve whether the company starts the activity while its environmental document is pending or based on old capacity. Where the records do not reconcile, align the project and approval before operation; proceeding without that step can mean the actual impacts exceed the assessed scope.
Building use ignored
the premises has an address but the function, PBG or SLF does not support the use The evidence that matters is building documents, unit scope and intended operation. obtain technical verification and required change If that control is skipped, the activity runs in a non-compliant building.
PB UMKU missing
The warning sign appears when a supporting approval for product, service, profession or facility was never inventoried. Verify it with OSS supporting-licence list and sector rule. The responsible person should assign and complete each supporting approval; otherwise, the core business licence cannot lawfully support the final service.
Build the operating permission register
Connect each revenue line to its location, licence output, PB UMKU and sector condition.
Maintain licence verification after launch and change
Permission is not static. Capacity, products, location and standards can move the company outside the facts on which the original status relied.
Operational drift
A reliable check starts with change request, updated activity map and existing conditions. It should resolve whether the company changes process, product or service scope without a licence review. Where the records do not reconcile, run pre-change verification before implementation; proceeding without that step can mean the business outgrows the approved activity.
Capacity increase
output or equipment expands beyond the filed plan The evidence that matters is production records, machinery, investment and environmental thresholds. assess amendment and verification requirements If that control is skipped, a formerly compliant approval no longer covers the scale.
Renewal or report missed
The warning sign appears when the licence file has no owner for expiry, reporting or supervision evidence. Verify it with obligation calendar, receipts and inspection records. The responsible person should assign named responsibility and escalation; otherwise, an issued permission becomes unusable or sanctioned.
Sector rule updated
Treat the company relies on a standard that has been revoked or replaced as a decision gate, not an administrative detail. Keep current JDIH status, transitional provision and licence history in the transaction file, then update the control matrix and operating evidence. This reduces the chance that the internal procedure follows obsolete conditions.
Current risk-based licence verification framework
Government Regulation No. 28 of 2025 and BKPM Regulation No. 5 of 2025 are the current general framework. The relevant ministry or agency standard then supplies activity-specific conditions.
- Government Regulation No. 28 of 2025 : The current risk-based licensing framework covers basic requirements, business licences, supporting licences, OSS administration, supervision and sanctions; it revoked Government Regulation No. 5 of 2021.
- BKPM Regulation No. 5 of 2025 : The current OSS procedure regulation includes the general PT PMA investment threshold, the IDR 2.5 billion minimum issued and paid-up capital rule, OSS procedures and administrative consequences. Sector-specific exceptions and calculation bases still have to be checked.
- Official OSS guidance library : The OSS portal publishes current procedural guides for new applications, changes and transition cases. A successful screen or downloaded NIB does not by itself prove that every activity-level requirement is fulfilled.
- BPS KBLI 2025 and the official conversion guidance : KBLI 2025 became the national reference in 2026. Existing licences generally remain valid, but a substantive change in business purpose or scope can require alignment through AHU and OSS rather than a cosmetic code substitution.
The risk level and required output must be checked for the exact KBLI, project scale, location and current OSS configuration. Portal wording can evolve, and sector rules can impose additional approvals. Verify live status and obtain competent advice before regulated operations.
Release each revenue activity from its own permission register
For every revenue line, the register should show activity, location, risk level, core licence, verification, prerequisites, PB UMKU, product or professional approvals, effective date, restrictions and evidence owner. Commercial teams should not contract or invoice until the responsible compliance owner releases that line.
Repeat the release when a material fact changes. An unchanged NIB number does not prove that a new product, site, capacity or operating method remains within the original permission.
Set activity-level release controls
Prevent sales and operations from starting until the exact permission evidence is complete.
Frequently asked questions
Does an NIB allow a company to operate immediately?
It depends on the activity's risk level and conditions. Some low-risk activities may rely on the NIB, while others require a standard certificate, verification, a licence, prerequisites or supporting approvals.
What is the difference between a standard certificate and a licence?
They are different risk-based outputs. The required form and any verification depend on the activity's risk classification and sector standard. Read the live status and applicable rule.
What is PB UMKU?
It is a business licence supporting business activities, such as certain product, service, facility or professional approvals. The exact requirement depends on the sector and activity.
Can one activity be licensed at one address but not another?
Yes. Project locations can have different spatial, environmental, building and sector facts. Verify the licence and prerequisites for each place of operation.
When should licence status be rechecked?
Recheck after changes in KBLI, product, service, process, capacity, location, building, ownership condition or sector rule, and before renewal, major contracts or inspections.
