Has your NIB application stalled because the business codes in your deed do not match your OSS profile? A KBLI 2025 mismatch is one of the most frequent reasons incorporation files get stuck in Indonesia.
In this article, we explain how these code conflicts arise and the risks they create for licensing and tax. We also map the exact steps to align KBLI with your deed, OSS profile, and NIB in 2026.
What Is a KBLI Code Misalignment Between the Deed, OSS, and NIB?
For a PT, a KBLI mismatch arises where a main activity in OSS is not covered by the deed; a non-income-generating supporting activity need not appear in the deed.
KBLI stands for Klasifikasi Baku Lapangan Usaha Indonesia, the national standard classification of business fields. It is maintained by Statistics Indonesia (BPS), and each five-digit code describes one specific line of business. As of 2026, OSS validates entries against the KBLI 2025 edition published by BPS. This edition is the classification now referenced when companies register or update their business activities.
For a PT, main business activities are reflected in the deed, OSS data, and NIB; a non-income-generating supporting activity may appear only in OSS under the exception described above. First, the notarial deed of establishment lists them under the business purpose clause, known locally as Maksud dan Tujuan. Second, the company selects them in its business profile on the Online Single Submission (OSS) platform. Third, the resulting Nomor Induk Berusaha (NIB), the business identification number, reflects whatever OSS has on file.
The records should align for main activities and income-generating supporting activities. The problem often surfaces at the worst moment: during NIB issuance, licence renewal, a bank onboarding check, or a tax review. At that point, fixing it is far harder than preventing it during incorporation.
Why Do KBLI Codes Fall Out of Alignment?
Most code conflicts are not deliberate. They come from ordinary drafting habits, system updates, and business growth that outpaces paperwork. Understanding the cause matters, because each cause points to a different fix.
In practice, we see four recurring patterns behind misaligned business codes across client files.
1. The Deed Was Drafted with Outdated Codes
Some deeds still carry KBLI 2020 codes because the template was reused from an earlier file. When the OSS platform validates the entry against the current edition, the code either fails or maps to a different activity. This is the most common defect we encounter in deeds prepared without a compliance review.
2. OSS Was Updated Without a Deed Amendment
Founders sometimes add new KBLI codes directly in OSS because the portal allows the edit. For a limited company (PT), the deed is the legal foundation of the business scope. A new main activity or income-generating supporting activity must be reflected in the deed; the non-income-generating exception explained above still applies.
3. The Business Outgrew Its Registered Codes
Companies evolve. A trading company may add consulting services, or a manufacturer may start importing its own raw materials. A new main activity, or a supporting activity that generates income or profit, must be covered by the deed and registered in OSS; the non-income-generating exception explained above still applies.
4. Main and Supporting Codes Were Confused
OSS requires one primary code (KBLI utama) and allows several supporting codes (KBLI pendukung). Risk is assessed for each business activity; classifying an activity as main or supporting affects the applicable OSS requirements but does not itself change that activity’s risk level. High-risk classifications trigger additional verification and can delay the NIB.
Common KBLI 2025 Mismatch Types and Their Consequences
| Mismatch Type | Where It Shows Up | Typical Consequence |
|---|---|---|
| Deed lists older codes, OSS uses KBLI 2025 | Deed vs OSS profile | OSS validation fails and NIB issuance stalls |
| Codes added in OSS without a deed amendment | OSS profile vs deed | Licence applications rejected and compliance flags raised |
| Actual activity beyond registered codes | Operations vs all records | Fines, invoicing disputes, and tax reassessment risk |
| Main and supporting codes swapped | OSS profile and NIB | Wrong risk classification triggers extra verification |
What Are the Consequences of a KBLI OSS NIB Mismatch?
A KBLI OSS NIB mismatch can delay licence issuance and NIB approval. Where the activity is licensed or high-risk, regulators may require correction before further permits are issued. Tax exposure depends on whether actual invoicing matches the registered scope.
The consequences depend on where the defect is discovered and on the specific licensing requirements that apply to the activity. OSS validates codes electronically, so mismatches often stop a file before it starts. Others stay hidden until a regulator, bank, or client inspects the records.
The practical fallout usually takes one of the following forms:
- NIB applications can be rejected or suspended where OSS validation finds the codes do not match.
- Sector licences tied to high-risk KBLI codes may be blocked until the deed and OSS profile are aligned.
- Banks and tender committees can reject documents because the deed scope does not match the NIB.
- Tax invoices and filings may be questioned when actual activities differ from registered ones. This risk rises during a review by the Directorate General of Taxes.
- Regulators may treat unregistered activities as operating outside the licensed scope. This applies only where the activity requires its own licence or approval.
The pathway out of each defect depends on which record is driving the mismatch, as the alignment steps in the next section show.
How Do You Align KBLI with Your Deed Step by Step?
To align KBLI, first determine whether each activity is main or supporting; amend the deed before adding a main or income-generating supporting activity. Non-income-generating supporting activities may still be added in OSS under the exception explained above.
The sequence matters. Many companies make the mistake of editing OSS first, which deepens the inconsistency. For a PT, OSS draws main-activity data from the legal-administration system; the non-income-generating exception explained above still applies.
Follow the five steps below in order.
Step 1: Audit Codes Across All Three Documents
Pull the deed, the OSS-RBA business profile, and the NIB side by side. List every KBLI code on each record and mark every difference. This audit takes only a day or two and defines the entire work plan.
Step 2: Verify Each Code Against KBLI 2025 and Its Risk Level
Verify each intended activity in the OSS KBLI directory and against BPS's KBLI 2025 publication. BPS released KBLI 2025 on 24 December 2025 and revised it on 13 January 2026, while the current OSS directory displays KBLI 2025. Note each activity's risk rating in OSS, because codes classified as high risk (risiko tinggi) require extra verification.
Step 3: Amend the Deed Before Touching OSS
Engage a notary to amend the business purpose clause so it covers the corrected codes. AHU treats changes to Maksud dan Tujuan serta Kegiatan as amendments requiring Ministerial approval. The two to four week period in this guide is an indicative planning estimate, not a statutory processing deadline, and may vary with deed readiness and AHU or OSS processing. Clients budgeting the government fees involved in company setup should also reserve funds for later deed amendments, since notary and filing costs apply each time.
Step 4: Update the OSS-RBA Profile and Confirm the NIB
Once the approved amendment is in hand, update the business profile in OSS. Verify that the NIB reflects the corrected codes, not merely that the submission was accepted. A quick check of the licence details on the NIB document closes the loop.
Step 5: Synchronise Tax and Banking Registrations
Tax and bank records should match the corrected scope. Companies preparing the latest DGT forms should ensure activity descriptions align with the amended deed. Our guide to the tax registration sequence that follows incorporation explains how NPWP, PKP, and Coretax accounts connect to your registered activities.
Aligning KBLI with the Deed: Steps, Actors, and Typical Timing
| Step | Who Acts | Typical Timing |
|---|---|---|
| Audit codes across deed, OSS, and NIB | Company or service provider | 1 to 3 days |
| Verify codes and risk levels in KBLI 2025 | Company, using OSS and BPS references | 1 to 2 days |
| Notarial deed amendment and AHU approval | Notary and Ministry of Law and Human Rights | 2 to 4 weeks |
| OSS-RBA profile update | Company via the OSS portal | 1 to 5 days |
| Synchronise NPWP, PKP, and bank records | Company, tax office, and banks | 1 to 2 weeks |
Where KBLI Codes Appear Across Corporate Records
| Record | What It Contains | Controlling Authority |
|---|---|---|
| Deed of establishment | Business purpose clause with KBLI codes | Notary and Ministry of Law and Human Rights |
| OSS-RBA business profile | Registered codes and risk ratings | OSS system under the investment authority |
| NIB | Licence summary reflecting OSS registration | OSS system |
| NPWP and PKP registrations | Activities assumed for tax filing and invoicing | Directorate General of Taxes (DJP) |
Which Document Takes Legal Precedence When Codes Conflict?
For most PT and PT PMA matters, the notarial deed takes precedence for the authorised business scope. OSS and the NIB are administrative records that must accurately reflect the deed, while sector-specific licensing rules may require separate activity codes to be reflected first.
For a PT, whether local or foreign-owned (PT PMA), the deed of establishment is the constitutional document. It defines the company's purpose, and every licence, registration, and tax profile derives from it. When OSS and the deed disagree on the authorised business scope, regulators generally look to the deed unless a sector-specific licence requires separate activity codes to be reflected first.
This is why editing OSS first before amending the deed is generally the wrong move for a PT or PT PMA. The platform may accept the change, but the record then lacks a legal foundation. The safe order is generally deed, then OSS, then everything downstream, including the tax registrations administered by the Directorate General of Taxes (DJP).
Companies that lack in-house compliance staff often outsource this work. Knowing how to choose the right partner for compliance support is worth the effort, because a careless provider can introduce new inconsistencies while fixing old ones.
Conclusion
A KBLI 2025 mismatch is usually cheaper to fix early. The correction sequence is simple once it is mapped: deed first, OSS second, then the NIB and tax registrations. The discipline lies in auditing all three records before making any change. Avoid letting the OSS profile drift from the deed.
We help clients:
- Audit their KBLI codes
- Coordinate notarial deed amendments with the AHU approval process
- Update OSS-RBA profiles
- Verify that the NIB and tax registrations match
Our corporate secretarial and tax teams work as one. A single corrected record set then flows through every registration your company holds.
If your incorporation file is stalled or your records no longer match your actual business, contact 3E Accounting Indonesia. Use our contact page and we will review your deed, OSS, and NIB records together.
Get Your KBLI Codes Aligned the Right Way
Our team reviews your deed, OSS profile, and NIB, then manages the amendment and update process end to end so your registrations match your real business.
Frequently Asked Questions
A non-income-generating supporting activity may be added in OSS without amending the deed. However, a new main activity or an income-generating supporting activity requires a notarial deed amendment and AHU approval before the OSS profile is updated.
A company selects one primary code (KBLI utama) and may add several supporting codes (KBLI pendukung). Main activities and income-generating supporting activities must fall within the business scope stated in the deed, while the non-income-generating exception described earlier applies.
Yes, indirectly. Tax registrations assume the activities recorded in OSS and the deed. If actual operations differ, tax filings and VAT invoices can come under question during a review by the Directorate General of Taxes.
Typically three to six weeks, depending on document readiness, the amendment type, the business activity, and the relevant licensing requirements. This is an indicative planning estimate rather than a statutory deadline. The notarial deed amendment and AHU approval often take about two to four weeks, and the OSS update, NIB confirmation, and tax synchronisation usually follow within days.
There is no general migration obligation requiring existing companies to restate every code solely because KBLI 2025 was published. However, when an existing company updates its OSS profile or applies for a new licence, OSS validates entries against the classification currently in force, so codes should be verified against KBLI 2025 before those events.
Abigail Yu
Director
Abigail Yu oversees executive leadership at 3E Accounting Group, leading operations, IT solutions, public relations, and digital marketing to drive business success. She holds an honors degree in Communication and New Media from the National University of Singapore and is highly skilled in crisis management, financial communication, and corporate communications.








