Deddy Rizaldy & Partners Law Firm
×
Regulatory Note

Investment and OSS   |   2 AUGUST 2026

OSS Implementation and Investment Licensing under BKPM Regulation No. 5 of 2025

BKPM Regulation No. 5 of 2025 provides implementing procedures for risk-based licensing and investment facilities through OSS. Companies should treat OSS as a controlled regulatory record and ensure that system data matches their legal and operational position.

AuthorDRP Law

Executive Summary

BKPM Regulation No. 5 of 2025 provides implementing procedures for risk-based licensing and investment facilities through OSS. Companies should treat OSS as a controlled regulatory record and ensure that system data matches their legal and operational position.

Background

Regulatory compliance should be translated into assigned controls, documented evidence, reporting calendars, and escalation triggers. A licence or filing is most useful when the underlying operation remains consistent with the facts represented to the authority. OSS Implementation and Investment Licensing under BKPM Regulation No. 5 of 2025 should be approached as a connected legal, factual, and decision-making problem. In the investment and oss context, the quality of the final position depends on whether the governing instruments, authority records, chronology, correspondence, operational facts, and available remedies are reviewed together. A conclusion reached from one document or one legal provision may overlook qualifications, implementing rules, later conduct, or evidence that changes the practical assessment. This publication therefore focuses on the sequence of analysis rather than offering a universal answer. The first task is to define the relevant person, company, asset, permit, transaction, or government action. The second is to identify the legal source and the institution or contractual actor with authority. The third is to test the position against contemporaneous records and the procedure that governs any filing, objection, response, negotiation, investigation, or claim. For regulatory matters, formal approval and continuing compliance must be considered separately. A licence, registration, certificate, filing, or system status does not by itself prove that the activity continues to satisfy its conditions. Compliance should be translated into named control owners, source evidence, monitoring intervals, reporting calendars, change-management triggers, and escalation routes. This makes the regulatory position capable of being demonstrated during inspection, renewal, financing, transaction due diligence, or enforcement. The analysis is current as at 2 August 2026. The application of any law, regulation, court decision, administrative practice, or contractual provision depends on the specific facts and may change after publication.

Key Legal Issues

  • OSS profiles should reflect current shareholders. This issue defines the legal scope of the assessment.
  • Licensing outputs depend on accurate business classification and supporting commitments. The point must be tested against contemporaneous evidence.
  • Investment and activity reports should be supported by source records and responsible internal review. Procedure and timing are central.
  • Data inconsistencies may delay applications. The operational consequences should be assessed before a position is implemented.
  • Notarial. The position should anticipate how an authority, court, counterparty, shareholder, complainant, or other stakeholder may respond.

Analysis

The principal authorities identified for this topic are listed below. They should be read together with any implementing measures, sector-specific instruments, later amendments, binding court decisions, official guidance, contractual provisions, corporate instruments, and transitional rules applicable to the matter. The legal hierarchy and the date on which an instrument became effective may be decisive. • BKPM Regulation No. 5 of 2025 on Risk-Based Licensing Procedures and Investment Facilities. Before relying on an authority, confirm that it applies to the relevant person, entity, activity, asset, transaction, location, procedural stage, and period. Where an official system or institution maintains the operative record, the record should be verified rather than inferred from an earlier submission. The scope of any discretion, appeal, objection, cure, or review mechanism should also be mapped. 3.1 OSS profiles should reflect current shareholders. This issue defines the legal scope of the assessment. Counsel should identify who holds the relevant right, duty, power, or exposure; the instrument from which it arises; and any limits on authority. The review should distinguish legal form from actual conduct and should record inconsistencies rather than silently choosing one version. Authority can depend on legislation, implementing rules, constitutional documents, delegations, contracts, licences, resolutions, or an institution's procedural mandate. For OSS Implementation and Investment Licensing under BKPM Regulation No. 5 of 2025, this point should be converted into a compliance control: a responsible owner, required evidence, review frequency, system or filing dependency, approval threshold, and escalation trigger. Management should be able to demonstrate both the formal regulatory status and the operational facts supporting that status. 3.2 Licensing outputs depend on accurate business classification and supporting commitments. The point must be tested against contemporaneous evidence. Useful material may include executed documents, official records, system data, correspondence, meeting minutes, reports, financial entries, technical records, witness knowledge, and proof of delivery or submission. The legal team should identify the source, custodian, date, completeness, and reliability of each record. Missing records and later-created summaries should be labelled so that decision-makers understand the evidentiary limits. For OSS Implementation and Investment Licensing under BKPM Regulation No. 5 of 2025, this point should be converted into a compliance control: a responsible owner, required evidence, review frequency, system or filing dependency, approval threshold, and escalation trigger. Management should be able to demonstrate both the formal regulatory status and the operational facts supporting that status. 3.3 Investment and activity reports should be supported by source records and responsible internal review. Procedure and timing are central. The applicable framework may prescribe a form, authorised signatory, service method, supporting document, cure opportunity, objection route, hearing sequence, or deadline. A substantively reasonable position may still be weakened by using the wrong forum or failing to preserve a procedural step. A calendar should distinguish statutory deadlines, contractual deadlines, internal approval dates, and practical milestones for collecting evidence and preparing submissions. For OSS Implementation and Investment Licensing under BKPM Regulation No. 5 of 2025, this point should be converted into a compliance control: a responsible owner, required evidence, review frequency, system or filing dependency, approval threshold, and escalation trigger. Management should be able to demonstrate both the formal regulatory status and the operational facts supporting that status. 3.4 Data inconsistencies may delay applications. The operational consequences should be assessed before a position is implemented. Legal exposure can affect cash flow, licences, financing, contractual performance, insurance, governance, personnel, public statements, and relationships with authorities or counterparties. Scenario analysis should compare immediate action, conditional action, negotiated adjustment, and preservation of the status quo. Each scenario should state its assumptions, dependencies, reversible steps, and indicators that would require escalation. For OSS Implementation and Investment Licensing under BKPM Regulation No. 5 of 2025, this point should be converted into a compliance control: a responsible owner, required evidence, review frequency, system or filing dependency, approval threshold, and escalation trigger. Management should be able to demonstrate both the formal regulatory status and the operational facts supporting that status. 3.5 Notarial. The position should anticipate how an authority, court, counterparty, shareholder, complainant, or other stakeholder may respond. That includes testing the strongest counterargument, not only confirming the preferred interpretation. Communications should be accurate, proportionate, and consistent across legal submissions, corporate records, regulatory filings, and operational instructions. Where uncertainty remains, the decision record should explain the chosen risk tolerance and the safeguards applied. For OSS Implementation and Investment Licensing under BKPM Regulation No. 5 of 2025, this point should be converted into a compliance control: a responsible owner, required evidence, review frequency, system or filing dependency, approval threshold, and escalation trigger. Management should be able to demonstrate both the formal regulatory status and the operational facts supporting that status.

