Remote PT PMA Registration Handover Controls: Credentials, Originals, and Authority

Remote incorporation is not complete when an agent says the company exists; the owner needs verified records, controlled credentials, original documents, authority, and a usable operating file.

A remote PT PMA registration project should be designed around owner control from the first engagement. Identify the contracting provider, responsible people, exact authority, notary relationship, deliverables, submission channels, payment milestones, original documents, portal accounts, recovery details, and handover conditions. The company should be able to reconstruct what was submitted, by whom, on what authority, and what official result was returned without relying on one salesperson's chat history.

After selecting a provider, design submission, credential, document, access, and final-handover controls so the foreign founders can take possession of a complete and independently verifiable company record. Use the remote registration requirements to confirm the setup and signing sequence, then require company-controlled recovery details, original-document custody records, submission evidence, acceptance checks, and a dated authority termination and handover plan.

Key takeaways

• Limit agent authority to named tasks, documents, systems, periods, and revocation events.
• Approve the exact factual submission before filing and retain the filed version and official response.
• Use company-controlled email, recovery, and credential custody wherever the official system allows.
• Release final payment only against an indexed, verified, and tested handover pack.

In this article

• Define agent authority and deliverables
• Approve and freeze every submission
• Control credentials, originals, and payments
• Run the final handover acceptance test
• Official references and review basis
• The release test for a remote PT PMA registration handover

Define agent authority and deliverables

The engagement schedule should name the Indonesian legal entity providing the service, responsible professional or notary relationships, scope, exclusions, dependencies, government and third-party charges, professional fees, refund terms, timeline assumptions, and evidence delivered at each milestone. Attach an authority matrix showing which person may prepare, translate, sign, submit, receive, amend, pay, collect originals, access portals, speak to authorities, and appoint another party. Prohibit undisclosed delegation and open-ended authority.

AHU operates the official online corporate-services environment for limited companies, while OSS is the official risk-based business licensing system. The company should distinguish a provider's private dashboard from the official record. Use the AHU portal and OSS portal as primary reference points and verify current access and submission routes rather than following links sent only in chat.

Before any power of attorney or signature, review the exact document, language, governing law, authority, expiry, substitution right, bank or tax effect, and revocation route with Indonesian counsel. Keep the signed original and a controlled scan. Do not sign blank pages, undated resolutions, unknown forms, pre-approved future amendments, or authority to open and control bank accounts unless the scope is specifically understood and approved.

Approve and freeze every submission

Create a submission register covering company name, shareholder and beneficial owner identities, directors and commissioners, address, capital, business purposes and KBLI, project locations, investment values, tax data, contacts, email, telephone, signatories, and supporting documents. For each submission, preserve the source fact, translation, draft, reviewer comments, approved version, submitter, system, timestamp, official receipt, request, response, correction, and final output.

AHU provides an official limited-company profile search , and OSS includes public NIB search functionality. Public results can support verification, but they do not prove that every document, license condition, or internal corporate record is complete. Compare official records with the approved submission and obtain issuer confirmation or professional review when status is unclear.

Require founder approval of the exact factual version before submission. Prohibit providers from changing names, ownership, addresses, capital, activities, project data, or contact details to make a system accept the file without written approval and advice. If an authority requests clarification, log the request and proposed response separately. Never recreate or backdate evidence to hide a rejected or mistaken filing.

Control credentials, originals, and payments

Use a credential architecture before accounts are created. Where systems allow, register a company-controlled domain email, recovery channel, and phone rather than a provider's personal account. Inventory every portal, username owner, role, certificate or authorization code, recovery method, device, one-time-code route, API or shared link, export ability, and backup. Apply least privilege and two-person recovery. Do not send passwords or one-time codes in ordinary group chats.

DGT's current first-access Coretax guidance shows that taxpayer access and activation are official processes. OSS guides similarly require access credentials sent to the registered email. A provider may assist, but the company must understand who owns each account and how access will be recovered after the engagement ends.

Maintain an original-document register with title, issuer, entity, number, date, language, signature or seal, legalization or translation status where relevant, physical custodian, scan location, checkout, and return. Pay only to verified contractual or official payees under approved milestones. Independently confirm changed bank details. Separate government charges, notary or third-party costs, and professional fees, and retain receipts without treating a provider-created invoice as an authority receipt.

Run the final handover acceptance test

The handover pack should include executed constitutional and corporate documents, AHU outputs, shareholder and beneficial owner records, NIB and each licensing status, tax registration and access, address and premises evidence, capital and funding records, official submissions and receipts, provider and notary invoices, original-document inventory, portal and credential inventory, authority register, open authority requests, compliance calendar, and unresolved exceptions. Label drafts and superseded versions so they cannot be mistaken for current records.

Use official searches and portals to validate core identifiers, then compare the record against the approved target state. The AHU beneficial ownership search states that its data is submitted by authorities, corporations, notaries, or authorized corporate contacts; treat it as one data source and reconcile it with the company's ownership evidence rather than assuming it independently proves every UBO fact.

Test operational control: founders or authorized company staff log in through known official URLs, recover access, export current records, identify every open condition, receive a notice, locate an original, show payment evidence, and explain the next tax, license, bank, and reporting deadlines. Revoke provider access that is no longer required and document retained support roles. Compare the final file with the registration package audit before signing acceptance or releasing the last payment.

Official references and review basis

The following primary sources were checked on August 1, 2026. They establish the regulatory or service boundary used in this article; bank, tax office, OSS, AHU, and immigration decisions can still depend on the current record and the facts of a particular application.

• AHU — Official portal — Official Indonesian corporate-services portal and contact context.
• AHU — Limited-company profile search — Official search for limited-company profile data.
• AHU — Beneficial ownership search — Official search describing the sources of submitted beneficial ownership data.
• OSS — Official risk-based licensing portal — Official business licensing portal, guides, and public NIB search context.
• DGT — First access to Coretax — Current official taxpayer access and activation guidance.

The release test for a remote PT PMA registration handover

Accept the project only when the company controls its official records, approved submission history, portal and recovery access, original documents, authority register, payment evidence, current status, conditions, and compliance calendar. Founders should be able to retrieve and explain the file without depending on the agent's private dashboard, personal email, device, or memory.

Public searches and provider documents are verification inputs, not guarantees that every legal, licensing, tax, or banking condition is complete. Obtain Indonesian professional review for authority, document authenticity, and unresolved status. Use the full Indonesia company registration framework to test whether the handover supports real operations rather than registration alone.

Related insights

• Remote registration for foreign founders
• Registration package audit
• Agent due diligence
• Power of attorney for remote setup