NIB Data Reconciliation for Foreign-Owned Companies in Indonesia
Align the NIB with AHU, ownership, capital, KBLI 2025, project locations, tax, banking, and the effective licence state used in operations.
A foreign-owned company should reconcile its NIB field by field against the latest deed and AHU approval, shareholder and beneficial-owner records, capital approvals, KBLI 2025 classification, project locations, tax profile, bank KYC file, and live licence outputs. The official OSS portal describes the NIB as the business identity, but the reconciliation must also confirm which licences and conditions govern each activity.
Run the review after first issuance and after any change to name, address, shareholders, directors, capital, activity, location, or responsible contacts. Not every difference requires the same correction path: AHU may be authoritative for corporate data, tax administration for the registered taxpayer, and OSS for project and licensing data. The control file should identify the source of truth, dependent fields, filing order, owner, and evidence that the update became effective.
Nib data reconciliation decision controls
Use the control, evidence, and release condition together; no single document should carry more meaning than it actually proves.
| Control stage | Question to resolve | Evidence anchor |
|---|---|---|
| Set the source of truth for each NIB field | list every NIB field and identify the corporate, tax, OSS, or operational record that authoritatively supports it | NIB field inventory |
| Reconcile foreign ownership and capital data | compare shareholders, nationalities, beneficial ownership, issued capital, paid-up capital, and approved investment data across current records | Share register and deed |
| Reconcile KBLI 2025 and project locations | map every real revenue and operating activity to the current KBLI and the exact project location shown in OSS | Product and service catalogue |
| Align tax, bank, contract, and contact data | compare the reconciled NIB identity and address with Coretax, bank KYC, contracts, invoices, customer onboarding, registered email, and phone channels | Coretax taxpayer profile |
| Approve corrections and recurring refresh triggers | execute the approved sequence, capture before-and-after records, and assign refresh triggers for corporate and operating events | Correction plan and approvals |
In this article
Key takeaways
- Approve the source hierarchy and filing sequence before making changes.
- Stop downstream updates until corporate approvals and authoritative ownership data agree.
- Treat each KBLI-location pair as a separate licence and evidence decision.
- Close every downstream difference through its proper process and retain acceptance evidence.
- Make NIB reconciliation a required close step for every material company or project change.
Scope the NIB data reconciliation before acting
Share the company facts, intended outcome, current records, and unresolved conditions so the NIB data reconciliation review can be bounded.
Set the source of truth for each NIB field
The responsible team should list every NIB field and identify the corporate, tax, OSS, or operational record that authoritatively supports it. For set the source of truth for each nib field, the live OSS output, not a generic description of the system, determines which activity, project, licence state, condition, and follow-up record needs attention.
Teams can overwrite a correct field with a value copied from a dependent or stale document. A reviewer should trace nib field inventory and deed and ahu records to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For set the source of truth for each nib field, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect nib field inventory with deed and ahu records, then show how tax and coretax profile and oss project and licence records affect the next approval. Record the source for nib field inventory, the reviewer of deed and ahu records, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Decision rule
Approve the source hierarchy and filing sequence before making changes.
- NIB field inventory
- Deed and AHU records
- Tax and Coretax profile
- OSS project and licence records
For set the source of truth for each nib field, preserve the source record, reviewer, date, exception, and approval so another team can reproduce the decision without relying on memory.
Reconcile foreign ownership and capital data
A supportable decision begins when the company can compare shareholders, nationalities, beneficial ownership, issued capital, paid-up capital, and approved investment data across current records. For reconcile foreign ownership and capital data, the live OSS output, not a generic description of the system, determines which activity, project, licence state, condition, and follow-up record needs attention.
Foreign ownership and capital mismatches can affect licensing, bank KYC, reporting, and the credibility of later amendments. A reviewer should trace share register and deed and ahu and beneficial-owner records to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For reconcile foreign ownership and capital data, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect share register and deed with ahu and beneficial-owner records, then show how capital approvals and ledger and oss investment data affect the next approval. Record the source for share register and deed, the reviewer of ahu and beneficial-owner records, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Evidence rule
Stop downstream updates until corporate approvals and authoritative ownership data agree.
- Share register and deed
- AHU and beneficial-owner records
- Capital approvals and ledger
- OSS investment data
For reconcile foreign ownership and capital data, turn the result into a controlled work item with a responsible person, due date, evidence location, escalation path, and release condition. For the adjacent control framework, compare NIB in Indonesia Explained: Business Identification Number After Company Registration .
Test the NIB data reconciliation evidence
Reconcile the authoritative, operational, contractual, tax, banking, and evidence fields that affect the NIB data reconciliation decision.
Reconcile KBLI 2025 and project locations
Before the next commitment, management should map every real revenue and operating activity to the current KBLI and the exact project location shown in OSS. For reconcile kbli 2025 and project locations, the live OSS output, not a generic description of the system, determines which activity, project, licence state, condition, and follow-up record needs attention.
A correct company identity does not cure a missing activity, duplicated project, legacy code, or incorrect operating site. A reviewer should trace product and service catalogue and kbli 2025 descriptions to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For reconcile kbli 2025 and project locations, 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 product and service catalogue with kbli 2025 descriptions, then show how oss activity-location records and premises and project evidence affect the next approval. Record the source for product and service catalogue, the reviewer of kbli 2025 descriptions, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Control point
Treat each KBLI-location pair as a separate licence and evidence decision.
- Product and service catalogue
- KBLI 2025 descriptions
- OSS activity-location records
- Premises and project evidence
For reconcile kbli 2025 and project locations, record both the accepted position and the rejected alternatives; this prevents a later portal edit or provider message from silently changing the decision.
Regulatory Notes and Limitations
NIB Data Reconciliation for Foreign-Owned Companies in Indonesia 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 NIB Data Reconciliation for Foreign-Owned Companies in Indonesia, an NIB is an official business identity, but the licence state required to operate depends on the activity, risk level, location, and supporting approvals shown in OSS.
- For NIB Data Reconciliation for Foreign-Owned Companies in Indonesia, oSS workflow screens and document labels should be checked at execution because system implementation and transition treatment can change.
- For NIB Data Reconciliation for Foreign-Owned Companies in Indonesia, a government-issued record does not replace tax, corporate, bank, premises, product, or sector evidence that another authority or counterparty may require.
Official References and Review Basis
Primary materials for NIB Data Reconciliation for Foreign-Owned Companies in Indonesia 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 NIB Data Reconciliation for Foreign-Owned Companies in Indonesia.
- Online Single Submission portal : Official NIB, four-level risk classification, business licensing, KBLI, and support portal.
- 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.
- BPS KBLI 2020–2025 conversion table : Official correspondence table for reviewing changes between KBLI 2020 and KBLI 2025.
- AHU company profile search : Official search for Indonesian limited-liability-company profile data.
- Coretax DJP implementation page : Official tax administration portal guidance effective for administration from January 2025.
Align tax, bank, contract, and contact data
The control file must show how the company will compare the reconciled NIB identity and address with Coretax, bank KYC, contracts, invoices, customer onboarding, registered email, and phone channels. For align tax, bank, contract, and contact data, the live OSS output, not a generic description of the system, determines which activity, project, licence state, condition, and follow-up record needs attention.
A government data correction may not automatically update private counterparties or account recovery controls. A reviewer should trace coretax taxpayer profile and bank kyc and signatories to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For align tax, bank, contract, and contact data, the practical deliverable is a version-controlled decision row that remains usable when the activity, location, counterparty, or responsible person changes. It should connect coretax taxpayer profile with bank kyc and signatories, then show how contract and invoice master data and company-controlled contact channels affect the next approval. Record the source for coretax taxpayer profile, the reviewer of bank kyc and signatories, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Release test
Close every downstream difference through its proper process and retain acceptance evidence.
- Coretax taxpayer profile
- Bank KYC and signatories
- Contract and invoice master data
- Company-controlled contact channels
For align tax, bank, contract, and contact data, close the stage only when the authoritative record and the operating evidence agree, or when an unresolved difference has a named owner and stop condition.
Approve corrections and recurring refresh triggers
For NIB data reconciliation, execute the approved sequence, capture before-and-after records, and assign refresh triggers for corporate and operating events. For approve corrections and recurring refresh triggers, the live OSS output, not a generic description of the system, determines which activity, project, licence state, condition, and follow-up record needs attention.
A one-time clean-up will decay if future amendments do not update the same dependent systems. A reviewer should trace correction plan and approvals and submission and acceptance receipts to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.
For approve corrections and recurring refresh triggers, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect correction plan and approvals with submission and acceptance receipts, then show how exception and dependency register and annual and event-driven review calendar affect the next approval. Record the source for correction plan and approvals, the reviewer of submission and acceptance receipts, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.
Stop condition
Make NIB reconciliation a required close step for every material company or project change.
- Correction plan and approvals
- Submission and acceptance receipts
- Exception and dependency register
- Annual and event-driven review calendar
For approve corrections and recurring refresh triggers, the output should name the owner, source evidence, unresolved condition, acceptance test, and the event that permits the next step. Where this stage changes another workstream, review Changing a PT PMA in Indonesia .
Compare the proposed nib data reconciliation action with HSJGlobal’s Indonesia company registration scope before changing the company or operating plan.
Keep the NIB aligned with the company that actually operates
The NIB is useful when its identity, ownership, capital, activities, locations, and contact data can be traced to current authoritative records. Reconciliation turns it from a standalone PDF into a controlled business record.
Repeat the check after every material corporate or operational change, and close dependent tax, bank, contract, and licence updates before declaring the event complete.
Turn the NIB data reconciliation into an approved next step
Create a sequenced action file with owners, evidence, exceptions, stop conditions, and an approved release point for NIB data reconciliation.
Frequently asked questions
