Post-revenue KBLI repair

Wrong KBLI After Revenue Starts: Indonesia Containment and Repair Plan

Contain unsupported activity, map the affected record chain, correct the authoritative sources, and restart only against verified licence evidence.

By Elara Vance Updated August 4, 2026 6-minute read

An Indonesian company that discovers a wrong KBLI after revenue has started should pause the affected activity, preserve the existing records, and open a controlled remediation file before editing OSS. The current risk-based licensing framework in Government Regulation No. 28 of 2025 requires the relevant business licensing for the activity; a later data correction does not automatically validate earlier invoices, contracts, imports, staff assignments, premises use, or customer delivery.

The repair sequence depends on what is wrong: the economic activity may have been described inaccurately, the correct KBLI may be missing, the location may be attached to the wrong project, or the selected code may trigger different ownership and licence conditions. Management should separate future containment from historical review, identify which authoritative record must change first, and approve a documented restart gate instead of treating a successful portal edit as the end of the incident.

Post-revenue incident triage

The first review should show which activity occurred, where it occurred, which records relied on the old code, and what evidence is required before it resumes.

Exposure	Immediate control	Repair evidence
Sales and invoices	Flag affected transactions and stop new commitments	Contract, invoice, delivery, and tax mapping
OSS and licences	Preserve current outputs before editing	Correct activity, location, risk, and licence status
Corporate records	Compare deed purpose and approvals	Notarial or internal approval path, if required
Tax and accounting	Tag historical entries without deleting them	Ledger, invoice, withholding, VAT, and filing treatment
Bank and counterparties	Identify representations based on the old activity	Updated KYC pack and controlled notification

Scope the post-revenue KBLI repair before acting

Share the actual activity, current KBLI, locations, licence outputs, and first affected transaction so the containment boundary can be defined.

Key takeaways

Contain the affected activity before changing data, because future exposure and historical exposure require different decisions.
Preserve downloads, screenshots, contracts, invoices, and ledger entries so the original state remains reviewable.
Use KBLI 2025 and its official correspondence tools, but classify the real activity rather than choosing the closest label.
A corrected OSS record does not erase earlier licence, tax, contractual, or premises questions.
Restart only when the required licence state and dependent records are evidenced and approved by named owners.

Contain the unsupported activity without destroying evidence

Containment should stop new exposure while keeping the historical record intact. Freeze new quotations, orders, invoices, imports, deliveries, and staff assignments only for the affected activity, then record the time and person who authorized the pause.

Deleting portal screenshots, rewriting invoice descriptions, or backdating approvals makes the repair harder to defend. The incident file should preserve what management knew, which document was relied on, and how the mismatch was discovered.

For contain the unsupported activity without destroying evidence, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect name the affected products, services, customers, and locations. with download current ahu, oss, nib, licence, and tax records., then show how lock relevant contracts, invoices, bank entries, and filings against alteration. and assign legal, licensing, tax, finance, and commercial owners. affect the next approval. Record the source for name the affected products, services, customers, and locations., the reviewer of download current ahu, oss, nib, licence, and tax records., the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Decision rule

Approve a narrow containment boundary that protects customers and operations without unnecessarily stopping unrelated licensed activities.

Name the affected products, services, customers, and locations.
Download current AHU, OSS, NIB, licence, and tax records.
Lock relevant contracts, invoices, bank entries, and filings against alteration.
Assign legal, licensing, tax, finance, and commercial owners.

Use the pre-operation sequence in the KBLI correction workflow as a reference, but add a separate historical-transaction workstream because revenue has already started.

Reclassify the real activity under KBLI 2025

The company should describe what it actually sells, who receives it, how it is delivered, which assets and staff perform it, and where performance occurs before choosing a replacement code. The BPS KBLI 2020–2025 conversion table supports correspondence review but does not replace this factual classification.

A code selected only from a familiar title may omit manufacturing, warehousing, distribution, platform, installation, or regulated professional elements. Each material revenue stream should be tested against the current official description and OSS scope.

For reclassify the real activity under kbli 2025, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect write a product-and-service catalogue in operational language. with map customers, delivery methods, assets, personnel, and project locations., then show how check kbli 2025 descriptions and any 2020–2025 correspondence. and record rejected alternatives and the reason they do not fit. affect the next approval. Record the source for write a product-and-service catalogue in operational language., the reviewer of map customers, delivery methods, assets, personnel, and project locations., the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Evidence rule

