A corporate deed amendment Indonesia can trigger two separate government update layers after the notarial work: the corporate record in AHU/Ministry systems and, where the changed information is reflected in business licensing, the OSS profile or licensing data. These steps are connected, but they are not the same filing.
Under Article 21 of Law No. 40 of 2007 on Limited Liability Companies, specified amendments to a PT’s articles require Ministerial approval.
Corporate Deed Amendment Indonesia: The Three-Layer Rule
For an existing PT, think about an amendment in three layers:
| Layer | Core question |
|---|---|
| Notarial deed | What corporate decision or article is changing? |
| AHU / Ministry | Does the change require approval or notification? |
| OSS | Does the changed corporate information also appear in the business-licensing profile? |
The correct sequence is usually corporate decision and deed → AHU/Ministry processing → OSS reconciliation where relevant.
This matters because an amended deed does not by itself prove that downstream government databases have been synchronized.
Which Amendments Require Ministerial Approval?
The Company Law does not treat every amendment in the same way.
That approval category includes changes to the company name and/or domicile, purposes and business activities, duration, authorized capital, reductions of issued and paid-up capital, and the company’s closed or public status.
These are Article 21 paragraph (2) amendments. For them, the corporate process should be planned around obtaining a Ministerial approval decision rather than merely sending a notification.
Name and Domicile
If the company changes its registered name or the city/regency stated as its domicile in the articles, the corporate record changes materially and should not be treated as an OSS-only profile edit.
Purposes, Objectives and Business Activities
Changing the purposes and business activities deserves particular attention because it can affect both the articles and the business-licensing layer. A new business activity may also require a separate KBLI and licensing analysis after the deed change.
Capital Changes
An increase in authorized capital falls within the approval-category framework because the amount of authorized capital is an Article 21 paragraph (2) item. A reduction of issued and paid-up capital is also expressly within the approval list.
Which Amendments Use Ministerial Notification?
For amendments outside that list, Article 21 paragraph (3) generally requires notification to the Minister rather than prior approval.
The distinction is procedural but important. An amendment should not be labeled simply as an ‘AHU update’ without identifying whether the legal route is approval or notification.
The Company Law also requires these amendments to be contained in or stated in an Indonesian-language notarial deed.
Changes to company data can also accompany or follow corporate decisions without always changing an Article 21 paragraph (2) item. For implementation, the notary and company should classify the exact change rather than assume one filing path covers every corporate update.
The Deed and AHU Filing Have Separate 30-Day Deadlines
Two different 30-day periods can apply, and confusing them can create an avoidable filing problem.
If the amendment is not already contained in notarial RUPS minutes, Article 21 paragraph (5) requires it to be stated in a notarial deed no later than 30 days from the RUPS resolution.
The next deadline is separate: Article 21 paragraphs (7)-(9) generally require the approval application or amendment notification to reach the Minister within 30 days from the notarial deed, after which the filing can no longer be submitted under that route.
A practical timeline therefore looks like this:
| Event | Main timing control |
|---|---|
| RUPS adopts amendment | Starting corporate decision |
| Amendment stated in separate notarial deed | Generally within 30 days from the RUPS if not already in notarial RUPS minutes |
| Approval application or notification filed | Generally within 30 days from the notarial deed |
The current administrative layer is Minister of Law Regulation No. 49 of 2025, which is officially listed as in force and replaced Minister of Law and Human Rights Regulation No. 21 of 2021.
When Does the Corporate Amendment Become Effective?
Do not assume the legal effective date is always the date printed on the amendment deed.
The effective date also differs: under Article 23, an approval-type amendment generally takes effect from the Ministerial approval decision, while a notification-type amendment generally takes effect from the Minister’s receipt notification.
That distinction can matter when the company signs contracts, submits licensing changes or represents its updated corporate position to banks and counterparties.
Before using the amended information downstream, confirm that the AHU/Ministry stage applicable to the change has actually been completed.
When Does OSS Need to Be Updated?
AHU and OSS serve different functions. AHU records the corporate legal entity and its corporate changes; OSS manages the business-licensing layer.
For a PT whose legality data comes from AHU Online, the official OSS business-entity-change guide states that the underlying data change must first be processed through the notarial/legal-data route before the corresponding change is made in OSS.
OSS currently maintains a dedicated business-entity data-change workflow, confirming that post-incorporation company changes can require a separate licensing-system update after the corporate change itself.
The practical rule is therefore:
- complete the required deed and AHU/Ministry amendment
- confirm the new corporate data is recorded
- review the OSS business-entity change menu
- synchronize fields that OSS obtains from or compares with AHU data
- separately assess whether the amendment changes the company’s actual licensing requirements
Which Corporate Fields Can Flow From AHU to OSS?
The same OSS guide shows old OSS data against new AHU Online data for PT profile information, capital, management and shareholders, and purposes and objectives.
The workflow specifically demonstrates AHU-derived or compared data in areas including:
- legal-entity profile information
- authorized, issued and paid-up capital
- directors or other management and shareholders
- purposes and objectives
- deed and notarial formation data
This does not mean every field can be freely edited inside OSS. The guide shows several AHU-sourced fields as automatically displayed and directs businesses back to the notarial/corporate process where those legal-source fields need changing.
Capital Changes
If authorized, issued or paid-up capital changes legally, update the corporate record first and then check the OSS capital section against the new AHU data.
Management or Shareholder Changes
If a transaction changes directors, commissioners or shareholders and the new position has been recorded through the corporate process, review whether OSS is displaying the updated AHU-derived management and shareholder data.
Purposes and Objectives
If the company’s corporate purposes change, that amendment can affect more than the deed. Compare the new AHU purposes and objectives with the activities actually licensed in OSS.
Not Every Deed Amendment Changes a Business Licence
A corporate amendment and a licensing amendment should not be treated as synonyms.
For example, a deed change can alter corporate governance language without creating a new business activity. In that situation, the company may need the corporate amendment and AHU processing without necessarily needing a new business licence.
By contrast, changing the company’s purposes to add a new operating activity can trigger another question: does OSS need a new or updated KBLI, project record, risk-based Business Licensing or PB UMKU?
The correct test is therefore field-specific:
| Change | AHU / Ministry review | OSS review |
|---|---|---|
| Company name | Yes | Check company-name/business-entity data synchronization |
| Registered corporate domicile | Yes | Check corresponding business-entity/profile data |
| Purposes and business activities | Yes | Review KBLI and licensing implications |
| Authorized capital | Yes | Reconcile OSS capital data |
| Issued/paid-up capital | Corporate filing depends on change | Reconcile OSS capital data where reflected |
| Directors/commissioners | Corporate data update | Check AHU-derived management data in OSS |
| Shareholders | Corporate data update | Check AHU-derived shareholder/investment-status data in OSS |
| Internal article wording with no OSS field impact | Corporate amendment as applicable | OSS update may not be necessary |
The OSS column is a reconciliation step, not a statement that every corporate change automatically creates a new licence.
Corporate Amendment Update Checklist
After signing a corporate amendment, use this sequence:
- Identify the legal category. Is the change an Article 21 approval item, another amendment requiring notification, or a separate company-data change?
- Check the notarial deadline. If the RUPS resolution was not already in a notarial deed, confirm the 30-day conversion deadline.
- Submit the AHU/Ministry filing. Track the separate 30-day approval or notification period.
- Confirm effectiveness. Obtain the Ministerial approval decision or receipt notification applicable to the change.
- Open the OSS business-entity change workflow. Compare the old OSS data with the updated AHU data.
- Reconcile corporate fields. Review name, profile, capital, management/shareholders, purposes and other affected data.
- Review licensing impact separately. Determine whether the amended purposes, activity, ownership or location changes any KBLI, risk classification, Business Licensing, PB UMKU or investment requirement.
- Check downstream records. Update tax, banking, contracts, beneficial-ownership information and sector records only where the changed fact is relevant to those systems.
Jakarta Legal ID’s notary guide for foreign investors provides broader context on corporate deeds and amendments, while its NIB and OSS guide explains the business-licensing system that may need reconciliation after the corporate change.
Conclusion
A corporate deed amendment in Indonesia should be managed as a sequence, not as a single document update.
First determine what the deed changes. Next classify whether the amendment requires Ministerial approval or notification and complete the AHU/Ministry process within the applicable statutory period. Only then should the company treat AHU-sourced OSS data as ready for synchronization.
The final question is separate: does the corporate amendment also change the business itself? If it changes activities, ownership, capital, location or another field used in licensing, review the OSS consequences. If it changes only a corporate provision that has no licensing-data effect, an OSS amendment may not be necessary.
Coordinate the Deed, AHU and OSS Update as One Compliance Project
If your Indonesian PT is changing its name, corporate purposes, capital, shareholders, management or other registered information, Jakarta Legal ID provides notary, PT PMA/PMDN setup and business-licensing support within its current service scope.
Request a consultation to map which part of the amendment requires AHU/Ministry processing and which changed fields should then be reconciled in OSS.
FAQ – Corporate Deed Amendment Indonesia
Does every corporate deed amendment require Ministerial approval?
No. Article 21 paragraph (2) identifies specific amendments requiring approval, while amendments outside that list are generally notified to the Minister.
Which PT amendments require Ministerial approval?
The Company Law lists changes to company name or domicile, purposes and business activities, duration, authorized capital, reduction of issued and paid-up capital, and closed/public company status.
How long does a company have to file an amendment with AHU?
The Company Law generally requires an approval application or notification within 30 days from the notarial deed containing the amendment. A separate 30-day rule can also apply between the RUPS resolution and the notarial deed where the resolution was not already recorded in notarial RUPS minutes.
Does the deed amendment automatically update OSS?
A PT whose source legality data comes from AHU should complete the underlying corporate/notarial change first and then use the OSS business-entity change workflow to reconcile relevant AHU-derived data. The deed itself should not be treated as proof that OSS is already synchronized.
Which PT data should be checked in OSS after an AHU amendment?
The official OSS workflow shows comparison of profile information, capital, management and shareholders, and purposes and objectives, among other AHU-derived corporate data.
Does changing a corporate deed always require a new business licence?
No. The licensing impact depends on what changed. A new business activity may require KBLI or licensing review, while an internal corporate amendment with no relevant OSS field or operational change may not require a new licence.
References & Sources
- Law No. 40 of 2007 on Limited Liability Companies — Status Record — peraturan.go.id
- Law No. 40 of 2007 on Limited Liability Companies — Government Text — pajak.go.id
- Law No. 6 of 2023 Enacting the Job Creation Government Regulation in Lieu of Law — peraturan.go.id
- Minister of Law Regulation No. 49 of 2025 on PT Formation, Amendment and Dissolution — peraturan.go.id
- OSS Guide — Changes to Business Licensing: Business Entity Data — oss.go.id
- OSS Business Entity Data Change Guide — Detailed Workflow — s3-stg.oss.go.id
Recommended Next Articles
- notary services for foreign investors and corporate amendments — jakartalegalid.com
- NIB and OSS registration guide for Indonesian businesses — jakartalegalid.com
- beneficial ownership updates after acquisitions — jakartalegalid.com