Indonesia Address Provider Exit and Replacement Plan
Recover correspondence, originals, authority access, address evidence, and account data before moving corporate, OSS, tax, bank, and contract records.
An Indonesia company should replace an address provider through a controlled overlap, not a same-day cancellation. First preserve the incumbent address evidence, mail and authority-contact history, original documents, portal recovery channels, and unresolved notices; then qualify the replacement site and sequence the authoritative corporate, OSS, tax, bank, contract, and counterparty updates. DGT's taxpayer-data change service illustrates that each record has its own supporting-document route.
The company must determine whether it is only changing a correspondence service, changing its legal domicile, moving to another tax-office jurisdiction, changing an OSS project location, or relocating actual operations. Those events have different approvals and dependencies. Keep the old service active long enough to receive straggling notices and prove the transition, but tightly limit the provider's retained access and authority.
Address-provider replacement decision controls
Use the control, evidence, and release condition together; no single document should carry more meaning than it actually proves.
| Control stage | Question to resolve | Evidence anchor |
|---|---|---|
| Trigger the exit and freeze the current record | record the reason for replacement, effective dates, current addresses, provider access, open filings, correspondence, and operational dependencies | Provider contract and notices |
| Recover documents, data, mail, and authority access | collect originals, scans, visitor records, mail, tax letters, government notices, access credentials, and service histories under a signed index | Signed document inventory |
| Qualify the replacement address against the real activity | test the new parcel, building, permitted use, provider authority, mail process, inspections, price, term, and failure protections | Spatial and building evidence |
| Sequence authoritative and dependent updates | approve the deed or corporate step first where required, then reconcile AHU, OSS, tax, bank, contracts, invoices, licences, payroll, and counterparties | Corporate approval and notarial route |
| Run overlap, acceptance, and old-provider closure | test mail, visits, downloads, recovery, inspection response, and record consistency before ending the old service and revoking access | Test correspondence and visitor event |
Key takeaways
- Do not issue termination until the company can reproduce the complete current state.
- Treat every missing original, notice, or access route as a priced and owned exit exception.
- Accept the new address only after live evidence and use-specific conditions are verified.
- Use a dependency map and hold each downstream update until its accepted source record exists.
- Close the incumbent only after a dated live test and documented straggler-notice period.
Scope the address-provider replacement before acting
Share the company facts, intended outcome, current records, and unresolved conditions so the address-provider replacement review can be bounded.
In this article
Trigger the exit and freeze the current record
The responsible team should record the reason for replacement, effective dates, current addresses, provider access, open filings, correspondence, and operational dependencies. For trigger the exit and freeze the current record, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.
Cancelling first can strand government mail, originals, recovery channels, or proof used by banks and regulators. A reviewer should trace provider contract and notices and current address evidence to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For trigger the exit and freeze the current record, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect provider contract and notices with current address evidence, then show how mail and authority-contact log and user and recovery-channel inventory affect the next approval. Record the source for provider contract and notices, the reviewer of current address evidence, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Test trigger the exit and freeze the current record through normal progress, delayed current address evidence, and failure of mail and authority-contact log. The normal case confirms the intended order for provider contract and notices; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for user and recovery-channel inventory. Retain this stage-specific result with the final approval and review calendar.
Evidence rule
Do not issue termination until the company can reproduce the complete current state.
- Provider contract and notices
- Current address evidence
- Mail and authority-contact log
- User and recovery-channel inventory
For trigger the exit and freeze the current record, preserve the source record, reviewer, date, exception, and approval so another team can reproduce the decision without relying on memory.
Recover documents, data, mail, and authority access
A supportable decision begins when the company can collect originals, scans, visitor records, mail, tax letters, government notices, access credentials, and service histories under a signed index. For recover documents, data, mail, and authority access, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.
Missing correspondence or provider-controlled accounts can conceal deadlines and prevent the company from updating its own records. A reviewer should trace signed document inventory and mail and courier reconciliation to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For recover documents, data, mail, and authority access, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect signed document inventory with mail and courier reconciliation, then show how portal and account access map and open-notice and deadline schedule affect the next approval. Record the source for signed document inventory, the reviewer of mail and courier reconciliation, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Test recover documents, data, mail, and authority access through normal progress, delayed mail and courier reconciliation, and failure of portal and account access map. The normal case confirms the intended order for signed document inventory; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for open-notice and deadline schedule. Retain this stage-specific result with the final approval and review calendar.
Control point
Treat every missing original, notice, or access route as a priced and owned exit exception.
- Signed document inventory
- Mail and courier reconciliation
- Portal and account access map
- Open-notice and deadline schedule
For recover documents, data, mail, and authority access, turn the result into a controlled work item with a responsible person, due date, evidence location, escalation path, and release condition.
Qualify the replacement address against the real activity
Before the next commitment, management should test the new parcel, building, permitted use, provider authority, mail process, inspections, price, term, and failure protections. For qualify the replacement address against the real activity, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.
A fast replacement can reproduce the same zoning, service, documentation, or operational mismatch that caused the exit. A reviewer should trace spatial and building evidence and provider title or occupancy rights to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For qualify the replacement address against the real activity, 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 spatial and building evidence with provider title or occupancy rights, then show how service-level and inspection protocol and activity-location suitability memo affect the next approval. Record the source for spatial and building evidence, the reviewer of provider title or occupancy rights, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Test qualify the replacement address against the real activity through normal progress, delayed provider title or occupancy rights, and failure of service-level and inspection protocol. The normal case confirms the intended order for spatial and building evidence; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for activity-location suitability memo. Retain this stage-specific result with the final approval and review calendar.
Release test
Accept the new address only after live evidence and use-specific conditions are verified.
- Spatial and building evidence
- Provider title or occupancy rights
- Service-level and inspection protocol
- Activity-location suitability memo
For qualify the replacement address against the real activity, record both the accepted position and the rejected alternatives; this prevents a later portal edit or provider message from silently changing the decision. For the adjacent control framework, compare PT PMA Registered Address Requirements in Indonesia .
Test the address-provider replacement evidence
Reconcile the authoritative, operational, contractual, tax, banking, and evidence fields that affect the address-provider replacement decision.
Sequence authoritative and dependent updates
The control file must show how the company will approve the deed or corporate step first where required, then reconcile AHU, OSS, tax, bank, contracts, invoices, licences, payroll, and counterparties. For sequence authoritative and dependent updates, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.
Updating dependent records before their authoritative source creates inconsistent names, dates, jurisdictions, and supporting files. A reviewer should trace corporate approval and notarial route and ahu and oss update receipts to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For sequence authoritative and dependent updates, the practical deliverable is a version-controlled decision row that remains usable when the activity, location, counterparty, or responsible person changes. It should connect corporate approval and notarial route with ahu and oss update receipts, then show how tax-office and coretax route and bank and counterparty notification pack affect the next approval. Record the source for corporate approval and notarial route, the reviewer of ahu and oss update receipts, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Test sequence authoritative and dependent updates through normal progress, delayed ahu and oss update receipts, and failure of tax-office and coretax route. The normal case confirms the intended order for corporate approval and notarial route; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for bank and counterparty notification pack. Retain this stage-specific result with the final approval and review calendar.
Stop condition
Use a dependency map and hold each downstream update until its accepted source record exists.
- Corporate approval and notarial route
- AHU and OSS update receipts
- Tax-office and Coretax route
- Bank and counterparty notification pack
For sequence authoritative and dependent updates, 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.
Official References and Review Basis
Primary materials relevant to address-provider replacement were checked on August 4, 2026. Their application depends on the company's current facts and does not replace a matter-specific legal, tax, licensing, accounting, security, premises, immigration, labour, or bank review.
- Ministry of Law Regulation No. 49 of 2025 : Current requirements and procedure for incorporation, amendment, and dissolution filings; it revoked Regulation No. 21 of 2021.
- AHU limited-liability-company service : Official Ministry of Law service for limited-liability-company incorporation, amendments, dissolution, and related records.
- Government Regulation No. 28 of 2025 : Current risk-based business licensing framework; it revoked Government Regulation No. 5 of 2021.
- Government Regulation No. 21 of 2021 : Current national spatial-planning framework, including spatial-use conformity controls.
- 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.
- Law No. 27 of 2022 on Personal Data Protection : National personal-data-protection framework relevant to identity and contact records handled by service providers.
Regulatory Notes and Limitations
Indonesia Address Provider Exit and Replacement Plan 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.
- A registered or correspondence address does not by itself authorize a regulated activity, customer service, storage, production, or other physical operation at that site.
- Test the exact parcel, building use, local spatial rules, activity, and required OSS output immediately before signing, filing, or moving.
- Keep corporate, OSS, tax, bank, contract, and provider records aligned; each system may require its own evidence and update route.
Run overlap, acceptance, and old-provider closure
For address-provider replacement, test mail, visits, downloads, recovery, inspection response, and record consistency before ending the old service and revoking access. For run overlap, acceptance, and old-provider closure, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.
A new contract is not evidence that notices arrive or that the company can pass a real authority or bank check. A reviewer should trace test correspondence and visitor event and before-and-after record reconciliation to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For run overlap, acceptance, and old-provider closure, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect test correspondence and visitor event with before-and-after record reconciliation, then show how revoked provider authority and credentials and post-change review calendar affect the next approval. Record the source for test correspondence and visitor event, the reviewer of before-and-after record reconciliation, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Test run overlap, acceptance, and old-provider closure through normal progress, delayed before-and-after record reconciliation, and failure of revoked provider authority and credentials. The normal case confirms the intended order for test correspondence and visitor event; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for post-change review calendar. Retain this stage-specific result with the final approval and review calendar.
Record standard
Close the incumbent only after a dated live test and documented straggler-notice period.
- Test correspondence and visitor event
- Before-and-after record reconciliation
- Revoked provider authority and credentials
- Post-change review calendar
For run overlap, acceptance, and old-provider closure, the output should name the owner, source evidence, unresolved condition, acceptance test, and the event that permits the next step. Where this stage changes another workstream, review Cheap Registered Address Risks for PT PMA Explained .
Use the Indonesia company registration service scope to coordinate each deed, OSS, licensing, banking, or post-registration dependency identified for address-provider replacement.
End the old address only after the new control chain works
The risk in an address-provider change is not the new monthly fee; it is the loss of notices, originals, account recovery, and consistency across authoritative and dependent records.
A controlled overlap, live acceptance test, and signed exception log let the company change providers without creating an invisible break in corporate, tax, licensing, banking, or customer evidence.
Turn the address-provider replacement into an approved next step
Create a sequenced action file with owners, evidence, exceptions, stop conditions, and an approved release point for address-provider replacement.
Frequently asked questions