PT PMA Capital Evidence Across the Deed, OSS, Bank, and LKPM
Different reviewers ask different questions; one indexed evidence file can answer corporate, licensing, banking, accounting, and reporting checks.
PT PMA capital is not verified by one universal certificate. The deed and shareholder records evidence the legal subscription and share allocation. OSS holds the planned investment for business activities and locations. The bank evidences actual receipts, senders, sources, purposes, and outflows. The accounting ledger classifies equity and use. LKPM reports realised investment supported by project records. A credible file connects these records without pretending they are the same.
Build the evidence chain at the time of each event, not months later. For the general IDR 2.5 billion paid-up capital baseline under BKPM Regulation No. 5 of 2025, retain the shareholder approval, deed, payment evidence, company account trail, equity ledger, and first-year use. A PT PMA setup evidence review should also map the separate total-investment plan and activity-specific exceptions.
| Reviewer | Primary question | Core evidence |
|---|---|---|
| Notary/corporate | What shares were subscribed and paid? | Deed, approvals, register, paid-up support |
| Bank | Who sent money, from where, and why? | KYC, remittance, statements, purpose |
| Accountant/auditor | How is the event classified and measured? | Ledger, FX, contracts, reconciliation |
| Investment reporting | What plan and realisation belong to the project? | OSS, assets, invoices, payments, LKPM |
In this article
Key takeaways
- Corporate evidence proves shares and obligations; bank evidence proves transactions; neither replaces the other.
- OSS investment plans require project support, while LKPM requires period realisation evidence.
- Third-party payments and foreign-currency remittances need additional authority and reconciliation.
- Capital use during the first 12 months should be linked to assets, building construction, or company operations.
- Index evidence by event, project, and record so later reviewers can reproduce the conclusion.
Define what the reviewer is trying to verify
A notary may need support for the paid-up statement and cap table. A bank tests identity, source of funds, transaction purpose, expected use, and sanctions or financial-crime risk. An accountant tests recognition, measurement, exchange rates, ownership, and documentation. BKPM or an OSS-related review may test planned and realised investment, location, business activity, and compliance. A tax reviewer may test whether a payment is equity, debt, revenue, or an expense.
Write the question on each evidence index. “Prove capital” is too broad. Better questions include: Did Shareholder A pay for the shares recorded in the deed? Did the PT PMA receive the funds? Was an outflow a permitted company operation? Does the LKPM figure tie to qualifying project expenditure? The answer then points to the smallest complete evidence set.
Existence
The legal share obligation and approved capital structure.
Receipt
The bank-credit event and verified sender.
Classification
Equity rather than loan, fee, revenue, or advance.
Deployment
Permitted use and project-realisation evidence.
Assemble the corporate subscription record
Retain the final deed, Ministry of Law approval, shareholder and board resolutions, share subscription or closing schedule, shareholder register, share certificate record where applicable, and evidence supporting paid-up status. The names, shares, nominal values, rupiah amounts, percentages, and dates should calculate and reconcile. Corporate shareholders also need authority evidence from their governing bodies.
If the capital changes later, preserve the pre-change and post-change records, approvals, deed amendment, filings, and payment or conversion evidence. Do not overwrite the original cap table with a spreadsheet that has no version history. A capital evidence file should allow a future buyer or auditor to reconstruct every issuance, transfer, and contribution.
- Final deed and approval
- Subscriber and shareholder resolutions
- Share schedule and register
- Paid-up support and contribution date
- Corporate-authority chain
- Amendment and version history
Assemble the bank event from debit to credit
For each contribution, keep the shareholder account debit, SWIFT or transfer message, beneficiary credit, account statement, currency conversion, bank fees, payment reference, source-of-funds evidence, and bank correspondence. Verify the sender against the subscribing shareholder or document the authorised third-party payer. The account name and company legal name should match or be explained.
If the contribution is paid in foreign currency, create a rupiah bridge showing the deed amount, transferred amount, conversion rate, credited amount, charges, and treatment of differences. The bank evidence should not be edited into a composite screenshot. Keep original files and a controlled summary. The capital proof for bank account opening guide helps prepare the institution-facing subset.
Debit
Shareholder statement and authorised payment instruction.
Transmit
Bank message with sender, beneficiary, purpose, and value date.
Credit
PT PMA statement and currency conversion.
Reconcile
Rupiah equity entry, fees, differences, and evidence index.
Connect the OSS investment plan to a real project budget
For each activity and location, retain the investment workbook, asset list, construction plan, working-capital calculation, quotations, premises evidence, procurement timeline, and funding sources. State the calculation method and any activity-specific exception. The budget should explain the OSS figure; a copied threshold with no deployment plan is weak evidence.
Version the plan when the company adds a KBLI, changes location, revises the project, or replaces assets. Record management approval and the reason for the change. The company should be able to explain why the planned investment differs from paid-up capital and how future financing will cover the gap.
| Project evidence | Supports | Version trigger |
|---|---|---|
| Asset and construction schedule | Fixed investment plan | Vendor, design, location, or timing change |
| Working-capital model | Operating-cycle requirement | Price, staff, inventory, or customer-term change |
| Allocation method | Shared project resources | New KBLI or location |
| Funding schedule | Equity, loan, and operating-cash bridge | Financing or cash-flow change |
Prove permitted use through approvals, invoices, and the ledger
For capital-proceeds payments during the first 12 months, retain the budget approval, contract, invoice, beneficiary check, payment approval, bank transaction, tax document, receipt or delivery evidence, and accounting entry. Asset purchases should enter the asset register; construction should connect to site and progress; operating expenses should connect to the real company activity.
Review related-party payments, cash, transfers back to shareholders, and agent-controlled accounts separately. The permitted categories in BKPM Regulation No. 5 of 2025 do not eliminate company-law, tax, transfer-pricing, bank, or licence requirements. Evidence should show both a permitted high-level category and a lawful underlying transaction.
Asset
Purchase, title, delivery, location, register, and business use.
Construction
Site rights, permit dependency, contract, milestone, and progress.
Operations
Budget, contract, invoice, approval, payment, tax, and ledger.
Exception
Escalation for related party, cash, refund, or shareholder transfer.
Prepare LKPM from project-coded accounting data
Map each reported realisation line to the project code, general-ledger account, asset or expense schedule, invoice, payment, and location. Retain the current and prior filing, submission evidence, preparer, reviewer, and any explanatory notes. The method should distinguish planned investment, period expenditure, cumulative realisation, and non-qualifying or differently classified costs.
Complete the reconciliation before submission, not after an inquiry. Review major additions, imports, construction, working capital, funding, employment, production or service status, and changes from the OSS plan. A clean evidence file lets management correct a classification or project mapping without rewriting the underlying books.
- Current OSS plan and project codes
- Period and cumulative ledger extract
- Asset, construction, and working-capital schedules
- Invoice and payment sample set
- Prior filing and change explanation
- Prepared-by and reviewed-by record
Official references and review basis
Primary materials checked on July 25, 2026. The cited rules should be read together with the current five-digit KBLI, OSS output, and any sector-specific regulation applicable to the proposed activity.
Final decision
Capital verification is a chain. The deed proves the legal share structure, the bank proves money moved, the ledger proves classification, project records prove use, and LKPM shows reported realisation. Build links among them rather than searching for one magic certificate.
An indexed file created at each event is faster to review and harder to manipulate. It also protects the company when staff, providers, banks, or shareholders change.
Frequently asked questions