Non-Resident Founder Handover After PT PMA Setup

After remote Indonesia incorporation, non-resident founders should receive and test control of the deed and Ministry of Law record, share and beneficial-owner records, OSS account and licences, Coretax, company email and phone, bank onboarding, original documents, providers, contracts, and compliance calendar. AHU's limited-liability-company service is the authoritative corporate platform; provider possession of a PDF or login is not the same as founder-controlled governance.

The handover should show who can bind the company, where originals are held, who receives government notices, which provider retains access, which licences are effective, what bank and tax work remains, and how an overseas owner responds to urgent local events. Remote control needs company-owned recovery channels, named local responders, dual authorization, secure records, and clear limits on powers of attorney and provider discretion.

Non-resident founder handover decision controls

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

Key takeaways

• Sign acceptance only after an independent field-by-field reconciliation.
• Test login and recovery before removing or retaining any provider user.
• Separate completed, pending, conditional, rejected, and not-applicable work before approving launch.
• Replace open-ended instructions with dated mandates and reserved decisions.
• Close the setup only after tests pass and every exception has an owner and date.

In this article

• Accept corporate records
• Take account control
• Reconcile operating readiness
• Official References and Review Basis
• Regulatory Notes and Limitations
• Define local authority
• Run acceptance
• End remote setup with founder-controlled evidence

Accept the corporate and ownership record

For non-resident founder handover, reconcile the signed deed, Ministry of Law approval, articles, shareholders, directors, commissioners, capital, beneficial owners, registers, resolutions, and originals against the founder-approved structure. For accept the corporate and ownership record, the corporate decision must follow the effective deed, Ministry of Law record, valid organ approval, ownership and beneficial-ownership facts, authority limits, and the downstream records that rely on them.

A remote founder may receive a polished certificate while the filed structure, names, powers, or capital differ from instructions. A reviewer should trace signed deed and ahu approval and articles and authority provisions to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For accept the corporate and ownership record, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect signed deed and ahu approval with articles and authority provisions, then show how share and ubo registers and original-document inventory affect the next approval. Record the source for signed deed and ahu approval, the reviewer of articles and authority provisions, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test accept the corporate and ownership record through normal progress, delayed articles and authority provisions, and failure of share and ubo registers. The normal case confirms the intended order for signed deed and ahu approval; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for original-document inventory. Retain this stage-specific result with the final approval and review calendar.

• Signed deed and AHU approval
• Articles and authority provisions
• Share and UBO registers
• Original-document inventory

For accept the corporate and ownership record, the output should name the owner, source evidence, unresolved condition, acceptance test, and the event that permits the next step.

Take control of identity and recovery channels

The responsible team should move company email, phone, domains, cloud records, AHU-related contacts, OSS, tax, accounting, and provider portals to company-controlled, named access with recovery and audit logs. For take control of identity and recovery channels, the corporate decision must follow the effective deed, Ministry of Law record, valid organ approval, ownership and beneficial-ownership facts, authority limits, and the downstream records that rely on them.

Provider-owned channels can prevent recovery or permit unauthorized filings after the project ends. A reviewer should trace company email and phone ownership and named user and role matrix to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For take control of identity and recovery channels, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect company email and phone ownership with named user and role matrix, then show how recovery and multifactor tests and provider access retention or revocation affect the next approval. Record the source for company email and phone ownership, the reviewer of named user and role matrix, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test take control of identity and recovery channels through normal progress, delayed named user and role matrix, and failure of recovery and multifactor tests. The normal case confirms the intended order for company email and phone ownership; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for provider access retention or revocation. Retain this stage-specific result with the final approval and review calendar.

• Company email and phone ownership
• Named user and role matrix
• Recovery and multifactor tests
• Provider access retention or revocation

For take control of identity and recovery channels, preserve the source record, reviewer, date, exception, and approval so another team can reproduce the decision without relying on memory. For the adjacent control framework, compare Indonesia Company Registration for Non-Residents .

Reconcile licences, tax, bank, and operating readiness

A supportable decision begins when the company can compare the corporate record with NIB, KBLI, projects, licence states, address, tax activation, invoices, payroll, bank KYC, funding, and first-revenue conditions. For reconcile licences, tax, bank, and operating readiness, the corporate decision must follow the effective deed, Ministry of Law record, valid organ approval, ownership and beneficial-ownership facts, authority limits, and the downstream records that rely on them.

Incorporation can be legally complete while the company cannot bank, invoice, employ, import, sell, or operate. A reviewer should trace oss and licence register and coretax and filing status to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For reconcile licences, tax, bank, and operating readiness, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect oss and licence register with coretax and filing status, then show how bank and capital plan and pre-operation release checklist affect the next approval. Record the source for oss and licence register, the reviewer of coretax and filing status, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test reconcile licences, tax, bank, and operating readiness through normal progress, delayed coretax and filing status, and failure of bank and capital plan. The normal case confirms the intended order for oss and licence register; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for pre-operation release checklist. Retain this stage-specific result with the final approval and review calendar.

