Your OSS Integration Survival Guide for PERMEN LH 22/2025
October 27th Changed Everything: Your OSS Integration Survival Guide for PERMEN LH 22/2025
PERMEN LH 22/2025 Analysis Series - Article 3 of 4
- Who Decides Your Environmental Permit? Indonesia's Authority Maze
- The Sector Trap: Why Your Industry Classification Determines Your Approval Path
- October 27th Changed Everything: Your OSS Integration Survival Guide
1.0 The Critical Implementation Timeline: From Promulgation to OSS Integration
PERMEN LH 22/2025 Article 16 establishes immediate legal effectiveness: "Peraturan Menteri/Badan ini mulai berlaku pada tanggal diundangkan" (This Ministerial/Agency Regulation comes into force on the date of promulgation). The regulation was promulgated and signed by Minister/Agency Head HANIF FAISOL NUROFIQ on October 22, 2025, creating legal force from that date. However, Article 2(3) mandates integration with the Online Single Submission (OSS) system: "Pelaksanaan penerbitan Persetujuan Lingkungan...dilakukan melalui sistem informasi lingkungan hidup yang dikelola oleh Kementerian/Badan yang terintegrasi dengan Sistem OSS" (Implementation of Environmental Approval issuance...is conducted through the environmental information system managed by the Ministry/Agency integrated with the OSS System). The Ministry announced October 27, 2025 as the operational implementation deadline for OSS system integration, creating a 5-day preparation window between legal effectiveness (October 22) and operational launch (October 27). During this 5-day period, businesses and local governments faced compressed timelines to understand location-based authority criteria, remap existing applications to new jurisdiction rules, and prepare for automated routing through OSS. The integration connects two systems: AMDANET (AMDAL Network - the Ministry's environmental assessment platform) and OSS (Online Single Submission - Indonesia's centralized business licensing platform managed by Lembaga OSS per Article 1(9) definition). The October 27 deadline marked the point when OSS began automatically routing environmental approval applications based on location data input, geographic boundary matching against provincial and regency databases, and application of authority determination rules from Articles 3-9, effectively removing applicant discretion in choosing submission jurisdiction (see Matrix 1.1 below).
Matrix 1.1: PERMEN LH 22/2025 Implementation Timeline
| No. | Date | Event | Legal/Operational Status | Key Actions Required |
|---|---|---|---|---|
| 1.1 | October 22, 2025 | Regulation promulgated and signed | Legally effective per Article 16 | Regulation text published, legal force established |
| 1.2 | October 22-27, 2025 | 5-day preparation window | Transitional period | Businesses/governments study new criteria, Ministry conducts socialization |
| 1.3 | October 27, 2025 | OSS integration operational | Fully operational - automated routing begins | OSS system routes applications based on location data |
| 1.4 | November 2025 | AMDANET automation (announced) | Gradual deployment | Automated jurisdiction screening, SLA enforcement begins |
2.0 Transitional Provisions: Administrative Completeness Cutoff
Article 14 of PERMEN LH 22/2025 establishes critical transitional provisions protecting applications already in process before October 27, 2025. Article 14(1) states: "Permohonan Persetujuan Lingkungan yang telah dinyatakan lengkap secara administratif sebelum Peraturan Menteri/Badan ini berlaku, tetap diproses berdasarkan ketentuan peraturan perundang-undangan sebelum berlakunya Peraturan Menteri/Badan ini" (Environmental Approval applications that have been declared administratively complete before this Ministerial/Agency Regulation comes into force, continue to be processed based on statutory provisions before this Ministerial/Agency Regulation came into force). The critical term is "dinyatakan lengkap secara administratif" (declared administratively complete) - this requires formal written declaration from the receiving government office that all required documents have been submitted and the application file is complete, not merely submission of documents without formal completeness confirmation. Article 14(2) addresses the scenario where applications declared complete before October 27 later return for revision: "Dalam hal terdapat perbaikan dan/atau penyempurnaan dokumen sebagaimana dimaksud pada ayat (1), dilakukan berdasarkan kewenangan sesuai dengan ketentuan Peraturan Menteri/Badan ini" (In the event there are improvements and/or refinements to documents as referred to in paragraph (1), they are conducted based on authority in accordance with the provisions of this Ministerial/Agency Regulation). This creates a potential "jurisdiction shift" scenario: an application declared complete under old rules (processed by local government) may require revisions that under new rules would fall under provincial or central authority, forcing mid-process jurisdiction transfer. The administrative completeness cutoff creates two populations of applications: "grandfathered" applications (declared complete before October 27) continuing under old sector-based rules, and "new regime" applications (submitted October 27 onward or declared complete after October 27) subject to location-based authority determination (see Matrix 2.1 below).
Matrix 2.1: Transitional Provisions - Application Status Scenarios
| No. | Application Status as of October 27, 2025 | Authority Determination Rule | Processing Under | Jurisdiction Change Risk | Article Reference |
|---|---|---|---|---|---|
| 2.1 | Declared administratively complete before October 27 | Old rules (sector-based) | Old authority (pre-PERMEN 22/2025) | Low - unless revisions required | Article 14(1) |
| 2.2 | Submitted but NOT yet declared complete before October 27 | New rules (location-based) | New authority (PERMEN 22/2025) | High - full re-evaluation under new criteria | Article 14 (by exclusion) |
| 2.3 | Declared complete before October 27, later requires revisions | New rules apply to revisions | May shift to new authority during revision | High - revision triggers jurisdiction reassessment | Article 14(2) |
| 2.4 | Submitted on or after October 27 | New rules (location-based) | New authority (PERMEN 22/2025) | N/A - processed under new rules from start | Article 14 (by operation) |
Matrix 2.2: Administrative Completeness Definition
| Component | Requirement | Evidence | Common Mistake |
|---|---|---|---|
| Document Submission | All required documents per environmental instrument (AMDAL, UKL-UPL, etc.) | Receipt acknowledgment from government office | Assuming submission = completeness |
| Formal Completeness Declaration | Written statement from government office declaring "lengkap administratif" | Official letter with reference number and date | Relying on verbal confirmation |
| Date of Declaration | Date on formal completeness letter determines old vs new rules | Letter date before or after October 27, 2025 | Using submission date instead of declaration date |
Critical Distinction: Submission ≠ Administrative Completeness. Only formal written declaration of "lengkap administratif" before October 27 protects under old rules.
3.0 OSS System Integration: Automated Authority Routing
Article 2(3) mandates that environmental approval issuance be conducted through "sistem informasi lingkungan hidup yang dikelola oleh Kementerian/Badan yang terintegrasi dengan Sistem OSS" (environmental information system managed by the Ministry/Agency integrated with the OSS System), creating a unified digital gateway for all environmental approval applications. The OSS system integration operates through several technical steps: (1) applicants log into OSS portal using NIB (Nomor Induk Berusaha - Business Identification Number); (2) applicants input project location data including geographic coordinates, address, and administrative boundaries (province, regency/city, district, village); (3) OSS system performs automated geographic matching against government administrative boundary databases to determine whether project crosses provincial boundaries, regency boundaries, or remains within single jurisdiction; (4) OSS applies location criteria matrix from Articles 3-9 to determine appropriate authority level; (5) OSS routes application to central (Ministry/Agency), provincial (Governor), local (Regent/Mayor), or special zone (IKN/Batam) environmental approval desk; (6) receiving authority processes application through relevant teams (Environmental Feasibility Assessment Teams for AMDAL, Environmental Agencies for UKL-UPL); (7) approval decisions are issued digitally through OSS and linked to NIB. The automation eliminates applicant "forum shopping" (choosing preferred government office) but creates new requirements for geographic precision - incorrect coordinates can route applications to wrong authorities, causing processing delays while jurisdiction gets corrected. Article 11 establishes Service Level Agreements (SLAs) for each government level: central government must process within specified timeframes per environmental instrument type, provincial government follows separate SLA schedules, and local government adheres to distinct processing timelines. Article 12 creates SLA enforcement through complaint mechanisms: if authorities exceed processing deadlines without written explanation, applicants may file complaints through OSS, triggering supervisory review and potential administrative sanctions against responsible officials (see Matrix 3.1 and 3.2 below).
Matrix 3.1: OSS Integration Process Flow
| Step | Process | System Component | User Action | System Action | Output |
|---|---|---|---|---|---|
| 1 | Login | OSS Portal | Enter NIB and credentials | Authenticate user identity | Access to environmental approval module |
| 2 | Location Input | OSS Geographic Module | Enter project coordinates, address, administrative boundaries | Validate against government boundary database | Confirmed location data |
| 3 | Authority Determination | AMDANET + OSS Integration | Review auto-determined authority | Apply Articles 3-9 location criteria + check Lampiran I/II for KBLI codes | Authority assignment (Central/Provincial/Local/IKN/Batam) |
| 4 | Application Routing | OSS Workflow Engine | Submit application with required documents | Route to appropriate government desk | Application received by correct authority |
| 5 | Processing | AMDANET Assessment Module | Monitor status through OSS | Assessment teams review technical documents | Draft approval/rejection decision |
| 6 | Decision Issuance | OSS Approval Module | Receive notification | Issue digital approval linked to NIB | Persetujuan Lingkungan document |
Matrix 3.2: Service Level Agreements (SLAs) by Authority Level
| Authority Level | Environmental Instrument | Maximum Processing Days | Legal Basis | Complaint Mechanism |
|---|---|---|---|---|
| Central (Minister/Head) | AMDAL | Per technical complexity | Article 11(1) | OSS complaint system (Art 12) |
| UKL-UPL | Per technical complexity | Article 11(1) | OSS complaint system (Art 12) | |
| Provincial (Governor) | AMDAL | Per technical complexity | Article 11(2) | OSS complaint system (Art 12) |
| UKL-UPL | Per technical complexity | Article 11(2) | OSS complaint system (Art 12) | |
| Local (Regent/Mayor) | AMDAL | Per technical complexity | Article 11(3) | OSS complaint system (Art 12) |
| UKL-UPL | Per technical complexity | Article 11(3) | OSS complaint system (Art 12) |
Note: Specific SLA day counts vary by environmental instrument complexity and are established through Ministry technical guidelines referenced in Article 11.
4.0 Approval Modifications and Jurisdiction Reassessment
Article 13 addresses modifications to existing environmental approvals after PERMEN LH 22/2025 takes effect, creating scenarios where approved projects must return for permit modifications that may trigger jurisdiction shifts under new authority rules. Article 13(1) states: "Perubahan Persetujuan Lingkungan untuk rencana Usaha dan/atau Kegiatan yang telah memiliki Persetujuan Lingkungan sebelum Peraturan Menteri/Badan ini berlaku, dilakukan berdasarkan kewenangan sesuai dengan ketentuan Peraturan Menteri/Badan ini" (Changes to Environmental Approval for planned Business and/or Activity that already has Environmental Approval before this Ministerial/Agency Regulation comes into force, are conducted based on authority in accordance with the provisions of this Ministerial/Agency Regulation). This provision means that even projects approved under old rules (pre-October 27, 2025) must use new location-based authority criteria when seeking modifications, potentially requiring submission to different government levels than the original approving authority. Modification scenarios triggering jurisdiction reassessment include: (1) geographic expansion - project expands footprint across administrative boundaries not originally crossed; (2) activity addition - project adds new activities with different KBLI codes that appear in Lampiran I or II; (3) scale increase - project increases capacity/scale to threshold requiring higher authority (e.g., small-scale operation escalating to AMDAL-required scale); (4) technology change - process modifications increasing pollution potential or environmental risk. Article 13(2) specifies that modifications not requiring new environmental documents (minor administrative changes, ownership transfers, facility name changes) can be processed by original approving authority without jurisdiction reassessment. The modification provisions create long-term compliance obligations: projects approved under pre-2025 sector-based rules must monitor any changes against post-2025 location-based criteria to determine if modifications require submission to new authorities (see Matrix 4.1 below).
Matrix 4.1: Environmental Approval Modifications - Jurisdiction Scenarios
| No. | Modification Type | Requires New Environmental Document? | Authority Determination | Example | Article Reference |
|---|---|---|---|---|---|
| 4.1 | Geographic expansion | YES (if crosses new boundaries) | New authority per current location rules | Factory approved by Regent expands across regency boundary → now requires Governor | Article 13(1) |
| 4.2 | Activity addition with different KBLI | YES (if new KBLI in Lampiran I/II) | New authority if KBLI escalates | Warehouse adds chemical storage (new KBLI in Lampiran I) → requires Minister | Article 13(1) |
| 4.3 | Scale increase to AMDAL threshold | YES | New authority per current rules | UKL-UPL operation scales up to AMDAL-required size → reassess authority | Article 13(1) |
| 4.4 | Technology change increasing risk | YES (if pollution/risk increase) | New authority if escalates to Lampiran I criteria | Mine adds submarine tailings disposal → triggers central authority (Art 4) | Article 13(1) |
| 4.5 | Administrative changes only | NO | Original authority | Ownership transfer, facility name change, administrative corrections | Article 13(2) |
Key Principle: Modifications requiring new environmental assessment documents trigger full jurisdiction reassessment under PERMEN 22/2025 rules, even for projects originally approved under old regulations.
5.0 Coordination Mechanisms and Special Provisions
Article 10 establishes coordination mechanisms for complex scenarios where authority determination remains ambiguous or where multiple government levels have legitimate jurisdictional interests. Article 10(1) states: "Dalam hal terdapat Usaha dan/atau Kegiatan yang sulit ditentukan kewenangannya, Menteri/Kepala, gubernur, atau bupati/wali kota melakukan koordinasi untuk menetapkan pihak yang berwenang" (In the event there are Business and/or Activities where authority is difficult to determine, the Minister/Head, Governor, or Regent/Mayor conduct coordination to establish the authorized party). This provision addresses edge cases such as: projects straddling administrative boundaries with unclear primary location; activities with novel technologies not clearly fitting KBLI classifications; conflicts between location criteria (suggesting one authority) and sectoral lists (suggesting different authority); disputes over PMA versus PMDN status affecting agriculture/forestry/fisheries authority. Article 10(2) requires coordination results to be documented in writing: "Hasil koordinasi sebagaimana dimaksud pada ayat (1) ditetapkan dalam bentuk tertulis" (Coordination results as referred to in paragraph (1) are established in written form), creating binding determinations that both applicants and government offices must follow. The coordination mechanism provides flexibility for genuinely complex cases but also creates potential delays - applications caught in coordination processes may face extended processing times while government levels negotiate jurisdiction. Article 15 addresses one specific special provision: activities in the Exclusive Economic Zone (ZEE - Zona Ekonomi Eksklusif) beyond 12 nautical miles from coastline automatically fall under central government authority even if not specifically listed in Lampiran I, establishing maritime jurisdiction principles that extend central authority to Indonesia's full 200 nautical mile EEZ claim per international law. These coordination and special provisions serve as regulatory safety valves, preventing jurisdictional deadlock when standard criteria produce ambiguous or contradictory results (see Matrix 5.1 below).
Matrix 5.1: Coordination Mechanisms for Ambiguous Authority Cases
| No. | Scenario Triggering Coordination | Potential Authority Conflict | Coordination Participants | Resolution Method | Article Reference |
|---|---|---|---|---|---|
| 5.1 | Project straddles administrative boundary (unclear primary location) | Local vs Provincial, or Provincial vs Central | Relevant Ministers/Governors/Regents | Written coordination agreement | Article 10(1), 10(2) |
| 5.2 | Novel technology/activity without clear KBLI classification | Classification determines Lampiran I/II applicability | Ministry + Provincial/Local government | Ministry issues classification guidance | Article 10(1) |
| 5.3 | Location criteria vs Lampiran I/II conflict | Geography suggests one authority, KBLI suggests another | Relevant government levels | Apply Lampiran I/II (sectoral) override per Articles 4(6), 6(5) | Article 10(1) |
| 5.4 | PMA vs PMDN status dispute | Investor nationality determines authority for agriculture/forestry/fisheries | Investment Coordinating Board + Environmental authority | Verify investment registration status | Article 10(1) |
| 5.5 | EEZ (200 NM) maritime activities | Beyond 12 NM but within Indonesia's EEZ claim | Central government (automatic) | No coordination needed - Central authority per Article 15 | Article 15 |
Coordination Timeline: No specific SLA for coordination processes - potential source of processing delays for complex cases.
Continue Reading: PERMEN LH 22/2025 Analysis Series
This is Article 3 of 4 in this comprehensive legal analysis series:
- Who Decides Your Environmental Permit? Indonesia's Authority Maze - Authority distribution and location criteria
- The Sector Trap: Why Your Industry Classification Determines Your Approval Path - Sectoral classifications in Lampiran I and II
- October 27th Changed Everything: Your OSS Integration Survival Guide (this article) - Implementation timeline and OSS integration
Regulation Reference
Full Citation: Peraturan Menteri Lingkungan Hidup dan Kepala Badan Pengendalian Lingkungan Hidup Nomor 22 Tahun 2025 tentang Kewenangan Penerbitan Persetujuan Lingkungan (Ministerial/Agency Regulation Number 22 of 2025 on Authority for Issuing Environmental Approvals)
Key Implementation Articles:
- Article 2(3): OSS integration mandate
- Article 10: Coordination mechanisms
- Article 11: Service Level Agreements (SLAs)
- Article 12: SLA enforcement and complaint mechanisms
- Article 13: Environmental approval modifications
- Article 14: Transitional provisions
- Article 15: EEZ special provisions
- Article 16: Effective date (date of promulgation)
Legal Analysis by the CRPG Environmental Law Team | Analysis Date: November 16, 2025 | Regulation Effective: October 27, 2025
LEGAL DISCLAIMER: This article is provided for informational and educational purposes only and does not constitute legal advice, legal opinion, or professional consultation. The analysis presented herein is based on the authors' interpretation of PERMEN LH 22/2025 and related regulations as of the publication date and may contain errors, omissions, or inaccuracies despite reasonable efforts to ensure accuracy. Laws and regulations are subject to amendment, judicial interpretation, and administrative clarification that may affect the applicability or interpretation of the provisions discussed. This article does not create an attorney-client relationship between the authors, the Center for Regulation, Policy and Government (CRPG), and any reader. Readers should not act or refrain from acting based solely on the information contained in this article without seeking appropriate legal counsel from qualified Indonesian legal practitioners licensed to practice environmental and administrative law. The application of transitional provisions, administrative completeness determinations, OSS system procedures, and approval modification requirements under PERMEN LH 22/2025 depends on specific factual circumstances including exact application submission dates, formal completeness declaration dates, modification scope and scale, OSS system data accuracy, and coordination outcomes between government levels, all of which require case-specific legal analysis. Neither the authors nor CRPG assume any liability for actions taken or not taken based on information in this article, nor for any direct, indirect, incidental, consequential, or punitive damages arising from use of or reliance on this material. For specific legal guidance on OSS integration procedures, transitional provision applicability, administrative completeness requirements, approval modification processes, or coordination mechanisms under PERMEN LH 22/2025, consult with qualified legal counsel familiar with Indonesian environmental law, digital licensing systems, and current regulatory practice.