How to File LKPM Investment Report in Indonesia
An LKPM is ready to file only when the reporting entity, project, period, investment realization, operating stage, workforce, constraints, and supporting ledger agree.
To file an LKPM investment report in Indonesia, begin outside the OSS form. Identify the exact legal entity and project that must be reported, confirm the reporting period and current submission window, freeze the period-end data, reconcile cumulative investment realization to the prior accepted report and accounting records, then enter the approved figures through the official OSS reporting workflow. Preserve the submitted report, receipt or status evidence, source schedules, and every validation request. A portal submission is an output of the control process, not the source of the numbers.
For each reporting period, reconcile the proposed LKPM figures to the PT PMA investment realization tracker , accounting records, bank evidence, corporate approvals, tax data, and licensing records before entering OSS. Keep a period-specific workpaper showing the opening position, additions, reversals, classifications, source evidence, approvals, and bridge to the previously accepted report. Complete an independent reviewer check before submission and retain the report, receipt or status evidence, and every follow-up request.
Key takeaways
- Confirm the reporting entity, project, business stage, period, and current deadline before preparing figures.
- Bridge the prior accepted cumulative balance to current-period additions and the new cumulative total.
- Report facts supported by invoices, contracts, bank evidence, payroll, asset records, and the ledger.
- Retain the exact submission version, official status, validation exchanges, and approved corrections.
In this article
Review the LKPM scope
Map the entity, projects, stage, period, authority, and prior submissions before preparing the report.
Confirm the LKPM reporting population and period
Create a reporting-scope memo before anyone opens the form. Record the PT PMA legal name, NIB, project or business-activity identifier, KBLI, location, risk and licensing status, construction or preparation versus operational or commercial stage, business scale, current reporting period, due window shown by the official system, and the person authorized to submit. Compare the current OSS project list with the prior accepted LKPM and the company's live activity register. A missing, duplicated, transferred, or stale project must be resolved before figures are allocated.
Indonesia's investment law establishes an investor reporting obligation, while the current risk-based licensing and OSS procedures are governed by updated instruments. The official Permeninves/BKPM 5 of 2025 record is the current procedural reference, and the OSS LKPM guide provides the live filing route. Confirm applicability and the period displayed in OSS rather than copying a historic calendar, because official windows and extensions can change.
Assign one scope owner and one reviewer. Save a dated export or screenshot of the reportable projects without exposing credentials, then map each to its deed, NIB, KBLI, location, license stage, cost center, fixed-asset register, and prior LKPM line. If the project identity or stage in OSS is wrong, document the discrepancy and obtain current OSS or Indonesian investment-law advice before filing a convenient but inaccurate classification.
| Scope field | Evidence to freeze | Stop condition |
|---|---|---|
| Entity and project | NIB, OSS project record, KBLI, location, prior LKPM | Project is missing, duplicated, or attached to the wrong entity |
| Reporting stage | Current licensing and operational evidence | Construction and commercial facts conflict |
| Reporting period | Current OSS window and official announcement | Team is relying only on last year's dates |
| Submission authority | Named user, approval, access and recovery record | External agent controls the only account or receipt |
Build the LKPM investment realization bridge
Prepare a project-by-project bridge with four columns that cannot be collapsed: approved or recorded investment plan, cumulative realization accepted in the prior LKPM, current-period qualifying additions, and current cumulative realization. Add separate schedules for land and buildings, machinery or equipment, other fixed assets, working capital or other categories used by the current form, workforce, production or revenue information where applicable, and reported constraints. Keep accounting classifications visible so a bank transfer, shareholder loan, capital contribution, expense, advance, or asset purchase is not treated as the same economic fact.
The official OSS LKPM materials show that the system asks users to select business data and review investment-plan and realization information. That interface does not decide whether a transaction belongs in a particular realization category. Use the official LKPM operating guide to identify the current fields, then support classification with the underlying contract, invoice, acceptance, payment, ownership, accounting, and project facts. Escalate uncertain items rather than forcing the ledger total into the form.
Run a roll-forward test and a duplication test. Every current addition should have a unique evidence identifier, project, category, transaction date, amount, currency and conversion basis if relevant, ledger account, payment reference, and reviewer. Check whether shared assets or central costs have been allocated twice, whether taxes or financing are embedded improperly, whether advances have become assets, and whether reversed transactions remain in cumulative totals. Link unresolved items to the financial reporting reconciliation framework rather than hiding them in a plug number.
Plan
Preserve the current OSS or approved plan by project; do not present it as cash already transferred or expenditure already realized.
Period movement
Tie additions and reversals to source documents, acceptance, bank movement, asset or expense treatment, and a named project.
Cumulative total
Reconcile prior accepted total plus approved movements to the new total and explain every difference from the ledger.
Reconcile LKPM realization
Bridge plan, prior accepted totals, current evidence, ledger entries, and cumulative realization before submission.
Submit the LKPM through OSS with controlled evidence
Use a maker-reviewer-approver workflow even if OSS permits one user to complete every screen. The maker enters only the approved schedule. The reviewer compares every material page with the frozen source pack, including project identity, stage, realization categories, workforce and production data, constraints, declarations, attachments, and reporting period. The authorized approver confirms that open exceptions are disclosed and that the final figures match the signed bridge before the submit action is released.
The official OSS guide for non-micro and non-small operational or commercial LKPM identifies the government channel and current workflow context. Navigation labels can change, so use the current portal reached independently rather than a copied login link. Never share one-time codes in an uncontrolled chat, and never allow an adviser to change the project, stage, or figures without retaining the submitted version and management approval.
Immediately after submission, download or otherwise preserve the complete report and official receipt or status evidence available in OSS. Record the submission time, user, report identifier, period, project list, file hash or controlled version, and any system message. Compare the rendered submission with the approved schedule; do not assume the upload preserved formatting, units, or every row. Store the evidence in a company-controlled location and update the compliance calendar with the next expected period and any validation follow-up.
Before submit
Approved bridge, project scope, source index, open exceptions, reviewer sign-off, authorized submitter and tested access.
At submit
Correct official domain, current period, complete project selection, reviewed declarations, controlled attachments and final confirmation.
After submit
Full report, official receipt or status, identifier, timestamp, version, validation queue, next deadline and access log.
Close LKPM validation requests and corrections
Submission is not the final control state when OSS or the investment authority asks for clarification or correction. Open a request log that records the official message, report and project, issue date, receipt channel, response deadline, question, requested evidence, owner, draft answer, review, submission proof, and current status. Reconcile every answer with the report already filed and with later submissions so the company does not create incompatible explanations across periods.
The current regulatory framework includes supervision and sanctions as part of risk-based licensing administration. The official PP 28 of 2025 record confirms that supervision and sanctions sit within the licensing system. That does not mean every portal message has the same legal effect. Classify the communication, verify the competent authority and deadline, and obtain qualified advice for a warning, disputed realization, suspected false statement, license consequence, or enforcement action.
If a correction is required, preserve the original submission and explain the factual cause, affected project and period, amount or field, accounting effect, prior and future cumulative effect, approval, corrected filing route, and receipt. Do not overwrite the workpaper or manufacture support after the event. At period close, reconcile the accepted LKPM to the ledger, asset register, tax records, corporate funding records, and next-period opening balance. A clean handoff is the strongest defense against repeated cumulative errors.
Validation log
Message, authority, date, deadline, question, evidence, answer, approval, submission proof and outcome.
Correction memo
Original fact, error cause, affected fields and periods, corrected value, accounting bridge and future treatment.
Close pack
Accepted report, receipts, correspondence, final bridge, ledger mapping, next opening balance and unresolved matters.
Official references and review basis
The following primary sources were checked on August 1, 2026. They establish the regulatory or service boundary used in this article; bank, tax office, OSS, AHU, and immigration decisions can still depend on the current record and the facts of a particular application.
- OSS — Investment Activity Report guide — Primary current filing route and LKPM guide context.
- OSS — Non-UMK operational LKPM guide — Primary workflow for non-micro and non-small operational or commercial reporting.
- BPK — Permeninves/BKPM 5 of 2025 — Current official record for OSS licensing, supervision, procedures, and sanctions.
- BPK — PP 28 of 2025 — Current risk-based licensing framework, including supervision and sanctions.
- BPK — Investment Law 25 of 2007 — Primary investment-law record for investor obligations; review amendments and applicability.
The release test for an Indonesia LKPM filing
Release the filing only when the correct entity and project population, reporting stage, current period, approved investment plan, prior accepted realization, current additions, cumulative totals, workforce and operating facts reconcile to controlled evidence. The report should be reproducible by another reviewer without access to an agent's private spreadsheet or account.
Retain the submitted report, official status, validation trail, correction history, ledger bridge, and next-period opening balance. Treat any unresolved project identity, classification, deadline, false-data concern, or enforcement message as a stop-and-escalate item. For wider entity readiness, compare the filing record with the Indonesia company registration framework .
Close the filing evidence
Preserve the report, receipt, validation, correction, reconciliation, and next-period opening balance.
Frequently asked questions
