Indonesia AHU registry: what a PT lookup actually returns

Indonesia’s company register assigns an AHU number to every incorporated entity. The Ministry of Law and Human Rights issues it. The same identifier repeats across incorporation records, shareholder filings, and beneficial ownership disclosures. When you follow ownership through Indonesian paperwork, that number ties the trail together.

Teams outside the country usually encounter AHU data through an export from one of the legacy paid databases. The issue is age. Their snapshot can trail the ministry system by months. I ran into this during a Jakarta diligence review. The data room showed two founders holding equal stakes. The ministry record disagreed. A capital restructuring had been filed three weeks earlier and one founder had already exited via a share transfer.

The AHU register tracks two main company forms. Standard limited companies appear as PT entities. The Omnibus Law reforms introduced PT Perorangan, a simplified vehicle for a single owner. Both sit inside the same ministry system. Beneficial ownership disclosures live there too when a company files them.

Query the registry through OpenRegistry and the response mirrors the upstream payload returned by the ministry. Field names stay in Indonesian. The MCP server places them inside jurisdiction_data rather than translating them into a synthetic schema.

A typical company profile includes fields such as:

• nama_perseroan for the registered company name in Indonesian
• nomor_ahu for the AHU registration number
• status_badan_hukum for the entity’s legal status
• tanggal_pendirian for the incorporation date
• alamat for the registered address
• modal_dasar and modal_disetor for authorised and paid‑up capital

Governance records appear in separate structures depending on the filings a company has submitted. Director and supervisory roles usually retain their Indonesian titles. Direksi refers to the management board. Dewan komisaris denotes the supervisory board. Indonesia uses a two‑tier model. Those labels matter when you map who actually holds authority inside the firm.

Beneficial ownership disclosures appear where the company has submitted them to the ministry. The upstream dataset exposes fields such as nama_pemilik_manfaat and kewarganegaraan. Coverage is uneven. Reporting depends on company submissions rather than an automated reconciliation across filings.

The registry surface is narrower than the UK system many investigators expect. Companies House publishes long filing histories with attached documents. AHU behaves differently. The interface usually returns the current state of the register plus a small set of related records. The underlying Indonesian platform does store notarial deeds and other paperwork. Access often sits behind a separate paid request inside the ministry portal.

That gap shows up during diligence work. Imagine the paid‑up capital figure changes between two registry pulls. The AHU entry confirms that the update took effect. The notarial deed that authorised the change might not appear in the response. Indonesian corporate law requires a notary to record many structural actions. Those deeds remain outside the core registry interface.

The query pattern through the OpenRegistry MCP server matches the structure used for other jurisdictions. Start with a search call to locate the entity.

search_companies({
  "jurisdiction": "ID",
  "query": "PT Tokopedia"
})

The response lists matching entities together with their AHU numbers. Once the identifier is known, the company profile call retrieves the full register snapshot.

get_company_profile({
  "jurisdiction": "ID",
  "company_number": "AHU-0058743.AH.01.01"
})

Governance and ownership records sit behind separate endpoints.

get_officers({
  "jurisdiction": "ID",
  "company_number": "AHU-0058743.AH.01.01"
})

If the company has filed beneficial ownership disclosures, they appear here:

get_persons_with_significant_control({
  "jurisdiction": "ID",
  "company_number": "AHU-0058743.AH.01.01"
})

Each response comes straight from the ministry register. The server does not reinterpret Indonesian field names. If the AHU record changes tomorrow, the query output changes too. No cached translation layer in between.

Indonesia becomes more interesting once the target sits inside a regional holding structure. A common arrangement places the parent company in Singapore or the Cayman Islands while Indonesian operating subsidiaries register through AHU. Mapping that structure means querying each jurisdiction directly. Subscription databases try to assemble corporate trees in advance. Over time they drift. Officer names remain outdated. Share allocations linger long after a transfer.

PT Perorangan entities introduce another wrinkle. A single individual forms them. The shareholder and director often end up being the same person. A quick screening pass can misread that pattern as a nominee setup if the legal form is not recognised.

For teams building automated diligence pipelines, the useful part is consistency. The same MCP interface that queries Indonesia also queries registries such as GB, NL, or HK. Each jurisdiction still returns its own upstream schema. The legal detail stays intact.

The Indonesian registry endpoint is available through OpenRegistry at openregistry.sophymarine.com.