Activity data reconciliation
How Wrong KBLI Affects Banking and Tax in Indonesia
A KBLI mismatch can make the company's licences, transaction narrative, bank KYC file, tax treatment and invoices describe different businesses.
A wrong KBLI can disrupt much more than the NIB. Banks use the company's legal purpose, OSS activities, contracts, expected counterparties and transaction profile to understand the business, while tax registrations and invoices must reflect the transactions actually carried out. If the deed describes consulting, OSS records wholesale trade and incoming funds look like software subscriptions, the company may face KYC questions, licence gaps, invoice uncertainty and inconsistent regulatory reports. The correction starts with factual activity mapping, not a portal edit: identify what the company sells, to whom, how it delivers, where it operates and which revenue flows exist; classify that activity under current KBLI 2025; check foreign ownership and risk-based licence consequences; amend the deed or AHU data when needed; then update OSS and downstream bank and tax records.
Key takeaways
- Map products, services, customers, delivery methods and revenue before selecting a code.
- Use KBLI 2025 and the official conversion guidance for current classification work.
- Do not change OSS before checking whether the deed and AHU record must change first.
- Notify the bank with a coherent business narrative and supporting contracts after correction.
- Have an Indonesian tax adviser confirm transaction treatment; KBLI alone does not decide every tax result.
Map the mismatch before editing OSS
Connect the real activities, contracts, payments, deed purpose and current licences to the correct KBLI 2025 code.
Where one wrong activity code appears downstream
The same mismatch creates different questions in each system. Record the current value, intended value, evidence owner and correction dependency before changing anything.
Corporate record
Purpose and activities
The deed and AHU data may need amendment when the business purpose changes substantively.
OSS record
KBLI, project and licence
Risk level and activity-specific requirements follow the classified business and location.
Bank file
KYC transaction profile
Banks may ask why customers, payments or contracts differ from the declared activity.
Tax file
Registration and invoices
Transaction facts—not a convenient code—determine the tax analysis and supporting evidence.
Evidence basis: BPS KBLI 2025 and the official conversion guidance · Government Regulation No. 28 of 2025
A code error can be narrow, such as selecting the wrong product scope within a legitimate business purpose, or structural, such as operating a revenue line never authorised in the deed. The correction route differs. Preserve the old record and approval receipts so the company can explain the timeline rather than creating an unexplained overnight change.
The activity analysis should use the current KBLI selection workflow and link each proposed code to contracts, delivery evidence and project locations. Where a bank has already raised questions, answer the factual KYC issue while the legal and OSS correction proceeds; do not submit a new unsupported description merely to match one payment.
Trace the KBLI mismatch through the bank KYC file
A bank evaluates the whole commercial story. A clean NIB cannot overcome contracts and transaction flows that point to a materially different business.
Expected payments differ
A reliable check starts with customer contracts, invoices, website, product descriptions and forecast transaction table. It should resolve whether the onboarding profile predicts local consulting fees but the account receives overseas product payments. Where the records do not reconcile, explain the real model and correct the activity record where necessary; proceeding without that step can mean payments are delayed or enhanced due diligence remains open.
Counterparties look inconsistent
suppliers and customers belong to sectors unrelated to the declared KBLI The evidence that matters is counterparty list, purchase orders and delivery chain. show how each counterparty fits the classified activity or revise the classification If that control is skipped, the bank cannot reconcile the economic purpose of transfers.
Import or merchant tools requested
The warning sign appears when the company seeks facilities unsupported by its current business permissions. Verify it with licence outputs, customs status, marketplace terms and processing agreements. The responsible person should complete the relevant activity and supporting-licence checks first; otherwise, a banking product is refused despite the account remaining open.
Amendment not disclosed
Treat the company changes KBLI but leaves the bank with the old profile as a decision gate, not an administrative detail. Keep new deed or AHU evidence, updated NIB, licences and board-approved business narrative in the transaction file, then submit a coordinated KYC update with effective dates. This reduces the chance that later monitoring treats legitimate payments as unexplained deviations.
Separate tax analysis from the classification shortcut
KBLI helps describe the business but does not replace analysis of the actual supply, parties, place of performance, invoice and payment. Ask what transaction occurred.
Invoice description mismatch
invoices use a service label that is absent from the company's authorised activities The evidence that matters is signed contract, acceptance record, tax invoice data and licence status. align the authorised activity before repeating the transaction If that control is skipped, commercial and tax evidence point to an unlicensed revenue line.
Withholding assumed by code
The warning sign appears when the company applies a tax treatment solely because of its KBLI label. Verify it with transaction terms, recipient status, applicable tax rule and adviser analysis. The responsible person should document the treatment for the specific payment; otherwise, returns and certificates use an unsupported rate or category.
VAT readiness overlooked
Treat a new revenue line changes taxable-supply or invoicing requirements as a decision gate, not an administrative detail. Keep sales forecast, PKP status, invoice process and customer contracts in the transaction file, then confirm the VAT and invoice workflow before billing. This reduces the chance that the company cannot issue compliant documents when the first sale occurs.
Historical period ignored
A reliable check starts with transaction ledger, old licences, returns and effective correction date. It should resolve whether the company corrects the code but never reviews earlier invoices and returns. Where the records do not reconcile, scope a historical review and corrective filings where required; proceeding without that step can mean the legal record improves while past exposure remains unaddressed.
Build the correction dependency list
Identify which AHU, OSS, bank and tax updates must happen first and which can run in parallel.
Run the correction in an order downstream systems can follow
The exact route depends on whether the change is clerical, a KBLI conversion or a substantive change in business purpose. Capture each before-and-after record.
Fact map first
The warning sign appears when teams propose a preferred code before documenting the actual business. Verify it with product and service catalogue, customer types, delivery process, premises and revenue model. The responsible person should approve one factual activity memo; otherwise, the chosen code is optimised for convenience rather than accuracy.
AHU dependency
Treat the new activity is outside the effective purpose stated in the deed as a decision gate, not an administrative detail. Keep notarial review, shareholder approval and AHU submission evidence in the transaction file, then complete the corporate amendment before or with the OSS sequence. This reduces the chance that oSS and corporate records immediately diverge again.
OSS activity update
A reliable check starts with OSS validation, project data, standard certificate or licence and prerequisites. It should resolve whether the correct code creates new risk level, location or supporting-licence requirements. Where the records do not reconcile, finish the activity-level licence path rather than stopping at NIB reissue; proceeding without that step can mean the code appears but the permission to operate is incomplete.
Downstream notification
bank, tax, contracts and accounting retain the old activity description The evidence that matters is institution update receipts, revised templates and effective-date register. assign an owner to each downstream update If that control is skipped, the mismatch survives outside OSS.
Current classification and OSS correction basis
KBLI 2025 and the 2025 licensing framework now form the current starting point. The official transition material protects existing licences in many non-substantive conversions but preserves update duties for substantive changes.
- BPS KBLI 2025 and the official conversion guidance : KBLI 2025 became the national reference in 2026. Existing licences generally remain valid, but a substantive change in business purpose or scope can require alignment through AHU and OSS rather than a cosmetic code substitution.
- Government Regulation No. 28 of 2025 : The current risk-based licensing framework covers basic requirements, business licences, supporting licences, OSS administration, supervision and sanctions; it revoked Government Regulation No. 5 of 2021.
- BKPM Regulation No. 5 of 2025 : The current OSS procedure regulation includes the general PT PMA investment threshold, the IDR 2.5 billion minimum issued and paid-up capital rule, OSS procedures and administrative consequences. Sector-specific exceptions and calculation bases still have to be checked.
- OSS business-data change guide : The official guide distinguishes changes to entity data, location data, addresses, investment plans and business licensing. The correct route depends on the field and the status of the existing licence.
- Official OSS guidance library : The OSS portal publishes current procedural guides for new applications, changes and transition cases. A successful screen or downloaded NIB does not by itself prove that every activity-level requirement is fulfilled.
A bank's KYC decision is institution-specific, and tax treatment depends on the real transaction and current tax law. The regulatory sources support the classification and licensing sequence; they do not guarantee account approval or supply a universal tax answer.
Approve one reconciled business activity record for every system
The approved record should state each product or service, current KBLI 2025 code, deed basis, project location, risk level, licence status, expected customer and supplier types, payment flow and invoice description. Attach the evidence and effective date rather than distributing only a new code number.
Use that record to update AHU, OSS, bank KYC, tax operations, contracts and accounting templates in a controlled sequence. Close the project only after every system either matches or contains a documented, lawful reason for a difference.
Reconcile the downstream records
Turn the approved activity map into a bank, tax, contract and accounting update register.
Frequently asked questions
Can a bank reject payments because the KBLI is wrong?
A bank may question, delay or restrict transactions when the declared activity, counterparties and payments do not reconcile with its KYC profile. The institution decides the outcome; provide factual evidence and correct the underlying record.
Does changing a KBLI automatically change the company's tax treatment?
No. Tax depends on the real transaction and applicable tax rules. A corrected KBLI can improve consistency, but it does not replace analysis of VAT, withholding, invoicing and prior periods.
Must every KBLI 2020 code be replaced manually with KBLI 2025?
Official transition guidance indicates that existing licences generally remain valid and many non-substantive conversions can be handled through the system. A substantive business-purpose or scope change can require AHU and OSS action.
Should the deed be amended before OSS?
If the intended activity falls outside the effective corporate purpose, the notarial and AHU change is usually a dependency. Confirm the exact sequence for the company and preserve both corporate and OSS receipts.
What should be sent to the bank after a KBLI correction?
Provide the effective corporate record, updated NIB and licences, concise business narrative, transaction forecast, material contracts and any other documents requested by the bank. Do not send a code without explaining the commercial model.
