Investment realization control

PT PMA Investment Realization Tracker: From IDR 10 Billion Plan to LKPM

A finance-and-compliance workflow for translating an approved PT PMA plan into supportable project records and periodic LKPM figures.

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

A PT PMA should convert its approved investment plan into a transaction-level tracker before the first project payment. The tracker needs one control row for each applicable KBLI-location unit, then records the approved category, vendor or counterparty, invoice, payment, asset or expense treatment, reporting period, and cumulative realization. BKPM Regulation No. 5 of 2025 generally sets a planned investment value of more than IDR 10 billion outside land and buildings per five-digit KBLI and project location, subject to listed activity and location exceptions; the same regulation supplies the current LKPM framework.

The tracker is not a substitute for the Online Single Submission (OSS) record, accounting ledger, tax file, fixed-asset register, contract archive, or bank statement. Its job is to reconcile those sources and expose classification or timing differences before a report is submitted. Finance should pause a figure when the invoice purpose, project location, KBLI allocation, payment evidence, or accounting classification cannot be supported, because repeating an unsupported amount in later periods turns a local mistake into a cumulative control problem.

Minimum fields for an investment realization row

The row should let a reviewer trace an LKPM figure back to an approved project and original evidence without rebuilding the transaction from email.

Tracker field	Control question	Primary evidence
KBLI and location	Which regulated calculation unit receives the amount?	OSS activity and project record
Plan category	Was the expenditure included in the approved plan?	Board budget and investment schedule
Transaction	What was bought, from whom, and when?	Contract, purchase order, invoice
Payment	Did company cash settle the supported obligation?	Bank advice and bank statement
Accounting	How was the item recognized and capitalized?	Ledger and fixed-asset register
Reporting period	Is the amount new for this period or already cumulative?	Prior accepted LKPM and close file

Key takeaways

Track realization by the applicable KBLI-location unit, not only by legal entity.
Do not report a purchase merely because cash moved; retain the business purpose, invoice, receipt, and accounting entry.
Separate current-period additions from cumulative totals and lock prior accepted figures against accidental overwrite.
Route plan changes through approval before changing the tracker or OSS data.
Use a quarter-close exception list so unresolved items remain visible instead of being forced into a category.

Design the tracker before transactions accumulate

Map the approved KBLI-location plan, evidence fields, and quarter-close owners before the first reporting cut-off.

Build the tracker around the legal calculation unit

The realization tracker should mirror the investment-plan unit that applies to each PT PMA activity. The general rule uses a five-digit KBLI and project location, while the 2025 BKPM regulation lists different calculation treatment for specified activities, such as wholesale trade, food and beverage services, construction, integrated production, property, and certain location-based projects. The tracker must preserve whichever unit was used in the approved plan.

A company-wide total can look reasonable while one activity is overreported, another is missing, or expenditure from one project site is assigned to another. A stable activity-location identifier also allows finance to reconcile the same project across OSS, the board budget, the ledger, asset records, bank payments, and LKPM without relying on free-text descriptions.

Evidence rule

Create the control structure once, and require formal approval before a new KBLI, site, or exception rule changes the unit.

Use a unique project key for every applicable KBLI-location pair.
Record whether land and buildings are included or excluded for that activity.
Map every tracker row to the current OSS activity record.
Prevent one invoice from being counted twice across locations or categories.

Compare the structure with HSJGlobal’s PT PMA capital requirements guide when the approved plan and current OSS record do not use the same activity boundary.

Define evidence rules before the first project payment

A realization row should be opened only when the PT PMA can identify the contractual purpose, supplier, invoice or payment request, receiving project, payment path, and accounting treatment. The tracker should not treat a transfer to an employee, related party, or advance account as final realization until the underlying project evidence and settlement are available. This preserves a traceable difference between cash movement and supported investment expenditure.

Evidence standards should reflect the transaction type. Equipment may require a purchase agreement, invoice, import or delivery evidence, payment, commissioning record, and asset register entry. Professional work may require a scope, invoice, deliverable acceptance, withholding-tax evidence, and ledger posting. Foreign-currency expenditure also needs a consistent conversion basis so cumulative figures can be reproduced.

Control point

Finance should mark incomplete transactions as pending rather than forcing them into the current reporting period.

Set mandatory evidence by asset, construction, service, and advance category.
Record vendor legal name and related-party status.
Store transaction currency, IDR equivalent, and conversion source.
Link reversals, credit notes, cancellations, and reallocations to the original row.

Use the same evidence discipline described in the PT PMA capital proof guide , while keeping capital contribution evidence distinct from project expenditure evidence.

Reconcile the tracker with accounting and bank records

The tracker is ready for reporting only when each posted amount agrees with the PT PMA ledger and can be traced to a bank settlement or a documented non-cash treatment. Timing differences should be labeled rather than hidden. An invoice received before period end, a payment after period end, a deposit awaiting delivery, and a capitalized asset placed in service are different states and may require different reporting treatment.

A three-way reconciliation should compare the tracker total, the relevant general-ledger and fixed-asset balances, and supported cash flows. The reviewer should investigate duplicate invoice numbers, round-sum entries, unexplained manual journals, payments from an unexpected shareholder or affiliate, and transactions assigned to a location that does not match the contract or delivery evidence.

Release test

