KBLI 2025 Transition Strategy | Smart Compliance Guide

Q: When should I update my KBLI codes to 2025?

Verify live OSS support first, then update through the official workflow for your sector. Unsupported changes can lock your NIB, block customs clearance, or create Coretax mismatches.

Q: What happens if I miss the June 2026 KBLI deadline?

Existing permits remain valid, but new regulatory actions (permits, LKPM reports, import approvals) require KBLI 2025 codes. Delayed migration creates compliance gaps visible to Coretax.

Q: Does Coretax affect my KBLI transition?

Yes. Coretax links your KBLI codes to KLU tax classification. Any mismatch between your business activities and registered codes now triggers automated audit flags through the DGT benchmarking system.

Zantara AI

Loading Zantara...

The Transition Paradox

Indonesia's KBLI 2025 migration presents a paradox that is testing the nerve of every business operator in the country: the law says alignment is required, the transition window has closed, and the live OSS workflow still needs to be verified before each remediation step.

This isn't a scenario where you can simply rush to comply. Premature updates can lock your NIB, block customs clearance, and create data mismatches that follow you into the Coretax system. But waiting indefinitely now creates post-deadline gaps that can surface during new filings, LKPM reporting, imports, banking, tax, or investor due diligence.

The winning strategy is strategic patience — acting decisively but at the right moment, with full preparation completed in advance.

The Current State of Play

What's Active

BPS Regulation No. 7 of 2025 is legally in force since December 18, 2025
The Coretax Administration System is rolling out in phases since January 1, 2026
BKPM Regulation No. 5 of 2025 has reduced PT PMA paid-up capital to IDR 2.5 billion
PP No. 28 of 2025 has expanded Fiktif Positif (deemed approval) mechanisms

What Still Needs Verification

The OSS system must be checked live before any filing; unsupported or partially mapped KBLI 2025 codes can still create risk-parameter gaps.
Sectoral implementing regulations from technical ministries are still pending
Old-to-new KBLI mappings should be checked against the current OSS/AHU record, not assumed from an outdated planning table

The Deadline

Post-June 2026 — legacy codes should be treated as potential "ghost codes" unless the current OSS/AHU record confirms the correct KBLI 2025 mapping for new permit applications, import approvals, or LKPM reporting.

Phase 1: The Audit (Do This Now)

Strategic patience doesn't mean inaction. The preparation phase should start immediately.

Map Your Current Codes

Pull your NIB and list every KBLI code registered to your business. For each code, determine:

Does it still exist in KBLI 2025? Some codes have been abolished.
Has it been split? The "one-to-many" principle means your code may now map to 2-3 specific sub-codes. Which one matches your primary revenue stream?
Has it been merged? The "many-to-one" principle may have consolidated your codes.
Has the risk level changed? A shift from Low Risk to Medium-High means new licensing requirements.

Test Your Financial Profile

For each prospective new KBLI code, assess the DGT's benchmarked financial ratios:

What Net Profit Margin does the DGT expect for companies with this code?
Does your actual margin fall within the expected range?
If you're significantly below the benchmark, can you document why? (Market expansion costs, seasonal factors, Bali-specific economics)

This assessment is critical because under Coretax, the moment you update your KBLI, the DGT's algorithms will benchmark your next tax filing against the new code's expected profile.

Review Foreign Ownership Implications

The Category J/K split in the digital sector has direct foreign ownership consequences. If your current code has moved from an "open" category to a "restricted" one, you may need to restructure before updating.

Phase 2: The Remediation File (Post-Window)

Prepare Notarial Deeds

If your KBLI code change requires amending your company's Articles of Association (Anggaran Dasar), have the notarial deed drafted before you file. Do not wait until a blocked transaction exposes the gap. Once the live OSS path for your sector is confirmed, you want to execute within days, not weeks.

Build Your Defense File

For any KBLI code where your financial profile deviates from the expected benchmark, prepare documentation before the SP2DK arrives:

Market entry costs that temporarily suppress margins
Seasonal business patterns (especially relevant for Bali tourism)
Industry-specific cost structures that differ from the national average
One-off write-downs or restructuring charges

Having this file ready converts a potentially adversarial tax inquiry into a routine clarification.

Consolidate Unnecessary Codes

