NIB Registration in Indonesia: Prepare Business Data Before Applying Through OSS

Build the company record before entering project data

A company should prepare its established legal identity before treating OSS as a blank application form. Keep the current deed and amendments, the corresponding Ministry of Law/AHU record, Taxpayer Identification Number (NPWP), ownership and management details, and an authorized contact together. These are reference materials for reconciliation; they are not a promise that every document will be uploaded in every application.

Under PP 28/2025, Articles 206–207 , a business actor has one NIB. The registration includes profile, business capital, NPWP, KBLI and location data, with company information integrated from the legal-administration system and tax data validated through the relevant integration. Compare imported fields with the underlying records before continuing; an automatically populated value can still reveal an unresolved upstream discrepancy.

For a company whose formation documents are incomplete, resolve that dependency through company registration in Indonesia before presenting the entity as established in OSS. A foreign-invested company should use its actual investment status and applicable company route. A domestic small-business illustration is not authority to select a different status or scale for convenience.

Nominate a person to approve the source record and another person, where practical, to compare the draft against it. Record the responsible filer, access owner and working contact details. Account access establishes who can use the system; it does not replace the company’s authorization to make declarations. Keep credentials and recovery access under company control.

The useful preparation endpoint is a single agreed company record , with a date and a source beside each material field. Do not maintain one spelling of the legal name in the deed folder, another in the tax worksheet and a third in the filing instructions.

Prepare a source-backed record for each activity and location

Prepare a separate activity/location row for each project you intend to declare. Article 211 of PP 28/2025 requires main-activity data for each five-digit KBLI and business location, including product type, capacity, workforce and planned investment. The control sheet below adds an editorial filing safeguard: identify what supports each input and what would make you hold the application.

Confirm the classification version and the actual activity

As checked on November 4, 2026, the live OSS business-classification directory is labelled KBLI 2025. BPS Regulation 7/2025 has also been amended by BPS Regulation 6/2026, effective September 10, 2026 . Use the current description and scope, not a code copied from an old checklist. Describe what the company will sell, produce or deliver, and how it will earn revenue, before selecting the classification.

The official KBLI conversion explanation shows that old codes may remain, change, split, merge or be rearranged. A numerical match does not prove unchanged scope. Retain the old-to-new mapping when legacy records are involved, then check that the selected scope covers the planned work. Do not add unrelated activities simply to keep future options open.

The OSS business-data change manual illustrates conditional location, map, premises, investment, workforce and product-capacity fields. Its older legal references are not the current governing rules; use it to recognize data categories, then follow the fields presented in your actual route. A map point, polygon file or building record is conditional, not a universal attachment checklist.

Where one entity has activities at two sites, keep the entity identity shared and distinguish the project evidence. Likewise, two activities at one site still need coherent activity descriptions and allocations. The registered office and the business location answer different questions. Check which question the live form is asking rather than forcing every address to match.

Company identity, activity scope and site evidence must converge before the draft is released. The final check should assess the combination, because individually plausible entries can describe different businesses when assembled.

Resolve contradictions before accepting OSS declarations

Reconcile fields across records before accepting declarations. A green validation message should not end your review: it may confirm that a field can be processed without proving that the business assumptions behind it are correct. Keep unresolved questions in a short exception list with the field, conflicting sources, proposed correction and person responsible.

Separate a source error from an application error

If the company name, legal record or tax identifier differs from the authoritative source, establish which record is wrong before overwriting a convenient field. Correct the source through the appropriate process when required, then confirm that OSS reflects the correction. If the source is correct and the application entry is wrong, amend the application through the route that applies to its current status.

Legacy KBLI records require a similar distinction. The government’s KBLI 2025 implementation policy separates numerical-only alignment from a substantive change in company purposes or activities. Do not commission a corporate amendment solely because an old number differs, or assume automatic mapping authorizes a new activity. Compare the substance first and retain the mapping evidence.

• Compare the activity narrative, chosen scope and product list. A trading description should not silently become manufacturing in another field.
• Reconcile the address with the map and site area. A correct street address paired with the wrong coordinates is still a location problem.
• Check budget totals and units. Keep company capital, project investment and working-capital assumptions distinguishable rather than reusing one number everywhere.
• Read each declaration against the supporting evidence. Stop if the declaration says a condition is already satisfied when the team has only planned to satisfy it.

For foreign investment, project investment and company capital need their applicable regulatory checks; this preparation sheet does not set a universal minimum. Resolve the relevant activity, location and sector conditions before approving the figures. A value chosen merely to pass a screen is not a defensible investment plan.

Move from prepared data to a checked NIB output

Use the applicable current OSS filing and access guidance for your applicant category. The sequence below is a control sequence for a prepared company application, rather than a promise that all accounts display identical menu names. Existing NIB holders should first determine the appropriate addition or amendment route instead of creating a duplicate identity.

1. Sign in through the official OSS service with the company’s authorized access. Confirm that the account is associated with the correct business actor.
2. Compare the company profile with the approved master record. Resolve identity and integration discrepancies before adding project detail.
3. Enter the selected activity, business location and requested business data. Follow the conditional spatial, environmental and premises questions that appear for that activity and site.
4. Review the risk result, required declarations and application draft together. Approve only statements that the company can support, then complete the system’s submission or issuance action.
5. Save the application reference or status evidence, downloaded NIB and accompanying outputs. Reopen the files and compare the business identity and activity/location details with the approved records.

Keep preparation and authority processing separate when planning the work. Source collection, budget reconciliation and account preparation can run in parallel; an unresolved legal identity or project condition must be cleared before the related declaration. There is no reliable single end-to-end duration for an unspecified activity and site, and a successful data-entry session is not an approval deadline.

Under PP 28/2025 , the risk route determines whether the activity requires NIB alone, NIB plus a Standard Certificate, a verified Standard Certificate, or a Business Licence. Applicable basic requirements and supporting business approvals must also be addressed. Therefore NIB issued and permission to start the particular operation are separate checks.

When carrying NIB data into the licensing workflow , retain both the issued document and the activity’s permission status. If a requirement is outstanding, save the notice and identify the evidence needed for the next action. Do not label a pending or unverified output as complete merely because the NIB file can be downloaded.

Release the NIB application only when the records agree

Release the NIB application when the company record is supported, each activity/location row is explainable, and the final declarations match the evidence. Save the approved data sheet with the submitted version so the company can later establish what it declared and why.

Hold submission for an unresolved identity mismatch, unsuitable KBLI scope, uncertain site answer or unsupported figure. After issuance, close the registration task only when the NIB and accompanying outputs have been checked; keep any remaining operating-permission requirements as assigned follow-up work. That preserves a clear boundary between a completed registration record and an activity that is ready to operate.