Indonesia Company Number Lifecycle: AHU Identity, Amendments, and Counterparty Use

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 identifier lifecycle, the immediate acceptance point is to prove legal identity against the documented deed and AHU legal-entity approval.

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 identifier lifecycle file, the responsible officer should preserve NIB issued through OSS as evidence for the decision to check each KBLI and location.

Understand exactly what AHU approval establishes

AHU approval establishes that the limited liability company has obtained Indonesian legal-entity status based on the submitted deed and corporate data. It is essential evidence of incorporation and should be checked against the executed deed for the exact name, approval number and date, notary, shareholders, capital, domicile, directors, and commissioners. A screenshot or draft application is not equivalent to the issued approval and accessible corporate record. For the identifier lifecycle, the immediate acceptance point is to run separate gates against the documented operational license, tax, bank, capital, or visa.

Use AHU business-entity services to understand and verify the corporate output. AHU approval does not by itself prove that the KBLI is open to the shareholders, the NIB or sector license is active, the address is suitable, NPWP access works, capital was deposited, UBO data is complete, a bank account is approved, or a visa has been issued. Treat it as the corporate gate that releases separate tax, OSS, banking, accounting, employment, and operational tasks. Within the identifier lifecycle file, the responsible officer should preserve deed, approval, record, receipt, and corrections as evidence for the decision to take direct custody.

Verify the company through official records and source documents

Start with the legal-entity identity shown by the deed and AHU approval, then use the AHU company profile search to check the current corporate profile. Separately obtain and validate the NIB and licensed activities through OSS . A company number, NIB, tax number, deed number, and license number serve different functions; one cannot be used as proof that every other record is current or that a particular transaction is permitted. For the identifier lifecycle, the immediate acceptance point is to approve the specific reliance against the documented tax, bank, signer, and contract evidence.

Match the exact legal name, registered address, establishment and amendment data, directors, commissioners, shareholders, UBO information, NIB, KBLI, project location, risk level, licenses, tax identity, bank account name, and person signing the transaction. Save the search date, official output, source URL, and any access limitation. If a public search does not reveal a field, request the underlying official document and verify it with the issuing system or professional responsible for the record. Within the identifier lifecycle file, the responsible officer should preserve legal entity, deed history, boards, and shareholders as evidence for the decision to confirm corporate identity.

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 identifier lifecycle, the immediate acceptance point is to respect legal mandate against the documented PT PMA or permitted representative office.

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 identifier lifecycle file, the responsible officer should preserve KBLI, location, risk, and status as evidence for the decision to read each line.

The implementation tracker should follow the AHU-to-OSS update sequence so the corporate amendment is not mistaken for completion across dependent records.

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 identifier lifecycle, 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 identifier lifecycle file, the responsible officer should preserve NIB and applicable standards or permits as evidence for the decision to check operational status, not number alone.