NIB VERIFICATION
NIB Check Indonesia: What Foreign Investors Should Know
A decision-led briefing on corporate identity, KBLI, project location, risk level, license status, supporting permissions, and live reconciliation, for foreign investors who need evidence they can verify before acting in Indonesia.
Foreign investors should check an Indonesian NIB against the current legal entity, AHU record, address, responsible persons, five-digit KBLI, project locations, risk levels, and related OSS outputs. The NIB is not universal proof that every proposed transaction is licensed. Medium and high-risk activities can require a Standard Certificate, verification, license, PB UMKU, premises, environmental, building, or sector evidence before operation. A defensible decision begins with the real commercial activity and the people, money, documents, locations, and authority needed to carry it out. The team should compare those facts with current official sources, obtain recipient-specific requirements, and maintain one approved master record. Inconsistent versions should be corrected before submission because later systems and institutions often reuse the same data.
Key takeaways
- Foreign investors should check an Indonesian NIB against the current legal entity, AHU record, address, responsible persons, five-digit KBLI, project locations, risk levels, and related OSS outputs.
- Build the NIB check from current official requirements and recipient-accepted evidence.
- Treat the NIB check as incomplete until its corporate, regulatory, payment, and operating records agree.
- Keep official outputs, source data, payments, credentials, and unresolved conditions under company control.
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 NIB check, the immediate acceptance point is to match the legal entity against the documented name, AHU data, address, and responsible person.
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 NIB check file, the responsible officer should preserve KBLI, location, risk, and scale as evidence for the decision to match the transaction.
NIB verification
Identity. Name, AHU data, address, and responsible person; match the legal entity.
Activity. KBLI, location, risk, and scale; match the transaction.
Authority. Certificate, license, status, and conditions; confirm operational permission.
Validate the evidence before the next commitment
Convert the open questions into a dated review file with named owners, accepted evidence, and a clear stop condition.
Read the NIB according to entity type and risk level
The NIB is the business identification number produced through OSS for an eligible business actor, including a PT PMA and, under the applicable rules, certain representative offices. For a low-risk activity it also functions as the business license; for higher risks it must be read with the required Standard Certificate or license. Its existence does not create commercial powers that the entity type itself lacks, so a KPPA remains inside its representative-office mandate. For the NIB check, the immediate acceptance point is to read each line against the documented KBLI, location, risk, and status.
Register and interpret the NIB under Government Regulation 28 of 2025 and BKPM Regulation 5 of 2025 . Verify legal name, identifier, address, responsible persons, KBLI, project location, risk level, status, and obligations against the deed and approved facts. A wrong KBLI or address can make a formally issued NIB unusable. Keep the PDF, OSS profile, credentials, recovery method, submission history, and correction owner under company control. Within the NIB check file, the responsible officer should preserve pDF, OSS data, access, and corrections as evidence for the decision to retain control.
NIB checks
| Control | Evidence | Decision |
|---|---|---|
| Entity | PT PMA or permitted representative office | Respect legal mandate |
| Activity | KBLI, location, risk, and status | Read each line |
| Evidence | PDF, OSS data, access, and corrections | Retain control |
Separate the corporate legal-entity record from the NIB
The phrase company number can refer to different identifiers and should not be accepted without seeing the document. The notarial deed and AHU business-entity record establish the company's corporate identity and legal-entity approval, while the NIB is issued through OSS as the business identification number. They are connected but serve different functions, and neither should be substituted for the other in a contract or diligence file. For the NIB check, the immediate acceptance point is to verify the required status against the documented certificate, license, PB UMKU, and conditions.
Verify the legal name, deed and AHU approval details, taxpayer data, NIB, responsible persons, address, five-digit KBLI, project locations, risk level, license status, and issue dates. Under Government Regulation 28 of 2025 , the NIB can also serve as the business license for low-risk activity; higher-risk activity needs the additional output shown in OSS. A valid corporate entity can therefore exist without being ready to perform every proposed activity. Within the NIB check file, the responsible officer should preserve deed and AHU legal-entity approval as evidence for the decision to prove legal identity.
Identifier map
Corporate
Deed and AHU legal-entity approval
Prove legal identityBusiness
NIB issued through OSS
Check each KBLI and locationOperating
Certificate, license, PB UMKU, and conditions
Verify the required statusResolve the decision gaps before filing
Reconcile the corporate, regulatory, payment, and operating facts before they become amendments or rejected submissions.
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 NIB check, the immediate acceptance point is to verify obligations attached to the activity against the documented NIB.
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 NIB check file, the responsible officer should preserve NIB plus Standard Certificate as evidence for the decision to check whether verification is required and complete.
Move from the deed to OSS in dependency order
The incorporation workflow should move from approved source data to name, deed, legal-entity approval, tax data, and OSS licensing. Each output becomes an input for the next system, so a correction to shareholders, address, capital, or activity can create work across several records. Release control should sit with the investor or an authorized company officer, not solely with the filing agent. For the NIB check, the immediate acceptance point is to confirm data and filing owner against the documented entity tax registration and access.
Use AHU business-entity services for the corporate record and the OSS framework under Government Regulation 28 of 2025 for risk-based business licensing. After each submission, compare the official output with the approved data sheet. Record the identifier, issue date, responsible account, downloadable evidence, corrections, and next dependency before marking a stage complete. Within the NIB check file, the responsible officer should preserve NIB and applicable standards or permits as evidence for the decision to check operational status, not number alone.
For a counterparty or acquisition check, retain the dated evidence produced by the NIB validation workflow rather than relying on a forwarded PDF alone.
Dependency sequence
Corporate. Name, deed, and AHU approval; verify legal identity and governance.
Tax. Entity tax registration and access; confirm data and filing owner.
Licensing. NIB and applicable standards or permits; check operational status, not number alone.
Verify the company, activity, location, status, and conditions before relying on the NIB
The approval decision for the NIB check 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 corporate identity, KBLI, project location, risk level, license status, supporting permissions, and live reconciliation, 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 NIB check 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. The safe sequence is to confirm the exact facts, identify the authority or institution that decides each stage, collect evidence in the form that recipient accepts, and assign corrections before money or authority moves. Recheck current official and institution-specific requirements immediately before filing, funding, signing, employing, or operating.
Put the approved route under company control
Record the decision, authority, documents, access, payment limits, and follow-up calendar in one owner-approved mandate.
Frequently asked questions
Can a valid NIB still contain unusable activity data?
Yes. A formally issued NIB can be inconsistent with the deed, real activity, location, risk status, or required licenses. Verify the underlying data and dependent outputs.
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.
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.
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.
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.