Adopt a written classification memo only when the activity narrative and the selected KBLI describe the same commercial reality.

Write a product-and-service catalogue in operational language.
Map customers, delivery methods, assets, personnel, and project locations.
Check KBLI 2025 descriptions and any 2020–2025 correspondence.
Record rejected alternatives and the reason they do not fit.

Compare the proposed code with the PT PMA KBLI selection framework before it is approved for filing.

Test the post-revenue KBLI repair evidence

Reconcile the proposed code with AHU, OSS, tax, contracts, invoices, banking, and premises before filing corrections.

Map the affected corporate, licence, and ownership chain

The repair team should test the new code against the deed purpose, shareholder approvals, foreign-ownership conditions, investment plan, OSS project, risk level, premises, and sector approvals. One mismatch can require several coordinated actions, while another may be correctable within OSS without a deed amendment.

The sequence matters because downstream records can inherit data from an authoritative source. Editing a dependent record first can produce temporary inconsistencies that affect licensing verification, tax administration, bank KYC, or customer due diligence.

For map the affected corporate, licence, and ownership chain, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect compare the deed purpose and current ahu profile with the new activity. with screen foreign-ownership and investment conditions for the new code., then show how identify the oss risk level, licence product, and verification state. and list tax, bank, customs, premises, employment, and contract dependencies. affect the next approval. Record the source for compare the deed purpose and current ahu profile with the new activity., the reviewer of screen foreign-ownership and investment conditions for the new code., the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Control point

Do not file until a responsibility matrix identifies the authoritative source, dependent records, filing owner, and acceptance evidence for every changed field.

Compare the deed purpose and current AHU profile with the new activity.
Screen foreign-ownership and investment conditions for the new code.
Identify the OSS risk level, licence product, and verification state.
List tax, bank, customs, premises, employment, and contract dependencies.

Use the foreign-ownership screening process where the replacement code changes the ownership analysis.

Regulatory Notes and Limitations

Wrong KBLI After Revenue Starts: Indonesia Containment and Repair Plan provides a decision and evidence framework, not a universal legal opinion. Review the current official output and company-specific facts before filing, contracting, paying, or operating.

For Wrong KBLI After Revenue Starts: Indonesia Containment and Repair Plan, kBLI classification describes economic activity; it does not by itself prove foreign-ownership eligibility, premises suitability, or completion of every licence condition.
For Wrong KBLI After Revenue Starts: Indonesia Containment and Repair Plan, kBLI 2025 and the official 2020–2025 correspondence table must be reviewed against the actual product, service, customer, delivery model, and location.
For Wrong KBLI After Revenue Starts: Indonesia Containment and Repair Plan, changing an activity can affect investment, licensing, tax, customs, employment, environmental, building, and bank records, so each function should confirm its own field.

Official References and Review Basis

Primary materials for Wrong KBLI After Revenue Starts: Indonesia Containment and Repair Plan were checked on August 4, 2026 and support this page's framework; they do not replace a matter-specific legal, tax, licensing, accounting, security, premises, or bank review of Wrong KBLI After Revenue Starts: Indonesia Containment and Repair Plan.

Government Regulation No. 28 of 2025 : Current risk-based business licensing framework; it revoked Government Regulation No. 5 of 2021.
Ministry of Investment and Downstream Industry/BKPM Regulation No. 5 of 2025 : Current OSS procedures, investment facilities, supervision, and reporting framework.
Online Single Submission portal : Official NIB, four-level risk classification, business licensing, KBLI, and support portal.
BPS KBLI 2020–2025 conversion table : Official correspondence table for reviewing changes between KBLI 2020 and KBLI 2025.
Presidential Regulation No. 10 of 2021 : Investment business-field framework, as amended.
Presidential Regulation No. 49 of 2021 : Current amendment to the investment business-field framework.

Review historical transactions by risk and period

Historical review should group transactions by activity, location, period, value, customer exposure, licence dependency, and tax treatment. The purpose is not to assume every prior transaction is invalid; it is to identify which facts require advice, correction, disclosure, or additional evidence.

A sample may be inadequate when the same unsupported activity appears across many months or locations. Finance should reconcile the population to revenue accounts and bank receipts, while legal and tax owners assess the consequences within their mandates.

