Once an Indonesian company’s new legal name has been approved, the remaining work is mostly about consistency. AHU, OSS, tax records, banks, contracts, invoices, licences, counterparties, websites, and internal systems should be reviewed so that documents used after the change no longer conflict with the company’s approved legal identity.
The legal starting point is that Permenkum 49/2025 classifies a change of company name as an amendment to the articles of association requiring ministerial approval.
For the corporate filing itself, Article 10 of Permenkum 49/2025 requires covered amendment applications to be submitted through a notary electronically through SABH.
This guide begins after that corporate amendment stage. It focuses on what a business should reconcile once the approved name becomes the reference point for its continuing operations.
After Company Name Change Indonesia: What to Update First
For after company name change Indonesia implementation, do not update records randomly. Work outward from the official corporate record.
A practical order is:
- confirm the final AHU/SABH corporate record and amendment documents
- reconcile OSS business-entity data
- review the corporate taxpayer identity
- update banking and payment records
- review contracts, customers, and suppliers
- check licences, certificates, and sector registrations
- update invoices, accounting, HR, websites, and other operational records
The exact list will vary by business. A company with mining, industrial, construction, import, regulated product, employment, property, or financing arrangements may have more external records to reconcile than a simple service company.
1. Confirm the Final AHU and Corporate Record
Before changing external records, establish one authoritative company-name file.
Keep the amendment deed, ministerial approval or other relevant AHU output, and current corporate record together. Record the old legal name, new legal name, approval details, and the date from which your internal teams will begin using the new name operationally.
This file becomes the evidence package for banks, customers, suppliers, tax administration, licensing systems, landlords, insurers, and other parties that ask why the company name changed.
Avoid allowing different departments to work from different spellings or abbreviations. The legal name appearing in the approved corporate record should be the reference for formal documentation.
2. Reconcile the New Name in OSS
For a PT whose legality data comes from AHU Online, the official OSS business-entity change guide states that data changes in OSS can be made only after the underlying data change has first gone through the notarial process.
The same guide explains that the OSS change screen displays the old profile data according to OSS alongside the new profile data according to AHU Online.
That sequence matters. For an AHU-sourced PT, do not treat OSS as the system that creates the legal company-name amendment. Use the completed corporate change as the upstream record, then review the OSS synchronization or change workflow.
Check More Than the Displayed Company Name
When reviewing OSS, look beyond the company-name field.
Check whether the business profile still correctly reflects the company’s email, NPWP, telephone details, address information, investment status, business purposes, management and shareholder data, and other information relevant to the company’s actual record. A company-name project should not become an excuse to alter unrelated facts, but it is a useful point to detect inconsistencies already visible between systems.
Then review the company’s NIB, business licences, Standard Certificates, PB UMKU items, or other OSS-generated records that are operationally important. Whether a particular licence requires additional action depends on the sector and the way the relevant authority handles changed company identity data.
3. Review the Corporate Taxpayer Identity
Tax administration should be checked separately rather than assuming that every corporate amendment automatically appears correctly in every tax-facing record.
For tax administration, DJP lists PER-7/PJ/2025 as active and uses it as the current technical framework for taxpayer administration, including taxpayer-data changes.
For legal-entity taxpayers, the current PER-7/PJ/2025 annex expressly covers changes to corporate taxpayer identity and lists electronic submission channels including the Taxpayer Portal and systems integrated with DJP’s administration.
The current corporate taxpayer change-data form also records the taxpayer name together with information such as the amendment decision and amendment document in the taxpayer-identity section.
After the corporate name change, therefore check the taxpayer profile actually visible in the current DJP system and determine whether any identity-update action or supporting document remains necessary for the company’s circumstances.
Reconcile Tax and Bookkeeping Master Data
Once the tax-facing identity is correct, review the operational records that use it.
Useful checks include:
- invoice and billing templates
- customer and vendor master data
- accounting-software company profiles
- bookkeeping headers and management reports
- tax working papers
- reimbursement and expense forms
- purchase orders
- payment instructions
- finance-team email templates
These are practical reconciliation steps, not separate statutory filings in every case. Their purpose is to prevent the old company name from continuing to appear on documents generated after the legal change.
4. Update Bank and Payment Records
Banks should be contacted directly because document requirements and internal procedures can differ between institutions and account types.
Prepare a bank update pack that may include the amendment deed, ministerial or AHU evidence, current corporate documents, updated management authorization where relevant, and any forms requested by the bank.
Review more than the account display name. Depending on the company’s arrangements, ask whether the name change affects:
- current and savings accounts
- internet-banking profiles
- payment gateways
- merchant facilities
- corporate cards
- loan or facility records
- guarantees or security documents
- authorized-signatory records
- virtual accounts
- incoming-payment instructions
Do not tell customers to use a new beneficiary name until the receiving bank confirms how the account is recorded. That reduces avoidable payment rejection or reconciliation problems.
5. Review Contracts, Customers and Suppliers
A legal-name change should trigger a contract review, but it should not automatically be described as requiring a new contract or novation in every case.
Start by checking each material agreement for:
- legal-name or party-identification provisions
- notice obligations
- change-of-details clauses
- invoice requirements
- bank-account notification rules
- licence or regulatory representations
- assignment or novation provisions
- formal notice addresses
Where a contract requires notice of changed corporate particulars, send the notice in the required format and retain delivery evidence. Where no formal amendment is needed, customers or suppliers may still need the new legal name for procurement, vendor onboarding, accounts payable, invoicing, or compliance systems.
For major financing, property, shareholder, joint-venture, distribution, government, or regulated-sector contracts, review the document individually rather than relying on a generic name-change email.
6. Review Licences, Certificates and Sector Records
Do not assume that every permit automatically follows the AHU name change.
Create an inventory of licences and approvals used by the company and check each one against the new legal name. Depending on the business, this can include OSS records, PB UMKU, sector licences, industrial approvals, mining licences, construction or electrical certifications, environmental approvals, import-related registrations, product approvals, or professional credentials.
For each record, classify it as:
- automatically synchronized or already correct
- editable through an official system
- requiring notification to an authority
- requiring reissuance or endorsement
- requiring no action other than internal record retention
- unresolved and needing confirmation from the competent authority
This approach is safer than assuming one rule applies to every licence.
7. Update Public-Facing and Internal Records
After government and regulated records are under control, update the materials people use every day.
Review:
- website legal notices and footer information
- email signatures
- letterhead
- quotations and proposals
- invoice templates
- purchase orders
- HR documents
- employment templates
- procurement records
- internal policies
- accounting and ERP company profiles
- insurance records
- leases
- customer portals
- supplier portals
- marketplace or payment-platform profiles
- company stamps where still used
Keep a controlled historical record linking the old legal name to the new one. Archived contracts, tax documents, bank statements, licences, and invoices issued before the change should not simply be rewritten. The company may need to demonstrate later that records under both names belong to the same corporate history.
Practical Post-Change Reconciliation Checklist
Before closing the project, confirm that:
- the final AHU/SABH corporate record reflects the new legal name
- the amendment deed and approval evidence are retained
- OSS data has been reviewed against the AHU-originating data
- NIB and important OSS licensing records have been checked
- the current DJP taxpayer identity has been reviewed
- tax and bookkeeping master data uses the correct legal name
- bank records have been updated or confirmed
- payment instructions match the bank’s accepted beneficiary name
- material contracts have been checked for notification requirements
- customers and suppliers have received updated corporate details where needed
- licences and certificates have been reviewed individually
- invoice, purchase-order, website, email, and ERP templates have been updated
- historical documents under the former name remain traceable
- unresolved sector-specific changes have been assigned to a responsible person
The most useful project record is a simple reconciliation tracker showing the system or counterparty, old name, new name, evidence required, responsible person, submission date, and completion status.
Conclusion
After a company name change in Indonesia, the main risk is inconsistent identity data across systems and documents rather than the branding exercise itself.
Start with the approved corporate record, then reconcile OSS and tax administration before moving to banks, contracts, licences, invoices, counterparties, and internal systems. Government systems should be handled according to their current official procedures; private institutions and contracts should be checked against their own requirements instead of assuming a universal process.
A documented reconciliation trail also matters. Keeping the amendment evidence together with records of each completed update makes it easier to explain the transition from the former legal name to the new one during licensing, banking, tax, audit, contractual, or due-diligence reviews.
Reconcile the New Company Name Across Your Business Records
If your Jakarta company has completed a legal-name amendment, Jakarta Legal ID can assist with a consultation to map the corporate, OSS, tax, bookkeeping, licensing, and document updates that should be reviewed after approval.
The scope should be matched to the company’s actual licences, taxpayer records, banks, contracts, operating systems, and counterparties rather than applying a generic update list to every business.
For help coordinating corporate documents, signing requirements and any required deed preparation with the responsible licensed notary, review our Notary Services and agree the scope for the specific document or corporate action.
Read More: Notarial Documents in Indonesia: Company, Contract and Property Guide
FAQ After Company Name Change Indonesia
Does OSS update automatically after a company name change?
For a PT whose legality data originates from AHU Online, official OSS guidance treats the AHU/notarial data change as the upstream step. The business should then use the OSS business-entity change workflow and confirm that the new AHU-originating profile data is reflected correctly.
Should the company update its tax data after changing its legal name?
The tax profile should be reviewed. Current PER-7/PJ/2025 covers corporate taxpayer identity changes, and the current corporate taxpayer change-data form includes taxpayer-name and amendment information.
Does a company-name change require a new bank account?
There is no universal answer across all banks and products. Contact the bank and follow its corporate-data update procedure. The bank may update the existing account record or require additional documentation depending on the account and facility.
Do all existing contracts need to be signed again after the company name changes?
Not necessarily. Review each material contract for notice, party-identification, amendment, assignment, novation, invoicing, and change-of-details provisions. The appropriate action depends on the contract rather than one universal name-change rule.
Should old invoices and contracts be replaced with the new company name?
Historical documents should generally remain traceable as records of what was issued or signed at the time. Update templates and future-facing records, while retaining evidence that connects the former legal name with the approved new name.
Do business licences need to be reissued after a company name change?
Not every licence follows the same procedure. Review each important OSS and sector-specific licence to determine whether the name is synchronized, editable, subject to notification, or requires action by the competent authority.
References & Sources
- Current Status of Ministry of Law Regulation No. 49 of 2025 — peraturan.bpk.go.id
- Official Text of Ministry of Law Regulation No. 49 of 2025 — peraturan.go.id
- OSS Guide to Changes in Business Licensing – Business Entity Data — s3-stg.oss.go.id
- Current Taxpayer Administration Regulation PER-7/PJ/2025 — pajak.go.id
- Official Annex to PER-7/PJ/2025 — pajak.go.id