If you have KBLI codes registered for activities you no longer perform, plan to remove them during the migration. Unused codes are liability magnets — they create phantom benchmarks and can trigger audit questions about undeclared revenue streams.

Phase 3: The Execution (After Live OSS Verification)

Don't Force a Premature Update

This is the most important piece of tactical advice: do not attempt an unsupported KBLI update in OSS; verify the official live workflow first.

Premature updates can:

Lock your NIB if the system encounters an error during code migration
Block customs clearance if your import license references a code the system can't process
Create Coretax mismatches if the DGT database updates before the OSS logic is complete

Monitor BKPM Communications

Check official BKPM and OSS channels before filing. When the live workflow supports your sector, execute your prepared changes immediately. Clean movers in a stable workflow have an advantage over operators who discover the issue only during a blocked transaction.

Verify After Update

After updating your codes in OSS:

Confirm the new codes appear correctly on your NIB
Check that the risk classification matches your expectation
Verify that your import licenses (API-P/API-U) are still valid under the new codes
Cross-reference with your Coretax portal to ensure synchronization

The Five Traps to Avoid

Trap 1: The Code That Splits

Your current code maps to multiple new codes. You pick the wrong one — the one that triggers a higher risk level or a restricted foreign ownership category. Always choose based on your actual primary revenue stream, not administrative convenience.

Trap 2: The KITAS Disconnect

If you rely on an Investor KITAS (C314), remember: the immigration threshold for personal share ownership remains at IDR 10 billion, even though the corporate entry capital is now IDR 2.5 billion. Plan your visa strategy separately from your corporate structure.

Trap 3: The Coretax Benchmark Shock

Updating your KBLI triggers an automatic update in the DGT's profiling system. If your new code has dramatically different profit margin expectations, your very next tax filing could trigger an SP2DK. Prepare the defense file before updating.

Trap 4: The LKPM Reporting Gap

Your quarterly LKPM must reference your KBLI codes. If you update codes mid-quarter, ensure continuity in your reporting. A gap or mismatch between old and new codes in LKPM can trigger an investment license review.

Trap 5: The Fiktif Positif Overreliance

If you're in a sector where OSS can't process your new code, you might be tempted to rely on Fiktif Positif (deemed approval through bureaucratic silence). Remember: Fiktif Positif shifts all compliance risk to you. The government can retroactively revoke any license issued via automatic approval if post-audit reveals data errors.

The Bali Factor

Bali-based businesses face unique considerations in this transition:

Tourism Seasonality

If your financial profile shows dramatic seasonal variation (high margins in peak season, losses in low season), document this pattern clearly. The DGT's benchmarks are national averages — Bali's unique economics need explanation.

Villa and Hospitality Classification

The line between "hospitality" and "property" determines your tax benchmark, entertainment tax exposure, and licensing requirements. Use the migration as an opportunity to ensure your classification reflects your actual operating model.

Digital Nomad Service Providers

Coworking spaces, coliving operators, and digital services targeting nomads occupy classification grey areas. The KBLI 2025 update may provide more specific codes — or push you into categories with unexpected implications. Audit carefully.

Multi-Activity Businesses

Many Bali businesses operate across multiple activities (restaurant + event venue + retail shop). Each activity may map to a different KBLI code with different risk levels. The KBLI 2025 migration is an opportunity to clean up multi-code registrations and ensure each activity is correctly classified.

The Timeline

Period	Action	Priority
Now	Complete KBLI audit, map old codes to new	Critical
Immediate	Prepare notarial deeds, build defense files	High
Before filing	Verify live OSS/AHU workflow, then execute remediation	Critical
After update	Verify updates, ensure Coretax sync, update LKPM	Critical
Post-window	Treat legacy codes as potential ghost-code risk	Deadline

The Strategic Mindset

The businesses that will navigate this transition most successfully share a common approach: they treat KBLI 2025 not as a compliance burden but as a strategic audit of their entire regulatory position.

This is a rare opportunity to:

Correct historical misclassifications without penalty (during the grace period)
Align your licensing identity with your fiscal identity before Coretax makes mismatches automatically visible
Access new incentives (FGP manufacturing status, green finance, crypto formalization) that the new codes unlock
Remove dead codes that create phantom audit exposure

The window has closed. The system path may still vary by sector and record. Use this phase to verify, remediate, and document thoroughly so the next filing does not expose an unresolved gap.

That's the art of strategic patience.