• OSS and licence register
• Coretax and filing status
• Bank and capital plan
• Pre-operation release checklist

For reconcile licences, tax, bank, and operating readiness, turn the result into a controlled work item with a responsible person, due date, evidence location, escalation path, and release condition.

Official References and Review Basis

Primary materials relevant to non-resident founder handover 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.

• Law No. 40 of 2007 on Limited Liability Companies : Company-law framework for incorporation, shares, general meetings, directors, commissioners, and corporate actions, as amended.
• 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.
• Presidential Regulation No. 13 of 2018 : Beneficial-ownership identification and reporting framework for corporations.
• Government Regulation No. 28 of 2025 : Current risk-based business licensing framework; it revoked Government Regulation No. 5 of 2021.
• Online Single Submission portal : Official NIB, four-level risk classification, business licensing, KBLI, and support portal.
• Coretax DJP implementation page : Official tax administration portal guidance effective for administration from January 2025.

Regulatory Notes and Limitations

Non-Resident Founder Handover After PT PMA Setup 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.

• Company-law appointment or share ownership does not by itself supply immigration permission, work authorization, bank acceptance, or an effective business licence.
• Foreign public documents, translations, notarization, apostille or legalization, and validity periods depend on the origin, document type, recipient, and live filing practice.
• Reconcile the deed, Ministry of Law record, beneficial ownership, OSS, tax, bank, and internal authority matrix before relying on an appointment or ownership change.

Define provider, director, and local-response authority

Before the next commitment, management should document each notary, address provider, accountant, tax representative, director, commissioner, bank user, immigration sponsor contact, and emergency responder with scope, term, limits, fees, and termination. For define provider, director, and local-response authority, the corporate decision must follow the effective deed, Ministry of Law record, valid organ approval, ownership and beneficial-ownership facts, authority limits, and the downstream records that rely on them.

Remote owners can lose practical control when local participants rely on broad or overlapping informal authority. A reviewer should trace provider contract and authority index and power-of-attorney register to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For define provider, director, and local-response authority, 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 provider contract and authority index with power-of-attorney register, then show how reserved matters and payment limits and emergency and authority-visit protocol affect the next approval. Record the source for provider contract and authority index, the reviewer of power-of-attorney register, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test define provider, director, and local-response authority through normal progress, delayed power-of-attorney register, and failure of reserved matters and payment limits. The normal case confirms the intended order for provider contract and authority index; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for emergency and authority-visit protocol. Retain this stage-specific result with the final approval and review calendar.

• Provider contract and authority index
• Power-of-attorney register
• Reserved matters and payment limits
• Emergency and authority-visit protocol

For define provider, director, and local-response authority, record both the accepted position and the rejected alternatives; this prevents a later portal edit or provider message from silently changing the decision. Where this stage changes another workstream, review Registering a Company in Indonesia Remotely: Foreign Founders Without Visiting .

Run a live founder acceptance and 90-day review

The control file must show how the company will require the founders to recover an account, retrieve an original, approve a payment path, read a licence status, locate a tax deadline, contact the local responder, and review open exceptions. For run a live founder acceptance and 90-day review, the corporate decision must follow the effective deed, Ministry of Law record, valid organ approval, ownership and beneficial-ownership facts, authority limits, and the downstream records that rely on them.

A checklist without live tests can hide inaccessible systems and unclear ownership until the first deadline or dispute. A reviewer should trace live access test evidence and founder control certification to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For run a live founder acceptance and 90-day review, the practical deliverable is a version-controlled decision row that remains usable when the activity, location, counterparty, or responsible person changes. It should connect live access test evidence with founder control certification, then show how open-item and deadline schedule and 30-, 60-, and 90-day review plan affect the next approval. Record the source for live access test evidence, the reviewer of founder control certification, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test run a live founder acceptance and 90-day review through normal progress, delayed founder control certification, and failure of open-item and deadline schedule. The normal case confirms the intended order for live access test evidence; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for 30-, 60-, and 90-day review plan. Retain this stage-specific result with the final approval and review calendar.

• Live access test evidence
• Founder control certification
• Open-item and deadline schedule
• 30-, 60-, and 90-day review plan

For run a live founder acceptance and 90-day review, 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.

Connect the non-resident founder handover control to the wider Indonesia company registration workstream before committing people, travel, or funds.

End remote setup with founder-controlled evidence

A non-resident founder has practical control only when corporate authority, original records, recovery channels, licences, tax, bank, providers, and local response work without hidden dependence on the incorporation team.

Test those controls, preserve the handover evidence, and review the first 90 days before treating the remote incorporation as operationally complete.

Related insights

• Indonesia Company Registration for Non-Residents
• Registering a Company in Indonesia Remotely: Foreign Founders Without Visiting
• Post-Incorporation Compliance Guide for PT PMA