Indonesia OSS Account Handover After Incorporation

An Indonesia OSS handover is complete only when the company controls the registered contact channels and authorized users, can access the account without a provider, and has reconciled every entity, activity, location, licence, submission, and unresolved condition. BKPM Regulation No. 5 of 2025 supplies the current OSS procedural framework; the handover must also preserve proof of what was filed, issued, verified, rejected, or left pending.

Do not accept a folder containing only an NIB. A usable handover includes an authority map, secure credential transfer, current exports, a project-by-project licence register, support tickets, deadlines, and named owners for tax, investment reporting, sector permits, and future amendments. Shared passwords, provider-owned email addresses, missing phone access, or unexplained portal statuses are release blockers because the company may be unable to operate or update its own regulatory record.

Key takeaways

• The company must control its own recovery channels and authorized users.
• Reconcile live OSS fields to AHU, tax, address, ownership, and project evidence.
• Preserve submissions and statuses, not only final-looking PDF outputs.
• Separate issued, effective, verified, conditional, rejected, and pending licence states.
• Keep unresolved support cases and deadlines inside the signed handover schedule.

In this article

• Map authority and users
• Reconcile live OSS data
• Build the licence register
• Transfer filings and open cases
• Test and close the handover
• Regulatory Notes and Limitations
• Official References and Review Basis
• Take control of OSS before the setup team exits

OSS handover acceptance file

The receiving team should test access and reconcile the live account before signing acceptance.

Establish the company authority and user map

List every individual or provider with OSS access, the legal basis for that access, the registered contact channel, and the actions each role can perform. Test recovery using company-controlled devices before any provider account is removed.

An account can appear operational while the company lacks the email, phone, identity, or authority required to recover it. Shared credentials also prevent reliable attribution of later filings.

For establish the company authority and user map, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect identify the registered responsible person and source authority. with move recovery email and phone control to the company., then show how create named users instead of permanent shared credentials. and record revoked, retained, and emergency provider access. affect the next approval. Record the source for identify the registered responsible person and source authority., the reviewer of move recovery email and phone control to the company., the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test establish the company authority and user map through normal progress, delayed move recovery email and phone control to the company., and failure of create named users instead of permanent shared credentials.. The normal case confirms the intended order for identify the registered responsible person and source authority.; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for record revoked, retained, and emergency provider access.. Retain this stage-specific result with the final approval and review calendar.

• Identify the registered responsible person and source authority.
• Move recovery email and phone control to the company.
• Create named users instead of permanent shared credentials.
• Record revoked, retained, and emergency provider access.

For establish the company authority and user map, turn the result into a controlled work item with a responsible person, due date, evidence location, escalation path, and release condition. For the filing sequence that precedes handover, compare the OSS registration workflow .

Reconcile entity, ownership, KBLI, and project data

Compare the OSS legal name, address, shareholders, management, capital, KBLI codes, project locations, investment data, and contact fields with the latest authoritative corporate and tax records. Export or capture the live state with a review date.

A handover can transfer access to an internally inconsistent account. Downstream licences, reports, banks, and counterparties may rely on fields inherited from an earlier deed, address, shareholder, or project plan.

For reconcile entity, ownership, kbli, and project data, 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 match ahu and deed data to the oss entity profile. with match each kbli to its actual activity and location., then show how reconcile capital and investment figures to approved records. and list stale, duplicate, transitional, or unexplained projects. affect the next approval. Record the source for match ahu and deed data to the oss entity profile., the reviewer of match each kbli to its actual activity and location., the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test reconcile entity, ownership, kbli, and project data through normal progress, delayed match each kbli to its actual activity and location., and failure of reconcile capital and investment figures to approved records.. The normal case confirms the intended order for match ahu and deed data to the oss entity profile.; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for list stale, duplicate, transitional, or unexplained projects.. Retain this stage-specific result with the final approval and review calendar.

• Match AHU and deed data to the OSS entity profile.
• Match each KBLI to its actual activity and location.
• Reconcile capital and investment figures to approved records.
• List stale, duplicate, transitional, or unexplained projects.

For reconcile entity, ownership, kbli, and project data, record both the accepted position and the rejected alternatives; this prevents a later portal edit or provider message from silently changing the decision.

Build the licence and condition register from live records

For every activity-location pair, record the risk level, NIB, certificate or permit, verification state, supporting approval, conditions, validity, issuer, and current portal status. Open the live record rather than inferring status from a filename.

A PDF labeled certificate may still depend on verification or another approval. Missing a condition during handover can delay first revenue or create noncompliance after the provider engagement ends.

For build the licence and condition register from live records, the practical deliverable is a version-controlled decision row that remains usable when the activity, location, counterparty, or responsible person changes. It should connect separate issuance from effectiveness and verification. with record pb-umku and sector dependencies., then show how capture validity, renewal, reporting, and site conditions. and assign a business owner to every continuing obligation. affect the next approval. Record the source for separate issuance from effectiveness and verification., the reviewer of record pb-umku and sector dependencies., the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test build the licence and condition register from live records through normal progress, delayed record pb-umku and sector dependencies., and failure of capture validity, renewal, reporting, and site conditions.. The normal case confirms the intended order for separate issuance from effectiveness and verification.; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for assign a business owner to every continuing obligation.. Retain this stage-specific result with the final approval and review calendar.

