NUMBER CHECK
How to Validate an Indonesia AHU Company Number Against Deeds and NIB
A decision-led briefing on validation of an AHU company number, for foreign investors who need evidence they can verify before acting in Indonesia.
An AHU company number should be checked against the establishment or amendment output, exact legal name, deed, board and shareholder data, and then distinguished from the NIB, NPWP, and sector license numbers. Before founders sign a deed, pay a provider, submit an application, or begin operations, the responsible team should reconcile the corporate facts, current official requirements, supporting evidence, approval owner, and unresolved conditions. The practical answer changes when the activity, sector, location, ownership chain, role, or transaction changes, so decisions should be recorded rather than passed along as provider assurances. The decision record should name the responsible owner and the evidence accepted for each unresolved condition.
Key takeaways
- An AHU company number should be checked against the establishment or amendment output, exact legal name, deed, board and shareholder data, and then distinguished from the NIB, NPWP, and sector license numbers.
- Build the company-number validation from current official requirements and recipient-accepted evidence.
- Treat the company-number validation 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 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 company-number validation, the immediate acceptance point is to confirm corporate identity against the documented legal entity, deed history, boards, and shareholders.
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 company-number validation file, the responsible officer should preserve NIB, KBLI, location, risk, and licensing outputs as evidence for the decision to confirm operating scope.
Company verification sequence
| Control | Evidence | Decision |
|---|---|---|
| AHU | Legal entity, deed history, boards, and shareholders | Confirm corporate identity |
| OSS | NIB, KBLI, location, risk, and licensing outputs | Confirm operating scope |
| Transaction | Tax, bank, signer, and contract evidence | Approve the specific reliance |
Verify the validation of an AHU company number before the next commitment
Turn the current facts, official checks, accepted evidence, open conditions, and responsible owners into one dated decision file.
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 company-number validation, the immediate acceptance point is to check each KBLI and location against the documented NIB issued through OSS.
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 company-number validation file, the responsible officer should preserve certificate, license, PB UMKU, and conditions as evidence for the decision to verify the required status.
When identifiers are requested for a contract, use an NIB data reconciliation to confirm the AHU, OSS, address, activity, and responsible-person records refer to the same company.
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 statusUnderstand 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 company-number validation, the immediate acceptance point is to take direct custody against the documented deed, approval, record, receipt, and corrections.
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 company-number validation file, the responsible officer should preserve legal-entity incorporation and submitted corporate record as evidence for the decision to verify issued document.
Resolve the open conditions in the company-number validation
Reconcile the corporate, regulatory, document, payment, and operating dependencies that can change the result for this company.
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 company-number validation, 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 company-number validation 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.
Trace signing power from the deed to the specific transaction
A director's title does not answer every authority question. Start with the Indonesian Company Law , the articles of association, current AHU record, shareholders' or board resolutions, reserved matters, transaction thresholds, joint-signature rules, conflicts, and any lender, license, or shareholder-agreement condition. Then identify the legal act: an ordinary contract, property commitment, financing, guarantee, bank instruction, employment action, notarial deed, tax filing, OSS declaration, or delegated power can require different evidence. For the company-number validation, the immediate acceptance point is to match the transaction against the documented board or shareholder resolution and limits.
Prepare an authority certificate for material transactions that states the company, current directors, relevant constitutional clause, approval body, resolution date, signatory combination, financial limit, validity, and exclusions. Compare it with the counterparty's original or independently verified corporate documents. A specimen signature, business card, email, or possession of a company stamp is not enough. Where authority is delegated, inspect the power of attorney, authentication, substitution right, expiry, revocation, and whether the principal retained the power to grant it. Within the company-number validation file, the responsible officer should preserve signer, joint rules, and power of attorney as evidence for the decision to verify before commitment.
Authority chain
| Control | Evidence | Decision |
|---|---|---|
| Constitution | Deed, AHU record, and reserved matters | Use current corporate evidence |
| Approval | Board or shareholder resolution and limits | Match the transaction |
| Execution | Signer, joint rules, and power of attorney | Verify before commitment |
Approve the legal identity only after number and source-record reconciliation
The approval decision for the company-number validation 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 validation of an AHU company number, 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 company-number validation 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. 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. Recheck current official and institution-specific requirements immediately before filing, funding, signing, employing, or operating.
Put the approved company-number validation under company control
Record the final route, authority, source documents, access, payment limits, handover, review date, and next operating trigger.
Frequently asked questions
What should be confirmed before approving the company-number validation?
Confirm the current official position, recipient-specific requirements, authority, source documents, and unresolved conditions for validation of an AHU company number. Record the approval and evidence before the company signs, pays, files, or operates.
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. For this company-number validation, record how that answer applies to validation of an AHU company number and preserve the evidence used.
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. For this company-number validation, record how that answer applies to validation of an AHU company number and preserve the evidence used.
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. For this company-number validation, record how that answer applies to validation of an AHU company number and preserve the evidence used.
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. For this company-number validation, record how that answer applies to validation of an AHU company number and preserve the evidence used.
Regulatory notes, official references, and review basis
Requirements affecting validation of an AHU company number were checked against the linked official or institution-specific materials on August 10, 2026. The responsible company officer should reconfirm the rule, system status, recipient requirements, and transitional conditions that apply on the actual filing, payment, signing, or operating date for the company-number validation.
- AHU company profile search
- OSS
- AHU business-entity record
- Government Regulation 28 of 2025 — Government Regulation No. 28 of 2025 on Risk-Based Business Licensing; Government of Indonesia; established, promulgated, and effective 5 June 2025; in force as checked 10 August 2026.
