7 Critical AHU OSS Compliance Checks: AHU and OSS Don't Match, Which Information Should You Fix?

Companies evolve. Directors change, shareholders transfer shares, offices move, capital structures are adjusted, and business activities expand. Yet the information recorded across government systems does not always change at exactly the same time.

You may discover that your latest deed and AHU records show a new management structure while OSS still displays the previous director. Your corporate documents may reflect updated business activities, but older information remains in your licensing profile.

This is where AHU OSS Compliance becomes important. A mismatch does not automatically mean one system is “wrong.” The first step is understanding what changed, which system is responsible for that information, and what process should follow.

AHU and OSS Have Different Functions

AHU, under the Ministry of Law, administers corporate legal information. Permenkum No. 49 of 2025 currently governs the requirements and procedures for establishment, amendment, and dissolution of limited liability companies. It replaced Permenkumham No. 21 of 2021 in December 2025.

OSS, meanwhile, administers Indonesia’s risk-based business licensing framework. PP No. 28 of 2025 requires businesses to hold applicable business licensing and regulates OSS services, basic requirements, Business Licensing, supporting licenses, supervision, and sanctions. 

Therefore, AHU OSS Compliance is about ensuring related corporate and licensing records accurately reflect the company today.

Start With the Underlying Corporate Documents

When information differs, do not immediately change whichever system appears outdated.

Start with the latest shareholders’ resolutions, notarial deeds, ministerial approvals or notifications, and other supporting corporate documents.

For example, if a company appointed a new director, AHU OSS Compliance should begin by confirming whether that corporate change was properly completed through the applicable AHU procedure. Only then should the corresponding OSS information be reviewed.

This prevents businesses from trying to correct a licensing profile when the underlying corporate process itself remains incomplete.

When AHU Is Current but OSS Is Older

This situation can happen. Official OSS guidance for changing business-entity information specifically shows old formation data sourced from OSS alongside newer data sourced from AHU Online. The system allows businesses to review relevant changes before saving updated information. 

For AHU OSS Compliance, this means an updated AHU record does not justify ignoring outdated OSS information.

Businesses should verify whether the appropriate OSS business-data change process is required and confirm that the information displayed after the process correctly reflects current corporate records.

A Data Correction Is Different From a Company Amendment

Another important distinction is whether the information is outdated because the company legally changed something or because existing legal-entity data contains an error.

Permenkum No. 32 of 2025 specifically regulates applications for correcting legal-entity data. Under this regulation, notaries submit relevant legal-entity data and supporting documents through the Legal Entity Administration System. 

Good AHU OSS Compliance therefore requires identifying the nature of the problem before choosing the procedure.

A genuine director change, for example, is different from correcting information that was incorrectly recorded.

Management Changes Deserve a Wider Review

When directors or commissioners change, companies often focus only on the notarial deed.

However, AHU OSS Compliance should continue beyond signing documents. Once the underlying corporate process is completed, review whether the current management structure is correctly reflected wherever relevant.

Companies should also consider whether the change affects bank mandates, powers of attorney, contracts, tax administration, employment documentation, immigration arrangements for foreign management, or other records.

One completed corporate action can create several administrative follow-up tasks.

Business Activities Require Different Analysis

A mismatch can also involve activities rather than management.

Perhaps AHU reflects amended corporate purposes while OSS still contains older business information. Alternatively, the company may have expanded operationally without properly reviewing either system.

In this situation, AHU OSS Compliance should be considered alongside KBLI and business licensing requirements.

PP No. 28 of 2025 establishes risk-based licensing based on business activities and their risks. A corporate amendment alone should therefore not be assumed to complete every licensing requirement. 

KBLI 2025 Adds Another Reason to Review

Businesses should also consider Indonesia’s transition to KBLI 2025. Current OSS guidance explains that businesses using older KBLI classifications may need to undertake adjustment through a notary and AHU Online, followed by checking the updated information through the OSS business-data change menu. 

This makes AHU OSS Compliance particularly relevant in 2026.

However, companies should not mechanically change classifications simply to make systems look identical. The selected classification should accurately represent the company’s actual activities.

Check Address, Capital, and Shareholder Information

Management and activities are not the only potential mismatches.

During an AHU OSS Compliance review, compare the company name, address, shareholders, management, capital information, deed details, and other relevant profile information.

If something differs, trace the history of the change first.

The goal is not merely visual consistency between platforms. Each record should accurately represent the information it is legally or administratively intended to contain.

Look Beyond AHU and OSS

Once AHU OSS Compliance issues are identified, consider whether other records rely on the same outdated information.

A director change may affect banking authority. A shareholder change may require a beneficial ownership review. An address change may affect tax, licensing, or operational records. A new business activity may require additional risk-based licensing.

AHU OSS Compliance should therefore be part of a broader corporate compliance review rather than an isolated administrative exercise.

Make Data Reconciliation Routine

Businesses should not wait until due diligence, financing, licensing, investment, or a transaction reveals inconsistent information.

Periodic AHU OSS Compliance reviews can compare the latest deed, AHU information, OSS profile, NIB, business licenses, shareholders, management, address, capital, and actual activities.

This is especially important after restructuring, expansion, management changes, share transfers, or relocation.

Keeping records aligned can make future corporate processes considerably easier.

Do Your Company Records Tell the Same Story?

Your latest deed may show one management structure while AHU and OSS tell different versions of your company’s history. Which information is current, and which record still needs attention?

Synergy Pro can help review AHU OSS Compliance, compare corporate and licensing records, trace completed changes, and identify updates or corrections that may still be required.