INDONESIA REGISTRATION FILE
Documents Required to Register an Indonesia Company
A decision-led briefing on entity design, owners, managers, address, activity, capital, execution, and official outputs, for foreign investors who need evidence they can verify before acting in Indonesia.
Indonesia company registration starts with an approved business and ownership record, then adds party documents and execution evidence. For a foreign-investment PT PMA, the file commonly covers the name, domicile, address, business purpose and KBLI, project data, capital, shareholders, directors, commissioners, beneficial owners, signing authority, and any premises or sector evidence needed for OSS. Requirements change with the facts and accepting institution. 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
- Indonesia company registration starts with an approved business and ownership record, then adds party documents and execution evidence.
- Build the registration evidence from current official requirements and recipient-accepted evidence.
- Treat the registration evidence as incomplete until its corporate, regulatory, payment, and operating records agree.
- Keep official outputs, source data, payments, credentials, and unresolved conditions under company control.
Build one accepted registration document matrix
PT PMA registration needs documents for the decision being filed, not a universal packet of passport scans. The controlled matrix should cover the proposed name, domicile and address, business purpose and KBLI, project and investment data, share capital and subscriptions, each individual or corporate shareholder, directors and commissioners, beneficial owners, authorized signers, powers of attorney, and any premises or sector evidence needed for OSS. For the registration evidence, the immediate acceptance point is to approve source data against the documented name, activity, address, capital, and board.
Ask the accepting notary using AHU business-entity services to specify issuer, form, date, validity, original or certified copy, language, sworn translation, apostille or legalization, signature method, and required supporting authority. Use one master-data sheet to reconcile names, addresses, numbers, percentages, roles, and capital. The completed file should include both source documents and final outputs so later bank, tax, license, visa, audit, and amendment teams can verify the chain. Within the registration evidence file, the responsible officer should preserve identity, existence, authority, and UBO as evidence for the decision to authenticate as needed.
The final document inventory should include direct OSS account handover so the company can download outputs, answer queries, and recover access without the filer.
Document matrix
Corporate design. Name, activity, address, capital, and board; approve source data.
Parties. Identity, existence, authority, and UBO; authenticate as needed.
Outputs. Deed, AHU, tax, NIB, and licenses; preserve final evidence.
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.
Build an accepted shareholder and authority file
The filing team needs usable evidence for each shareholder, authorized signer, director, commissioner, address, and declared business activity. Foreign individuals typically provide passport and contact data, while foreign corporate shareholders need constitutional and authority records that identify the entity and the person empowered to sign. The accepting notary should confirm the exact document, legalization, apostille, translation, and validity requirements. For the registration evidence, the immediate acceptance point is to confirm the shareholder can subscribe against the documented charter, registry proof, and signer mandate.
Build a document register with issuer, document date, expiry or freshness rule, language, certification route, signatory, original location, and accepting institution. Indonesian company formation is processed through notarial and AHU business-entity services workflows, so a scan that looks complete to a provider may still require a different form or supporting authority. Resolve discrepancies in names, addresses, dates, and ownership before execution. Within the registration evidence file, the responsible officer should preserve pOA, legalization, and translation path as evidence for the decision to obtain notarial acceptance before signing.
Document readiness
| Control | Evidence | Decision |
|---|---|---|
| Identity | Passports and consistent personal data | Resolve spelling and expiry issues |
| Corporate authority | Charter, registry proof, and signer mandate | Confirm the shareholder can subscribe |
| Execution | POA, legalization, and translation path | Obtain notarial acceptance before signing |
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 registration evidence, the immediate acceptance point is to check operational status, not number alone against the documented NIB and applicable standards or permits.
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 registration evidence file, the responsible officer should preserve name, deed, and AHU approval as evidence for the decision to verify legal identity and governance.
Dependency sequence
Corporate
Name, deed, and AHU approval
Verify legal identity and governanceTax
Entity tax registration and access
Confirm data and filing ownerLicensing
NIB and applicable standards or permits
Check operational status, not number aloneResolve 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 registration evidence, 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 registration evidence file, the responsible officer should preserve NIB plus Standard Certificate as evidence for the decision to check whether verification is required and complete.
Take control of documents, credentials, and open obligations
A registration engagement is not complete until the company can operate without dependence on the provider's personal accounts or device. Handover should cover final documents, source data, credentials, registered email and phone details, authentication methods, originals, payment receipts, filing history, and unresolved obligations. Access should be tested by an authorized company officer. For the registration evidence, the immediate acceptance point is to transfer and test control against the documented OSS, tax, email, phone, and authentication.
Remote matters need an especially clear revocation and recovery plan. Reconcile the deed, AHU approval, tax record, NIB, licenses, shareholder register, beneficial-owner data, and bank application before acceptance. Record who holds each original, how each credential can be recovered, and when any power of attorney or temporary access must end. Within the registration evidence file, the responsible officer should preserve conditions, renewals, and corrections as evidence for the decision to assign owner and due date.
Handover register
Documents. Final files, originals, and filing receipts; inventory and verify.
Access. OSS, tax, email, phone, and authentication; transfer and test control.
Open work. Conditions, renewals, and corrections; assign owner and due date.
Submit only after names, authority, ownership, activity, capital, and address agree
The approval decision for the registration evidence 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 entity design, owners, managers, address, activity, capital, execution, and official outputs, 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 registration evidence 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
Which document proves that the company can operate?
No single document proves every operating right. The deed and AHU approval establish the entity; the NIB and any required verified certificate, license, premises, tax, and sector outputs determine readiness.
Should foreign documents be apostilled before the notary reviews them?
First confirm the recipient, document type, origin country, form, certification, translation, and acceptance route; premature authentication can waste time and money.
How should spelling differences be handled?
Resolve names, addresses, numbers, dates, roles, and percentages in the approved source data before execution, with documented transliteration or identity evidence where needed.
Are electronic copies always sufficient?
No. The notary, authority, bank, and other recipients decide whether originals, certified copies, wet ink, authentication, translation, or presence are required.
Who should control final company documents?
An authorized company officer should hold the official files, originals inventory, source data, receipts, credentials, recovery channels, and unresolved-items register.
