Penalties for Failing to Submit LKPM in Indonesia

A missed LKPM deadline is an evidence and authority-response incident: verify the obligation, preserve the record, remedy truthfully, and control every enforcement communication.

Failure to submit an LKPM can expose an Indonesian business to administrative action under the investment and risk-based licensing framework. The outcome should not be reduced to a universal fine or an automatic revocation claim. Authorities may consider the applicable obligation, business and project status, reporting period, prior compliance, warning history, response, accuracy, and current regulations. The immediate management task is to verify whether a report was required and missed, preserve the OSS and accounting evidence, confirm any official notice and deadline, and obtain advice on the lawful corrective route.

When non-filing or inaccurate filing has already occurred, open an incident file that records the affected entity and project, reporting period, obligation, OSS status, warning history, source data, decision tree, response approval, corrective submission, and completion evidence. Use the PT PMA compliance calendar to restore recurring deadline control, but assign separate owners and evidence requirements for the current enforcement response and any correction.

Key takeaways

• Verify the duty and missed period before admitting, denying, or correcting non-compliance.
• Distinguish reminders, validation requests, warnings, sanctions, suspension effects, and revocation claims.
• Never cure a late report by inventing realization, workforce, production, or operating facts.
• Close both the authority response and the control failure that allowed the deadline to be missed.

In this article

• Verify the missed LKPM obligation and factual timeline
• Classify the LKPM enforcement state before acting
• Remedy LKPM non-filing without creating false data
• Close the enforcement issue and recurrence risk
• Official references and review basis
• The decision gate after an LKPM deadline is missed

Verify the missed LKPM obligation and factual timeline

Open an incident record with the legal entity, NIB, project, KBLI, location, business scale, reporting stage, alleged period, current OSS status, previous report, expected deadline, actual submission history, notices, and account-access history. Identify when management first learned of the issue and what transactions or project facts existed in the period. Do not begin with a confession template or a backdated internal approval. Begin with a timeline that can be tested against official and company-controlled records.

Investment Law 25 of 2007 includes investor reporting obligations, while current OSS procedure and sanctions are addressed in Permeninves/BKPM 5 of 2025. Review the official Investment Law record together with the current 2025 OSS procedure record . Applicability can turn on project and reporting facts, so confirm the exact legal basis and current system record with qualified Indonesian advisers.

Freeze evidence before anyone changes data: portal history, user logs available to the company, reports and receipts, project exports, official emails or messages, prior advice, calendar assignments, ledger and asset data, bank transactions, contracts, invoices, payroll, and communications with the agent. If an external provider claims it filed, request the complete official submission and receipt rather than accepting a screenshot. Record what is unavailable without recreating it.

Classify the LKPM enforcement state before acting

Use a state ladder that preserves legal distinctions: internal discovery, portal reminder, data-validation request, written warning, repeated or escalated warning, formal administrative sanction, restriction or suspension consequence, and revocation-related action. Do not tell management that a warning is harmless, and do not tell the bank or a counterparty that an NIB has been revoked unless the competent authority record actually says so. Each state needs the source document, issue date, authority, response route, deadline, and available review or remedy advice.

BKPM currently warns that late or inaccurate LKPM reporting can lead from warnings to sanctions including NIB revocation. See the official BKPM LKPM submission notice . PP 28 of 2025 also places sanctions within the risk-based licensing framework. These sources establish material exposure; they do not prove that every missed report triggers the same step or timing. The actual notice and current record control the response.

Create an authority-response matrix. For each communication, list the exact allegation, facts accepted, facts disputed, missing evidence, requested action, deadline, responsible director, adviser, draft response, corporate approval, submission channel, receipt, and next status check. Escalate immediately if the record refers to license suspension, revocation, false information, an inspection, prior ignored warnings, or a deadline that may limit review rights. Do not rely on an agent's promise that the issue was fixed verbally.

Remedy LKPM non-filing without creating false data

Prepare the missing period from contemporaneous evidence wherever possible. Reconstruct the project population, prior cumulative realization, current additions, workforce, operating stage, production or revenue fields if applicable, and constraints using the ledger, invoices, contracts, bank records, asset register, payroll and approved project files. Mark estimates, missing evidence, and later-discovered information clearly for adviser review. A late truthful filing with disclosed limitations is different from inventing precision to make the form submit.

The official OSS LKPM guide provides the current filing channel. Whether the system permits a late filing, amendment, response, or another corrective route must be confirmed for the actual account and notice. Do not assume that submitting a current-period report cures a missing earlier period or that payment to a consultant removes the company's obligation. Obtain written advice for the sequence and any explanatory letter.

Approve a correction pack containing the factual timeline, legal and system status, missing period, source schedule, prior and corrected cumulative figures, open limitations, management representation, adviser comments, authorized submission, official receipt, and authority correspondence. Reconcile the correction into every later LKPM so cumulative totals do not diverge again. If the issue touches corporate funding, use the capital injection evidence controls to avoid relabeling financing as investment realization.

Close the enforcement issue and recurrence risk

An incident is not closed merely because a report was uploaded. Obtain and retain the current authority or OSS status, response receipt, submitted report, correction history, open validation items, legal advice, and any written acknowledgement available. Verify whether the NIB, standard certificate, license, project status, or operating permissions show any restriction. Coordinate accurate, need-to-know communications with directors, auditors, lenders, investors, banks, customers, and counterparties without overstating that the risk has disappeared.

PP 28 of 2025 confirms that supervision and sanctions form part of the current licensing framework. The official PP 28 record should be read with the actual sanction instrument and current OSS record. A service desk ticket, a corrected spreadsheet, or a provider assurance cannot replace a competent authority decision. Keep any unresolved legal effect visible in the board risk register.

Run a root-cause review across obligation identification, calendar ownership, source-data readiness, reviewer capacity, portal access, credential recovery, agent oversight, director escalation, and proof retention. Add a ninety-day look-ahead, backup submitter, pre-close rehearsal, evidence checklist, and post-submission verification. Test the control with the next reporting cycle and preserve the results. If the company lacks a wider control owner, align the repair with the post-incorporation compliance framework .

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.

• BKPM — LKPM submission notice — Current official warning that late or inaccurate LKPM can lead to warnings and sanctions, including NIB revocation.
• BPK — Investment Law 25 of 2007 — Primary investment-law record for reporting obligations; review amendments and applicability.
• BPK — Permeninves/BKPM 5 of 2025 — Current procedural framework for OSS licensing, supervision and sanctions.
• BPK — PP 28 of 2025 — Current risk-based licensing framework, including supervision and sanctions.
• OSS — LKPM guide — Primary current filing channel and operating guide context.

The decision gate after an LKPM deadline is missed

First verify the exact obligation, period, project, filing record, notice and current licensing state. Then preserve evidence, classify the enforcement state, reconstruct the report truthfully, obtain advice on the permitted response route, and retain every submission and authority acknowledgement. Never trade one missed deadline for false or irreconcilable data.

Keep the issue open until the company can prove both the external status and the internal repair. Escalate any warning, repeated non-compliance, license consequence, false-information concern, inspection, or procedural deadline to qualified Indonesian counsel. Review the wider Indonesia company registration framework before representing that operations remain fully ready.

Related insights

• PT PMA compliance calendar
• Post-incorporation compliance guide
• Capital injection and LKPM evidence
• Financial reporting reconciliation