Key Takeaways<\/p>\n
- \n
- Two consecutive missed LKPM periods are a sanction trigger under Article 373 of Ministerial Regulation No. 5 of 2025.<\/li>\n
- Four consecutive periods without additional investment realization can also trigger action in the circumstances specified by Article 373.<\/li>\n
- OSS verification may approve a submitted report or request a correction. Keep checking the status after receiving a submission receipt.<\/li>\n
- The LKPM sanction sequence starts with written warnings. Continued failure to report can lead to temporary suspension, an administrative fine, and revocation of business licensing under the regulation\u2019s conditions.<\/li>\n<\/ul>\n<\/div>\n
The Current Rule and Who Must File<\/h2>\n
![\"Penalties](\"http:\/\/investinasia.id\/blog\/wp-content\/uploads\/2023\/10\/document2.jpg\")
Penalties and Sanctions for Late or Incorrect LKPM Reporting (source:pexels)<\/figcaption><\/figure>\n Ministerial Regulation No. 5 of 2025 took effect on 2 October 2025, according to Indonesia\u2019s official regulation database. It replaced the earlier BKPM Regulation No. 5 of 2021. Older articles that apply the 2021 filing dates or sanction process need to be checked against the 2025 text.<\/p>\n
Article 285 requires an LKPM for each applicable business activity and location after a business obtains its Business Registration Number, or NIB<\/a>. Article 286 sets a six-month reporting cycle for small businesses and a quarterly cycle for medium and large businesses, subject to the exceptions stated in the regulation. A foreign-owned company should confirm its own OSS reporting units and classification rather than infer its filing cycle from its PT PMA structure<\/a> alone.<\/p>\n
For a medium or large business, Article 286 sets 15 January 2027 as the normal deadline for the October to December 2026 report. The rule also provides for an official notice if a reporting date coincides with a national holiday. Our quarterly LKPM guide<\/a> covers the preparation and submission cycle in more detail.<\/p>\n
When a Missed Report Becomes a Sanction Trigger<\/h2>\n
Article 373 identifies failure to submit LKPM for two consecutive reporting periods<\/strong> as a ground for administrative sanctions. A single missed deadline still needs to be resolved, but the article does not say that one late report automatically revokes an NIB or starts the full sanction sequence.<\/p>\n
Count the periods that apply to the company and check each activity and location in OSS. A company may have submitted one report while another reporting unit remains outstanding. Preserve the submitted forms and receipts so the compliance team can distinguish a genuinely missing report from a record that requires follow-up with the authority.<\/p>\n
How Incorrect or Incomplete Reports Are Handled<\/h2>\n
Article 287 provides for verification and evaluation through OSS. The result is either an approval notification or a request for correction. The regulation permits correction within the reporting period. A submission receipt therefore establishes that the company sent a report; it does not, by itself, establish that the report was approved.<\/p>\n
Check the request against the underlying records before editing a figure. Common review points include investment realization, workforce data, project location, and whether the activity belongs in the preparation or operational stage. Our case study on an incorrect LKPM reporting stage<\/a> shows why a filed report can still require closer review.<\/p>\n
Do not treat every correction request as an automatic Article 373 sanction. The regulation addresses verification and correction in Article 287, while Article 373 specifies particular sanction triggers. Article 290 also provides for an OSS compliance profile based on verified LKPM data, with follow-up measures addressed in Article 291.<\/p>\n
\nNotes from InvestinAsia Consultants<\/p>\n
Keep the submission receipt and the later approval or correction notice in the same file. If the figures came from several teams, record who supplied each figure and which OSS activity and location it belongs to. That makes a correction request easier to investigate.<\/p>\n<\/div>\n
When Repeated Zero Realization Raises a Separate Risk<\/h2>\n
A zero amount for one period can accurately reflect the company\u2019s activity. Article 373 does not make every zero LKPM unlawful. It identifies two more specific situations involving four consecutive periods<\/strong> without additional investment realization: a company\u2019s first LKPM reporting sequence, and reporting during the preparation stage.<\/p>\n
If several reports show no additional realization, review the project\u2019s actual progress, supporting records, and reporting stage. Give an accurate explanation in OSS. Do not repeat a prior investment amount or invent spending to avoid a zero figure. Our guide to LKPM investment realization<\/a> explains which amounts belong in the report.<\/p>\n
\nNeed to Review Missing Periods or Repeated Zero Reports?<\/p>\n
InvestinAsia LKPM Reporting covers preparation, review of reporting information, and submission coordination for the selected period.<\/p>\n
Indonesia LKPM Reporting Service<\/a><\/div>\n<\/div>\nDiscuss My LKPM Status on WhatsApp<\/a><\/div>\n<\/div>\nHow the Warning Sequence Escalates<\/h2>\n
Articles 374 to 376 set out a staged process. The steps depend on continued noncompliance during later reporting periods; they are not all imposed when the first deadline passes.<\/p>\n
\n\n\n
\n \nStage<\/th>\n What the Regulation Provides<\/th>\n What to Check<\/th>\n<\/tr>\n<\/thead>\n \n First written warning<\/td>\n Issued when an Article 373 trigger applies. Article 374 requires an LKPM in the next period.<\/td>\n The notice, affected activity, location, and next reporting period.<\/td>\n<\/tr>\n \n Second and third written warnings<\/td>\n Each can follow if the company again fails to submit the required LKPM in the following period.<\/td>\n Whether the company submitted the report required after the preceding warning.<\/td>\n<\/tr>\n \n Temporary suspension<\/td>\n Article 374 provides for suspension if the company still fails to report in the period after the third warning.<\/td>\n The suspension notice and the conditions stated for the affected business activity.<\/td>\n<\/tr>\n \n Administrative fine and possible revocation<\/td>\n Article 375 addresses an administrative fine. Article 376 provides for revocation of business licensing if the company fails to submit the next LKPM and fails to pay the fine under the stated conditions.<\/td>\n The applicable decision, payment obligation, and current OSS licensing status.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n Article 374 says a warning is declared no longer applicable when the company submits the LKPM required in the following period. Article 375 contains separate provisions for resolving a temporary suspension and any accompanying fine. Check the actual OSS notice before assuming that sending one overdue form has closed every outstanding measure.<\/p>\n
Revocation in Article 376 concerns business licensing under its stated conditions. The text does not support a general claim that every late report automatically freezes or cancels the company\u2019s NIB.<\/p>\n
What to Preserve When a Notice Arrives<\/h2>\n
Give the reviewer a dated record of the filing and the project, not just a screenshot of a warning. The following file helps identify both the reporting problem and the next required action:<\/p>\n
- \n
- The OSS notice, including its date, reference, affected activity, and location.<\/li>\n
- The NIB and the reporting units shown in the company\u2019s OSS account.<\/li>\n
- Receipts, approval notices, correction requests, and final copies of prior LKPM reports.<\/li>\n
- A period-by-period reconciliation of investment realization and its supporting accounting records.<\/li>\n
- Evidence of project stage, operational status, and any reason for zero additional realization.<\/li>\n
- A record of who will submit a correction or outstanding report and monitor the resulting OSS status.<\/li>\n<\/ul>\n
Article 286 requires OSS to issue a submission receipt, while Article 287 provides for a later approval or correction outcome. Save both. If the notice concerns a report that your team believes was submitted, compare the reporting period, activity, and location before responding.<\/p>\n
\nNotes from InvestinAsia Consultants<\/p>\n
When several OSS units share one accounting system, prepare the realization reconciliation by activity and location. A correct company-wide total can still be assigned to the wrong LKPM unit.<\/p>\n<\/div>\n
Plan the Next Reporting Period<\/h2>\n
Once the immediate notice is addressed, assign an owner to each OSS reporting unit and review its data before the next filing window. For a medium or large business, the normal deadline for the October to December 2026 LKPM is 15 January 2027 under Article 286. Check OSS and any official notice for the applicable filing window.<\/p>\n
The LKPM is an investment activity report, separate from a corporate annual tax return. Keep its supporting figures reconciled with accounting records without assuming that the two filings use identical classifications. InvestinAsia LKPM Reporting Service<\/a> can help coordinate reporting information, review, and submission for the applicable period.<\/p>\n
\nPrepare the Next LKPM With a Clear Evidence File<\/p>\n
Review the reporting units, source records, and OSS status before the next deadline.<\/p>\n