PT PMA Address Update After Incorporation Guide

A PT PMA address update should be managed as a cutover across corporate records, AHU, OSS entity data and project locations, licences, Coretax and KPP, bank KYC, beneficial ownership where affected, contracts, invoices, payroll, insurance, mail, and operating access. The new site must pass its own activity, spatial, building, lease, and sector review before the old address is released.

Separate a legal domicile move from an operating-site move; they may require different corporate and licence actions. Fix the effective date, approval route, mail overlap, old and new authority, system owners, customer notices, and operating stop. If the new address crosses tax-office jurisdiction, DJP guidance distinguishes a registered-office transfer from a data change. Do not rely on automatic synchronization.

Key takeaways

• Approve the old-to-new function map and cutover date.
• Do not vacate or amend until the new address passes its evidence gate.
• Keep affected operations blocked until the new site-specific licence state is effective.
• Keep old mail and authorized monitoring until critical recipients accept the new address.
• Close the project from a signed cross-system and physical-site reconciliation.

In this article

• Define the move
• Clear the new address
• Sequence government updates
• Regulatory Notes and Limitations
• Official References and Review Basis
• Move downstream records
• Close the address move
• Close the PT PMA move after the first live-cycle test

Pt pma address update decision controls

Use the control, evidence, and release condition together; no single document should carry more meaning than it actually proves.

Define the address-change scope and effective date

The control file must show how the company will separate domicile, administration, tax, bank, project, warehouse, factory, and other operating functions. For define the address-change scope and effective date, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.

An address project fails when teams assume every function moves together. A reviewer should trace old and new address functions and corporate and operating approvals to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For define the address-change scope and effective date, the practical deliverable is a version-controlled decision row that remains usable when the activity, location, counterparty, or responsible person changes. It should connect old and new address functions with corporate and operating approvals, then show how effective-date plan and mail and access overlap affect the next approval. Record the source for old and new address functions, the reviewer of corporate and operating approvals, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test define the address-change scope and effective date through normal progress, delayed corporate and operating approvals, and failure of effective-date plan. The normal case confirms the intended order for old and new address functions; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for mail and access overlap. Retain this stage-specific result with the final approval and review calendar.

• Old and new address functions
• Corporate and operating approvals
• Effective-date plan
• Mail and access overlap

For define the address-change scope and effective date, close the stage only when the authoritative record and the operating evidence agree, or when an unresolved difference has a named owner and stop condition.

Clear the new site before corporate cutover

For PT PMA address update, complete owner, lease, spatial, building, activity, licence, tax, bank, and service evidence for the new location. For clear the new site before corporate cutover, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.

Moving the legal record first can leave the company registered at an unusable site. A reviewer should trace right-of-use chain and spatial and building evidence to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For clear the new site before corporate cutover, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect right-of-use chain with spatial and building evidence, then show how oss project feasibility and tax and bank requirements affect the next approval. Record the source for right-of-use chain, the reviewer of spatial and building evidence, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test clear the new site before corporate cutover through normal progress, delayed spatial and building evidence, and failure of oss project feasibility. The normal case confirms the intended order for right-of-use chain; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for tax and bank requirements. Retain this stage-specific result with the final approval and review calendar.

• Right-of-use chain
• Spatial and building evidence
• OSS project feasibility
• Tax and bank requirements

For clear the new site before corporate cutover, the output should name the owner, source evidence, unresolved condition, acceptance test, and the event that permits the next step. For the adjacent control framework, compare Changing a PT PMA in Indonesia .

Sequence AHU, OSS, and licence changes

The responsible team should complete the corporate route and update entity, project, location, licence, verification, and supporting records in the approved order. For sequence ahu, oss, and licence changes, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.

An entity-address edit can leave operational projects or licences at the old site. A reviewer should trace deed and ahu evidence and oss before-and-after exports to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For sequence ahu, oss, and licence changes, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect deed and ahu evidence with oss before-and-after exports, then show how project and licence updates and verification and conditions affect the next approval. Record the source for deed and ahu evidence, the reviewer of oss before-and-after exports, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test sequence ahu, oss, and licence changes through normal progress, delayed oss before-and-after exports, and failure of project and licence updates. The normal case confirms the intended order for deed and ahu evidence; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for verification and conditions. Retain this stage-specific result with the final approval and review calendar.

• Deed and AHU evidence
• OSS before-and-after exports
• Project and licence updates
• Verification and conditions

