How to Read an Indonesia OSS Risk-Based License Output Before Signing a Lease
Read the activity, risk, project, spatial, building, environmental, verification, and supporting-approval fields before premises costs become fixed.
Before signing a lease, an Indonesian company should read the OSS output as an activity-location requirements map, not as a general approval of the building. Government Regulation No. 28 of 2025 supplies the current risk-based framework, while the live OSS record identifies the activity, risk level, licence product, and supporting conditions. Match those fields to the precise parcel, building use, planned fit-out, operational scale, and lease rights.
The company should make the lease conditional when spatial confirmation, building fitness, environmental treatment, sector approval, Standard Certificate verification, or another supporting licence is unresolved. A landlord's statement that the property is commercial, a prior tenant's licence, or a virtual-office package does not prove suitability for the new tenant's KBLI and operations. Allocate correction costs, access to owner documents, cooperation duties, commencement, and termination rights before paying a non-refundable deposit.
In this article
Pre-lease oss output review 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 |
|---|---|---|
| Read the activity and project identifiers | confirm the KBLI, scope description, project location, scale, and legal entity shown in the output | Live OSS activity record |
| Translate risk fields into operating dependencies | list the NIB, certificate, permit, verification, PB-UMKU, and sector conditions attached to the activity | Risk level and licence product |
| Test the parcel and building use | compare the geospatial parcel, local spatial plan, building function, access, utilities, safety, and landlord evidence with the planned activity | Parcel and spatial-plan evidence |
| Draft licence dependencies into the lease | allocate owner cooperation, document access, fit-out approvals, correction costs, rent commencement, deposit treatment, and termination rights | Conditions precedent |
| Run a pre-payment release review | confirm the final activity, parcel, building, licence path, owner cooperation, budget, and fallback before money becomes difficult to recover | Signed site due-diligence memo |
Scope the pre-lease OSS output review before acting
Share the company facts, intended outcome, current records, and unresolved conditions so the pre-lease OSS output review review can be bounded.
Key takeaways
- Reject the output as lease evidence until it matches the intended tenant and operation.
- Condition occupancy and launch on the effective licence state actually required.
- Do not rely on the address until site-specific official and building evidence supports the use.
- Make unresolved regulatory facts express conditions rather than informal promises.
- Release signing and payment only against an approved evidence and exception matrix.
Read the activity and project identifiers
For pre-lease OSS output review, confirm the KBLI, scope description, project location, scale, and legal entity shown in the output. For read the activity and project identifiers, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.
A valid output for another activity, affiliate, or project cannot support the proposed lease. A reviewer should trace live oss activity record and kbli 2025 description to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For read the activity and project identifiers, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect live oss activity record with kbli 2025 description, then show how project and legal-entity identifiers and operating narrative and scale affect the next approval. Record the source for live oss activity record, the reviewer of kbli 2025 description, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Record standard
Reject the output as lease evidence until it matches the intended tenant and operation.
- Live OSS activity record
- KBLI 2025 description
- Project and legal-entity identifiers
- Operating narrative and scale
For read the activity and project identifiers, 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 PT PMA Registered Address Requirements in Indonesia .
Translate risk fields into operating dependencies
The responsible team should list the NIB, certificate, permit, verification, PB-UMKU, and sector conditions attached to the activity. For translate risk fields into operating dependencies, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.
The risk label alone can conceal an incomplete verification or supporting approval that delays opening. A reviewer should trace risk level and licence product and verification status to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For translate risk fields into operating dependencies, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect risk level and licence product with verification status, then show how supporting business licences and conditions, validity, and authority affect the next approval. Record the source for risk level and licence product, the reviewer of verification status, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Decision rule
Condition occupancy and launch on the effective licence state actually required.
- Risk level and licence product
- Verification status
- Supporting business licences
- Conditions, validity, and authority
For translate risk fields into operating dependencies, preserve the source record, reviewer, date, exception, and approval so another team can reproduce the decision without relying on memory.
Test the parcel and building use
A supportable decision begins when the company can compare the geospatial parcel, local spatial plan, building function, access, utilities, safety, and landlord evidence with the planned activity. For test the parcel and building use, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.
A commercial address can still be unsuitable for a restaurant, warehouse, factory, customer-facing use, or regulated storage. A reviewer should trace parcel and spatial-plan evidence and pbg and slf or applicable building records to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For test the parcel and building use, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect parcel and spatial-plan evidence with pbg and slf or applicable building records, then show how lease title and landlord authority and operational access and utility facts affect the next approval. Record the source for parcel and spatial-plan evidence, the reviewer of pbg and slf or applicable building records, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Evidence rule
Do not rely on the address until site-specific official and building evidence supports the use.
- Parcel and spatial-plan evidence
- PBG and SLF or applicable building records
- Lease title and landlord authority
- Operational access and utility facts
For test the parcel and building use, turn the result into a controlled work item with a responsible person, due date, evidence location, escalation path, and release condition.
Test the pre-lease OSS output review evidence
Reconcile the authoritative, operational, contractual, tax, banking, and evidence fields that affect the pre-lease OSS output review decision.
Draft licence dependencies into the lease
Before the next commitment, management should allocate owner cooperation, document access, fit-out approvals, correction costs, rent commencement, deposit treatment, and termination rights. For draft licence dependencies into the lease, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.
A compliant site can become commercially unusable if the landlord will not provide documents or consent to regulatory work. A reviewer should trace conditions precedent and landlord document schedule to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For draft licence dependencies into the lease, 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 conditions precedent with landlord document schedule, then show how fit-out and inspection access and refund, suspension, and exit rights affect the next approval. Record the source for conditions precedent, the reviewer of landlord document schedule, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Control point
Make unresolved regulatory facts express conditions rather than informal promises.
- Conditions precedent
- Landlord document schedule
- Fit-out and inspection access
- Refund, suspension, and exit rights
For draft licence dependencies into the lease, record both the accepted position and the rejected alternatives; this prevents a later portal edit or provider message from silently changing the decision. Where this stage changes another workstream, review Indonesia Risk-Based Licensing for PT PMA Companies .
Run a pre-payment release review
The control file must show how the company will confirm the final activity, parcel, building, licence path, owner cooperation, budget, and fallback before money becomes difficult to recover. For run a pre-payment release review, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.
Teams often discover the real licence blocker only after deposit, fit-out, or long-term rent has been committed. A reviewer should trace signed site due-diligence memo and current oss and local evidence to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For run a pre-payment release review, the practical deliverable is a version-controlled decision row that remains usable when the activity, location, counterparty, or responsible person changes. It should connect signed site due-diligence memo with current oss and local evidence, then show how lease protections and cost owner and fallback site and decision authority affect the next approval. Record the source for signed site due-diligence memo, the reviewer of current oss and local evidence, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Release test
Release signing and payment only against an approved evidence and exception matrix.
- Signed site due-diligence memo
- Current OSS and local evidence
- Lease protections and cost owner
- Fallback site and decision authority
For run a pre-payment release review, 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.
Use the Indonesia company registration service scope to coordinate each deed, OSS, licensing, banking, or post-registration dependency identified for pre-lease oss output review.
Official References and Review Basis
Primary materials for How to Read an Indonesia OSS Risk-Based License Output Before Signing a Lease 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 How to Read an Indonesia OSS Risk-Based License Output Before Signing a Lease.
- Government Regulation No. 28 of 2025 : Current risk-based business licensing framework; it revoked Government Regulation No. 5 of 2021.
- Online Single Submission portal : Official NIB, four-level risk classification, business licensing, KBLI, and support portal.
- Jakarta Governor Regulation No. 31 of 2022 : Current Jakarta detailed spatial plan and zoning regulation shown as in force by Jakarta JDIH.
- Government Regulation No. 16 of 2021 : Building approval, technical standards, and building fitness framework.
- 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
How to Read an Indonesia OSS Risk-Based License Output Before Signing a Lease 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 How to Read an Indonesia OSS Risk-Based License Output Before Signing a Lease, address acceptability depends on the real activity, local spatial plan, building use, lease rights, sector rules, and the specific government or counterparty record being updated.
- For How to Read an Indonesia OSS Risk-Based License Output Before Signing a Lease, a corporate domicile, administrative office, warehouse, restaurant, factory, project site, and tax place of business can require different evidence and should not be treated as interchangeable.
- For How to Read an Indonesia OSS Risk-Based License Output Before Signing a Lease, local rules and official spatial data should be checked for the precise parcel and intended use immediately before signing or filing.
Sign the lease only when the OSS output and site evidence agree
The useful question is not whether the company has an NIB. It is whether the exact activity can reach its required licence state at the exact premises under the lease terms being offered.
Convert each unresolved field into a condition, cost allocation, cooperation duty, or exit right before signing. That keeps premises risk from becoming an avoidable licensing delay.
Turn the pre-lease OSS output review into an approved next step
Create a sequenced action file with owners, evidence, exceptions, stop conditions, and an approved release point for pre-lease OSS output review.
Frequently asked questions
