KYC document baseline

PT PMA Document Version Control for Bank KYC: Deed, NIB, NPWP, and UBO

A field-and-file control for deciding which deed, NIB, NPWP, ownership, UBO, and authority records are effective and ready for bank submission.

By Elara Vance Updated July 31, 2026 5-minute read

A PT PMA should submit bank KYC documents from one approved baseline that states which deed and amendments are effective, which Ministry evidence confirms them, which NIB, NPWP, license, shareholder, beneficial-owner, director, and authority records are current, and which fields remain in conflict. File date alone does not determine authority: a newer scan can be a draft, while an older establishment deed can remain relevant when read with later amendments. Every bank submission should have a manifest listing the document name, issuer, version, effective date, purpose, hash or controlled identifier, and approval owner.

Version control does not cure an incorrect source record. When the deed, Ministry record, Online Single Submission (OSS) data, tax file, beneficial-owner filing, or bank form disagrees, the company must identify the authoritative source and use the proper correction or explanation route. Ministry of Law Regulation No. 2 of 2025 and OJK Regulation No. 8 of 2023 make accurate ownership and beneficial-owner information relevant to both corporate and bank review. The baseline should be frozen for each submission while later changes enter a controlled update project.

Status	Meaning	Submission rule
Draft	Not executed or not legally effective	Never present as current evidence
Executed pending process	Signed but dependent on approval, receipt, or effective condition	Disclose status; confirm bank acceptance
Approved effective	Current source record for its field	Eligible for controlled baseline
Superseded	Replaced but retained for legal history	Include only when history or bank request requires
Expired or stale	No longer valid or outside receiving-party recency	Renew; do not silently reuse
Conflict	Field disagrees with another source	Stop affected submission until resolved or documented

Define the PT PMA source hierarchy

Map every company, ownership, license, tax, and authority field to its effective source and downstream documents.

Key takeaways

A current KYC file can require an establishment deed plus every amendment that affects the field under review.
Each data field should have an authoritative source and downstream document map.
Draft, executed-pending, effective, superseded, expired, and conflicting are different states.
Freeze a manifest for every bank submission and record exactly what the branch received.
Correct source records before regenerating downstream forms whenever the legal data is wrong.

Build a source hierarchy for every PT PMA field

The PT PMA should assign an authoritative source to each legal name, address, capital figure, shareholder, director, commissioner, beneficial owner, KBLI, project location, license status, NPWP, representative, and bank authority field. The source can differ by question: the deed and Ministry evidence establish corporate matters, OSS records licensing data, tax records establish tax identity, and the bank maintains its own mandate and customer record.

Published bank pages show the overlap. BNI lists the deed, NIB, NPWP, management composition, and authorized official; BCA lists deeds, amendments, Ministry evidence, boards, shareholders, NIB, and licenses. A bank form is a downstream representation of those sources, not authority to invent a middle value when sources disagree.

Release test

For each field, name the source, effective version, owner, and every downstream file that must change with it.

List exact legal fields and accepted source record for each.
Record source issuer, reference, effective date, and status.
Map the field to OSS, tax, UBO, bank, contract, and accounting uses.
Escalate fields with two plausible sources rather than choosing by file date.

Use the Indonesia company bank evidence guide as the field inventory.

Control deed history without flattening amendments

The deed package should preserve the establishment instrument and all effective amendments needed to reconstruct the current articles, capital, shareholders, directors, commissioners, address, and authority. A consolidated summary can help the reviewer, but it should not erase the legal history or claim to be an official document. Each deed should be linked to its Ministry approval, receipt, notification, or other applicable processing evidence and effective date.

The document controller should label drafts, unsigned versions, executed-pending records, effective records, and superseded provisions. A scan named ‘final’ is not proof of effectiveness. When a bank asks for ‘the latest deed,’ the submission owner should confirm whether the branch also needs the establishment deed, intervening amendments, current composition deed, and Ministry evidence.

Stop condition

The current-state summary should be reproducible from the controlled deed chronology and not from memory.

Number every deed and Ministry record in chronological order.
State which fields each amendment changed and when the change became effective.
Retain superseded documents in a read-only history folder.
Prevent draft or unsigned deeds from entering current KYC packages.

Compare the chronology with the Indonesia registration process guide .

Propagate changes to NIB, NPWP, UBO, and bank records

A source change should open a propagation log identifying every downstream record, owner, action, dependency, target date, and completion evidence. A director amendment can affect the corporate register, beneficial-owner analysis, OSS access, tax contacts, bank signers, digital users, contracts, payroll, and license submissions. An address or KBLI change can affect NIB, licenses, tax, premises, invoices, and the bank business narrative.

The OSS portal is the official risk-based licensing system, while the bank applies its own KYC record. Updating OSS does not update the bank, and a bank change does not correct the deed. Each system needs its own supported process. The company should use one effective date and explain temporary timing differences without presenting a downstream record as already updated.

Record standard

Close a source change only after every material downstream field is updated or held on a signed exception.

Open a change-impact record before the corporate action becomes effective.
Sequence deed, Ministry, OSS, tax, UBO, license, bank, and contract updates.
Retain submission receipts, status, effective dates, and rejected items.
Issue a refreshed master-data baseline after the propagation closes.

Use the post-registration steps guide to identify downstream owners.

