HSJGlobal

Corporate identity changes

Company Name Changes in Indonesia: Update the Deed, Registry and Operating Documents

Separate the legal amendment from the record updates that let banks, counterparties and operating teams use the new identity.

A company name-change deed and an updated trading identity perform different jobs in Indonesia. For an existing ordinary Perseroan Terbatas (PT), including a foreign investment company (PT PMA), the legal-name amendment requires ministerial approval; signing the deed alone does not make the amendment effective. Articles 21 and 23 of the Company Law establish that distinction. A brand refresh should first be checked against whether the registered company name actually changes.

Treat the work as a legal amendment followed by separate record updates. Prepare communications in advance, but distinguish the approval date from the date each licence, tax record, bank or counterparty accepts the new name. The scope here is an existing ordinary PT; a Perseroan Perorangan uses its own registration procedure. A merger, transfer of business or change of legal form needs a separate analysis.

Key takeaways

  • Define whether you are changing the registered legal name, a customer-facing brand, or both before commissioning filings.
  • A rename does not establish a replacement company; preserve evidence connecting the former name to the existing entity.
  • The legal timetable includes calendar-day filing limits; AHU examination and downstream acceptance are different clocks.
  • Check AHU-sourced information before confirming an OSS update, then inspect the documents actually issued.
  • Close the handover with recipient evidence: a filed request or an announcement email alone does not establish acceptance.

Define the rename before announcing it

Start with a written change specification: exact old and proposed names, current deed and approval references, current identifiers, and every other fact intended to change. Keep ownership, directors, address, capital and activities on separate lines. This prevents an apparently simple rename from concealing a wider amendment or a licensing change.

Check the proposed name before treating it as available. Government Regulation 43/2011 requires submission before the name amendment and sets conditions including Latin letters, distinctness from other lawful company names and restrictions concerning public bodies. For companies wholly owned by Indonesian citizens or Indonesian legal entities, Article 11 requires an Indonesian-language name. Have the notary assess the actual wording; do not reduce the assessment to a domain-name search.

The existing establishment deed and subsequent amendments provide the starting identity file. The records created during company formation in Indonesia should be retrieved before a later name amendment so the notary can trace the company being changed. A new incorporation checklist cannot substitute for that history.

Give the communications team a proposed launch date with dependencies, rather than an unconditional deadline. Shareholder preparation, notarial execution, AHU examination and recipient updates have separate completion points. The ministerial approval date is the legal-name change trigger. An earlier website or logo launch does not supply that approval.

Confirm what the rename actually changes

Bring the proposed spelling and a list of accompanying corporate changes so the amendment scope can be checked before signing.

Put the new name into the deed and AHU approval

For an ordinary PT, use the shareholder-to-notary-to-Ministry route below. Minister of Law Regulation 49/2025 is the current administrative framework and replaces Regulation 21/2021. The company and notary should agree the exact scope and supporting file before the corporate decision is executed.

For the notary’s file, prepare the amendment deed, shareholder decision, NPWP, payment evidence and address evidence. Article 11 also lists beneficial-owner documents: the directors’ authority to the notary, their beneficial-owner statement and the beneficial owner’s consent. Have the notary identify any additional agency support. Capital-payment or newspaper evidence belongs to the relevant capital-change branch, not automatically to a name-only amendment.

  1. Confirm the proposed name through the name-approval procedure. Keep the approved spelling and reference; Article 7 of Regulation 43/2011 requires the approved name to be stated in the deed within 60 days of name approval.
  2. Adopt the articles amendment through a valid shareholders’ meeting (RUPS) or binding written shareholders’ decision. Have the notary check the decision method, voting requirements, articles and signatory authority.
  3. Execute an Indonesian-language notarial amendment deed identifying the company and revised name. Reconcile its particulars with the current corporate record before filing.
  4. Authorize the notary to submit the amendment through the electronic legal-entity administration system, SABH. The notary completes the change form, uploads the deed and relevant support, and makes the required electronic declaration under Articles 9–11 of Regulation 49/2025 .
  5. Obtain the ministerial approval decision and compare its name, deed references and date with the submitted file. Preserve the decision and a current AHU record alongside the signed deed.

Track two separate 30-calendar-day limits : where the shareholder decision is not recorded in a notarial meeting deed, it must be stated in a notarial deed within 30 days of the decision; the approval application must then be submitted within 30 days of the amendment deed. Article 21 prevents filing after the applicable limit. These are legal limits, not suggested turnaround times.

