Indonesia Company Registration Authorities: Who Handles Each Approval?

Match the decision to its issuer

For an Indonesian PT, AHU handles the legal-entity file under Kementerian Hukum, DJP handles taxpayer registration, and the OSS framework handles business identification and risk-based licensing through the competent issuing and technical authorities. The table separates those decisions from their submission channels and the evidence another team should receive.

The government allocation comes from PP 28/2025, especially Articles 12 and 138 ; the legal-file route is described by the official AHU PT establishment service . DJP’s corporate taxpayer registration manual and Bank Mandiri’s onboarding requirements support the tax and bank distinctions. Institutional and system routes were checked on October 26, 2026.

Use “registered” only with a named register or output. A completed incorporation file is not proof that every proposed activity may start. The same caution applies when a service provider delivers a bundle: inspect the government documents inside the bundle rather than treating the bundle’s name as a legal status.

AHU and the notary handle different parts of the legal file

The notary is the professional submission route for the ordinary PT establishment application described by AHU. The official workflow includes company data, the establishment deed and the resulting decision. The ministerial legal-entity approval is the government output; the notarial deed is a different document with a different function.

Ask the notary for the final filed particulars and the issued decision, then reconcile the company name, deed references and management details before another team relies on them. A draft deed, name check, payment voucher or filing screenshot should not be described as the approval itself. Where the source record contains a genuine error, identify the proper legal correction with the notary rather than typing a different identity into a downstream portal.

AHU’s PT establishment instructions concern this entity route. Do not apply the ordinary PT file mechanically to an individual company, partnership or representative office: first identify the legal form and its actual output. A PT with foreign investment still needs its own investment and licensing analysis; a legal-entity decision does not decide all of those questions.

The underlying formation file remains the foundation for company registration in Indonesia , because later records need a consistent legal identity. Keep the company’s constitutive evidence available even when systems exchange data electronically; integration reduces data entry but does not merge the legal responsibilities of the participating institutions. The three government evidence lanes should remain identifiable even when one system exchanges information with another.

Read OSS authority and status at activity level

OSS is the integrated electronic licensing system. Lembaga OSS is its managing institution, defined in PP 28/2025 by the investment-government function; the current institution identifies itself as Kementerian Investasi dan Hilirisasi/BKPM. Its February 2026 OSS implementation update confirms the continuing implementation of PP 28/2025. Treat the system as a route to specified decisions, not as one universal approval.

Who issues, and who verifies?

Article 138 provides for issuance by Lembaga OSS, Lembaga OSS on behalf of a minister or agency head, and provincial or regency/city DPMPTSP heads on behalf of the relevant regional head. DPMPTSP means Dinas Penanaman Modal dan Pelayanan Terpadu Satu Pintu. Technical verification can sit with the competent institution even when formal issuance appears through OSS; preserve both the verifier and issuer in your project record.

For foreign investment (Penanaman Modal Asing, PMA), Article 138 routes the specified business-permission issuance through Lembaga OSS or Lembaga OSS on behalf of the minister/agency head instead of the ordinary provincial or regency/city path. In a Kawasan Ekonomi Khusus (KEK), the Administrator KEK holds the allocated zone role. In a Kawasan Perdagangan Bebas dan Pelabuhan Bebas (KPBPB), the relevant Badan Pengusahaan handles the specified zone route, including the PMA exception in Article 138(5). Do not extend that PB rule to every premises requirement or supporting approval without checking its separate allocation.

What does the status actually permit?

• Low risk: Article 130 makes NIB the business permission for the activity. Applicable basic requirements and other obligations still need their own review.
• Medium-low risk: NIB and a Standard Certificate based on the business’s declaration apply; the business must meet the standards when conducting the activity.
• Medium-high risk: NIB and an unverified Standard Certificate support preparation. Operational or commercial activity requires the verified certificate with NIB.
• High risk: NIB supports preparation before the required licence. NIB and that licence form the permission for operational or commercial activity.

These distinctions follow Articles 130–134 of PP 28/2025 . Where supporting business permission (PB UMKU) is required, add that output to the file as well. An unverified Standard Certificate should therefore trigger a verification task, not an announcement that the company is fully operational.

Read the actual activity scope, location, investment status and required outputs displayed in the current OSS system . Record the KBLI classification used in that project and check any applicable transition instructions. A generic list of agencies cannot identify the final technical reviewer without those project facts.

