PT PMA LKPM Reporting: Reconcile Investment Plans and Actual Activity

Freeze the LKPM scope and reporting calendar

Choose the activity and location before choosing the numbers. Article 285 of Regulation 5/2025 requires LKPM for each business activity and location after a Business Identification Number (NIB) is obtained. It covers investment, workforce, production, licensing, obligations and obstacles.

Record the company name, NIB, business-activity record, project address and selected reporting stage on a cover sheet. A company-wide bank total is too broad when expenditure belongs to several projects. Match the reporting record to the activity classification shown in Online Single Submission (OSS), rather than allocating everything to the first activity in the account.

For medium and large businesses, Article 286 sets these ordinary quarterly LKPM deadlines:

Official notices may adjust deadlines for national holidays. Use project facts to choose preparation or ready/operational/commercial reporting; the latter follows an OSS readiness statement.

As checked on October 27, 2026, BKPM's published 2026 notice confirms a 1–15 April window for that year's first quarter. Do not reuse that historical window as an announcement for a later period. Set an internal evidence deadline early enough to investigate differences and respond before the applicable filing window closes.

Separate the investment plan, funding and project progress

A shareholder transfer into the company's bank account is not, by itself, evidence of project expenditure. It explains funding. The investment plan describes intended deployment. Realization needs support for what was actually acquired or otherwise reportable under the applicable LKPM instructions.

Keep three references side by side: the plan currently shown in OSS, the last accepted cumulative report, and the period's source records. Preserve a dated copy of each. A board budget prepared for management may use a different scope or schedule from the OSS plan, so identify which baseline a variance compares.

The Annex XXVII instructions use the OSS investment plan and distinguish additional from cumulative realization. Fixed investment uses acquisition values without depreciation or asset revaluation. Accordingly, a net book value cannot simply replace the realization history.

Reconcile the underlying company identity against company registration requirements in Indonesia when formation records and OSS identifiers disagree. Keep that identity correction separate from deciding whether a particular machine, lease or operating payment belongs in this period's investment data.

Give the project manager a separate progress column: equipment delivered, installation incomplete, premises unavailable, or operations started. Finance should explain the amounts; the project owner should confirm the activity. Their records need to tell a consistent story even when physical progress and expenditure move at different speeds.

The reconciliation therefore needs three inputs before anyone evaluates the gap: the intended project, what was reported before, and the evidence of what happened during the close.

Build a variance bridge from source records to LKPM

Use an adjustment bridge to explain the difference between the source schedule and the proposed report. The following hypothetical example covers one fixed-asset component at one location. Its amounts are arithmetic examples, not minimum investment requirements, service prices or a complete LKPM calculation.

The IDR 900 million gap calls for an explanation of the remaining work. It is not a number to insert as realized investment. Ask whether the balance represents equipment still to be acquired, a delayed installation, or a plan that management no longer intends to implement.

For every adjustment, retain a transaction reference, original date, project allocation, reason, preparer and reviewer. This creates a reported-before check independent of payment status. Paying an old invoice this quarter must not cause the same acquisition to be counted again.

Keep working capital on its own schedule using the relevant form instructions; do not add all annual operating cash payments to this fixed-asset example. If earlier unreported expenditure emerges, flag its original date and review the applicable catch-up treatment instead of relabelling it as newly incurred.

A reviewer should be able to reconstruct the closing balance from the opening file and approved adjustments without relying on the preparer's memory.

Investigate activity that contradicts the investment figures

Investigate contradictions before treating a numerical gap as an error. A project can incur supported expenditure before producing revenue; a funded bank account can coexist with delayed procurement. The question is whether the records support the explanation.

• Investment rises but the site appears inactive: inspect delivery, acquisition and installation evidence. Identify whether assets are awaiting use or were assigned to the wrong project.
• Production or sales exist but the report still describes preparation: compare dated operational evidence with the selected stage and the OSS readiness record.
• Headcount changes without a project explanation: reconcile the workforce schedule to employment and payroll records using the form's definitions, rather than inferring headcount from salary expense.
• The same asset appears at two locations: determine the correct reporting allocation and preserve the reason for removing the duplicate. Do not silently split it to make both plans look complete.
• No additions appear despite continuing activity: distinguish genuine zero additions from missing invoices, unposted acquisitions and repeated reliance on an unsupported opening balance.

Record each difference as a timing, allocation or scope exception . Timing may require an explanation of when activity occurred. Allocation may require a revised project schedule. A genuine change to the planned activity or location needs review of the relevant OSS data change; editing an LKPM narrative alone may leave the underlying mismatch intact.

For each unresolved item, name the evidence owner and the action that would settle it. A supplier delivery note, project manager confirmation or corrected record is a useful closure condition; “finance to review” is not. BKPM's accuracy and timeliness warning makes clear that inaccurate or late reports can have administrative consequences.

Retain the submission record and resolve review requests

Preserve both what was sent and what happened after sending. Article 287 distinguishes approval from a correction request after verification. Article 286 provides a submission receipt; requested repairs may be made within the reporting deadline. A saved draft is not submission evidence.

Before sending, freeze the source schedule, bridge, explanations and reviewer sign-off as one version. The person entering OSS should compare the final screen with that version, including the period, activity, location, stage and cumulative amounts. Keep the submitted report or available system record with its timestamp and reference.

Assign someone to monitor the result. If a repair is requested, preserve the request, identify which bridge lines changed, and have the relevant evidence owner approve the response. Retain the revised version and resulting status together so a later reviewer can distinguish the original filing from its correction.

Use evidence allocation and LKPM submission checks to connect each supporting record to its reporting destination. A bank statement proves a movement of money; it does not explain every investment category, operational milestone or licensing answer in the submission.

If the reporting window has closed or a historical period cannot be edited through the available workflow, record the affected period and seek the applicable official handling route. Keep the discrepancy visible in the close file until it is resolved; avoid masking a prior error by changing unrelated current figures.

Approve explained LKPM variances and escalate the rest

Approve the LKPM file when the project identity is stable, additions can be traced, cumulative balances reconcile and operational evidence supports the selected stage. A supported difference from the plan can remain visible with a clear explanation; equality between plan and realization is not the approval test.

Escalate an unexplained opening balance, duplicate realization, incorrect location or unsupported stage before authorizing the affected figures. Prioritize the issue that changes the reporting perimeter, then the amount, then the explanation. Release the final version only after the responsible reviewer can identify the evidence behind each material adjustment.