For sequence ahu, oss, and licence changes, preserve the source record, reviewer, date, exception, and approval so another team can reproduce the decision without relying on memory. Where this stage changes another workstream, review PT PMA Registered Address Requirements in Indonesia .

Regulatory Notes and Limitations

PT PMA Address Update After Incorporation Guide provides a decision and evidence framework, not a universal legal opinion. Review the current official output and company-specific facts before filing, contracting, paying, or operating.

• For PT PMA Address Update After Incorporation Guide, address acceptability depends on the real activity, local spatial plan, building use, lease rights, sector rules, and the specific government or counterparty record being updated.
• For PT PMA Address Update After Incorporation Guide, a corporate domicile, administrative office, warehouse, restaurant, factory, project site, and tax place of business can require different evidence and should not be treated as interchangeable.
• For PT PMA Address Update After Incorporation Guide, local rules and official spatial data should be checked for the precise parcel and intended use immediately before signing or filing.

Official References and Review Basis

Primary materials for PT PMA Address Update After Incorporation Guide were checked on August 4, 2026 and support this page's framework; they do not replace a matter-specific legal, tax, licensing, accounting, security, premises, or bank review of PT PMA Address Update After Incorporation Guide.

• Directorate General of Taxes guidance on address changes : Official explanation of changing address data versus moving the registered tax office.
• Directorate General of Taxes taxpayer-data change service : Official scope and supporting-document route for company and address data changes.
• Coretax DJP implementation page : Official tax administration portal guidance effective for administration from January 2025.
• Online Single Submission portal : Official NIB, four-level risk classification, business licensing, KBLI, and support portal.
• Government Regulation No. 28 of 2025 : Current risk-based business licensing framework; it revoked Government Regulation No. 5 of 2021.
• Government Regulation No. 16 of 2021 : Building approval, technical standards, and building fitness framework.

Move tax, bank, contracts, and communications

A supportable decision begins when the company can complete Coretax or KPP, bank KYC, invoice, contract, insurance, payroll, supplier, customer, domain, signage, and mail changes. For move tax, bank, contracts, and communications, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.

Government acceptance does not automatically update counterparties or notice channels. A reviewer should trace djp acceptance and bank kyc receipt to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For move tax, bank, contracts, and communications, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect djp acceptance with bank kyc receipt, then show how notice and master-data log and mail custody and forwarding affect the next approval. Record the source for djp acceptance, the reviewer of bank kyc receipt, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test move tax, bank, contracts, and communications through normal progress, delayed bank kyc receipt, and failure of notice and master-data log. The normal case confirms the intended order for djp acceptance; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for mail custody and forwarding. Retain this stage-specific result with the final approval and review calendar.

• DJP acceptance
• Bank KYC receipt
• Notice and master-data log
• Mail custody and forwarding

For move tax, bank, contracts, and communications, turn the result into a controlled work item with a responsible person, due date, evidence location, escalation path, and release condition.

Run post-move reconciliation and close

Before the next commitment, management should test live records, first invoices and filings, bank access, mail, licences, and actual occupancy and resolve exceptions. For run post-move reconciliation and close, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.

Address defects often surface only after the first transaction or authority notice. A reviewer should trace final address matrix and first-cycle samples to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For run post-move reconciliation and close, a defensible review separates facts already evidenced, facts requested but not received, assumptions approved for planning, and conditions that still block release. It should connect final address matrix with first-cycle samples, then show how open exception schedule and close and renewal approval affect the next approval. Record the source for final address matrix, the reviewer of first-cycle samples, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test run post-move reconciliation and close through normal progress, delayed first-cycle samples, and failure of open exception schedule. The normal case confirms the intended order for final address matrix; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for close and renewal approval. Retain this stage-specific result with the final approval and review calendar.

• Final address matrix
• First-cycle samples
• Open exception schedule
• Close and renewal approval

For run post-move reconciliation and close, record both the accepted position and the rejected alternatives; this prevents a later portal edit or provider message from silently changing the decision.

Place the pt pma address update decision inside HSJGlobal’s Indonesia company registration scope before executing documents, filings, or funding.

Close the PT PMA move after the first live-cycle test

An address update is complete when the new corporate and operating functions are usable, licensed, reachable, and accepted across government and counterparty systems. The deed or OSS edit is only part of that state.

Maintain an overlap for notices and test the first invoice, filing, bank, mail, and licence cycle before releasing the old address and closing exceptions.

Related insights

• Changing a PT PMA in Indonesia
• PT PMA Registered Address Requirements in Indonesia
• PT PMA Address Requirements for Bank Account Opening