PT PMA License Condition Tracker After Registration: Verification, Evidence, and Renewal

After registration, a PT PMA needs an evidence-based tracker for every activity, location, risk level, standard, certificate, permit, condition, and change.

PT PMA registration should not be treated as blanket permission to operate. Indonesia's current risk-based licensing framework uses NIB and activity-specific risk levels, while medium-high and high-risk activities can depend on verified standards, certificates, permits, inspections, technical evidence, sector approvals, or other conditions. The exact requirement must be checked for the company's current KBLI, scale, product, process, location, project stage, and sector in OSS and the responsible authority's rules.

Build one license-condition tracker that says what each document proves and what it does not. Record the official name, activity, location, issuer, risk level, status, prerequisites, operational and commercial boundary, evidence, expiry or review date, reporting duty, owner, and change trigger. The incorporated/licensed/tax/bank status matrix helps prevent a completed corporate step from being misrepresented as completion of a separate operating gate.

In this article

• Map real activities and locations to licensing records
• Decode each status and operating boundary
• Assign evidence, renewal, and reporting controls
• Operate a go/no-go and change gate
• Official references and review basis
• The license evidence gate before a PT PMA starts or expands operations

Key takeaways

• Map each real activity and location to the exact KBLI and current risk-based licensing path.
• Distinguish issued, unverified, verified, fulfilled, effective, conditional, expired, suspended, and revoked states.
• Attach source evidence, named owners, renewal dates, reports, inspections, and change triggers.
• Use a documented go/no-go gate before the first sale, new site, product, process, or expansion.

Map real activities and locations to licensing records

Inventory what the PT PMA will actually do, not only what appears in its company purpose. Describe products and services, customers, delivery method, facilities, equipment, imports or exports, storage, manufacturing or processing, professional or technical activity, online channel, environmental and building use, employee and foreign-worker needs, and every operating location. Map each activity to the current five-digit KBLI and confirm whether supporting or auxiliary activities need separate treatment.

Government Regulation 28 of 2025 is the current central framework for risk-based business licensing and replaced Government Regulation 5 of 2021. BKPM also announced OSS adjustments aligned with the new regulation. Historic articles, screenshots, consultant templates, and an older OSS output may therefore be incomplete. Verify the live system and current sector rules on the decision date, and record who performed the check.

Create an activity-to-permission matrix with one row per KBLI and location. Include the company, project, address, risk level, NIB, standard certificate or permit, supporting approvals, technical standards, issuer, verification state, current evidence, operational boundary, and unresolved question. Use the license-by-business-activity guide for mapping discipline, then validate every conclusion officially.

Decode each status and operating boundary

For every license output write a plain-language status memo: what authority issued it, which entity, KBLI, project and location it covers, current risk level, whether standards are self-declared or verified, what conditions remain, whether preparation, construction, testing, operational, or commercial activity is allowed, and what event would suspend or invalidate reliance. Have Indonesian licensing counsel or the responsible authority confirm ambiguous language.

BKPM's 2026 explanation of the KLIK policy illustrates why status language matters: medium-high standard certificates shown as unverified and high-risk permits shown as not fulfilled may support preparation or construction in the described context, while operational and commercial activity still depends on fulfilled standards. Do not generalize KLIK or any facilitation policy to an unqualified project; use it as a reminder to verify the exact boundary.

Attach screenshots or exports with retrieval date, official document, verification result, correspondence, inspections, certificates, technical evidence, and review memo to the tracker. Do not overwrite an old status; retain history so management can see what changed. The first-payment critical path should remain blocked until the operating status, tax, invoice, bank, and contract controls are all ready.

Assign evidence, renewal, and reporting controls

Turn every condition into a task with an accountable business owner and evidence owner. Record submission lead time, authority processing dependency, inspection, professional certificate, premises document, product evidence, environmental or building record, recurring report, fee, expiry, renewal window, and escalation. Use calendar dates plus event triggers because some permissions change when the company changes activity, address, capacity, product, ownership, management, project stage, or technical process.

Review the tracker monthly during setup and at a risk-based frequency after go-live. Compare live OSS and sector status with the stored record; test that expiry reminders work; verify responsible users and credentials; inspect rejected or returned submissions; and confirm that operating evidence remains true. A certificate can be current while the premises, responsible professional, process, or product no longer matches its basis.

Connect licensing to contracts, procurement, site work, hiring, import, invoice release, sales, and payment collection. No department should infer readiness from a company-registration email. If an approval is delayed, define which preparatory actions remain lawful, which commitments must be conditional, and who can issue a go/no-go decision. The broader PT PMA business-license guide can support that governance design.

Operate a go/no-go and change gate

Before first operation or commercial activity, the responsible executive should approve a gate covering exact activity and location, corporate authority, current OSS and sector statuses, fulfilled standards and permits, premises and technical evidence, tax and invoicing readiness, bank collection, contracts, people, reporting calendar, and outstanding conditions. Legal or licensing reviewers should state assumptions and limitations. A conditional approval must define what is allowed, what is prohibited, and when it expires.

Repeat the gate before adding a product, service, channel, facility, city, project, capacity, equipment, import route, professional activity, or customer promise that changes the factual licensing map. Route marketing and sales descriptions through the activity owner so commercial language does not expand beyond permissions. Stop or contain activity when a required status expires, is suspended, becomes inaccurate, or cannot be evidenced.

Close each review with a signed status snapshot and exception log. Management should see red items, business impact, interim controls, authority dependency, owner, and resolution date. Never relabel an authority-dependent requirement as low risk merely because revenue is urgent. The defensible result is a current, traceable decision record that distinguishes company existence from lawful operation.

Official references and review basis

The following primary sources were checked on August 1, 2026. They establish the regulatory or service boundary used in this article; bank, tax office, OSS, AHU, and immigration decisions can still depend on the current record and the facts of a particular application.

• BPK — Government Regulation 28 of 2025 — Official legal portal for the current risk-based business licensing regulation, effective in 2025.
• OSS — Risk-based business licensing — Primary portal describing NIB and the four risk levels and providing current company licensing access.
• BKPM — OSS adjustment to PP 28/2025 — Official 2026 announcement on OSS alignment with the current regulation.
• BKPM — KLIK and operational status explanation — Current official example distinguishing preparatory access from fulfilled standards for operation.

The license evidence gate before a PT PMA starts or expands operations

The go-live file should connect each actual activity and location to current KBLI, risk level, NIB, standard certificate or permit, verification or fulfillment state, supporting approvals, premises and technical evidence, reporting duties, and named owners. It should explicitly state the operational and commercial boundary and keep authority-dependent conditions open until reliable evidence closes them.

Because licensing varies by sector, location, project, risk level, scale, product, and current regulation, qualified Indonesian advisers and responsible authorities should validate the matrix. Management should prevent contracts, marketing, hiring, procurement, invoicing, and payment collection from outrunning that evidence. Repeat the decision whenever the facts change, not only when a printed document expires. For a new entrant, connect the license matrix to the full Indonesia company registration and activation route .

Related insights

• Incorporated, licensed, tax-active, bank-ready matrix
• Business license guide for PT PMA
• Indonesia license by business activity
• First-payment critical path