PT PMA Shareholder Document Expiry and Consistency Control
Track identity, corporate existence, authority, ownership, UBO, translations, authentication, recipient acceptance, and refresh dates across every PT PMA workstream.
A PT PMA shareholder-document file should track each document's authoritative issuer, holder, issue date, expiry or freshness expectation, version, language, translation, notarization, apostille or legalization route, data fields, recipient acceptance, and next refresh date. AHU's Apostille service supports applicable Indonesian apostille workflows, but the required authentication path depends on the source country, document, recipient, and current practice.
The same passport, company extract, articles, register, resolution, power, address proof, and beneficial-owner evidence may be used by the notary, AHU, OSS, bank, tax, immigration, or counterparty under different freshness and format rules. A valid document can still be unusable if names, addresses, transliteration, ownership percentages, signatory roles, or dates conflict with later records. Maintain one controlled data dictionary and no-surprise refresh calendar.
Shareholder document lifecycle 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 |
|---|---|---|
| Create the shareholder source-document register | list every individual and corporate shareholder document, issuing authority, original location, custodian, file hash or version, issue and expiry dates, language, and intended recipients | Document and issuer identity |
| Map authentication, translation, and format requirements | confirm for each recipient whether notarization, certified copy, apostille, legalization, sworn translation, colour scan, electronic signature, file size, or original presentation is required | Recipient requirement matrix |
| Reconcile identity, authority, ownership, and UBO fields | compare names, transliteration, numbers, dates, addresses, entity status, directors, signatories, share percentages, control, resolutions, and powers with the proposed deed and data dictionary | Master shareholder data dictionary |
| Control recipient-specific packs and disclosures | build separate indexed packs for notary and AHU, OSS, bank, tax, funding, immigration, licences, and counterparties while minimizing unnecessary personal-data disclosure | Pack index and purpose |
| Refresh on expiry and business events | calendar formal expiry and recipient freshness, and trigger review for passport, address, director, ownership, UBO, name, registered-office, good-standing, power, transaction, bank, or immigration changes | Expiry and freshness calendar |
In this article
Key takeaways
- Give every relied-on document a unique record and controlled source.
- Pre-clear the route before ordering or reusing a document.
- No filing pack should contain an unexplained material field conflict.
- Approve each pack's purpose, recipient, version date, access, and disclosure record.
- Archive superseded versions but prevent them from returning to active use.
Scope the shareholder document lifecycle before acting
Share the company facts, intended outcome, current records, and unresolved conditions so the shareholder document lifecycle review can be bounded.
Create the shareholder source-document register
Before the next commitment, management should list every individual and corporate shareholder document, issuing authority, original location, custodian, file hash or version, issue and expiry dates, language, and intended recipients. For create the shareholder source-document register, 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.
Files stored by email name alone can be duplicated, altered, superseded, or used after expiry. A reviewer should trace document and issuer identity and original custody and secure copy to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For create the shareholder source-document register, 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 document and issuer identity with original custody and secure copy, then show how version and integrity record and issue, expiry, and freshness dates affect the next approval. Record the source for document and issuer identity, the reviewer of original custody and secure copy, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Decision rule
Give every relied-on document a unique record and controlled source.
- Document and issuer identity
- Original custody and secure copy
- Version and integrity record
- Issue, expiry, and freshness dates
For create the shareholder source-document register, record both the accepted position and the rejected alternatives; this prevents a later portal edit or provider message from silently changing the decision.
Map authentication, translation, and format requirements
The control file must show how the company will confirm for each recipient whether notarization, certified copy, apostille, legalization, sworn translation, colour scan, electronic signature, file size, or original presentation is required. For map authentication, translation, and format requirements, 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 document can be substantively correct but rejected for the wrong authentication, translation, or file format. A reviewer should trace recipient requirement matrix and apostille or legalization route to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For map authentication, translation, and format requirements, the practical deliverable is a version-controlled decision row that remains usable when the activity, location, counterparty, or responsible person changes. It should connect recipient requirement matrix with apostille or legalization route, then show how translator and certification record and electronic and physical format standard affect the next approval. Record the source for recipient requirement matrix, the reviewer of apostille or legalization route, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Evidence rule
Pre-clear the route before ordering or reusing a document.
- Recipient requirement matrix
- Apostille or legalization route
- Translator and certification record
- Electronic and physical format standard
For map authentication, translation, and format requirements, 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. For the adjacent control framework, compare Documents Required to Register a Company in Indonesia for Foreign Shareholders . Where this stage changes another workstream, review Indonesia Bank Account KYC for Foreign Shareholders .
Test the shareholder document lifecycle evidence
Reconcile the authoritative, operational, contractual, tax, banking, and evidence fields that affect the shareholder document lifecycle decision.
Reconcile identity, authority, ownership, and UBO fields
For shareholder document lifecycle, compare names, transliteration, numbers, dates, addresses, entity status, directors, signatories, share percentages, control, resolutions, and powers with the proposed deed and data dictionary. For reconcile identity, authority, ownership, and ubo fields, 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.
Small differences can create apparent different persons, invalid authority, or inconsistent beneficial ownership. A reviewer should trace master shareholder data dictionary and identity and entity fields to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For reconcile identity, authority, ownership, and ubo fields, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect master shareholder data dictionary with identity and entity fields, then show how authority and signatory fields and ownership and ubo reconciliation affect the next approval. Record the source for master shareholder data dictionary, the reviewer of identity and entity fields, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Control point
No filing pack should contain an unexplained material field conflict.
- Master shareholder data dictionary
- Identity and entity fields
- Authority and signatory fields
- Ownership and UBO reconciliation
For reconcile identity, authority, ownership, and ubo fields, the output should name the owner, source evidence, unresolved condition, acceptance test, and the event that permits the next step.
Regulatory Notes and Limitations
PT PMA Shareholder Document Expiry and Consistency Control 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.
Official References and Review Basis
Primary materials relevant to shareholder document lifecycle 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.
- Presidential Regulation No. 13 of 2018 : Beneficial-ownership identification and reporting framework for corporations.
- AHU Apostille service : Official Indonesian service for apostille applications; the required route depends on the document, country, and recipient.
- Law No. 27 of 2022 on Personal Data Protection : National personal-data-protection framework relevant to identity and contact records handled by service providers.
- Ministry of Investment and Downstream Industry/BKPM Regulation No. 5 of 2025 : Current OSS procedures, investment facilities, supervision, and reporting framework.
Control recipient-specific packs and disclosures
The responsible team should build separate indexed packs for notary and AHU, OSS, bank, tax, funding, immigration, licences, and counterparties while minimizing unnecessary personal-data disclosure. For control recipient-specific packs and disclosures, 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.
Reusing a broad folder can expose sensitive data or send stale and irrelevant documents to the wrong reviewer. A reviewer should trace pack index and purpose and recipient and access approval to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For control recipient-specific packs and disclosures, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect pack index and purpose with recipient and access approval, then show how data-minimization review and delivery and acceptance evidence affect the next approval. Record the source for pack index and purpose, the reviewer of recipient and access approval, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Release test
Approve each pack's purpose, recipient, version date, access, and disclosure record.
- Pack index and purpose
- Recipient and access approval
- Data-minimization review
- Delivery and acceptance evidence
For control recipient-specific packs and disclosures, preserve the source record, reviewer, date, exception, and approval so another team can reproduce the decision without relying on memory.
Refresh on expiry and business events
A supportable decision begins when the company can calendar formal expiry and recipient freshness, and trigger review for passport, address, director, ownership, UBO, name, registered-office, good-standing, power, transaction, bank, or immigration changes. For refresh on expiry and business events, 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 pack can become inconsistent before any document's printed expiry date. A reviewer should trace expiry and freshness calendar and event-driven change alerts to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For refresh on expiry and business events, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect expiry and freshness calendar with event-driven change alerts, then show how replacement and reacceptance evidence and superseded archive and access controls affect the next approval. Record the source for expiry and freshness calendar, the reviewer of event-driven change alerts, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Stop condition
Archive superseded versions but prevent them from returning to active use.
- Expiry and freshness calendar
- Event-driven change alerts
- Replacement and reacceptance evidence
- Superseded archive and access controls
For refresh on expiry and business events, turn the result into a controlled work item with a responsible person, due date, evidence location, escalation path, and release condition.
Compare the proposed shareholder document lifecycle action with HSJGlobal’s Indonesia company registration scope before changing the company or operating plan.
Keep one current shareholder truth across every filing
Document control is successful when every recipient receives the right current evidence while names, authority, ownership, beneficial ownership, translations, and authentication remain consistent.
Use a source register, data dictionary, recipient packs, expiry calendar, and event triggers to prevent a stale scan from blocking a transaction or contradicting the company's authoritative record.
Turn the shareholder document lifecycle into an approved next step
Create a sequenced action file with owners, evidence, exceptions, stop conditions, and an approved release point for shareholder document lifecycle.
Frequently asked questions
