STANDARD CERTIFICATE CHECK
PT PMA Standard Certificate Mistakes Foreigners Make
A decision-led briefing on risk tier, verification status, premises, standards, evidence, obligations, changes, and launch approval, for foreign investors who need evidence they can verify before acting in Indonesia.
Foreign founders often mistake a Standard Certificate PDF for unconditional permission to operate. The legal effect depends on whether the activity is medium-low or medium-high risk, whether verification is required and complete, and whether the correct KBLI, location, scale, standards, premises, personnel, technical evidence, prerequisites, and supporting permissions are satisfied. Changes can require reassessment even when the old document remains downloadable. 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.
Key takeaways
- Foreign founders often mistake a Standard Certificate PDF for unconditional permission to operate.
- Build the certificate verification from current official requirements and recipient-accepted evidence.
- Treat the certificate verification as incomplete until its corporate, regulatory, payment, and operating records agree.
- Keep official outputs, source data, payments, credentials, and unresolved conditions under company control.
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 certificate verification, 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 certificate verification file, the responsible officer should preserve verification required as evidence for the decision to wait for active status.
Operations should apply the OSS risk-based license output review to the actual site and process before signing a lease or approving first revenue.
Certificate status
Medium-low
Issued without prior verification
Still meet standardsMedium-high
Verification required
Wait for active statusChange
Activity, site, scale, or evidence
Reassess impactValidate 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, 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 certificate verification, the immediate acceptance point is to check whether verification is required and complete against the documented NIB plus Standard Certificate.
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 certificate verification file, the responsible officer should preserve NIB plus license as evidence for the decision to do not operate before required approval.
Avoid treating every Standard Certificate as immediately usable
The most serious mistake is reading only the certificate name and not the risk tier, activity, location, status, standards, verification, prerequisites, and obligations. A medium-low-risk declaration and a medium-high-risk certificate awaiting verification do not create the same operating position. Other errors include using the wrong KBLI, declaring an ineligible address, missing environmental or building evidence, assuming one certificate covers every project, and failing to revisit the output after a change. For the certificate verification, the immediate acceptance point is to keep a live register against the documented changes, obligations, updates, and renewals.
Create a certificate register from the live OSS record and supporting documents. For each activity, record the NIB, KBLI, location, risk, issuing or verifying authority, submission date, evidence set, queries, site visit, verification status, obligations, renewal or update triggers, and owner. Before first revenue, have operations and legal teams test the real process against the approved standards. Stop or redesign any activity that cannot satisfy the stated premises, personnel, equipment, or technical conditions. Within the certificate verification file, the responsible officer should preserve risk tier, status, activity, and location as evidence for the decision to do not trust the title alone.
Certificate mistakes
Read. Risk tier, status, activity, and location; do not trust the title alone.
Prove. Standards, premises, people, and technical evidence; complete verification.
Maintain. Changes, obligations, updates, and renewals; keep a live register.
Resolve the decision gaps before filing
Reconcile the corporate, regulatory, payment, and operating facts before they become amendments or rejected submissions.
Prove the registered address to every dependent institution
A PT PMA needs an Indonesian registered domicile and address that can be entered consistently in the deed, AHU, tax, OSS, bank, employment, and correspondence records. The evidence may include ownership or lease rights, landlord authority, building identity and permitted use, occupancy, zoning or spatial compatibility, and access for notices or inspections. The registered office and operating site may differ, but each must support its actual function. For the certificate verification, the immediate acceptance point is to prove use rights against the documented domicile, lease, landlord, and building.
Validate the premises before filing through AHU business-entity services and OSS under Government Regulation 28 of 2025 . Check whether the selected KBLI requires a clinic, restaurant, warehouse, factory, workshop, school, tourism premises, or another physical facility that a mailing address cannot provide. Control lease term, renewal, assignment, early termination, service scope, signage, records, move procedure, and responsibility for updating every dependent system. Within the certificate verification file, the responsible officer should preserve KBLI, zoning, space, and inspection as evidence for the decision to match real activity.
Address evidence
| Control | Evidence | Decision |
|---|---|---|
| Legal | Domicile, lease, landlord, and building | Prove use rights |
| Operational | KBLI, zoning, space, and inspection | Match real activity |
| Systems | AHU, tax, OSS, bank, and notices | Keep one address record |
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 certificate verification, 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 certificate verification file, the responsible officer should preserve certificate, license, status, and conditions as evidence for the decision to confirm operational permission.
NIB verification
Identity
Name, AHU data, address, and responsible person
Match the legal entityActivity
KBLI, location, risk, and scale
Match the transactionAuthority
Certificate, license, status, and conditions
Confirm operational permissionTreat the certificate as usable only at the status required for the exact activity
The approval decision for the certificate verification 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 risk tier, verification status, premises, standards, evidence, obligations, changes, and launch approval, 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 certificate verification 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 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 PT PMA invoice after receiving an unverified certificate?
Only if the applicable risk tier and current status provide the necessary authority and all other prerequisites are satisfied. Medium-high risk generally requires verification first.
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.