For review historical transactions by risk and period, a defensible review separates facts already evidenced, facts requested but not received, assumptions approved for planning, and conditions that still block release. It should connect extract the full invoice and credit-note population for the affected stream. with tie invoices to contracts, delivery evidence, ledger entries, and receipts., then show how separate open, completed, cancelled, refunded, and disputed transactions. and record advice, correction, notification, and retention decisions by period. affect the next approval. Record the source for extract the full invoice and credit-note population for the affected stream., the reviewer of tie invoices to contracts, delivery evidence, ledger entries, and receipts., the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Release test

Escalate any transaction involving safety, regulated products, customs, public customers, material tax positions, or explicit licence warranties before deciding the remedy.

Extract the full invoice and credit-note population for the affected stream.
Tie invoices to contracts, delivery evidence, ledger entries, and receipts.
Separate open, completed, cancelled, refunded, and disputed transactions.
Record advice, correction, notification, and retention decisions by period.

Maintain an exception register so unresolved historical items cannot be hidden by the corrected future workflow.

Correct records in sequence and approve a controlled restart

The company should execute the approved order of corporate, OSS, licence, tax, bank, and counterparty updates, retaining the submission and acceptance evidence for each step. The current BKPM Regulation No. 5 of 2025 is the central OSS procedure reference, but the specific route still depends on the company and activity.

A restart gate should verify the effective licence state, location, operating conditions, invoicing setup, contract wording, tax mapping, bank profile, and staff instructions. A portal status alone is insufficient if a required verification or supporting approval remains incomplete.

For correct records in sequence and approve a controlled restart, the practical deliverable is a version-controlled decision row that remains usable when the activity, location, counterparty, or responsible person changes. It should connect capture before-and-after authoritative records and filing receipts. with reconcile the final activity, address, capital, and ownership fields., then show how update transaction templates, chart-of-account mapping, and control owners. and obtain written restart approval and schedule a post-restart sample review. affect the next approval. Record the source for capture before-and-after authoritative records and filing receipts., the reviewer of reconcile the final activity, address, capital, and ownership fields., the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Stop condition

Release the activity only when every mandatory dependency is effective or a responsible adviser has documented why it is not required.

Capture before-and-after authoritative records and filing receipts.
Reconcile the final activity, address, capital, and ownership fields.
Update transaction templates, chart-of-account mapping, and control owners.
Obtain written restart approval and schedule a post-restart sample review.

Connect the repaired licence state to a recurring licence-condition tracker so the same mismatch does not return.

Place the wrong kbli after revenue starts: indonesia containment and repair plan decision inside HSJGlobal’s Indonesia company registration scope before executing documents, filings, or funding.

Restart the affected revenue stream only from a reconciled licence file

The repair is complete when the real activity, current KBLI, corporate authority, ownership position, OSS licence state, tax treatment, premises, bank record, contracts, and operating instructions tell the same story. A successful edit without that reconciliation leaves the business exposed.

Keep historical exceptions separate from future controls, approve the remediation sequence before filing, and retain evidence for each acceptance point. That gives management a defensible basis to resume the affected activity.

Turn the post-revenue KBLI repair into an approved next step

Build a sequenced remediation file with owners, acceptance evidence, historical exceptions, and a controlled operating restart.

Frequently asked questions

Should the company stop all operations after finding a wrong KBLI?

Not automatically. Define the affected activity, location, and licence dependency first. Pause the unsupported stream and any directly dependent transaction while preserving unrelated activities that remain properly authorized.

Does changing the KBLI in OSS legalize earlier invoices?

No automatic rule makes a later portal correction validate earlier conduct. Historical contracts, invoices, licences, tax, customs, and representations should be reviewed on their own facts.

Must the deed always be amended before OSS?

Not always. Compare the existing corporate purpose and AHU record with the replacement activity. The required sequence depends on whether the authoritative corporate record must change.

Which KBLI version should be checked in 2026?

Use the current KBLI 2025 materials and the official BPS 2020–2025 correspondence table where legacy records are involved, then confirm the implementation shown in OSS for the activity.

What evidence supports a restart decision?

Keep the corrected authoritative records, effective licence outputs, required verifications, tax and invoicing mapping, contract updates, staff instructions, exception log, and written approval by responsible owners.