Trace a corporate change across systems

Identify which deed, Ministry, OSS, NPWP, UBO, bank, license, and contract records must change and in what order.

Official References and Review Basis

Primary materials were checked on July 31, 2026. These links support the regulatory and banking framework used in this article; they do not replace a matter-specific legal, tax, licensing, accounting, security, or bank review.

Limited Liability Company Law No. 40 of 2007 : Company-law framework for shares, capital, corporate organs, records, and authority, as amended.
Government Regulation No. 28 of 2025 : Current risk-based business licensing framework and official unofficial English translation.
Online Single Submission risk-based licensing portal : Official explanation that four risk levels determine the business licensing and obligations to be fulfilled.
Ministry of Law Regulation No. 2 of 2025 : Current verification and supervision framework for corporate beneficial-owner information.
OJK Regulation No. 8 of 2023 : Customer due diligence, beneficial-owner review, ongoing monitoring, and electronic verification framework.
BNI Giro corporate-account requirements : Published checklist covering the deed, NIB, NPWP, management composition, authorized official, and initial deposit.
BCA Current Account requirements : Published corporate account, representative, power-of-attorney, management, shareholder, NIB, and license requirements.

Regulatory Notes and Limitations

Document control determines which evidence is released; it does not decide legal effectiveness or correct government records. Notarial, Ministry, OSS, tax, UBO, license, accounting, and bank questions require the responsible authority or adviser.

A newer file is not necessarily effective, and a superseded file can remain necessary to show legal history.
Updating one system does not automatically update the company’s other government, tax, license, contract, or bank records.
Bank product pages are baseline lists and do not prevent the branch from requesting further current evidence.
Restricted identification and source-of-funds material should have approved access, transmission, retention, and replacement controls.

Freeze a bank-specific submission manifest

Each bank application or refresh should receive a frozen manifest with the file name, controlled identifier, document title, issuer, date, status, fields supported, language, certification or authentication, confidentiality class, and approved recipient. Bank-specific forms can differ, but the underlying legal and ownership facts must agree across institutions.

The submission coordinator should assemble the package from read-only approved files, not personal email or messaging applications. The manifest should record the branch, officer or approved portal, delivery date, sender, acknowledgement, and later replacement. If the bank requests an updated file, the old submission remains in the audit trail and the response explains why the new version supersedes it.

Decision rule

No file leaves the controlled data room without a manifest entry and source-owner approval.

Use deterministic file names and controlled version identifiers.
Separate public corporate evidence from restricted personal and wealth evidence.
Record exact recipient, channel, date, and bank case reference.
Link every replacement to the superseded submission and bank request.

Read the PT PMA bank requirements guide before defining the bank-specific subset.

Run a pre-submission field and file audit

The final audit should compare the title, content, dates, signatures, status, and key fields of every outgoing document against the approved master data. It should also test that the ownership percentages reconcile, beneficial owners reach natural persons, directors and signers have current authority, licenses support the business narrative, and identification is usable under the bank’s current requirements.

The audit result should distinguish blocker, explainable presentation difference, non-critical formatting issue, and future refresh. A blocker affecting legal identity, ownership, control, authority, license, or source of funds should stop submission. A reviewer should not edit a source PDF to make the pack consistent; the owner must correct the source or approve a factual explanation.

Evidence rule

Release the baseline when the manifest and field comparison show one supportable current state and no hidden blocker.

Recalculate ownership and compare all names, dates, addresses, and identifiers.
Check signatures, notarial or Ministry status, expiry, recency, and formalities.
Open every link and confirm the manifest matches the actual file.
Have a second reviewer sign the release and exception list.

Use the bank KYC mistakes guide as an adversarial final check.

Connect this control to the wider Indonesia company registration workstream before committing people, travel, or funds.

Submit the PT PMA bank file only from an approved document baseline

The PT PMA should be able to prove why each file is current, what field it supports, and how it relates to earlier deeds and later system records. Build a source hierarchy, preserve legal history, propagate changes, and freeze a bank-specific manifest from read-only approved evidence.

Stop the submission when a draft appears current, two sources disagree, an amendment has not propagated, or a sensitive file lacks a controlled recipient. Correct the source or document the status before the bank receives a version it may rely on.

Freeze a bank-ready document baseline

Create the approved manifest, restricted evidence package, delivery record, replacement trail, and pre-submission audit.

Frequently asked questions

Should the PT PMA send only its latest deed to the bank?

Not always. The bank may need the establishment deed, relevant amendments, current management deed, and Ministry evidence to reconstruct the present company. Confirm the selected branch’s current requirements.

Does updating the NIB update the bank automatically?

No. OSS, tax, corporate, UBO, license, and bank records are separate systems or files. Use a propagation log and complete each supported update.

What is the difference between executed and effective?

An instrument can be signed but still depend on approval, receipt, notification, a condition, or another legal step. Record matter-specific status rather than assuming execution alone controls every downstream use.

Can the company edit a PDF to fix a spelling mismatch?

Do not alter source evidence. Identify which authoritative record is wrong and use the proper correction route or an approved factual explanation while preserving the original file.

What should the bank submission manifest contain?

List the controlled file identifier, title, issuer, date, status, supported fields, language and formalities, confidentiality, recipient, delivery channel, case reference, and replacement history.