Fixing PT PMA Capital Mismatches Between the Deed, OSS, Bank, and LKPM
Find the first incorrect event, preserve the original record, and correct corporate, licensing, accounting, banking, and reporting layers in the right order.
A PT PMA capital mismatch is not solved by making every system display the same number. First identify what each record should represent. The deed states corporate share capital; OSS states project investment; the bank shows actual transactions; the ledger classifies them; and LKPM reports realised investment. The error may be a wrong number, wrong label, wrong payer, wrong date, wrong project, missing payment, double-counted asset, or a filing that correctly differs from another record.
Freeze new capital-related filings and preserve all evidence before changing anything. Build a dated comparison, locate the earliest incorrect event, determine who has authority to correct it, and assess downstream effects. A structured PT PMA capital correction review should avoid backdating, fabricated receipts, or an OSS edit that creates a new inconsistency in the deed, books, bank KYC, tax, or LKPM.
| Symptom | Possible cause | First evidence |
|---|---|---|
| Deed exceeds bank receipt | Timing, instalment, FX, missing payment, wrong assumption | Subscription and bank trail |
| Bank receipt booked as loan | Wrong purpose or accounting entry | Approval, remittance, ledger |
| OSS plan duplicates assets | Copied project or shared-cost error | Project workbook and asset list |
| LKPM exceeds ledger support | Classification, period, or duplicate reporting | Filing bridge and source ledger |
Key takeaways
- A difference is not automatically an error; compare the purpose and time period of each figure.
- Correct the first wrong event before editing downstream records.
- Preserve original filings, statements, invoices, approvals, and access logs.
- Corporate amendments, accounting corrections, OSS changes, bank updates, and LKPM corrections have different authority and timing.
- Never fabricate capital evidence or backdate a document to force reconciliation.
In this article
Classify the difference before calling it an error
Create columns for authorised capital, issued capital, paid-up capital, shareholder payment, bank credit, equity ledger, shareholder loan, OSS fixed investment, OSS working capital, cumulative investment realisation, and LKPM period. Add source, date, currency, project, and responsible person. Normal differences—such as an OSS plan exceeding current paid-up equity—should be explained, not eliminated.
Classify the issue as corporate, payment, accounting, project-allocation, reporting, or evidence. More than one may apply. For example, the deed can be correct, a shareholder can pay through an undocumented group company, and the accountant can record the receipt as a loan. That is an authority and classification problem, not a reason to change the deed amount.
Purpose
What question was the record designed to answer?
Period
Is it a point-in-time, plan, period, or cumulative figure?
Entity/project
Which company, KBLI, and location does it belong to?
Evidence
Can the number be reproduced from original records?
Preserve the evidence and control system access
Download or secure the current deed, approvals, registers, OSS profile and outputs, LKPM filings and receipts, bank statements and messages, general ledger, invoices, asset register, contracts, emails, provider instructions, and access logs. Record who held credentials and who submitted each change. Preserve original files read-only and work on copies.
Restrict changes to authorised people and suspend a provider’s access if integrity is in doubt, while ensuring the company retains lawful access and business continuity. Do not delete an incorrect filing or rename it “draft.” A correction file should show the original, the issue, analysis, approval, amended record, submission evidence, and downstream reconciliation.
- Original corporate and shareholder records
- OSS and LKPM exports with submission evidence
- Bank statements, remittance messages, and KYC correspondence
- Ledger, asset register, invoices, and contracts
- System users, credentials, and submission logs
- Read-only evidence archive and working copy
Find the first wrong event in the chain
Build a timeline from shareholder approval through deed, payment, bank credit, accounting entry, OSS plan, asset purchase, and LKPM. Test each event against its source and authority. The earliest unsupported event usually determines the correction path. If a shareholder never paid the subscribed amount, changing LKPM cannot fix the corporate issue. If the payment is correct but booked as debt, a corporate amendment may be unnecessary.
Interview the preparer and reviewer separately when facts are unclear. Ask what information they had, which rule or instruction they used, and whether the system auto-populated a value. Do not assume fraud when a mapping or timing mistake is plausible, and do not assume a harmless clerical error when money or ownership is unsupported.
Chronology
Order every approval, filing, payment, purchase, and report.
Authority
Confirm who could validly create or approve the event.
Evidence
Reperform the calculation from original records.
Root cause
Stop at the first event that is wrong or unsupported.
Choose the correction route for the affected record
A corporate capital error may require shareholder approval, notarial work, Ministry of Law filing, or actual payment. An accounting misclassification may require a supported journal correction and disclosure. An OSS project error may require an amendment that remains consistent with the licensed activity and budget. An LKPM error may need a correction or explanation under current submission procedures. A bank mismatch may require an updated KYC explanation and transaction support.
Sequence corrections so one valid record is not changed to match an invalid one. Obtain the necessary legal, tax, accounting, and regulatory advice. Consider whether financial statements, tax filings, licences, dividends, shareholder rights, covenants, or customer representations were affected. The company’s directors should approve material remediation and record why the chosen route is lawful.
| Root record | Possible correction owner | Downstream review |
|---|---|---|
| Deed/share register | Shareholders and notary | Ministry record, OSS, bank, ledger |
| Bank/payment | Shareholder, company, bank | Equity, KYC, FX, source of funds |
| Ledger | Management and accountant/auditor | Tax, financial statements, LKPM |
| OSS/LKPM | Authorised OSS/reporting owner | Licence, project budget, evidence, future filing |
Execute the correction without rewriting history
Use current-dated approvals and state the original error and effective accounting or legal treatment accurately. Do not create a false bank receipt, backdate a shareholder resolution, edit a PDF statement, or ask a provider to issue a misleading certificate. If a payment is made late, record the actual date and obtain advice on the consequences rather than pretending it occurred at incorporation.
Submit amendments through the current authorised route and retain acknowledgements. Notify the bank, shareholders, auditor, tax adviser, regulator, or counterparty where required or prudent. The PT PMA capital evidence guide can be used to rebuild the supporting chain after the correction is approved.
Disclose
Describe the original error, cause, amount, period, and affected records.
Approve
Use the body with legal authority for the correction.
Submit
Follow the current system and retain official evidence.
Reconcile
Update downstream records and preserve the before-and-after trail.
Prevent recurrence with one capital-change control
Require a capital change form for every share issue, payment, shareholder loan, conversion, major asset purchase, KBLI or location addition, OSS investment change, and LKPM filing. The form should state purpose, record affected, amount, currency, project, approvals, evidence, accounting, tax, bank notification, filing owner, and reconciliation date.
Review access quarterly and before changing providers. Reconcile deed, shareholder register, bank, ledger, OSS, and LKPM at each material event and reporting period. A short independent check before submission costs less than a multi-system correction. Management should also investigate repeated “clerical” errors that benefit one party or obscure where money went.
- Pre-change purpose and authority
- Record and project impact assessment
- Bank, accounting, tax, and licence review
- Submission and evidence owner
- Post-change reconciliation
- Access and provider-control review
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
The correct mismatch fix begins with classification and chronology. Preserve the file, identify the first unsupported event, and change only the records that are actually wrong. Then reconcile the consequences across corporate, bank, accounting, OSS, and LKPM layers.
A transparent current-dated correction is safer than a cosmetically perfect history. After remediation, require one controlled capital-change form and a recurring cross-system reconciliation.
Frequently asked questions