Under Articles 13–15 of Regulation 49/2025 , examination is up to 14 working days from receipt. A returned application has a seven-calendar-day completion window; failure to complete it leads to rejection. A permitted resubmission still needs a valid underlying filing basis. No verified universal end-to-end duration covers shareholder preparation, AHU and every downstream recipient.

Before submission, ask for an itemized payment instruction identifying official charges separately from notarial and other professional work. Retain payment evidence, the submission reference and all correction notices with the application. This is a document-control recommendation, not a published service price or an approval promise.

Registry evidence should be read at the right level: AHU profiles and their evidence limits help distinguish a current recorded identity from the separate deed, licence and third-party checks. Compare the specific output rather than accepting a screenshot labelled “done”.

One approved identity, several record owners Compare the AHU-approved name with OSS, tax and bank records, then operating documents. Preserve the former-to-current identity trail. Connections indicate reconciliation rather than automatic updates. AHU-approved legal name OSS / NIB Tax record Bank / merchant file Contracts and document templates Former-to-current identity archive
Use the approved name as a common reference. Each recipient still needs its own update and completion check.

Reconcile OSS and tax identity records

AHU approval supplies the legal reference; it does not demonstrate that every downstream record already agrees. The current OSS business-entity amendment manual says that AHU-sourced entities must first change their source data through the notary. In OSS, its route is Perizinan Berusaha → Kelola Usaha → Perubahan → Perubahan Badan Usaha. Compare the old OSS information with the incoming AHU information before confirming and saving.

The same manual shows the company name as an automatically sourced, non-editable field. Correct AHU-sourced errors upstream rather than inventing a different spelling in an editable contact field. Keep the saved result, then open the issued Business Identification Number (NIB) and relevant licensing outputs to check the actual name displayed.

OSS also publishes a specific company-name change guide describing a Perubahan Nama Perusahaan form, the new AHU-matching name without the entity prefix in that particular field, and the corresponding new approval number. It describes updated issued products and a history view with Cetak NIB. Menu layouts can differ: follow the route present in the current account and validate its issued results. The field instruction is not permission to omit PT from legal documents.

Tax records are a separate reconciliation. DGT expressly treats a PT rename without changing legal form as a taxpayer identity data change supported by evidence of the change. Have the authorized tax user compare the company Taxpayer Identification Number (NPWP) record with the approval and deed; preserve the identifiers rather than creating another taxpayer registration to bypass an inconsistency.

DGT’s published Coretax data-update manual documents My Portal → Data Update, supporting documents, submission and a downloadable receipt. It does not establish that every legal-name field is freely editable in every account. Where source data or access prevents correction, use DGT’s documented data-change service with the supporting file. Retain both the request receipt and the later corrected record; they prove different stages.

Resolve a registry-to-system discrepancy

Identify which record supplies the disputed name and bring the approval, submitted data and issued output for a focused comparison.

Switch operating documents while preserving company history

Create an old-to-new identity bridge before distributing replacement documents. Record both names, the effective approval date, deed and decision references, existing corporate identifiers and the person responsible for each recipient. This working tool is a recommended control, not another government form.

Record owner Update to arrange Evidence to retain Release check
Legal / corporate records Add amendment deed and ministerial approval; preserve establishment history. Executed deed, approval and current AHU comparison. Old and new names trace to the same company.
Licensing / tax users Reconcile OSS products and the taxpayer identity record. Saved result, issued files and tax change outcome. Approved spelling appears in relevant current outputs.
Finance / bank / merchant provider Request customer-record and account-title review through each recipient’s channel. Submitted pack and recipient confirmation or outstanding conditions. Payment instructions use a recipient-accepted identity.
Contract / procurement owners Check notice, consent and document amendment requirements. Contract review, notices, acknowledgements or agreed amendments. Counterparty records and required notices are resolved.
Sales / operations Replace current invoice, purchase-order, letterhead and portal templates. Dated template versions and a sample generated document. Live documents use the approved legal identity.

Article 5(3) of the Company Law requires the company name and full address in correspondence, company announcements, printed materials and deeds to which it is a party. Turn that rule into a template inventory rather than changing only the website footer. Check invoice headers, purchase orders, quotations, delivery documents and customer or supplier portals relevant to the business.

