How to Unblock Your Company Profile in AHU Indonesia: Three Causes, Three Different Paths

The company needs to register a new director. Or the share structure has changed and the notary is waiting. Or an investor is asking for a clean corporate data extract before a deal closes. And then the SABH system returns a blocked status.

Access to the Legal Entity Administration System (Sistem Administrasi Badan Hukum or SABH), operating under AHU Online through the Directorate General of General Legal Administration (Ditjen AHU), is the gateway to every corporate action a PT or PT PMA can take in Indonesia. Director changes, amendments to the articles of association, share capital adjustments, beneficial ownership updates: all of them run through this system. When it is blocked, the company is effectively frozen. No change can be registered. No notarial deed can be submitted. And because SABH and OSS are integrated, the block can cascade into licensing complications as well.

The first thing to understand about unblocking a company profile in AHU Indonesia is that the fix depends entirely on why it was blocked. Three different causes produce three different resolution paths. Treating them as interchangeable, or following the procedure for one when the cause is actually another, adds weeks to an already urgent situation.

Cause One: The Annual Report Was Not Submitted Through SABH

This is the newest and currently the most common blocking cause for PT PMA and PT PMDN operators in mid-2026.

Minister of Law Regulation No. 49 of 2025 (Permenkum 49/2025), which took effect on 17 December 2025, introduced a mandatory obligation that did not exist in its current form before: every standard limited liability company, without exception, must now submit its Annual Report to the Ministry of Law through SABH after the report is approved at the Annual General Meeting of Shareholders (Rapat Umum Pemegang Saham or RUPS). The submission must be completed by a notary in the form of a notarial deed, within 30 days of the deed being signed.

Before Permenkum 49/2025, annual meeting minutes were generally treated as internal documents. That practice is now non-compliant. Companies that held their RUPS for FY2024 without subsequently filing through SABH are in breach, and the system can block their access accordingly. BP Lawyers, a Jakarta-based corporate law firm, confirmed in a June 2026 publication that the AHU blocking deadline for FY2024 annual reports ran to 1 June 2026, with enforcement active from that date.

What the Resolution Path Looks Like

The unblocking pathway for this cause is procedural rather than discretionary. The steps run in sequence:

• Hold or ratify the Annual General Meeting of Shareholders for the relevant financial year, if this has not yet been done. The RUPS must formally approve the Annual Report.
• Execute a notarial deed recording the RUPS resolution. This is not a step that can be bypassed or substituted with meeting minutes alone.
• Submit the deed through SABH within 30 days of signing. The submission is made by the notary through the AHU Online system, not by the company directly.
• Confirm SABH access is restored after successful registration. The block tied to the annual report non-submission should lift once the filing is accepted.

One practical point that catches companies off guard: if the company also has a Beneficial Ownership issue (covered in the next section), resolving the annual report submission alone may not fully restore access. Both causes need to be addressed to clear a company that has accumulated multiple blocking triggers simultaneously. For companies still navigating this for the first time, the corporate secretary compliance framework for Indonesia provides the broader context of how the RUPS, notarial deed, and SABH submission sequence fit within the annual compliance calendar.

Cause Two: Beneficial Ownership Was Not Reported, or the Report Was Inaccurate

This is the blocking cause that most frequently generates confusion, because companies that believe they have already fulfilled the obligation still find their SABH access blocked.

The Beneficial Ownership (BO) reporting obligation derives from Presidential Regulation No. 13 of 2018 (Perpres 13/2018), which requires every corporation to identify and report the natural person who ultimately owns or controls it. Minister of Law Regulation No. 2 of 2025 (Permenkum 2/2025) strengthened this significantly by introducing active verification of BO data, replacing the earlier passive self-declaration system. Under Article 22 paragraph (3) of Permenkum 2/2025, a corporation that fails to report its beneficial owner, or that submits inaccurate information, faces two distinct administrative sanctions: blocked access to SABH, and placement on a public blacklist published on the Ditjen AHU official website.

The blocking from a BO failure can arise from three specific situations:

• The company never filed a BO report at all, either at establishment or subsequently
• The company filed a BO report but the data is outdated, for example because a shareholder structure changed and the BO declaration was not updated to reflect the new beneficial owner
• The company filed what it believed was an accurate BO report, but the AHU verification process identified an inconsistency between the declared beneficial owner and other data in the system

Why Clicking “Submit” on the BO Form Is Not Enough

Here is the procedural point that most companies discover only after the fact: submitting or updating a Beneficial Ownership report through the AHU Online portal does not automatically lift the block. The system does not restore access upon submission.

Two independent Indonesian legal practitioners describe the same procedural requirement: after the BO data has been corrected and submitted in the AHU portal, the company or its authorized representative must separately file a formal unblocking request. This is done by sending a letter or email to the Subdirektorat Badan Hukum at the Ministry of Law (Kemenkumham), accompanied by proof of the completed BO filing. Only upon review and approval of that request does the Ministry manually restore SABH access.

The implication is that completing the BO report is a necessary but not sufficient step. Companies that have done the filing and are waiting for the system to automatically restore access are waiting for something that will not happen without the additional manual request.

