PACKAGE CONTENT

Indonesia Company Setup Packages: What Should Be Included?

A decision-led brief on package components, exclusions, acceptance evidence, and post-setup work, built for foreign investors who need a controlled path from filing to lawful operations.

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

Foreign investors should buy Indonesia company formation services against defined deliverables rather than a broad promise to complete registration. The required scope depends on the activity, ownership, location, shareholder documents, risk-based license, tax position, bank expectations, and whether work will be managed remotely. A competent engagement assigns an owner and acceptance document to every stage, then hands over original documents, credentials, filing data, and an unresolved-items register. For package components, exclusions, acceptance evidence, and post-setup work, the decisive question is whether the service produces a company that the founders can independently control and continue operating. Learn more about the core Indonesia company registration service before selecting a filing scope.

Key takeaways

A complete handover includes credentials, originals, filing data, receipts, and open obligations.
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.

Set the service boundary and responsible owner

A formation service should state whether it covers design, incorporation, tax registration, OSS licensing, sector verification, banking support, immigration coordination, and compliance onboarding. Filing a deed is materially different from delivering a controlled operating handover. The service boundary should be explicit before work starts.

Convert the proposal into a responsibility matrix naming the adviser, notary, translator, shareholder, company officer, landlord, bank, and government authority. For every task, state the input, output, acceptance test, dependency, correction owner, and exclusion. The company should receive official documents and direct account control rather than screenshots that cannot be independently verified.

Service boundary

Design

Structure, ownership, KBLI, capital, and address

Action: Approve before execution

Registration

Deed, AHU, tax, and OSS outputs

Action: Verify against source data

Activation

Licenses, bank, finance, and handover

Action: Close open items with owners

Normalize price, scope, taxes, and exclusions

A provider quote is comparable only when scope, assumptions, taxes, third-party charges, and acceptance evidence are normalized. Headings such as complete setup, bank support, or all licenses have no operational meaning unless the proposal names the precise output and any condition outside the provider's control. The investor should convert each offer into the same comparison sheet.

Require legal entity, KBLI analysis, foreign ownership review, deed, AHU output, tax setup, OSS output, license verification, address work, bank assistance, immigration, compliance onboarding, originals, credentials, corrections, and cancellation terms to appear as included, excluded, optional, or conditional. Link payments to verifiable milestones and never pay capital or government charges into an unexplained personal or intermediary account.

Quote normalization

Scope

Named output and acceptance test Mark included, excluded, or conditional

Price

Fee, tax, disbursement, and currency Compare the same commercial basis

Risk

Correction, delay, refund, and liability term Allocate foreseeable failure costs

Fund the work that begins after legal incorporation

The largest omitted cost is often the work required after the company legally exists. An AHU approval may still be followed by OSS verification, address or premises evidence, sector permits, tax access, PKP analysis, bank KYC, accounting setup, payroll, immigration, and recurring reports. A quote that ends at incorporation can therefore be accurate but operationally incomplete.

Build a post-registration work breakdown that includes the DGT registration workflow , OSS obligations, bank evidence, corporate records, and investment reporting. PKP treatment depends on taxable activity and turnover conditions; the DGT PKP guidance should be checked rather than assuming every company is immediately VAT-ready. Attach an owner, start trigger, expected evidence, and budget to each downstream task.

Common exclusions	Evidence	Control action
License completion	Verification and supporting permits	Check commercial-use status
Finance activation	Tax, accounting, bank, and invoice controls	Prepare before first transaction
Ongoing compliance	Monthly, annual, LKPM, and corporate duties	Fund a responsible owner

Define acceptance evidence for every deliverable

Every service promise should end in an acceptance document. Registration submitted is not equivalent to legal-entity approval; NIB issued is not equivalent to every license being verified; bank assistance is not equivalent to account approval; and visa preparation is not equivalent to immigration approval. The contract should use the correct endpoint.

Define acceptance against official outputs from AHU business-entity services , OSS, DGT, and any sector authority. Include downloaded files, QR or record checks, source data, issue dates, account ownership, payment receipts, originals, and an exceptions log. Where an authority makes the final decision, require complete submission evidence and a correction or escalation process instead of a guarantee.

Acceptance evidence

Corporate

Approved deed and AHU legal-entity record

Action: Check names, roles, shares, and capital

Licensing

NIB and required verified output

Action: Read status and conditions

Handover

Files, credentials, originals, and open-item log

Action: Test independent company control

Take control of documents, credentials, and open obligations

A registration engagement is not complete until the company can operate without dependence on the provider's personal accounts or device. Handover should cover final documents, source data, credentials, registered email and phone details, authentication methods, originals, payment receipts, filing history, and unresolved obligations. Access should be tested by an authorized company officer.

Remote matters need an especially clear revocation and recovery plan. Reconcile the deed, AHU approval, tax record, NIB, licenses, shareholder register, beneficial-owner data, and bank application before acceptance. Record who holds each original, how each credential can be recovered, and when any power of attorney or temporary access must end.

Handover register

Documents

Final files, originals, and filing receipts Inventory and verify

Access

OSS, tax, email, phone, and authentication Transfer and test control

Open work

Conditions, renewals, and corrections Assign owner and due date

Choose the package that names every dependency and owner

The decision for Indonesia Company Setup Packages: What Should Be Included? 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 is the difference between incorporation and full setup?

Incorporation normally ends with the legal entity and related corporate outputs. Full setup may also include tax, OSS and sector licenses, address work, bank support, finance controls, immigration, compliance onboarding, and handover. Define the endpoint precisely.

What should be delivered at handover?

Require final official files, source data, credentials, registered contact details, originals, receipts, ownership and governance records, license status, tax access, unresolved items, renewal dates, and correction history.

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.

Can a provider guarantee OSS, bank, or visa approval?

No provider controls an authority, bank, or Immigration decision. A responsible provider can prepare, submit, monitor, correct, and evidence an application, but the contract should not promise guaranteed approval. Ask for the assumptions, acceptance documents, correction process, and escalation route.

Official references