Bank and merchant-provider acceptance is recipient-specific. Send the existing corporate evidence plus the rename documents, and ask what each institution needs for its customer record, account title and transaction channels. A ministry decision should not be represented as proof that a bank has completed its own update. Verify new payment instructions through an established independent channel before distributing them.

Review existing contracts for notice, consent and amendment clauses. Do not silently overwrite the historical contracting name or describe a name-only amendment as a transfer to another entity. Where a continuity notice is appropriate, identify the former and approved names, approval reference and relevant contract. Use a formal amendment when the contract or recipient requires one; escalate disputed continuity or security-document issues for legal review.

Keep executed historical documents unchanged in the archive. Mark superseded templates so staff stop generating them, while preserving their issue dates and links to the rename evidence. Test one current invoice or order from the production system, not just its design preview: cached templates and vendor master data can continue to supply the old name.

Repair name mismatches at their source

Diagnose the first record that diverges from the approved identity. Repeating downstream submissions while leaving that source wrong spreads conflicting versions. Keep the disputed output, exact field, error message, submission date and responsible system owner together so the correction can be reproduced.

The approval or deed contains the wrong particulars

Pause distribution of the affected documents and ask the notary to compare the shareholder decision, executed deed, filed form and decision. The correction route depends on which instrument is wrong. Do not edit a PDF, backdate a replacement or assume that an informal email changes the official record.

AHU is correct but OSS still shows the former name

Compare the new approval reference with the AHU-sourced panel and the output generated after saving. Use the company’s amendment history to distinguish an old downloaded copy from an unresolved current record. If the saved profile and issued product disagree, retain both files for the system support case instead of filing a duplicate business registration.

A filing is returned or a deadline has passed

Read the formal notice immediately and assign the response to the notary and document owner. The seven-calendar-day return window under Article 14 needs its own diary entry. Where the original deed or submission limit has expired, have the notary establish the valid new corporate and filing basis before resubmitting; a support ticket does not extend a statutory limit.

A counterparty rejects the new-name document

Ask which identity comparison failed: legal name, tax record, account beneficiary, authority or contract notice. Supply the relevant continuity evidence and retain the counterparty’s response. If payment or delivery is blocked, control that transaction separately while the record is corrected. An internal spreadsheet marked complete cannot override the recipient’s unresolved requirement.

Release the company name against three evidence gates

Release the renamed company’s operating documents only when three gates have evidence: legal effectiveness, reconciled official records and acceptance for the intended transaction. The first gate needs the amendment deed and approval; the second needs the relevant current AHU, OSS and tax comparisons; the third needs the bank, provider or counterparty outcome that the transaction actually depends on.

The responsible company officer should retain one handover index linking every closed item to its file and date, with unresolved recipients assigned individually. If an inconsistency could cause a rejected payment, incorrect tax document or disputed contracting party, keep that use on hold and escalate the specific issue. Completing one gate does not close the others.

Prepare the rename evidence handover

Bring the deed, approval, current system outputs and recipient status list to define the remaining actions for your planned transaction.

Frequently asked questions

Can we use the approved business brand instead of renaming the PT?

First identify which name is changing. A customer-facing brand and the registered legal name can be different. Keep the legal entity identifiable in contracting and required company disclosures; assess any brand or trademark work separately from the articles amendment.

Does changing the foreign parent’s name automatically rename its Indonesian subsidiary?

No. Establish whether the change concerns the shareholder’s identity or the Indonesian company’s own name. The subsidiary should not replace its registered name merely because its parent has rebranded. Have the notary identify the relevant corporate-record amendment.

Should we remove PT when preparing the new documents?

The OSS name-change guide’s instruction concerns a particular input field. It should not be applied indiscriminately to deeds, contracts or correspondence. Use the complete approved legal identity in the format required by the document and recipient.

What should a rename work order include?

Specify the legal amendment, filing support, record checks and downstream updates individually. Identify who handles the tax record, bank and contractual notices, what completion evidence is included, and which recipient decisions remain outside the provider’s control.

Can the amendment file also change directors or business activities?

List the additional changes explicitly before signing. Each needs the appropriate corporate authority, supporting documents and downstream treatment. A name-only release check cannot establish that a different director, activity or project is correctly authorized and recorded.

On this page
Chat with an Expert