• Separate issuance from effectiveness and verification.
• Record PB-UMKU and sector dependencies.
• Capture validity, renewal, reporting, and site conditions.
• Assign a business owner to every continuing obligation.

For build the licence and condition register from live records, 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. Place continuing licence conditions inside the post-incorporation compliance guide .

Transfer submission evidence and unresolved cases

Collect application inputs, uploaded documents, submission receipts, correspondence, support tickets, rejection notices, corrections, and approval outputs in a searchable structure. Link every open case to the affected activity and deadline.

Without the submission history, the company cannot explain how a field was populated or continue a correction without recreating earlier work. Provider assurances are not a substitute for the government record and support history.

For transfer submission evidence and unresolved cases, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect index inputs, outputs, receipts, and correspondence by project. with record ticket numbers, last action, and requested response., then show how identify expiring documents and pending verifications. and state which party funds and performs correction work. affect the next approval. Record the source for index inputs, outputs, receipts, and correspondence by project., the reviewer of record ticket numbers, last action, and requested response., the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test transfer submission evidence and unresolved cases through normal progress, delayed record ticket numbers, last action, and requested response., and failure of identify expiring documents and pending verifications.. The normal case confirms the intended order for index inputs, outputs, receipts, and correspondence by project.; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for state which party funds and performs correction work.. Retain this stage-specific result with the final approval and review calendar.

• Index inputs, outputs, receipts, and correspondence by project.
• Record ticket numbers, last action, and requested response.
• Identify expiring documents and pending verifications.
• State which party funds and performs correction work.

For transfer submission evidence and unresolved cases, the output should name the owner, source evidence, unresolved condition, acceptance test, and the event that permits the next step.

Run a live acceptance test and close provider access

The receiving owner should log in, recover access, download a current record, locate each project, inspect a licence status, identify the next reporting task, and submit no changes during the test. Then approve retained support access for a defined period or remove it.

A checklist signed without a live test can hide inaccessible functions, undocumented impersonation, or missing records. The first failed login after a regulatory deadline is an avoidable control incident.

For run a live acceptance test and close provider access, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect test login, recovery, navigation, download, and role switching. with reconcile the final handover index to live oss., then show how rotate shared secrets and revoke unnecessary access. and schedule a 30-day review of open items and account logs. affect the next approval. Record the source for test login, recovery, navigation, download, and role switching., the reviewer of reconcile the final handover index to live oss., the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

Test run a live acceptance test and close provider access through normal progress, delayed reconcile the final handover index to live oss., and failure of rotate shared secrets and revoke unnecessary access.. The normal case confirms the intended order for test login, recovery, navigation, download, and role switching.; the delayed case states what may continue safely; and the failure case assigns the stop, correction, notification, and evidence-preservation steps for schedule a 30-day review of open items and account logs.. Retain this stage-specific result with the final approval and review calendar.

• Test login, recovery, navigation, download, and role switching.
• Reconcile the final handover index to live OSS.
• Rotate shared secrets and revoke unnecessary access.
• Schedule a 30-day review of open items and account logs.

For run a live acceptance test and close provider access, preserve the source record, reviewer, date, exception, and approval so another team can reproduce the decision without relying on memory.

Compare the proposed indonesia oss account handover after incorporation action with HSJGlobal’s Indonesia company registration scope before changing the company or operating plan.

Regulatory Notes and Limitations

Indonesia OSS Account Handover After Incorporation 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 Indonesia OSS Account Handover After Incorporation, 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 Indonesia OSS Account Handover After Incorporation, oSS workflow screens and document labels should be checked at execution because system implementation and transition treatment can change.
• For Indonesia OSS Account Handover After Incorporation, 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 Indonesia OSS Account Handover After Incorporation 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 Indonesia OSS Account Handover After Incorporation.

• Ministry of Investment and Downstream Industry/BKPM Regulation No. 5 of 2025 : Current OSS procedures, investment facilities, supervision, and reporting framework.
• Government Regulation No. 28 of 2025 : Current risk-based business licensing framework; it revoked Government Regulation No. 5 of 2021.
• Online Single Submission portal : Official NIB, four-level risk classification, business licensing, KBLI, and support portal.

Take control of OSS before the setup team exits

The company owns the regulatory consequences of its OSS record even when a provider performed the filings. Take control of recovery channels, named users, live data, licence conditions, submissions, and unresolved cases before treating registration as handed over.

A live acceptance test and signed exception schedule protect future amendments, reporting, licence verification, and operating decisions from depending on an inaccessible provider account.

Related insights

• OSS Registration for a PT PMA: Step-by-Step Guide
• Post-Incorporation Compliance Guide for PT PMA
• PT PMA License Condition Tracker After Registration