COMPANY RECORDS
Indonesia Company Registry: Search Records and Request Company Extracts
Find the intended entity, obtain the right profile and keep evidence of what the search actually established.
An Indonesia company registry search should produce a record tied to the intended legal entity, not just a similar name. Start with AHU’s company search and identify the correct record before requesting a profile. Keep the transaction trail and the delivered extract together; if identity, scope or delivery remains unresolved, the search is still open.
Key takeaways
- Preserve the legal name and search date so another person can reproduce the lookup.
- Select the profile product by the question it must answer, rather than its label alone.
- Keep payment, submission and delivery evidence as separate completion stages.
- An AHU extract supports a record check; licensing and ownership questions may need different evidence.
Choose the correct company record
Use the company’s legal name from its deed or existing official document, rather than a trading name, website domain or invoice logo. Record the supplied spelling and any former name before searching. A close name match should remain provisional until another identifier connects it to the intended entity.
On the AHU company search , choose Perseroan for an ordinary limited liability company. AHU separately routes Perseroan Perorangan and unincorporated business entities , including CV and firms. An empty result in one category does not settle whether the business appears elsewhere; confirm the legal form before ordering anything.
Search the recorded name, review the available matches and compare the location and official references wherever displayed. Do not order a profile merely because the name looks familiar. Keep enough search detail to show which candidate you selected. The underlying company registration in Indonesia creates the entity record; retrieving that record is a separate task and does not create a new company.
Identify the record before ordering
A legal form or name mismatch can send the request to the wrong record. Bring the identifiers already available.
Request and save the AHU extract
For an Indonesian company extract, first identify the correct AHU record, then select the available profile product, complete its request and voucher process, and save the delivered file. Treat “extract” as your business description of the output: specify the actual AHU product name when giving instructions to a colleague or provider.
- Confirm the target entity and the purpose of the request before selecting a profile.
- Choose the profile option offered for that record. AHU’s published instructions distinguish Profil Terakhir and Profil Lengkap; check the displayed scope against the information you need.
- Use the linked voucher route, check its service description and current charge, complete the requested applicant details, and retain the payment reference.
- Submit the profile request with the appropriate voucher. Keep the transaction details and watch the email address supplied in the form.
- Download the delivered profile, open it and verify the company identity before marking the request complete.
The AHU profile-request instructions describe the voucher, submission and download sequence, but were last edited in November 2021. Use them as orientation, not a current tariff or processing-time promise. Follow the live transaction’s payment and access instructions, and download promptly. A payment receipt alone is request evidence , not the company extract.
Applicant requirements also depend on the route. The individual-company profile form explicitly requests a voucher, NIK, name, contact details, address and request purpose. That form is not the ordinary PT workflow. If a mandatory identifier is unavailable, resolve the accepted applicant route before paying; never insert invented identity data.
Build a completion evidence file
Separate retrieval progress from the strength of the result. The following working map prevents a paid request from being reported as delivered, or an unexamined download from being reported as a verified record. These are suggested file controls, not additional AHU legal requirements.
| Stage | Evidence to retain | What is complete | What remains open |
|---|---|---|---|
| Search identified | Search date, spelling, category and selected match | The intended entity was found | Similar names or an unconfirmed legal form |
| Request submitted | Product name, voucher/payment reference and transaction details | A particular output was requested | Paid but no completed request or delivery |
| Extract received | Original delivered file and retrieval date | A readable profile was obtained | Wrong entity, unreadable file or missing scope |
| Record reconciled | Field comparisons and exceptions log | The record answers the stated request | Conflicting deeds or an unresolved later change |
For the comparison, use the fields relevant to your request. Article 29 of the Company Law describes register data including company identity, address, deed and ministerial references, amendments, shareholders and management, and dissolution-related information. A statutory list of register contents does not mean every field appears in every free search screen or purchased output.
Write down the precise reference and date you compared, rather than “documents checked.” reconciling registry identifiers with underlying documents is useful when a deed number, approval reference and NIB have been treated as interchangeable. Preserve the original download separately from translations or highlighted working copies so another reviewer can retrace the comparison.
Separate a request from its delivered evidence
A voucher, transaction and profile answer different questions. Clarify which artifact is missing before repeating the request.
Recognize the extract’s evidence limits
An extract records information within its scope. It does not independently establish that a supplier can perform a contract, owns a bank account, has no debts or holds every permission required for a particular activity. Keep the answer to the stated evidence question separate from broader counterparty approval.
For operational questions, check the Business Identification Number (NIB) and applicable licensing evidence separately. The official OSS portal provides an NIB search and explains that business risk levels determine licensing obligations. A company-name match at AHU cannot replace that activity-specific check.
For beneficial ownership, use AHU’s separate Pemilik Manfaat search with its stated limitations: the data are submitted by ministries or institutions, corporations, notaries or authorized persons. Treat the result as reported information requiring appropriate corroboration, rather than proof that every ownership layer has been independently investigated.
Recover an empty search or missing file
When no result appears, first correct the search inputs and legal category. Compare the exact name against the company’s documents and check whether a name change explains the mismatch. Keep the unsuccessful search date and wording; do not turn “not located in this search” into “does not exist.”
The live AHU search notice says records outside its stated Company Law 40/2007 coverage can be requested manually through Ditjen AHU. Use the manual-request notice and AHU contact details when that limitation fits the record. Supply the known legal name and available official references so the request concerns an identifiable company, rather than an unrestricted name hunt.
For a missing download, distinguish an unpaid voucher, an unsubmitted request and an unavailable delivered file. Check the transaction details and email folders, then raise the issue through AHU’s published support channel with the reference and error details. Avoid sending unnecessary identity documents by unsecured email. If the file names a different company or conflicts with a later deed, pause reliance on that extract and resolve the discrepancy before ordering again.
Close the company record request with confidence
Close a routine company record request when the intended entity is identified, the requested output is saved and readable, and the relevant references reconcile with the purpose of the search. Record the retrieval date and any limitation alongside the file so its meaning survives a handover.
Escalate a missing record, unexplained name change, conflicting reference or absent required field. Specify the unresolved question and the document needed to answer it. A successful download completes retrieval; the receiving bank, contracting party or authority still decides whether that evidence meets its own stated requirements.
Resolve the remaining record question
Set out the unmatched reference or missing field and the evidence the recipient has requested.
Frequently asked questions
Is an English translation the official AHU extract?
Keep the original AHU output and identify any translation separately. Ask the intended recipient whether it requires a particular translator, certification or original-language document before commissioning additional work.
Can a colleague order using my identity details?
Do not assume that sharing identity data creates an accepted application route. Confirm who will be named as applicant, whose contact details will receive delivery and what authorization the applicable route requires.
Does an extract have a universal expiry date?
Use the recipient’s stated freshness requirement. A recently downloaded file can still require further checking if a material change is known; record both the retrieval date and any unresolved change.
Should I send the entire evidence file to every counterparty?
Send only the records needed for the stated purpose through an appropriate channel. Keep the full transaction and comparison trail in your controlled file; it may contain applicant details unrelated to the recipient’s request.