OSS WORKFLOW

OSS Registration for a PT PMA: Step-by-Step Guide

A decision-led brief on master data, KBLI, project, location, investment, risk output, verification, and post-filing control, built for foreign investors who need a controlled path from filing to lawful operations.

By Elara Vance Updated August 3, 2026 4-minute read

OSS turns verified company and project facts into the NIB and risk-based licensing outputs. Accurate KBLI, location, investment, scale, and activity data matter because they determine conditions and verification. The conclusion must be matched to the exact KBLI, sector, location, shareholders, authority, and transaction rather than applied as a slogan. Document the legal basis, approved source data, responsible owner, filing evidence, and every unresolved condition before signing, funding, or operating. For master data, KBLI, project, location, investment, risk output, verification, and post-filing control, rely on current official outputs and fact-specific Indonesian advice instead of guaranteed provider claims. Learn more about the core Indonesia company registration service before selecting a filing scope.

Key takeaways

Do not release the next stage until the prior official output and source data are verified.
Choose the entity, KBLI, ownership model, and location before finalizing the deed.
Treat AHU incorporation, OSS licensing, tax readiness, banking, and immigration as separate evidence gates.
Keep investment value and paid-up capital separate from provider fees and recurring operating costs.

Enter verified corporate and project data into OSS

OSS registration should begin only after the PT PMA's approved corporate master data is available. Enter the legal identity, responsible persons, address, project location, five-digit KBLI, activity description, scale, investment plan, land and building treatment, employment, environmental and spatial data, and other required facts from verified sources. Convenience selections can change ownership eligibility, risk level, capital calculation, license output, and reporting obligations.

The current workflow is governed by Government Regulation 28 of 2025 and implemented through BKPM Regulation 5 of 2025 . Generate the NIB and then inspect every activity for its risk tier, Standard Certificate or license status, verification, prerequisites, PB UMKU, and obligations. Download the outputs, record system access and recovery contacts, reconcile them to the deed, and assign each incomplete condition instead of calling the company operational.

OSS stages

Input

Corporate, KBLI, project, location, and investment data Approve before entry

Output

NIB, certificate, license, and obligations Read each activity

Control

Downloads, access, corrections, and open conditions Complete handover

Move from the deed to OSS in dependency order

The incorporation workflow should move from approved source data to name, deed, legal-entity approval, tax data, and OSS licensing. Each output becomes an input for the next system, so a correction to shareholders, address, capital, or activity can create work across several records. Release control should sit with the investor or an authorized company officer, not solely with the filing agent.

Use AHU business-entity services for the corporate record and the OSS framework under Government Regulation 28 of 2025 for risk-based business licensing. After each submission, compare the official output with the approved data sheet. Record the identifier, issue date, responsible account, downloadable evidence, corrections, and next dependency before marking a stage complete.

Dependency sequence	Evidence	Control action
Corporate	Name, deed, and AHU approval	Verify legal identity and governance
Tax	Entity tax registration and access	Confirm data and filing owner
Licensing	NIB and applicable standards or permits	Check operational status, not number alone

Read the NIB, risk level, and operating conditions together

An NIB is a business identity and, for low-risk activity, the business license; it is not a universal authorization for every KBLI. Medium-low risk generally adds an unverified Standard Certificate, medium-high risk requires a verified Standard Certificate, and high risk requires an NIB plus a license. The actual output follows the activity, scale, location, and current sector rules.

This risk structure is set out in BKPM Regulation 5 of 2025 and the governing Government Regulation 28 of 2025 . Read the OSS output for verification status, prerequisites, obligations, and supporting PB UMKU rather than stopping at the NIB. If the premises, environmental approval, professional credential, or sector permission remains incomplete, do not treat the company as commercially ready.

OSS license status

Low risk

NIB

Action: Verify obligations attached to the activity

Medium risk

NIB plus Standard Certificate

Action: Check whether verification is required and complete

