Registration evidence control
PT PMA Identity and Share Data Reconciliation Before Notarial Filing
Names, identity numbers, addresses, corporate authority, share data and signatures must reconcile across foreign documents, notarial records, AHU, OSS, tax and banking.
A PT PMA document mismatch should be resolved before the notary or provider copies it into the deed, AHU, tax and OSS systems. The highest-risk differences involve legal names, passport or registration numbers, dates of birth or incorporation, nationality or jurisdiction, addresses, authorised representatives, share counts and values, director or commissioner data and signature authority. Build a source-of-truth schedule for every individual and corporate shareholder using valid primary documents; record transliteration, punctuation and address conventions; verify any legalisation, apostille, certification and sworn-translation requirement; and require the notarial draft and filing forms to match the approved schedule. Do not silently edit a source document or invent a shortened name to fit a field. When a system imposes a format limit, document the approved representation and preserve the full legal identity in the underlying file.
Key takeaways
- Create one approved identity and ownership schedule before drafting begins.
- Use primary valid documents and verify the authority of every corporate signatory.
- Treat spelling, numbering and address differences as controlled exceptions.
- Review the final deed and filing data—not only the first draft.
- Keep certified, translated and submitted versions with a change log and effective dates.
The pre-filing document consistency test
Each field needs one controlling source and an approved representation. Differences should be explained, not hidden.
Identity
Exact legal name and number
Use valid passport or corporate registry evidence and record transliteration.
Authority
Current signatory power
Trace resolutions, incumbency and powers to the person signing.
Ownership
Shares and values reconcile
Match subscriptions, cap table, deed, registers and investment plan.
Format
Certification and translation
Confirm apostille or legalisation, copies, dates and sworn translation where required.
Evidence basis: Law No. 40 of 2007 on Limited Liability Companies · BKPM Regulation No. 5 of 2025
Build the source-of-truth schedule
Reconcile names, numbers, addresses, authority, shares and signatures before the notarial draft.
The document pack should follow the applicable foreign shareholder document requirements for individuals and corporate shareholders. A corporate shareholder usually needs a chain that identifies the legal entity, authorised decision-makers, ultimate owners where requested and the person empowered to subscribe or sign.
Mismatch correction becomes more expensive as the same error travels downstream. A passport spelling fixed before drafting may take minutes; the same spelling embedded in a deed, AHU record, tax profile, NIB and bank account can require several coordinated processes and fresh originals.
Build the identity, authority and ownership source schedule
The schedule should be approved by the founders and notary team before documents are drafted. It remains the comparison base through final issuance.
Name variants
The warning sign appears when passport, foreign registry and translated documents use different order, spacing or transliteration. Verify it with current primary document and documented transliteration rule. The responsible person should approve one legal representation and list known variants; otherwise, one person appears as several identities across systems.
Expired or replaced identity
Treat the filing uses an old passport or superseded corporate extract as a decision gate, not an administrative detail. Keep current validity, replacement link and filing-date requirement in the transaction file, then refresh the pack and record the old-to-new relationship. This reduces the chance that the authority or bank rejects stale evidence.
Corporate signatory unclear
A reliable check starts with constitutional documents, board resolution, incumbency and specific power. It should resolve whether a foreign employee signs without board or registry evidence of authority. Where the records do not reconcile, trace authority to the subscription and Indonesian filing; proceeding without that step can mean the shareholder's consent or signature is challenged.
Share math differs
share count, nominal value, percentage and total capital do not reconcile The evidence that matters is cap table, subscription approval, deed capital and currency calculation. run arithmetic and ownership checks before signing If that control is skipped, AHU, OSS and immigration evidence show inconsistent ownership.
Control certification, translation and draft changes
Formal validity and data accuracy are separate. A perfectly certified document can still contain facts inconsistent with the transaction.
Wrong certification route
Treat a copy is notarised locally but the receiving process needs apostille, legalisation or another form as a decision gate, not an administrative detail. Keep issuing jurisdiction, document type and current Indonesian acceptance requirement in the transaction file, then confirm the route before couriering originals. This reduces the chance that the pack is rejected despite genuine content.
Translation changes legal data
A reliable check starts with source document, sworn translation and terminology schedule. It should resolve whether names, addresses, offices or corporate forms are translated inconsistently. Where the records do not reconcile, have bilingual facts checked line by line; proceeding without that step can mean the Indonesian draft identifies a different entity or authority.
Draft revised off-schedule
a provider edits share or officer details after founder approval The evidence that matters is version-controlled draft, redline and approved source schedule. require change approval and final comparison If that control is skipped, the executed deed contains an unnoticed commercial change.
Signature page detached
The warning sign appears when signatures are collected without the final complete document or version reference. Verify it with complete execution copy, page count and signing instruction. The responsible person should bind signatures to the approved final version; otherwise, the signatory cannot prove what was authorised.
Audit certification and execution
Verify formalities, translations, redlines and signing versions before submission.
Verify every issued record before downstream use
Do not assume the filing system reproduced the draft accurately. Compare official outputs immediately while correction evidence is fresh.
AHU profile not compared
A reliable check starts with executed deed, AHU output and approved source schedule. It should resolve whether the deed is accepted but the ministerial or profile data contains a spelling or office error. Where the records do not reconcile, submit the correct route promptly and preserve receipts; proceeding without that step can mean the error enters tax, OSS and bank onboarding.
OSS auto-data differs
entity data imported into OSS is stale or formatted differently The evidence that matters is current AHU and OSS business profile with timestamps. resolve the controlling source before editing OSS If that control is skipped, the two government records diverge.
Tax and bank copy old data
The warning sign appears when onboarding documents use an earlier draft or expired identity. Verify it with final issued pack, authorised signatory list and submission checklist. The responsible person should issue one controlled downstream pack; otherwise, institutions establish inconsistent customer records.
No correction log
Treat teams fix fields independently without recording reason and effective date as a decision gate, not an administrative detail. Keep mismatch register, evidence, submission and acceptance receipt in the transaction file, then maintain one cross-system correction owner. This reduces the chance that a later update reverses a valid correction.
Corporate and OSS basis for document consistency
The Company Law and effective corporate record govern authority and ownership, while BKPM and OSS procedures govern business registration data and changes. Foreign-document formalities must be checked for the relevant jurisdiction and use.
- Law No. 40 of 2007 on Limited Liability Companies : The Company Law, as amended, defines the roles and accountability of shareholders, directors and commissioners. Authority should be traced to the deed, shareholder or board decisions and valid delegations.
- BKPM Regulation No. 5 of 2025 : The current OSS procedure regulation includes the general PT PMA investment threshold, the IDR 2.5 billion minimum issued and paid-up capital rule, OSS procedures and administrative consequences. Sector-specific exceptions and calculation bases still have to be checked.
- Official OSS guidance library : The OSS portal publishes current procedural guides for new applications, changes and transition cases. A successful screen or downloaded NIB does not by itself prove that every activity-level requirement is fulfilled.
- OSS business-data change guide : The official guide distinguishes changes to entity data, location data, addresses, investment plans and business licensing. The correct route depends on the field and the status of the existing licence.
Apostille, legalisation, certification, translation and validity requirements depend on the document, issuing country, receiving authority and transaction date. Confirm the route with the Indonesian notary or competent authority before obtaining costly originals.
Authorise filing only from a zero-unexplained-mismatch certificate
The certificate should compare every founder and corporate shareholder field across primary documents, translations, cap table, deed draft and filing forms. A difference may remain only when its reason, approved representation and supporting evidence are recorded.
Repeat the comparison against the executed deed, AHU result and OSS profile before releasing the pack to tax authorities, banks, immigration advisers or counterparties. This final check stops one source error from becoming a multi-system amendment.
Stop mismatches before downstream use
Compare the deed, AHU and OSS outputs and document every correction at issuance.
Frequently asked questions
Will a small spelling difference stop PT PMA registration?
It can trigger clarification or create downstream inconsistency, especially in legal names and identity numbers. Resolve it through the primary document and an approved transliteration or representation rule.
Do foreign shareholder documents need an apostille?
It depends on the document, issuing country, use and current acceptance route. Confirm whether apostille, legalisation, certification, translation or recent issuance is required before preparing the pack.
Can a provider shorten a long corporate name for OSS?
Do not permit an unexplained change. If a system has a technical limit, document the approved display representation and preserve the full legal name in the controlling and supporting records.
Who can sign for a foreign corporate shareholder?
A person whose authority is established through the foreign entity's constitutional, registry, board or power documents and satisfies the Indonesian transaction's formal requirements.
When should the final data check occur?
Check before signing, before filing, immediately after the deed and AHU output, after OSS data appears and before the pack is used for tax, bank, licence or immigration work.
