LKPM Warning and Sanction Response: Evidence, Corrections, and Filing Control

Operate LKPM as an investment-record reconciliation

LKPM is not a narrative marketing update. The reporting owner should reconcile OSS project data with actual investment realization, capital goods and working capital classifications, workforce, production or operating status, project location, licensing progress, and obstacles for the applicable period. Current risk-based licensing administration is governed by Government Regulation 28 of 2025 and implemented through BKPM Regulation 5 of 2025 ; the company should check the current OSS calendar and filing status for its scale and project. For the LKPM response plan, the immediate acceptance point is to confirm the reporting population against the documented entity, project, KBLI, location, scale, and period.

Maintain a roll-forward from the previous accepted report. Investigate negative movement, double counting, exchange-rate changes, capital recorded in the wrong project, assets paid by a parent, data imported from old OSS records, and differences from the general ledger. Save the submitted form, receipt, status, source schedules, reviewer sign-off, correction correspondence, and next filing date. Respond to warnings or requests with evidence rather than repeatedly resubmitting unsupported numbers. Within the LKPM response plan file, the responsible officer should preserve ledger-to-OSS investment and workforce schedules as evidence for the decision to explain every movement.

Read the NIB, risk level, and operating conditions together

An NIB is a business identity and, for low-risk activity, the business license; it is not a universal authorization for every KBLI. Medium-low risk generally adds an unverified Standard Certificate, medium-high risk requires a verified Standard Certificate, and high risk requires an NIB plus a license. The actual output follows the activity, scale, location, and current sector rules. For the LKPM response plan, the immediate acceptance point is to check whether verification is required and complete against the documented NIB plus Standard Certificate.

This risk structure is set out in BKPM Regulation 5 of 2025 and the governing Government Regulation 28 of 2025 . Read the OSS output for verification status, prerequisites, obligations, and supporting PB UMKU rather than stopping at the NIB. If the premises, environmental approval, professional credential, or sector permission remains incomplete, do not treat the company as commercially ready. Within the LKPM response plan file, the responsible officer should preserve NIB plus license as evidence for the decision to do not operate before required approval.

Move from the deed to OSS in dependency order

The incorporation workflow should move from approved source data to name, deed, legal-entity approval, tax data, and OSS licensing. Each output becomes an input for the next system, so a correction to shareholders, address, capital, or activity can create work across several records. Release control should sit with the investor or an authorized company officer, not solely with the filing agent. For the LKPM response plan, the immediate acceptance point is to check operational status, not number alone against the documented NIB and applicable standards or permits.

Use AHU business-entity services for the corporate record and the OSS framework under Government Regulation 28 of 2025 for risk-based business licensing. After each submission, compare the official output with the approved data sheet. Record the identifier, issue date, responsible account, downloadable evidence, corrections, and next dependency before marking a stage complete. Within the LKPM response plan file, the responsible officer should preserve name, deed, and AHU approval as evidence for the decision to verify legal identity and governance.

Build an accepted shareholder and authority file

The filing team needs usable evidence for each shareholder, authorized signer, director, commissioner, address, and declared business activity. Foreign individuals typically provide passport and contact data, while foreign corporate shareholders need constitutional and authority records that identify the entity and the person empowered to sign. The accepting notary should confirm the exact document, legalization, apostille, translation, and validity requirements. For the LKPM response plan, the immediate acceptance point is to resolve spelling and expiry issues against the documented passports and consistent personal data.

Build a document register with issuer, document date, expiry or freshness rule, language, certification route, signatory, original location, and accepting institution. Indonesian company formation is processed through notarial and AHU business-entity services workflows, so a scan that looks complete to a provider may still require a different form or supporting authority. Resolve discrepancies in names, addresses, dates, and ownership before execution. Within the LKPM response plan file, the responsible officer should preserve charter, registry proof, and signer mandate as evidence for the decision to confirm the shareholder can subscribe.

Test the company before its first commercial transaction

Legal incorporation is only one readiness state. The company may still need verified OSS outputs, sector or supporting permits, tax access, PKP analysis, accounting and invoice controls, payroll arrangements, a bank account, premises evidence, and recurring reporting ownership before it can execute the planned transaction. Each state should be independently evidenced. For the LKPM response plan, the immediate acceptance point is to activity can proceed under conditions against the documented applicable OSS and tax outputs.

Use DGT registration guidance for the tax registration workstream and Government Regulation 28 of 2025 for the licensing baseline. Build a first-transaction test covering authority, contract, invoice, tax, payment, license, delivery, accounting entry, and reporting. Do not let a certificate date become the commercial launch date unless every required control passes. Within the LKPM response plan file, the responsible officer should preserve bank, people, premises, controls, and reporting as evidence for the decision to first transaction can be executed.

Operations should apply the OSS risk-based license output review to the actual site and process before signing a lease or approving first revenue.