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 WhatsAppFor decades, Indonesian businesses operated with a dual identity. The KBLI (Klasifikasi Baku Lapangan Usaha Indonesia) was your licensing identity — managed by BPS and enforced by BKPM, it determined what you were permitted to do. The KLU (Klasifikasi Lapangan Usaha) was your fiscal identity — managed by the Directorate General of Taxes (DGT/DJP), it categorized your revenue for tax purposes.
These systems rarely talked to each other. A company might be licensed as a "Management Consultancy" (KBLI 7020) to bypass certain foreign equity caps, but report taxes as "General Wholesale" (KLU 46xxx) to justify lower operating margins. Because the databases were siloed, discrepancies were common, often unnoticed, and rarely punished.
That arbitrage is dead. With the enactment of BPS Regulation No. 7 of 2025 (KBLI 2025) and its synchronized integration with the Coretax Administration System (CTAS), these two classification systems have fused into a singular mechanism for fiscal surveillance.
The hidden insight: your KBLI code has evolved from a static bureaucratic label into the primary fiscal determinant of your corporate entity.
Under the new Coretax regime, the DGT no longer passively accepts the KLU reported by taxpayers during annual filing. Instead, the system acts as a centralized data aggregator, pulling live data directly from the OSS-RBA database.
The moment a business updates its license in OSS — to renew a permit or expand into a new sector — that data flows instantly to the DGT. The Coretax system automatically updates the taxpayer's Master File, overriding the historical KLU with the new KBLI data.
The Coretax transition is being used as a massive data cleansing exercise. The DGT forces reconciliation between registered activity and actual revenue streams. A company claiming to be inactive while OSS shows active license renewals triggers an immediate red flag.
The gap between "what we say we do for the license" and "what we say we do for taxes" is eliminated. If you're a "Manufacturer" in OSS, you must be a "Manufacturer" in Coretax, with all associated tax obligations and manufacturing-level profit expectations.
The most sophisticated aspect of this convergence revolves around benchmarking. The DGT doesn't have the manpower to manually audit every taxpayer. Instead, it relies on automation and statistical probability. The KBLI/KLU code is the keystone.
The DGT uses KLU codes to establish "standard" financial ratios for every industry sector, including:
Consider a company registered under KBLI 6202 (Computer Consultancy). The DGT's algorithm expects a financial profile consistent with a service-based consulting firm — typically high gross margins and a net profitability range of 15-30%.
Now consider that this company is actually engaged in low-margin hardware trading (buying and selling servers) but retained the "Computer Consultancy" code for legacy reasons. Hardware trading operates on margins of 2-5%.
When the company files a tax return reporting a 4% net profit margin, the Coretax system compares this against the KLU benchmark for "Consultancy" (25%). The system sees a massive "profit gap." It doesn't know the company is trading hardware — it only knows the company is coded as a Consultant but earning like a Trader.
The consequence: The algorithm flags the company as under-reporting income. This triggers an automated SP2DK (Request for Explanation), asking the taxpayer to justify the deviation. The burden of proof shifts entirely to the taxpayer.
The KBLI code is now the denominator in the equation that determines your tax compliance score.
The convergence feeds directly into the DGT's Compliance Risk Management (CRM) system — an automated engine that profiles taxpayers and selects them for audit without initial human intervention.
The CRM system places every taxpayer into one of four quadrants based on two axes:
X-Axis: Probability of Non-Compliance Derived from historical behavior (late filings, previous amendments) and data mismatches between reported figures and third-party data (banks, customs, OSS).
Y-Axis: Consequence of Non-Compliance Measures revenue magnitude and the potential tax gap.
The KLU is the primary variable for calculating the "Potential Tax Gap" on the Y-axis. The system compares your actual tax payment against the "potential" payment expected from a typical company with your specific KLU.
A common practice — born of uncertainty or convenience during registration — is dumping activities into generic codes or "Other Business Activities Not Elsewhere Classified" (n.e.c.).
Generic codes are assigned the highest risk profiles by the DGT. Historically, these codes have been used to obscure activities and facilitate tax avoidance. A business using a generic "Trading" code because it was the easiest option during incorporation gets benchmarked against the most profitable traders in the country, creating a perpetual struggle to justify "underperformance."
One of the most critical changes for tax authorities is the bifurcation of Information & Communication:
Includes publishing, broadcasting, content production, and dedicated codes for YouTubers, influencers, and digital content producers. By creating specific codes for these actors, the DGT can apply targeted "Norma" rates to their revenue and bring the informal digital economy into the formal tax net.
Reserved for telecommunications, programming, consultancy, and computing infrastructure.
Case Study: Data Centers (63112 vs. 63102)
Under KBLI 2020, data centers operated under the catch-all 63112 (Data Processing). KBLI 2025 abolishes 63112 and introduces 63102 (Computing Infrastructure, Hosting, and Related Activities).
"Data Processing" implies a service activity, often asset-light. "Infrastructure/Colocation" implies a capital-intensive, asset-heavy business model. The tax consequences are fundamentally different:
A company failing to migrate to 63102 risks having its depreciation expenses challenged during an audit, as the system will still benchmark them against asset-light service providers.
Under Coretax, SP2DKs are increasingly automated based on KBLI/KLU logic:
Your reported profit margin deviates significantly from the industry benchmark for your KLU. A "Consultancy" firm reporting a 4% NPM when the benchmark is 25% gets flagged immediately.
The DGT has benchmarks for how much Input VAT a specific KLU should have relative to Output VAT. If a "Consultancy" firm claims massive Input VAT refunds — behavior typical of manufacturing or trading — the system flags it. Consultants sell time; they don't buy enough physical goods to generate refundable VAT at that level.
If a KLU indicates a purely domestic business but Coretax detects significant offshore payments (via withheld Article 26 tax), it suggests an undeclared business line, a hidden royalty scheme, or profit shifting.
The DGT has tightened the definition of "Concrete Data" that triggers an audit. If a business receives income implying a different KBLI — such as a "Construction" withholding slip received by a "Trading" company — this is now treated as concrete data of misclassification, justifying an immediate Specific Tax Audit that bypasses the usual inquiry stage.
As companies grow, they naturally pivot. A software development house (Category K) might begin generating significant revenue from ad revenue on a media blog (Category J) or from selling branded merchandise (Trade).
In OSS, this drift is often ignored — the company continues to renew its existing license without adding new KBLI codes. In Coretax, this drift is fatal.
If the new revenue stream has a different VAT treatment or withholding tax obligation than the registered KBLI, the system flags a "VAT Gap." A "Software" company reporting high logistics costs (because they're actually selling merchandise) triggers an anomaly — why would a software consultancy have high freight bills? This flags an audit to investigate potential inflated expenses.
KBLI 2025 introduces specific codes for digital platforms (marketplaces, ride-hailing apps, online health consultations). Many platforms previously registered simply as "IT Companies."
PMK 37/2025 mandates that online marketplace platforms withhold Article 22 Income Tax on income earned by domestic sellers. If a platform remains registered as an IT service provider but operates as a marketplace, it's failing to withhold these taxes.
The nightmare scenario: The DGT calculates the total Gross Merchandise Value (GMV) flowing through the platform and, due to misclassification, assesses it as the company's own revenue rather than just commission. This leads to a massive — albeit factually incorrect — tax bill that the company must fight to disprove in tax court.
KBLI 2025 introduces codes 39001 (Carbon Capture) and 39002 (Carbon Storage). These are the precursors to a Carbon Tax regime. By forcing companies to register under these specific codes, the government identifies the exact population of taxpayers liable for future carbon levies or eligible for carbon credit trading.
A company engaging in carbon storage without the proper code — perhaps hiding it under "General Mining Support Services" — risks being accused of avoiding specific carbon levies. Correctly registering allows participation in the formal carbon credit exchange but also flags the company for immediate scrutiny regarding environmental compliance and carbon accounting.
The June 2026 transition window has closed. Here's what businesses must do:
Review every KBLI code on your NIB. Does it match your revenue reality? Unused codes are liability magnets — remove them.
For each KBLI, determine the DGT's benchmarked profit margin. If your actual margin is significantly lower, prepare a "Defense File" documenting the commercial reasons (market expansion costs, one-off write-downs) before the SP2DK arrives.
Did your code split in 2025? Choose the new code that best reflects your cost structure. If your business has high server costs, choose "Infrastructure" (Category K) rather than "Publishing" (Category J) to justify lower margins and higher depreciation.
Update your "Place of Business" and KLU data in the Coretax portal. Ensure the "Main KLU" represents your dominant revenue stream, not just the legacy business.
The KBLI code has evolved from a static bureaucratic label into a sophisticated fiscal instrument. It acts as the genetic marker that tells the DGT's algorithms what your business should look like. Deviations from this digital expectation — in profit margins, VAT behavior, or cost structures — are now the primary triggers for automated audit.
The selection of a KBLI code must be elevated from a clerical task to a boardroom strategy decision. In the era of Coretax, accuracy is not just a compliance requirement — it's the first line of defense against the algorithmic auditor.
The window to correct the "DNA" of your business is open until June 2026. Ignoring it is a risk no modern enterprise in Indonesia can afford to take.