For PT PMA entities, the BO reporting requirement has a direct intersection with immigration compliance. A company with a blocked AHU profile, including one arising from a BO issue, cannot process Investor KITAS renewals without first resolving the SABH access status. The KITAS renewal guide for 2026 covers the pre-renewal compliance check that surfaces this dependency, and why it needs to be identified before, not during, the renewal application.

Cause Three: Outstanding Tax Debt Reported to Ditjen AHU by DJP

The third blocking cause operates through an inter-agency mechanism that has been in place since 2021 and is specifically designed to compel payment of outstanding tax obligations.

The Directorate General of Taxes (Direktorat Jenderal Pajak or DJP) has a formal coordination arrangement with Ditjen AHU under which DJP can request that SABH access be blocked for companies with unresolved tax debt. DJP has confirmed publicly that this mechanism collected over IDR 657 billion in tax payments in 2021 alone, a figure cited in an official Ditjen AHU press release, which reflects how systematically the mechanism is used. The blocking is not triggered by filing errors or late returns: it is triggered by a specific formal request from DJP to Ditjen AHU based on unpaid assessed tax obligations.

How This Block Gets Lifted

Unlike the BO pathway, the resolution here does not involve a submission to the Ministry of Law at all. The path runs through DJP directly:

• Identify the specific tax obligation that triggered the DJP’s request for blocking. This requires contacting the relevant Tax Service Office (Kantor Pelayanan Pajak or KPP) that issued the assessment.
• Settle the outstanding tax debt, which may include the principal amount, interest, and any administrative penalties under the Harmonized Tax Regulations (Undang-Undang HPP).
• DJP requests Ditjen AHU to unblock the company’s SABH access once payment is confirmed. The company cannot request unblocking from AHU directly in this scenario; the request must come from DJP.

The timeline for this depends entirely on how quickly the tax assessment is resolved and how quickly DJP processes the inter-agency unblocking request internally. In practice, this tends to be the slowest of the three paths because it involves two separate government agencies and a payment verification step before either acts.

For companies that have been managing their tax reporting through Coretax and are uncertain whether any outstanding assessed liability has triggered a DJP flag, the operational recommendation is to run a Coretax account position check before assuming the blocking is from one of the other two causes. A company that spends three weeks completing a BO filing and a manual unblocking request, only to discover the real cause was a DJP-flagged tax debt, has lost time that a correct initial diagnosis would have saved.

Explore Our Services Corporate Secretary in Indonesia

When Multiple Blocking Causes Stack

A company that has been operationally active but administratively neglected for more than a year can find itself with all three causes active simultaneously: an annual report never filed through SABH, a BO declaration that was last updated two ownership structures ago, and a tax assessment that DJP escalated to AHU six months prior.

In that situation, there is no single unblocking letter that resolves everything at once. Each cause requires its own resolution path, and the sequencing matters. It is generally more efficient to address the tax debt and BO filing simultaneously, since both can be initiated independently, and then move to the annual report SABH submission once SABH access is at least partially restored through the BO and tax channels. Attempting to file the annual report deed through a notary while SABH access is completely blocked will fail at the submission stage regardless.

The other consequence of stacked blocking is the downstream effect on everything the company needs to do while the block is in place. A company that cannot update its SABH record also cannot make director changes, cannot process share transfers, and cannot accurately respond to banking KYC requests or investor due diligence queries that reference the company’s registered corporate data. For companies planning a director change or shareholder restructuring alongside the unblocking process, understanding how those two workflows interact is addressed in the guide to changing directors and shareholders in a PT PMA, which covers the Article 17 Permenkum 49/2025 requirement that SABH access be confirmed before any corporate change filing can be submitted.

Diagnosing the Cause Before Taking Action

The practical first step when a company discovers its AHU profile is blocked is not to immediately file a BO report or draft an unblocking letter. It is to confirm which cause is actually in play.

The AHU Online system does not always display a clear error message distinguishing between blocking types. The most reliable diagnosis approach involves checking three things in parallel:

• Check the AHU Online portal for any notification or flag visible in the company’s profile page under the Beneficial Ownership section, and under the Annual Report submission status if visible
• Check the company’s Coretax account for any outstanding DJP assessments or tax collection flags that may have triggered the inter-agency blocking mechanism
• Contact the notary who handles the company’s SABH filings, since notaries with active AHU portal access can often identify the blocking status more quickly than the company can through the public-facing interface

XPND assists PT PMA and domestic PT companies with SABH unblocking across all three cause categories, including BO data correction and the manual unblocking request to the Subdirektorat Badan Hukum, annual report preparation and RUPS coordination for Permenkum 49/2025 compliance, and liaison with the relevant KPP for DJP-initiated blocks.

The cost of leaving a blocked AHU profile unresolved is not administrative. It is operational. Every corporate action that cannot be registered, every compliance gap that accumulates while the block persists, and every stakeholder interaction that surfaces an unresolved company status adds to the remediation cost when the block is finally addressed. Getting the diagnosis right at the start, and following the correct resolution path for each cause, is what determines whether that cost stays manageable.

Reach out to XPND’s corporate compliance team to diagnose the cause of your AHU block and initiate the correct unblocking process without losing time to the wrong procedure.