Implications

The matrix is an initial organising tool. It should be replaced or supplemented by a matter-specific chronology, document index, authority map, issue list, and risk register once the relevant records have been reviewed. ISSUE KEY EVIDENCE RISK IF UNMANAGED IMMEDIATE CONTROL OSS profiles should reflect Licences, registrations, corporate Regulatory status not matching the Confirm scope, authority, and current shareholders data, and delegated authority actual activity controlling instruments. Licensing outputs depend Source records, system extracts, Inability to demonstrate compliance Issue preservation instructions on accurate business technical reports, and submissions during supervision and build an evidence index. classification and supporting commitments Investment and activity Approval dates, reporting Late or defective filing, renewal, Create a procedural map with reports should be calendars, receipts, and regulator objection, or response verified dates and owners. supported by source notices records and responsible internal review Data inconsistencies may Operational data, inspection Operational disruption, sanction, Quantify scenarios and assign delay applications findings, incidents, and remediation transaction, or financing exposure continuity safeguards. logs Notarial Management review, corrective Recurring gaps because ownership Test counterarguments and action, and change-control records and escalation are unclear approve a communication protocol. IMMEDIATE CONTROL Preserve the relevant record, identify the decision-maker and authority, confirm procedural deadlines, and prevent avoidable escalation while the facts are verified. LEGAL ASSESSMENT Map the verified facts and documents against the applicable legal framework, contractual position, regulatory expectations, and realistic exposure scenarios. STRATEGIC Select a proportionate course of action, define approval and communication protocols, EXECUTION document implementation, and revisit the strategy as new evidence or legal developments emerge. 6.1 Questions for Decision-Makers • What precise decision, right, obligation, or exposure is being assessed in relation to oss implementation and investment licensing under bkpm regulation no. 5 of 2025? • Which law, regulation, contract, licence, corporate instrument, or official decision controls the issue? • Which facts are verified by contemporaneous evidence, and which remain assumptions or disputed allegations? • What procedural step or deadline could determine whether a right, defence, approval, or remedy remains available? • What operational, financial, governance, regulatory, and reputation consequences arise under each realistic scenario? • Who is authorised to approve the strategy, communicate externally, implement controls, and monitor later developments?

Practical Considerations / Next Steps

5.1 Nominate accountable OSS administrators and backup access controls. Begin by defining ownership of the task, the decision required, and the documents that must be available. Record any assumptions and gaps so that later reviewers can distinguish confirmed facts from matters still under investigation. The output should be a controlled work product with a clear approval path, not an informal collection of opinions. 5.2 Review company and project data against legal records. The work should reconcile legal requirements with the organisation's actual process and systems. Where records conflict, identify the source of truth, the person responsible for correction, and whether a notification, amendment, reservation of rights, or other protective step is required before the inconsistency becomes material. 5.3 Maintain a filing calendar and evidence folder for each submission. Timing should be planned backwards from the external deadline or business decision. Allow time for authority checks, document collection, technical or financial input, internal review, translation where relevant, authorised signature, submission, and proof of delivery. Contingency time is important where portals or third parties are involved. 5.4 Escalate system and substantive inconsistencies promptly. Implementation should be proportionate to the assessed exposure. Immediate measures should prevent further harm and preserve options; longer-term measures should address root cause, ownership, training, monitoring, and recurrence. Remediation should be accurate and should not overwrite the historical record needed for advice or proceedings. 5.5 Conduct an OSS readiness review before financing, M&A, or expansion. The final position should be communicated only through approved channels. Management should know which developments require board, insurer, lender, regulator, counterparty, employee, or public disclosure. After the decision, the team should monitor new evidence and legal developments and adjust the plan when its assumptions no longer hold.

Conclusion

For OSS Implementation and Investment Licensing under BKPM Regulation No. 5 of 2025, compliance should be demonstrable in both records and operations. The most useful control environment links each obligation to a responsible owner, reliable source evidence, a review date, an escalation threshold, and a documented response when facts change or an exception occurs. Periodic review is important because legislation, system requirements, regulator practice, ownership, business activities, and operational conditions may change. This note should therefore be used as a starting framework for a current, fact-specific assessment rather than as a substitute for confirmation with the relevant authority or professional adviser.