OSS record integrity
Indonesia OSS Project and Location Mismatch Recovery for Foreign Firms
A live NIB can coexist with conflicting AHU, shareholder, address, KBLI, investment, licence and responsible-person data that blocks later approvals.
An OSS data mismatch is material when the live business record no longer matches the effective legal entity, actual activity, project location, investment plan or responsible person. Foreign firms often discover the problem during a bank KYC refresh, licence verification, LKPM filing, tax update, director change or foreign-worker application—even though the NIB still downloads successfully. Do not overwrite fields until the controlling source is identified. Preserve the current OSS output, latest deed and AHU profile, shareholder register, address evidence, KBLI map, project and investment data, activity-level licences, tax record and institutional profiles. Classify each difference as a display issue, clerical correction, corporate amendment, activity change, location change or licence-impacting update. Then correct it in dependency order and save before-and-after evidence, because a quick portal fix can unintentionally reopen or invalidate a connected approval.
Key takeaways
- Export and preserve the current state before any correction.
- Identify the controlling record for each field instead of treating OSS as the source of every fact.
- Separate clerical fixes from substantive corporate, activity and location changes.
- Assess licence consequences before changing KBLI, project or address data.
- Reconcile bank, tax, manpower and contract records after the official correction.
Mismatch triage by controlling source
Assign every field to the record that legally or operationally controls it. The same visible error may require a different correction route depending on its origin.
Entity data
Deed and AHU first
Names, shareholders, directors and purpose may depend on an effective corporate change.
Activity data
KBLI and real operations
A code change can alter risk level, licences, investment plan and foreign ownership analysis.
Location data
Exact project and premises
Address, land area and spatial or building dependencies must stay connected.
Downstream data
Bank, tax and manpower
Correct OSS does not automatically update every institution that used the old record.
Evidence basis: Government Regulation No. 28 of 2025 · BKPM Regulation No. 5 of 2025
Triage the OSS mismatches
Classify entity, activity, location and investment differences by controlling source and licence impact.
Mismatches commonly arise when a notarial amendment, portal update and operational change happen on different dates. They also arise from provider handovers that omit filed project data. A correction log should therefore record the old value, correct value, legal basis, effective date, portal route, connected approvals and downstream recipients.
Control of the account is a prerequisite. Use the OSS handover controls to verify authorised users, recovery channels and the live project list before instructing a change. Otherwise, a technically correct amendment can be lost behind a provider-controlled login or duplicated in another project record.
Classify each mismatch before touching the portal
A field-level register prevents unrelated corrections from being bundled into one risky submission. Resolve the source and consequence first.
Corporate identity mismatch
The warning sign appears when name, shareholder, director or purpose differs from the latest effective AHU record. Verify it with executed deed, AHU approval or receipt, effective date and shareholder register. The responsible person should complete or verify the corporate change before OSS correction; otherwise, oSS is made consistent with a draft rather than the legal entity.
Activity mismatch
Treat the KBLI or scope does not describe products, services or revenue actually delivered as a decision gate, not an administrative detail. Keep business model, contracts, KBLI 2025 source and activity licence matrix in the transaction file, then approve the correct classification and its licence impact. This reduces the chance that the company fixes a code while leaving the operation unlicensed.
Location mismatch
A reliable check starts with lease, parcel, map, building evidence and OSS project identifier. It should resolve whether registered office, project address, land area or postal code points to the wrong place. Where the records do not reconcile, choose the official address or location change route; proceeding without that step can mean licence prerequisites attach to the wrong site.
Investment mismatch
project investment values do not reconcile with the approved budget and activity basis The evidence that matters is BKPM calculation, asset and working-capital plan and project list. recalculate before changing the OSS figures If that control is skipped, the update creates another reporting inconsistency.
Protect connected licences while correcting OSS data
The NIB is not the only output. Review each activity's risk level, standard certificate, licence, prerequisite and supporting approval before submission.
Verified certificate at risk
Treat a KBLI or location change may affect a previously verified standard certificate as a decision gate, not an administrative detail. Keep live licence status, issuing authority and change consequence analysis in the transaction file, then obtain a written plan for preservation or re-verification. This reduces the chance that the company loses operational status unexpectedly.
Basic requirement changes
A reliable check starts with KKPR or spatial evidence, environmental route and site data. It should resolve whether the new project location has different spatial or environmental dependencies. Where the records do not reconcile, complete the applicable prerequisite in sequence; proceeding without that step can mean the portal update stalls at a location gate.
Supporting licence omitted
a PB UMKU remains tied to an old activity, product or address The evidence that matters is supporting-licence inventory and identifiers. confirm whether amendment or new application is required If that control is skipped, the core activity updates while the supporting permission stays stale.
Transition path ignored
The warning sign appears when legacy or KBLI 2020 data is changed without checking current conversion guidance. Verify it with BPS conversion table, OSS transition notice and existing licence status. The responsible person should use the current transition route and preserve valid licences; otherwise, a non-substantive conversion is treated as a new uncontrolled project.
Protect the connected approvals
Map each proposed change to standard certificates, licences, prerequisites and supporting permissions.
Close downstream gaps after the OSS correction
Portal completion is the midpoint. Institutions that relied on old information need a dated, evidence-based update.
Bank profile remains old
A reliable check starts with updated NIB, licences, AHU record and business narrative. It should resolve whether kYC still shows the previous activity, director or address. Where the records do not reconcile, submit the bank's required change pack; proceeding without that step can mean legitimate transactions trigger avoidable monitoring questions.
Tax data remains old
tax registration, invoices or authorised users reflect prior facts The evidence that matters is tax profile, invoice templates, authority records and effective date. coordinate tax and invoice changes with an adviser If that control is skipped, new and old periods are documented inconsistently.
Foreign-worker file differs
The warning sign appears when rPTKA or immigration sponsorship uses a previous address, activity or responsible person. Verify it with current approvals, work location and sponsor records. The responsible person should assess and file required amendments before deployment; otherwise, personal approvals rely on stale company data.
Contracts not updated
Treat counterparties receive documents that conflict with active corporate or OSS data as a decision gate, not an administrative detail. Keep template register, material contracts and compliance representations in the transaction file, then update representations and notify where required. This reduces the chance that the company breaches warranties or fails diligence.
Current OSS change and KBLI transition sources
The 2025 risk-based framework, BKPM procedure regulation, official OSS change guides and KBLI 2025 transition materials should be read together for current corrections.
- 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.
- 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.
- 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.
The OSS interface and available change route depend on the entity, field, licence status and transition history. Preserve screenshots and submission identifiers and obtain authority or professional guidance when a change could affect a verified licence or existing operation.
Close the mismatch only when every dependent record is evidenced
The closure certificate should list each field, controlling source, old and new value, effective date, OSS receipt, affected licences and downstream update evidence. A clean NIB without the connected records is not sufficient closure.
Keep unresolved differences visible with an owner and deadline. Do not mark them immaterial merely because the portal accepts a submission; assess how the difference affects the company's authority, permission to operate and institutional representations.
Close every downstream gap
Reconcile bank, tax, manpower and contract records after the official OSS update.
Frequently asked questions
Can an NIB remain valid when OSS data is wrong?
A downloadable NIB may still exist while individual fields or connected activity licences are inconsistent. Verify the live business profile and each activity's status rather than relying on the PDF alone.
Should OSS be changed before the deed?
If the field depends on a corporate amendment, complete and verify the required deed and AHU process first or use the coordinated route advised for that change. Do not update OSS to a future or draft fact.
Will an OSS correction automatically update the bank and tax office?
Do not assume so. Each institution has its own data and update process. Submit the relevant evidence and retain its acceptance receipt.
Can changing KBLI cancel a licence?
A substantive activity change can alter risk level, prerequisites and activity-level permissions. Assess the connected outputs before submitting and preserve the prior record.
What evidence should be kept after a correction?
Keep before-and-after exports, controlling corporate or property records, the approved change memo, OSS submission receipt, new outputs, affected-licence analysis and downstream update confirmations.
