KBLI 2025: moving from 55193 to 55203

A KBLI number can change without the business changing. Conversely, the business can change while the recorded KBLI remains the same or was never correct.

Those are not the same problem. Treating them as one can turn a harmless administrative conversion into an expensive deed amendment. It can also leave a real operating mismatch hidden behind a new number.

What changes

KBLI 2025 is now Indonesia's official business classification. Where the business activity has not substantively changed, official transition guidance says the systems will convert the numerical code automatically and existing licences that were issued, verified or approved remain valid. If a corporate action changes the company's purposes, objectives or business activity, a deed or AHU adjustment may be required. Verify the live OSS and AHU records rather than assuming every record has already converted.

But that protection is narrower than it sounds. It does not prove that the old code described what the company really did. It does not approve a new activity. And it does not remove the other approvals attached to the project, location or operating model.

Before anyone changes a deed or clicks through OSS, classify the company into one of three lanes.

Lane	What happened	Correct first response
Code-only conversion	The number changed; purpose, customers, operator, contracts and revenue model did not.	Verify the official mapping, compare the new definition with the facts, save the conversion evidence and reconcile records.
Substantive change	The company is adding a service, serving a different customer, operating at a new location, or changing who owns/operates the asset.	Treat it as a new or amended business activity. Review deed, OSS, risk-based licences, investment eligibility and reporting before operating.
Legacy mismatch	The old code was never a faithful description of the actual business.	Do not call it "automatic migration". Build a remediation plan with counsel, the notary, OSS/licensing support and a qualified Indonesian tax adviser.

The villa example: 55193 becomes 55203

The official BPS conversion table maps KBLI 2020 code 55193, Vila, to KBLI 2025 code 55203, Aktivitas Vila on a one-to-one basis.

For a company whose real business remains the operation of villa accommodation for short tourist stays, that may be a straightforward code conversion. The word "may" matters. The classification still has to be checked against the company's deed, licences, location, contracts and actual flow of money.

Now compare that with a different fact pattern: the company does not operate accommodation it owns or controls for its own account. Instead, it manages villas belonging to several third-party owners, makes daily operating decisions and earns a management fee. KBLI 2025 contains a separate description, 55901, for management of accommodation belonging to another party.

This distinction answers one of the most common questions in Bali:

Operating one's own villa activity is not automatically the same business as
managing accommodation for someone else.

Do not select 55203 or 55901 from those two sentences alone. Ownership/control, contracts, who employs the team, who bears operating risk, who invoices the guest and who receives guest money can change the analysis. Those facts need to be tested against the official descriptions and live OSS requirements.

What an automatic conversion does and does not establish

Automatic conversion is an administrative bridge between classifications. It can avoid unnecessary relicensing when the substance has not changed.

It is not a compliance certificate.

An automatic result does not, by itself, establish that:

the activity is open to the foreign investment structure being used;
a new location or new project is covered;
spatial, environmental, building or tourism requirements have been met;
the company named in OSS is the party that operates the activity and contracts with the guest for payment and refunds;
historic LKPM reporting used the right activity and location;
the company's deed, contracts, invoices and financial records all describe the same business.

This is the part owners often miss. The government can preserve an existing licence through a classification transition without blessing every historic fact behind it.

The seven-step migration protocol

1. Freeze the evidence before changing anything

Export or save dated copies of:

the latest deed and Ministry approval/receipt in AHU;
NIB and every business licence, certificate or standard in OSS;
the list of KBLI codes, projects and business locations;
prior LKPM submissions and their statuses;
contracts, invoices and bank-flow evidence showing who really operates and earns the revenue.

Do this before a notary or administrator edits the record. You need a before-and-after trail.

2. Use the official BPS conversion table

Start with the official mapping, not a blog post or a screenshot circulating in a WhatsApp group. Record whether it is one-to-one, one-to-many or another conversion scenario.

The mapping answers: "What new code corresponds to the old classification?" It does not answer: "Was the old classification correct for us?"

3. Write the activity in plain language

One paragraph is enough:

Illustrative example only: The company operates one two-bedroom villa in Canggu for short tourist stays. It signs the guest contract, invoices the guest, engages the on-site team, receives the booking revenue and bears refund and vacancy risk.

If the management team cannot agree on that paragraph, it is too early to select a KBLI.

4. Compare facts with the new definition

Check the official description line by line. Focus on verbs: own, operate, manage, rent, develop, sell, consult. Then focus on whose asset and whose customer are involved.

5. Assign the lane

Same facts and faithful one-to-one definition: likely code-only conversion.
New facts or a different service: substantive change.
Facts never matched the old code: legacy mismatch.

Do not let the portal's proposed mapping decide this factual question for you.

6. Coordinate the records

Where the change is code-only, confirm that OSS and AHU converted consistently and retain the proof. Where it is substantive, counsel and the notary should establish the order of deed, AHU, OSS and project-licence changes. The sequence matters because one system may rely on data from another.

7. Reconcile compliance reporting

Update the internal activity-location register and ensure future LKPM reporting uses the correct activity, project, location and phase. A classification cleanup should not create a discontinuity or double count the same investment realisation.

A normal case and a failure case

Normal case. A company has always operated one villa accommodation activity at the same location, under its own guest contracts and revenue account. The official table maps 55193 to 55203. The new description still matches the facts. The company documents the conversion, confirms consistency across AHU and OSS and continues the appropriate project-level compliance.

Failure case. A company historically used 55193 but earns fees for managing multiple villas owned and contracted by other parties. Its administrator accepts 55203 because OSS proposes it automatically. The number is newer; the mismatch is not fixed. A later licence, tax or counterparty review still sees contracts and cash flows that describe a different activity.

Questions to take into the review meeting

Is this only an official code conversion, or are our facts changing?
Does our recorded purpose in the deed cover the activity in plain language?
Who operates the activity, signs the guest contract, employs the team and is responsible for payment and refunds?
Are we operating our own accommodation activity or managing someone else's?
Is the activity available to our foreign-investment structure and business scale today?
Which requirements attach to each project and location?
Do OSS, AHU, contracts, tax records and LKPM now tell the same story?

The decision to avoid

Do not amend the company merely because a new number appeared. And do not rely on automatic conversion merely because changing the company feels difficult.

The safe objective is not "obtain the newest KBLI". It is make the legal record, licences, actual operation and reporting describe the same business.

Official sources

BPS Regulation No. 7 of 2025; BPS transition statement, 30 April 2026; BPS tourism clarification, 14 July 2026; official conversion table; official OSS conversion guide; OSS classifications 55203 and 55901.

This article provides general educational information, not legal, licensing or tax advice. The correct treatment depends on the company's deed, licences, activity, location, investment structure and current OSS record.