LKPM Reporting: Turn Investment Records into a Submission Checklist

Choose the LKPM period and activity record

Start with the business activity record. Article 285 of Regulation 5/2025 requires LKPM for each business activity and location after the Business Identification Number (NIB) is obtained. Copy the NIB, business activity number (NKU), five-digit business classification (KBLI), location, period and phase into the workpaper header as the matching key.

Under Article 286 , medium and large businesses report quarterly: Q1 by April 15, Q2 by July 15, Q3 by October 15, and Q4 by January 15 of the following year. Small businesses report by July 15 and January 15; micro businesses and activities funded from APBN/APBD government budgets are exempt under that article. Representative offices have separate reporting provisions. Confirm the applicable category before using this PT PMA preparation workflow.

The OSS October 2026 reporting notice specified October 1–15 for Q3, already ended as of this review date. Do not assume a late window or holiday extension: Article 286 requires official notification for holiday adjustments. Record the deadline and escalate a missed period promptly.

For medium and large businesses, distinguish preparation from operational or commercial reporting. Article 286 requires the OSS readiness declaration before the latter. Check the actual activity status and declaration together; neither a bank transfer nor a first invoice alone answers every readiness question.

Entity formation records supply the legal name and underlying company identity. Keep the deed and registration evidence from company formation in Indonesia with the current OSS profile, then reconcile subsequent changes.

Give every source item a reporting destination

To turn investment records into an LKPM submission checklist in Indonesia, give each source item a row, an activity and period, a reporting destination and a prior-inclusion check. Release the row when its evidence, amount and treatment agree; assign an owner to anything unresolved.

The following worksheet is an internal preparation tool, not an official form or a list of compulsory uploads. Its destinations follow Annex XXVII’s LKPM fields and instructions ; the matching tests are practical controls for deciding whether your records support the entry.

Add workbook columns for item ID, date, rupiah amount, activity/location, evidence reference, destination, prior inclusion, exception, owner and resolution date. A blank support reference is a hold point, not a completed checklist item. Give “not applicable” a reason.

Check the full ledger population for omissions. For project continuity, the investment realization tracking method supplies the history; retain this period’s field reconciliation separately.

When the source groups converge, matched and unresolved items need different routes so that an apparently clean total cannot conceal an unfinished investigation.

Reconcile the additions without repeating investment

Reconcile fixed-capital realization at original acquisition cost , rather than lifting the net book value from the balance sheet. Annex XXVII’s instructions exclude depreciation and asset revaluation from this realization measure. The preparation-stage instructions also distinguish additions, including previously unreported realization, from cumulative investment. Keep any earlier omission separately identifiable instead of disguising it as a new purchase.

A preparation-stage calculation to test the worksheet

These illustrative amounts are in IDR million for one activity and location, not a client case or investment threshold. Assume earlier reported fixed-capital realization of 400 and no unresolved allocation issue.

Fixed-capital additions are 95 + 30 = IDR 125 million; the cumulative bridge is 400 + 125 = IDR 525 million. If depreciation alone produces net book value of IDR 520 million, explain the IDR 5 million difference. This calculation determines neither working capital nor other fields.

Working capital needs its own basis. The preparation-stage instructions refer to readiness for operations and one operating turnover; operational-stage fields must follow their applicable instructions and the current OSS form. Cash held in the bank is not the working-capital calculation. Record the cycle and evidence used, and obtain a treatment decision for unclear items instead of applying the fixed-asset bridge to every balance.

For shared assets, document an allocation whose combined assignments do not exceed the supported amount. Escalate capacity or licensing changes to the licensing owner; allocating costs cannot repair an incorrect activity record.

Capture people, operations and licence evidence

The financial schedule is only part of the submission pack. Article 285 and Annex XXVII also address employment, production or services, licence requirements, obligations and business obstacles. Give each applicable field a named owner so that finance does not certify operational facts from assumptions.

• Reconcile workforce movements with HR records: opening headcount plus additions less departures should equal closing headcount. Apply the annex’s workforce definitions, which exclude directors and commissioners and include contract employees.
• Confirm production or service units and the period requested. The operational-stage annex places annual production realization in the Q4 report; retain the underlying annual schedule rather than copying a single quarter into an annual field.
• Check the current status and references for applicable basic requirements, business licensing and supporting business licences (PB UMKU). Keep evidence for applicable employment, partnership, environmental, safety and social-responsibility answers.
• Describe material obstacles with the affected activity, current impact, action taken and outstanding dependency. Ask the person closest to the issue to confirm the wording and supporting record.

For automatically populated identity or project information, compare the displayed record with the source documents. The preparation-stage annex instructions direct changes through Perubahan Badan Usaha and/or Perubahan Data Usaha. Do not leave an incorrect location in place and try to compensate by altering the investment total.

Package schedules, evidence references and exception decisions together, with controlled access to confidential employee and financial records.

Move from submission receipt to resolved OSS status

Use the company’s authorized OSS access. The Bantul investment office’s current reporting instructions describe the route as Pelaporan, then Laporan Kegiatan Penanaman Modal (LKPM). Check the applicable record and phase against the workpaper before entering values; use the official OSS LKPM guidance alongside the live form when screen details differ.

1. Compare the completed OSS fields with the approved workpaper, including period, activity, location, additions, cumulative amounts and explanations. Resolve validation messages without changing supported facts simply to make the screen accept a total.
2. Have the responsible business representative confirm the declaration and the underlying facts. Annex XXVII identifies the director or authorized representative as responsible for the report; appointing a preparer does not remove that responsibility.
3. Submit the completed report and preserve the OSS submission receipt with the submitted data version. A saved draft or an internal checklist is not evidence of submission.
4. Monitor verification, preserve the outcome and assign correction requests immediately. Keep the original figures, verifier’s request, revised evidence and resubmitted version connected by one reference.

A submission receipt and an approval receipt evidence different stages. Under Articles 286–287 , OSS issues a submission receipt; verification can produce approval or a request for correction. The article provides for evaluation during the reporting period and corrections up to its deadline. Submit with room to respond; do not treat the stated evaluation period as a guarantee or assume an unlimited correction window.

For system errors, retain the timestamp, affected activity and attempted action, then raise an OSS support request. An error screenshot does not establish an extension. For a closed period or prior error, establish the current correction route before overwriting history.

Escalate an LKPM file with unresolved evidence

Escalate incorrect activity data, unsupported figures, a failed cumulative bridge, an inconsistent phase or unanswered corrections. Give finance, HR, operations, licensing or the responsible director a specific evidence request and deadline. Never relabel an unresolved item as zero.

Release the reconciled version when its fields have support and the responsible representative can confirm the declaration. Preserve the receipt and monitor verification. Carry open requests and historical adjustments into the next cycle with their references intact.