Opening a Branch of an Indonesian PT: Registration and Tax

A branch remains the Indonesian PT

A branch of an Indonesian PT is an operating location or business unit of the same Indonesian limited-liability company, not a second company with a separate shareholder structure. The parent PT remains the contracting and governance centre unless the relevant documents and activity rules say otherwise. The branch needs a clear mandate, address, activity scope, and records that reconcile with the PT’s corporate and licensing data.

Start with an internal authority decision. It should identify the branch name or location, opening date, head of branch or responsible manager, permitted activities, signatory limits, bank or payment authority, contract threshold, staffing responsibility, asset custody, reporting line, and closing procedure. A branch head should not acquire broad company authority merely because the business calls a location a “branch.” The corporate record, contracts, and approval matrix should show exactly what is delegated.

Use the current Ministry of Law AHU service record to verify the PT’s foundational data and the live OSS risk-based licensing system record for business licensing. A branch project should not create a competing set of names, addresses, directors, activities, or authority descriptions that cannot be explained against the parent company’s official files.

Decide whether the new location is a branch or merely a project address

Not every location needs to be treated in the same way. A project site, warehouse, sales outlet, administrative office, factory, virtual address, temporary work site, or customer-service hub can have different legal, licensing, tax, and sector implications. Begin by recording the actual use of the location and how long it will operate. Then decide whether it is a branch for company purposes, a separately registered place of business for tax administration, a project location, or a permitted temporary site.

The key is consistency. If staff and customers treat the site as a full operating branch, but the corporate, OSS, tax, and local records call it a temporary project desk, the mismatch can create problems in permits, banking, tax, contracts, employment, and audit. A location should be described consistently in its lease, signage, invoices, customer correspondence, employment contracts, and internal authority schedule.

Classify the location before spending on fit-out

• Operating purpose: sales, management, service delivery, warehousing, manufacturing, project execution, administration, or customer support.
• Activity scope: current KBLI, sector permissions, product requirements, local zoning or building conditions, and whether the branch will perform the activity or only support it.
• Authority: whether the local team can negotiate, quote, contract, issue documents, receive payments, hold inventory, or engage suppliers.
• Tax and records: the parent NPWP identity, NITKU/location data, VAT invoice process, payroll owner, bookkeeping flow, and address used in tax systems.

Document the decision in a short location memorandum. It should state the physical address, start date, intended operating role, activity permissions to check, tax treatment to confirm, current owner, and the trigger that requires an update if the site grows or changes purpose.

Create a branch launch record

Build one launch record per location. It prevents an all-too-common situation in which the branch lease, OSS data, tax location, customer invoices, and staffing records each name the site differently. The record should be approved before commercial activity begins and updated when the location changes in a way that affects permissions or taxation.

If the branch plan reveals that the current PT does not have the relevant activity, location, or operating permissions, use company registration in Indonesia as the broader company-and-licensing route reference. The right response may be a corporate or OSS update, a different permitted location, or a separate entity—not simply opening the branch anyway.

NIB, business activities, and local permits

The branch should operate only within the parent PT’s current business activities and permissions. Check the live OSS risk-based licensing system data, relevant KBLI, risk classification, and effective outputs for the precise activity at the precise site. Some sectors and locations involve additional conditions that are not solved by entering an address in a corporate document. Maintain the final OSS output, source date, and a list of any commitments or local approvals still required.

This check matters when the branch becomes more operational than expected. For example, a sales office may add inventory, a warehouse may start packaging, a service desk may begin repairs, or a project office may become a permanent customer hub. Each change can affect the site’s compliance requirements. Use a pre-launch and change-control process so the licensing review happens before, not after, the new activity starts.

For a broader completion sequence after a company is registered, see the Indonesia post-registration steps guide . It is a separate operational checklist; a branch still needs a location-specific comparison against the PT’s actual permissions and records.

Tax identity: one NPWP, NITKU by location

DJP guidance on the Coretax transition states that, from 1 July 2024, branch taxpayers and taxpayers with business locations separate from their domicile or place of incorporation use a NITKU (Nomor Identitas Tempat Kegiatan Usaha) for each branch location, while the entity uses one NPWP. The same guidance says VAT reporting and payment for central and regional units use the central NPWP. See the official DJP guidance on one NPWP and NITKU for branch locations for the published explanation, then verify the current implementation for your taxpayer profile and systems.

This does not make branch tax compliance automatic. The tax team still needs accurate location data, central-versus-site responsibility, invoice and VAT process, payroll and withholding flow, bookkeeping access, evidence retention, and a calendar for returns or payments. Reconcile NITKU/location records with the actual branch address and the parent PT’s tax profile. If a site is added, moved, or closed, update the data in the correct order and retain evidence of the effective change.

Do not revive the old assumption that each branch has a separate NPWP simply because an older form or vendor checklist says so. Use the single-entity NPWP and location-specific NITKU model as the current starting point, then confirm the exact tax workflow with DJP for the PT’s facts. The Directorate General of Taxes is the appropriate official source for current tax-administration procedures and changes.