Loading Zantara...
Zantara AI
AI Business Advisor
Topics
Zantara AI
AI Business Advisor
Bali Zero handles visas, company setup, tax and property compliance in Indonesia. Ask us directly on WhatsApp.
Chat with Bali Zero on WhatsAppMost business owners in Indonesia think of their KBLI code as a licensing requirement — something you select during OSS registration and then forget about. That understanding is dangerously incomplete.
Your KBLI code (Klasifikasi Baku Lapangan Usaha Indonesia) maps directly to a KLU code (Klasifikasi Lapangan Usaha), which is the tax classification used by the DJP (Direktorat Jenderal Pajak, Indonesia's Directorate General of Taxes). The KLU determines which industry profit benchmarks your company is measured against, how your corporate tax returns are profiled, and whether your financials trigger an automated audit flag.
When KBLI 2025 reclassifies your business activity — and for many companies it will — your KLU changes with it. That single shift can cascade into altered tax benchmarks, different VAT treatment, and a recalibrated risk score in the DJP's systems.
This article explains the mechanics and gives you a practical framework for managing the transition.
The KLU system has historically mirrored the KBLI structure. Both use the same five-digit classification hierarchy, and the DJP's KLU table is derived from the BPS-issued KBLI. When BPS publishes a new KBLI revision, DJP issues an updated KLU regulation to match.
Here is how the mapping works in practice:
| Layer | KBLI Function | KLU Function |
|---|---|---|
| Section (letter) | Broad economic sector (e.g., G = Wholesale/Retail) | Sector-level tax benchmarking pool |
| Division (2-digit) | Industry group (e.g., 47 = Retail Trade) | DJP audit cluster assignment |
| Group (3-digit) | Sub-industry (e.g., 471 = Retail in Stores) | Gross profit margin benchmark range |
| Class (4-digit) | Specific activity (e.g., 4711 = Supermarket) | Operating expense ratio benchmark |
| Sub-class (5-digit) | Granular activity (e.g., 47111 = Mini-market) | Net profit margin target for audit scoring |
The deeper the code, the more specific the benchmark. A company classified under KLU 47111 (mini-market retail) is measured against different profit expectations than one under 47191 (general retail trade). The five-digit precision matters because DJP's benchmarking engine operates at the sub-class level.
Under KBLI 2025, many five-digit codes have been split, merged, or reassigned to different divisions entirely. A code that existed under KBLI 2020 may now sit in a different section with fundamentally different benchmark expectations.
The DJP maintains confidential benchmark tables — known internally as rasio benchmark — for each KLU code. These tables establish what the tax authority considers "normal" financial performance for a business in that sector. The key ratios include:
When you file your annual SPT Tahunan (corporate tax return), the CoreTax system automatically compares your reported ratios against the benchmark for your registered KLU. If your numbers deviate significantly — particularly if your reported profit margins are lower than the benchmark — your company accumulates risk points.
Enough risk points, and the system generates an SP2DK (Surat Permintaan Penjelasan atas Data dan/atau Keterangan): a formal request for explanation that is effectively the opening move of a tax audit.
Here is where things get consequential for businesses migrating their KBLI codes.
Consider a company previously classified as a "General Management Consultancy" (KBLI 2020: 70209). Under KBLI 2025, the activity might be reclassified to a more specific sub-class within professional services — say a code with benchmark GPM of 70% instead of the old code's 50%.
If your actual gross margin is 52%, you were comfortably within range under the old KLU. Under the new KLU, you are 18 percentage points below benchmark. The system flags this as a deviation. You receive an SP2DK. You now need to explain why your profitability is below sector norms.
KBLI 2025 introduces granular splits across hospitality, digital services, and real estate. A company that previously reported everything under a single broad code may now need to register multiple codes. Each code carries its own KLU benchmark.
If you continue reporting consolidated revenue under the primary code without properly allocating income across your registered activities, DJP's system sees a mismatch: your revenue profile does not match the expected pattern for a single-activity business.
If your KLU changes from one DJP division to another — say from "Information Services" (Section J) to "Professional Services" (Section M) — without any visible change in your actual business operations, this creates what DJP analysts call a sector-hop profile. It raises questions about whether the reclassification is being used to exploit more favorable benchmarks in the new category.
This is not theoretical. DJP has specifically flagged KBLI migration periods as windows for enhanced scrutiny, because historically some taxpayers have used reclassification as an opportunity to reset their benchmark profile.
The CoreTax Administration System (Sistem Inti Administrasi Perpajakan), launched in 2025, fundamentally changes how the KLU operates in the DJP's infrastructure.
CoreTax pulls data directly from the OSS-RBA system. When you update your KBLI in OSS, the change propagates to your taxpayer master file in CoreTax. Your KLU updates automatically. There is no lag period, no manual form to submit, and no opportunity to maintain different classifications across systems.
The transition to NPWP16 (NIK-based taxpayer identification) requires that your tax identity is fully synchronized with your business registration. Your NIB (Nomor Induk Berusaha) carries your KBLI codes. Your NPWP carries your KLU. Under NPWP16, these must match. A mismatch between your OSS-registered KBLI and your DJP-registered KLU is now a flaggable compliance error.
CoreTax does not operate in isolation. It cross-references your filed SPT against:
A KBLI change that is not reflected consistently across all of these touchpoints generates audit attention.
Before changing any codes, request your current KLU benchmark profile. You can approximate this by reviewing DJP's published benchmark data (available through the DJP Online portal) or by asking your tax consultant to pull the benchmark ratios for your current five-digit KLU.
Document your current position: where do your actual financials sit relative to the benchmark? If you are already below the GPM benchmark, migrating to a code with an even higher benchmark will compound the issue.
Use the official BPS KBLI 2025 concordance table to map your current code to its 2025 equivalent. Pay attention to whether:
Each of these scenarios has different KLU implications.
For each candidate KBLI 2025 code, research the corresponding KLU benchmark. Compare:
| Metric | Current KLU Benchmark | New KLU Benchmark | Your Actual Ratio |
|---|---|---|---|
| GPM | e.g., 50% | e.g., 65% | e.g., 52% |
| OPM | e.g., 20% | e.g., 30% | e.g., 22% |
| NPM | e.g., 10% | e.g., 15% | e.g., 11% |
| Input/Output VAT | e.g., 0.80 | e.g., 0.70 | e.g., 0.78 |
If the gap between your actuals and the new benchmark is significant, prepare documentation explaining why. Legitimate reasons include: startup-phase investment, market conditions, contractual pricing structures, or geographic cost differences.
Create an internal document that records:
This memo serves as your first line of defense if an SP2DK is issued. Having it prepared before the migration demonstrates good faith compliance.
Update your KBLI in OSS and your KLU in CoreTax simultaneously. Do not leave a window where the two systems show different classifications. The ideal approach:
If your KBLI 2025 migration results in multiple registered activity codes, ensure your accounting system can segregate revenue, COGS, and expenses by activity. DJP expects that multi-code businesses can demonstrate which revenue belongs to which activity. Consolidated reporting under a single code when you have multiple registered activities invites scrutiny.
To illustrate the practical impact, here are representative benchmark shifts that KBLI 2025 migration can produce:
| Business Type | Old Code (2020) | New Code (2025) | GPM Shift | Audit Risk |
|---|---|---|---|---|
| Villa Management | 68110 (Real Estate) | 55xxx (Accommodation) | 40% to 60% | High — margin expectations jump significantly |
| Digital Marketing Agency | 73100 (Advertising) | 63xxx (Digital Services) | 35% to 50% | Medium — new sector, new benchmarks |
| Coworking Space | 68201 (Property Rental) | 82xxx (Business Support) | 50% to 45% | Low — benchmark drops, favorable shift |
| Restaurant + Catering | 56101 (Restaurant) | 56101 + 56210 (split) | Single to dual benchmark | Medium — revenue allocation scrutiny |
| IT Consulting | 62010 (Programming) | 62010 + 63xxx (split) | 55% to 60%/50% | — depends on allocation |
The villa management example is particularly significant for Bali. Many villa operators were historically classified under real estate (Section L), which carries moderate profit expectations. Under KBLI 2025, short-term accommodation management is more accurately classified under accommodation services (Section I), which carries hospitality-level margin expectations — typically 15-20 percentage points higher. This single reclassification can transform a compliant taxpayer into an outlier overnight.
For PT PMA entities with related-party transactions, the KLU classification affects transfer pricing analysis. DJP uses KLU codes to select comparables in benchmarking studies. If your KLU changes, the pool of comparable companies used to evaluate your intercompany pricing changes with it.
A company previously benchmarked against management consultancies (wide profit range, many comparables) might now be benchmarked against specialized technical services (narrow profit range, fewer comparables). This can tighten the acceptable arm's-length range and expose previously compliant pricing arrangements to challenge.
If your business has transfer pricing documentation (TP Doc), it must be updated to reflect the new KLU and the revised comparable set. Do not wait until the annual TP Doc refresh — update it concurrently with the KBLI migration.
Your KLU also determines how DJP profiles your PPN (Pajak Pertambahan Nilai / Value Added Tax) behavior. Certain sectors have expected input-to-output VAT ratios. A manufacturer is expected to claim significant input VAT on raw materials. A consulting firm is expected to claim minimal input VAT.
If your KBLI migration moves you from a manufacturing-adjacent code to a services code, but your input VAT claims remain at manufacturing levels, DJP's system flags this as inconsistent. Conversely, if you move to a code with higher expected input claims and your claims are low, you may be leaving legitimate credits on the table.
Review your VAT position as part of the migration. Ensure your input VAT claims are consistent with the sector profile of your new KLU.
The June 2026 KBLI 2025 transition window has closed. The corporate tax filing deadline for fiscal year 2025 is April 30, 2026. This creates a critical sequencing question: do you file your FY2025 SPT under the old KLU or the new one?
Recommended approach:
This approach avoids filing a tax return under a KLU that was not in effect during the fiscal year being reported, which could create temporal inconsistencies in DJP's system.
If the KBLI migration triggers an SP2DK (tax clarification request), respond promptly and methodically:
The businesses that face the most difficulty are those that changed their KBLI without considering the tax implications and cannot explain why their financials deviate from the new sector benchmarks. Preparation is the difference between a routine clarification and a protracted audit.
Your KBLI code is not just a licensing label. It is the foundation of your tax identity in Indonesia. Under KBLI 2025 and the CoreTax system, the wall between business licensing and tax administration has been demolished.
Every company migrating its KBLI should treat the process as a tax event, not just a compliance checkbox. Map your benchmarks, prepare your documentation, align your systems, and coordinate the timing. The businesses that treat KBLI migration as a purely administrative exercise are the ones that will be explaining themselves to DJP in 2027.