Close the period only when every difference has an owner, reason, planned correction date, and decision on whether it affects the current LKPM.

Reconcile current-period additions and cumulative balances separately.
Tie fixed assets to the asset register and operating location.
Trace payments to company bank statements and authorized journals.
Keep an exception ledger for pending, rejected, reversed, and reclassified items.

Do not use a capital transfer as a proxy for realized investment; planned investment and paid-up capital remain different records .

Test the current realization balance

Reconcile project rows against invoices, bank statements, ledgers, assets, and the prior accepted period without overwriting exceptions.

Prepare LKPM from a locked period-close file

A medium or large PT PMA should operate a quarterly close file because the current BKPM regulation provides quarterly LKPM periods and submission deadlines. The official 2025 regulation states deadlines of April 15, July 15, October 15, and January 15 for the corresponding quarterly reports. The compliance owner should confirm the current schedule in OSS before every filing and retain the submitted output and status.

The close file should show the opening accepted cumulative figure, current-period supported additions, approved adjustments, and closing cumulative figure. It should also record the preparer, reviewer, filing account, submission timestamp, OSS receipt or status, and any system comment. Once submitted and accepted, the closing balance becomes the next period’s protected opening balance.

Stop condition

Do not overwrite the prior period to make the current quarter reconcile; process corrections through a documented route and preserve the audit trail.

Freeze the transaction cut-off and download the prior accepted record.
Review the exception ledger before transferring totals into OSS.
Capture screenshots or exports needed to prove the submitted fields and status.
Roll forward the accepted closing balances and outstanding actions.

Connect the close calendar with the broader PT PMA compliance schedule so tax, accounting, license, and investment reporting owners use compatible cut-offs.

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.

Ministry of Investment and Downstream Industry/BKPM Regulation No. 5 of 2025 : Current investment-value, paid-up capital, capital-use, OSS, and LKPM framework.
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.
Limited Liability Company Law No. 40 of 2007 : Company-law framework for shares, capital, corporate organs, records, and authority, as amended.

Regulatory Notes and Limitations

The tracker supports governance and evidence preparation; it does not decide legal classification by itself. LKPM fields, exceptions, OSS behavior, accounting, tax, and sector requirements must be confirmed for the actual PT PMA and reporting period.

The general more-than-IDR-10-billion rule is subject to activity, land-and-building, and location exceptions in the current regulation.
The same expenditure should not be duplicated across KBLI, locations, periods, or investment categories.
OSS status and instructions should be checked at each filing because system workflows and company records can change.
Corrections to authoritative records should be made through the proper corporate, accounting, licensing, or reporting route rather than through unsupported spreadsheet adjustments.

Escalate plan changes before they distort realization

A material change to activity, project location, asset mix, funding path, or commercial timing should be assessed before finance rewrites the realization tracker. The PT PMA may need board approval, an OSS update, license work, accounting changes, or a revised internal investment schedule. The correct response depends on the fact pattern; a spreadsheet edit cannot cure a mismatch in an authoritative company or government record.

The change request should describe the old plan, proposed plan, reason, affected KBLI-location units, license impact, budget movement, funding source, already incurred expenditure, and reporting treatment. Legal, licensing, tax, and accounting owners should review only the fields within their responsibility, then one coordinator should record the approved integrated position.

Record standard

Pause new project coding when the approved plan and intended operating activity no longer describe the same transaction.

Define materiality triggers for new activities, sites, facilities, and related-party spending.
Separate genuine plan changes from correction of data-entry errors.
Assess whether invoices or assets already recorded require reclassification.
Document the effective date and the first reporting period affected.

Use the Indonesia company registration service scope when a change reaches the deed, shareholders, directors, KBLI, location, or licensing workstream.

Keep the IDR 10 billion plan defensible through each LKPM cycle

The useful control is not a single IDR 10 billion total. It is a traceable bridge from the approved KBLI-location plan to each supported transaction, the company books, bank settlement, and the cumulative figure carried into the next LKPM period.

Hold unresolved transactions in an exception ledger, lock prior accepted balances, and escalate real plan changes before rewriting the tracker. That discipline gives management a figure it can explain rather than a number that merely fits the current filing screen.

Create a controlled LKPM close

Build the roll-forward, reviewer sign-off, submission record, and change log needed for a repeatable reporting cycle.

Frequently asked questions

Is paid-up capital reported as investment realization automatically?

No. A capital contribution and realized project expenditure are different events and records. The company should apply the current LKPM instructions and report only amounts supported and classified for the relevant field.

Can one invoice be allocated to several PT PMA projects?

Only when the allocation has a supportable business basis, does not duplicate the amount, and matches the relevant accounting and project records. Keep the calculation and approval with the source invoice.

What should happen to an advance paid before delivery?

Record the advance and evidence, but do not automatically treat it as a completed asset or service. Determine the correct accounting and LKPM treatment for the reporting period and track later settlement.

How should foreign-currency purchases enter the tracker?

Store the original currency, payment date, IDR equivalent, and documented conversion basis. Apply one approved method consistently and preserve enough evidence to reproduce the reported figure.

Should an accepted LKPM balance be edited in the next quarter?

No silent overwrite is appropriate. Protect the accepted opening balance and process any correction through a documented route that explains the reason, authority, period, and downstream impact.