High risk

NIB plus license

Action: Do not operate before required approval

Build an accepted shareholder and authority file

The filing team needs usable evidence for each shareholder, authorized signer, director, commissioner, address, and declared business activity. Foreign individuals typically provide passport and contact data, while foreign corporate shareholders need constitutional and authority records that identify the entity and the person empowered to sign. The accepting notary should confirm the exact document, legalization, apostille, translation, and validity requirements.

Build a document register with issuer, document date, expiry or freshness rule, language, certification route, signatory, original location, and accepting institution. Indonesian company formation is processed through notarial and AHU business-entity services workflows, so a scan that looks complete to a provider may still require a different form or supporting authority. Resolve discrepancies in names, addresses, dates, and ownership before execution.

Document readiness

Identity

Passports and consistent personal data Resolve spelling and expiry issues

Corporate authority

Charter, registry proof, and signer mandate Confirm the shareholder can subscribe

Execution

POA, legalization, and translation path Obtain notarial acceptance before signing

Test the company before its first commercial transaction

Legal incorporation is only one readiness state. The company may still need verified OSS outputs, sector or supporting permits, tax access, PKP analysis, accounting and invoice controls, payroll arrangements, a bank account, premises evidence, and recurring reporting ownership before it can execute the planned transaction. Each state should be independently evidenced.

Use DGT registration guidance for the tax registration workstream and Government Regulation 28 of 2025 for the licensing baseline. Build a first-transaction test covering authority, contract, invoice, tax, payment, license, delivery, accounting entry, and reporting. Do not let a certificate date become the commercial launch date unless every required control passes.

Readiness gates	Evidence	Control action
Incorporated	Deed and AHU legal-entity approval	Entity legally exists
Licensed and tax-ready	Applicable OSS and tax outputs	Activity can proceed under conditions
Operational	Bank, people, premises, controls, and reporting	First transaction can be executed

Complete OSS from verified company data and read every condition

The decision for OSS Registration for a PT PMA: Step-by-Step Guide should be approved only when the company structure, ownership position, documents, governance, capital, address, licensing, tax, banking, and responsible owners are consistent. If one of those facts remains conditional, record it as a pre-filing or pre-operation gate instead of hiding it inside a broad provider promise.

The board or founders should sign a short mandate naming the chosen route, approved source data, budget, payment limits, acceptance evidence, unresolved conditions, and first lawful transaction. That mandate gives the notary and providers clear instructions while preserving investor control over changes. Recheck current official rules immediately before filing because sector, OSS, tax, banking, and immigration requirements can change.

Frequently asked questions

What data should be approved before entering OSS?

OSS turns verified company and project facts into the NIB and risk-based licensing outputs. Accurate KBLI, location, investment, scale, and activity data matter because they determine conditions and verification. Confirm the answer against the current official rule and the company's exact deed, AHU, OSS, tax, bank, immigration, and sector facts before acting.

What is the correct registration order?

Define activity and structure, screen ownership and KBLI, approve documents and governance, execute the deed, obtain AHU approval, complete tax data, enter OSS, and satisfy the applicable risk-based and sector requirements.

Who should verify the final outputs?

An authorized company officer should compare the deed, AHU, tax, OSS, license, beneficial-owner, and bank data against the approved master record and retain direct access to each system or document.

Does company registration alone allow the business to start operating?

Not always. Legal-entity approval and an NIB are important outputs, but the activity may still require a verified Standard Certificate, a license, supporting PB UMKU, premises evidence, tax activation, or another sector condition. Read the status and obligations attached to the exact KBLI before the first commercial transaction.

Is paid-up capital the same as a registration fee?

No. Paid-up capital belongs to the company as shareholder equity and must be documented and used consistently with current rules. Provider fees, official charges, translations, address costs, and operating expenses are separate. Never transfer a capital amount to an agent merely because an invoice calls it a setup fee.

Official references