Keep tax, premises and bank decisions in their own lanes

DJP remains responsible for taxpayer registration even when information comes from AHU. Its corporate-registration manual describes both Coretax registration and AHU channels, and validation against AHU establishment data. Check the existing tax record first ; do not assume every new entity must submit the same separate NPWP application or that a number printed elsewhere proves the taxpayer account is usable.

Retain the NPWP, the available tax registration evidence and the company’s access arrangements. If the legal identity is wrong at source, reconcile the AHU record; if the tax record or access is wrong, use DJP’s tax service route and the relevant Kantor Pelayanan Pajak (KPP). The DJP manual’s registration and data-validation sections explain why a data handoff is different from a new government incorporation decision. NPWP alone does not establish every separate tax status the business may require.

Premises and technical review

PP 28/2025 treats spatial conformity (KKPR), environmental approval and building approvals (PBG and SLF) as basic-requirement categories, subject to their applicability and exceptions. Article 12 allocates issuance by location and competence, including regional and zone routes. A PMA project should not infer that its central PB issuer must personally perform every local site or technical assessment.

For building matters, SIMBG is the official building-management system ; it is not itself a regional government. Articles 106–123 of PP 28/2025 address PBG and SLF, including the distinction between construction approval and fitness for use. Ask which requirement applies to your actual premises and which technical and licensing offices handle it. A company address, landlord’s document or NIB should not silently stand in for the relevant site evidence.

The bank controls its account decision

Bank Mandiri’s published Kopra onboarding procedure requires bank KYC and document verification and lists approved or rejected application outcomes. It also distinguishes an application from an active usable account. That is a bank decision about its customer relationship, not a government ruling on whether the PT exists. Obtain the chosen bank’s current document and signatory requirements rather than assuming one bank’s process applies to all banks.

Escalate the missing output to the team that can change it

Send an escalation with the missing output identified, the application reference and the exact recorded status. The practical routing method below is a management tool derived from the authority split; it does not create an appeal right or an approval deadline. Escalate the decision, not merely the portal name. An OSS helpdesk may diagnose a technical failure, while a technical reviewer must address the substantive requirement.

1. If the deed and AHU particulars disagree, return the discrepancy to the notary handling the legal file. Attach the approved decision and the conflicting field; establish whether the source needs legal correction before editing downstream records.
2. If the NPWP exists but the company cannot access its tax record, separate account access from registration. Give DJP/KPP the legal identity, tax number and error details; avoid creating another taxpayer application merely to work around access.
3. If OSS cannot accept or transfer the application, preserve the error, project identifier and time of occurrence for OSS support. State whether the failure prevents filing or only prevents display of an already issued output.
4. If the file is submitted but awaits standards verification or a technical requirement, identify the reviewer and issuer shown for that application. Send the outstanding requirement and supporting documents to the competent office; a portal resubmission cannot by itself supply a missing technical finding.
5. If a bank requests more KYC evidence, respond through that bank’s process and obtain the account outcome separately. Do not label the government file rejected merely because bank onboarding remains unresolved.

Each handoff should name a person responsible inside the company, the external decision owner, the exact output expected and what would count as resolution. Save the return notice and corrected version together so the next team can see what changed. The distinction between routing registration submissions and correction requests is especially useful when a submission exists but the company cannot identify whether it is waiting for a system fix, revised evidence or a substantive decision.

For multiple activities or sites, keep separate entries where their authorities or completion conditions differ. One successful permission should close only the corresponding entry. A progress report can then say precisely that the legal entity is approved, the taxpayer record is confirmed and a named operational approval remains outstanding, instead of using an ambiguous overall percentage.

Choose the next authority from the evidence still missing

Proceed to the next workstream when its required upstream evidence exists and matches the company and project concerned. For incorporation, that means the issued legal decision and supporting file; for tax, the confirmed taxpayer record; for operations, the permissions and fulfilled conditions that apply to the particular activity and location. Bank readiness needs its own confirmation.

Hold the operational launch if the only available evidence is a filing receipt, an unverified certificate where verification is required, or an NIB being used to cover an additional permission. Identify the missing output, check its authority allocation and give that owner a complete correction or verification file. An uncertain issuer is a reason to resolve the route before submitting duplicate applications across offices.