Post-18 June 2026 · OSS-RBA recovery

KBLI 2025 Migration & Emergency OSS-RBA Account Recovery

The deadline to migrate your business profile to the KBLI 2025 structure was 18 June 2026. If you missed it, you may already be feeling it: a blocked OSS-RBA account, a suspended NIB, and director or staff KITAS you suddenly can't renew. CLAN runs an emergency KBLI 2025 audit, migrates your codes correctly, and works to restore your OSS access so your Bali or Indonesia company can operate again.

Recover my OSS account or call +62 853-1365-1587
Emergency OSS recovery
KBLI 2025 audit & migration
Restores KITAS eligibility
Handled in English
Kevin Tan

Written by Kevin Tan , Foreign Client Director

Last updated: 24 June 2026

The June 2026 fallout

The migration of existing companies to the KBLI 2025 structure had a hard deadline of 18 June 2026. It sounded administrative, and plenty of foreign-owned companies — especially smaller, owner-run operations in Bali — treated it as something to deal with later. Now “later” has arrived, and the consequences are concrete: OSS-RBA accounts that won’t let you update data, NIBs flagged or suspended, and KITAS renewals that mysteriously won’t go through.

The reason it bites so hard is that OSS sits at the centre of everything. Your business licences, your tax position and your immigration sponsorship all read from your OSS company profile. Break that profile, and the damage radiates outward.

How one missed migration becomes several problems

How an OSS block compounds
KBLI not migrated by 18 Jun Profile out of date
OSS functions blocked Can't update / license
NIB flagged or suspended Operations at risk
Director / staff KITAS stalls People can't renew

Each unresolved layer makes the next one harder to fix. Recovery is faster the earlier you start.

This is also why a recovery is rarely a single fix. By the time someone notices a blocked account, there are often two or three overlapping causes — a botched migration and a few missed LKPM filings and a licence that lapsed in the confusion. Untangling them in the right order is the actual work.

Our recovery process

  1. OSS & KBLI audit. We pull your full OSS profile, KBLI codes, licences and LKPM history and pinpoint exactly what is causing the block.
  2. Correct the KBLI 2025 mapping. We re-map your activities to the right KBLI 2025 codes — checking that the new codes preserve your foreign-ownership ceiling and don’t create a new risk-level or licensing problem.
  3. Clear the backlog. Outstanding LKPM reports and lapsed licences are brought current, because the system won’t fully release an account while obligations are open.
  4. Lift the suspension. We work through OSS to restore your NIB and normal account functions.
  5. Restore KITAS eligibility. With the company profile healthy again, we line up the affected work and investor KITAS renewals — see Work KITAS and Investor KITAS.

Why act now rather than wait

A suspension is not a stable state — it’s a deteriorating one. While it sits unresolved, more LKPM deadlines pass, more licences edge toward expiry, and any KITAS with a near-term renewal date gets closer to a hard stop that’s far more disruptive to fix. The companies that recover cleanly are the ones that start the audit early. Send us your company details and we’ll tell you what’s wrong and what it takes to put it right.

Related services

KBLI 2025 migration & OSS recovery — frequently asked questions

What was the 18 June 2026 KBLI migration deadline?

It was the hard deadline for existing companies to migrate their OSS business profiles from the older KBLI structure to KBLI 2025. Because codes were split, merged and renumbered, companies had to re-map their activities. Those that didn't migrate — or migrated incorrectly — now face blocked OSS functions.

Why is my OSS-RBA account blocked?

Common causes are a failed or incomplete KBLI 2025 migration, missing or late LKPM reports, or licence and data inconsistencies that the system flags automatically. The block typically stops you from updating data, issuing licences, and — most urgently for foreign-owned firms — renewing KITAS.

Can a blocked OSS account really stop my KITAS renewals?

Yes. Work and investor KITAS rely on a valid, active company profile in OSS. When the NIB is suspended or the company data is inconsistent, immigration and manpower processes that depend on it stall, which is why a KBLI or OSS problem quickly becomes a visa problem for your foreign management and staff.

How do you fix it?

We start with an audit of your OSS profile, KBLI codes, licences and LKPM status to find the exact cause of the block. Then we correct the KBLI 2025 mapping, bring any outstanding reports and licences up to date, and work through OSS to lift the suspension and restore normal functions.

Will changing my KBLI affect my foreign ownership or licences?

It can, which is why this is an audit, not a find-and-replace. Re-mapping to KBLI 2025 has to respect your foreign-ownership ceiling and the risk level of each new code. We check that the migrated codes keep you compliant and don't quietly create a new licensing or ownership problem.

How fast can recovery happen?

It depends on what caused the block and how many issues have stacked up. A single migration error is faster than a case with months of missed LKPM and lapsed licences. We triage urgent cases first — especially where a KITAS renewal is time-critical — and give you a realistic timeline after the audit.

A blocked OSS account doesn't fix itself

Every week a suspension sits unresolved, the knock-on problems — lapsed licences, stalled KITAS, missed reports — compound. Send us your company details and we'll audit your OSS status and map the recovery.

or reach us at +62 853-1365-1587 · clan.qu34@gmail.com