FIRST TRANSACTION
Indonesia First-Transaction Licence Gate: NIB, Certificates, PB UMKU, and Evidence
A decision-led briefing on license readiness before the first transaction, for foreign investors who need evidence they can verify before acting in Indonesia.
A new PT PMA should test the first contract, shipment, invoice, employee deployment, and payment collection against its activity, location, risk level, standard certificate, verification, supporting licenses, tax, and bank readiness. Treat every important claim as an evidence question: who has authority, which rule applies, what official output is required, what status makes it usable, and who owns the next action. If the result is conditional, record the condition as a pre-signing or pre-operation gate. That approach prevents a certificate, title, payment receipt, or provider message from being mistaken for a complete approval. The decision record should name the responsible owner and the evidence accepted for each unresolved condition.
Key takeaways
- A new PT PMA should test the first contract, shipment, invoice, employee deployment, and payment collection against its activity, location, risk level, standard certificate, verification, supporting licenses, tax, and bank readiness.
- Build the first-transaction release from current official requirements and recipient-accepted evidence.
- Treat the first-transaction release as incomplete until its corporate, regulatory, payment, and operating records agree.
- Keep official outputs, source data, payments, credentials, and unresolved conditions under company control.
Approve the first transaction through a cross-functional license gate
Before the first customer contract, shipment, invoice, employee deployment, or payment collection, the PT PMA should confirm that the actual activity, product, channel, project location, premises, customer promise, and goods or money flow fit the registered KBLI and current licensing outputs. An NIB proves business identity and can carry registrations, but it does not automatically satisfy every standard certificate, verified condition, PB UMKU, sector approval, location requirement, or pre-operation obligation. For the first-transaction release, the immediate acceptance point is to define the exact transaction against the documented activity, product, location, channel, and counterparty.
Use the current risk classification and conditions shown in OSS under Government Regulation 28 of 2025 . Obtain written release from corporate, licensing, tax, banking, accounting, employment, immigration, product, and contract owners as relevant. The release should name the exact transaction and preserved evidence; approval of one transaction type or location should not be generalized to every future sale. Within the first-transaction release file, the responsible officer should preserve NIB, certificate, verification, PB UMKU, and sector output as evidence for the decision to clear every dependency.
Operations should apply the OSS risk-based license output review to the actual site and process before signing a lease or approving first revenue.
First-transaction gate
Scope
Activity, product, location, channel, and counterparty
Define the exact transactionPermission
NIB, certificate, verification, PB UMKU, and sector output
Clear every dependencyExecution
Contract, invoice, bank, tax, ledger, and owner approval
Release the transactionVerify the license readiness before the first transaction before the next commitment
Turn the current facts, official checks, accepted evidence, open conditions, and responsible owners into one dated decision file.
Validate the NIB against the live company and activity facts
A PDF headed NIB is not enough for an investment, contract, payment, lease, or supplier decision. Check that the company name and identifier match the deed and AHU record; the responsible persons and address are current; the relevant five-digit KBLI and project location appear; the risk level and scale fit the actual business; and every certificate, license, verification, or supporting permission required for that activity is active. A QR code or system result proves only what the source currently displays, not facts outside its scope. For the first-transaction release, the immediate acceptance point is to match the transaction against the documented KBLI, location, risk, and scale.
Read the NIB within the risk-based system under Government Regulation 28 of 2025 and BKPM Regulation 5 of 2025 . Save the document and the supporting OSS outputs with the date and account used. Reconcile them to AHU, tax, premises, sector approvals, contracts, and the first planned transaction. Escalate mismatches before funds move; do not ask the counterparty merely to produce a newer screenshot. Within the first-transaction release file, the responsible officer should preserve certificate, license, status, and conditions as evidence for the decision to confirm operational permission.
Read the NIB, risk level, and operating conditions together
An NIB is a business identity and, for low-risk activity, the business license; it is not a universal authorization for every KBLI. Medium-low risk generally adds an unverified Standard Certificate, medium-high risk requires a verified Standard Certificate, and high risk requires an NIB plus a license. The actual output follows the activity, scale, location, and current sector rules. For the first-transaction release, the immediate acceptance point is to do not operate before required approval against the documented NIB plus license.
This risk structure is set out in BKPM Regulation 5 of 2025 and the governing Government Regulation 28 of 2025 . Read the OSS output for verification status, prerequisites, obligations, and supporting PB UMKU rather than stopping at the NIB. If the premises, environmental approval, professional credential, or sector permission remains incomplete, do not treat the company as commercially ready. Within the first-transaction release file, the responsible officer should preserve NIB as evidence for the decision to verify obligations attached to the activity.
OSS license status
Low risk. NIB; verify obligations attached to the activity.
Medium risk. NIB plus Standard Certificate; check whether verification is required and complete.
High risk. NIB plus license; do not operate before required approval.
Resolve the open conditions in the first-transaction release
Reconcile the corporate, regulatory, document, payment, and operating dependencies that can change the result for this company.
Verify the Standard Certificate when the risk tier requires it
A Standard Certificate has different legal significance depending on the OSS risk tier. For medium-low risk it is issued without prior verification, although the company remains responsible for meeting the standards and obligations. For medium-high risk, the certificate must be verified by the competent authority before it supplies the required operating authorization. The PDF title alone is therefore insufficient; status and activity must be checked. For the first-transaction release, the immediate acceptance point is to still meet standards against the documented issued without prior verification.
Review the output under BKPM Regulation 5 of 2025 and Government Regulation 28 of 2025 . Build the verification package from premises, technical standards, personnel credentials, environmental or building evidence, equipment, declarations, inspections, and sector documents actually required. Track submission, authority, queries, corrections, site visits, verified status, obligations, and changes. If the underlying address, KBLI, scale, or process changes, reassess the certificate rather than assuming it remains valid. Within the first-transaction release file, the responsible officer should preserve verification required as evidence for the decision to wait for active status.
Certificate status
| Control | Evidence | Decision |
|---|---|---|
| Medium-low | Issued without prior verification | Still meet standards |
| Medium-high | Verification required | Wait for active status |
| Change | Activity, site, scale, or evidence | Reassess impact |
Test the company before its first commercial transaction
Legal incorporation is only one readiness state. The company may still need verified OSS outputs, sector or supporting permits, tax access, PKP analysis, accounting and invoice controls, payroll arrangements, a bank account, premises evidence, and recurring reporting ownership before it can execute the planned transaction. Each state should be independently evidenced. For the first-transaction release, the immediate acceptance point is to activity can proceed under conditions against the documented applicable OSS and tax outputs.
Use DGT registration guidance for the tax registration workstream and Government Regulation 28 of 2025 for the licensing baseline. Build a first-transaction test covering authority, contract, invoice, tax, payment, license, delivery, accounting entry, and reporting. Do not let a certificate date become the commercial launch date unless every required control passes. Within the first-transaction release file, the responsible officer should preserve bank, people, premises, controls, and reporting as evidence for the decision to first transaction can be executed.
Readiness gates
Incorporated
Deed and AHU legal-entity approval
Entity legally existsLicensed and tax-ready
Applicable OSS and tax outputs
Activity can proceed under conditionsOperational
Bank, people, premises, controls, and reporting
First transaction can be executedRelease the exact transaction only after every license dependency is cleared
The approval decision for the first-transaction release should name the selected route, responsible company officer, accepted source data, supporting documents, official outputs, payment limits, unresolved conditions, and the event that permits the next commitment. For license readiness before the first transaction, a conditional result should remain a visible gate rather than being absorbed into a broad statement that setup is complete.
The founders or board should sign a short first-transaction release mandate that records the current facts, authority, required corrections, evidence location, system and credential owners, review date, and first transaction that the company intends to perform. A defensible decision begins with the real commercial activity and the people, money, documents, locations, and authority needed to carry it out. Recheck current official and institution-specific requirements immediately before filing, funding, signing, employing, or operating.
Put the approved first-transaction release under company control
Record the final route, authority, source documents, access, payment limits, handover, review date, and next operating trigger.
Frequently asked questions
What should be confirmed before approving the first-transaction release?
Confirm the current official position, recipient-specific requirements, authority, source documents, and unresolved conditions for license readiness before the first transaction. Record the approval and evidence before the company signs, pays, files, or operates.
Is an NIB always enough to begin operations?
Only for an activity where the current risk tier makes the NIB sufficient and all attached obligations and other applicable permissions are satisfied. For this first-transaction release, record how that answer applies to license readiness before the first transaction and preserve the evidence used.
How should a certificate status be verified?
Check the live OSS record, exact KBLI and location, risk tier, verification requirement, issuing authority, supporting evidence, conditions, and current status. For this first-transaction release, record how that answer applies to license readiness before the first transaction and preserve the evidence used.
What changes can affect a license?
KBLI, activity, scale, process, product, premises, project location, equipment, personnel, environmental facts, or corporate data can trigger reassessment or updates. For this first-transaction release, record how that answer applies to license readiness before the first transaction and preserve the evidence used.
Who should approve first revenue?
A company officer should sign a transaction-specific gate covering authority, active licenses, tax, invoice, bank, contract, delivery, accounting, and reporting. For this first-transaction release, record how that answer applies to license readiness before the first transaction and preserve the evidence used.
Regulatory notes, official references, and review basis
Requirements affecting license readiness before the first transaction were checked against the linked official or institution-specific materials on August 10, 2026. The responsible company officer should reconfirm the rule, system status, recipient requirements, and transitional conditions that apply on the actual filing, payment, signing, or operating date for the first-transaction release.
- OSS
- Government Regulation 28 of 2025 — Government Regulation No. 28 of 2025 on Risk-Based Business Licensing; Government of Indonesia; established, promulgated, and effective 5 June 2025; in force as checked 10 August 2026.
- BKPM Regulation 5 of 2025 — Minister of Investment and Downstreaming/Head of BKPM Regulation No. 5 of 2025; established 1 October 2025, promulgated 2 October 2025; in force as checked 10 August 2026.
- DGT registration guidance
