PT PMA Address-to-License Reconciliation After Setup

A PT PMA should reconcile each address by function: legal domicile, administrative office, OSS project location, operating site, tax place of business, bank KYC address, and contract notice address. Government Regulation No. 28 of 2025 links licensing to activities and requirements, while local spatial and building rules apply to the actual site. One valid registered-office document does not prove every operational use.

Run the review after setup and whenever the company, provider, premises, activity, or project changes. Map each record to the physical or administrative function it represents, preserve leases and owner evidence, and flag conflicting street formats, units, postal codes, or geospatial points. Correct the authoritative source first and treat operational site issues as licence blockers rather than cosmetic address updates.

Pt pma address-to-licence reconciliation decision controls

Use the control, evidence, and release condition together; no single document should carry more meaning than it actually proves.

Key takeaways

• Do not reconcile until each address has a defined function and owner.
• Block unsupported physical use until site evidence and required approvals are resolved.
• Treat each activity-location mismatch as a separate correction and operating decision.
• Close each downstream change through its own acceptance process.
• Close only from a reconciled address-function matrix and exception schedule.

In this article

• Inventory address functions
• Test physical-site evidence
• Reconcile licence locations
• Align downstream addresses
• Regulatory Notes and Limitations
• Official References and Review Basis
• Close the reconciliation
• Operate from addresses whose functions and licences are reconciled

Inventory every address and its function

The responsible team should list legal, administrative, operational, tax, bank, contract, warehouse, and project addresses separately. For inventory every address and its function, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.

Using one master field can hide sites with different regulatory purposes. A reviewer should trace address-function register and current deed and ahu to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For inventory every address and its function, the evidence file for this stage should let a new reviewer reproduce the decision without asking the original provider what happened. It should connect address-function register with current deed and ahu, then show how oss project list and tax, bank, and contract records affect the next approval. Record the source for address-function register, the reviewer of current deed and ahu, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

• Address-function register
• Current deed and AHU
• OSS project list
• Tax, bank, and contract records

For inventory every address and its function, preserve the source record, reviewer, date, exception, and approval so another team can reproduce the decision without relying on memory.

Test site, zoning, and building evidence

A supportable decision begins when the company can match operational addresses to the parcel, permitted use, building function, lease rights, and activity. For test site, zoning, and building evidence, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.

A registered address can be real yet unsuitable for the operation conducted there. A reviewer should trace parcel and local spatial evidence and pbg or slf as applicable to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For test site, zoning, and building evidence, operational ownership matters here because the same fact may be presented differently in corporate, licensing, tax, bank, contract, and site records. It should connect parcel and local spatial evidence with pbg or slf as applicable, then show how lease and owner authority and operational activity and scale affect the next approval. Record the source for parcel and local spatial evidence, the reviewer of pbg or slf as applicable, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

• Parcel and local spatial evidence
• PBG or SLF as applicable
• Lease and owner authority
• Operational activity and scale

For test site, zoning, and building evidence, turn the result into a controlled work item with a responsible person, due date, evidence location, escalation path, and release condition.

Reconcile OSS projects and licence conditions

Before the next commitment, management should compare every KBLI-location project, risk output, licence, verification, and condition with the actual site. For reconcile oss projects and licence conditions, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.

A correct entity address does not cure a wrong project pin or licence location. A reviewer should trace live oss project exports and kbli and risk output to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For reconcile oss projects and licence conditions, 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 live oss project exports with kbli and risk output, then show how licence and verification records and site-specific supporting approvals affect the next approval. Record the source for live oss project exports, the reviewer of kbli and risk output, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

• Live OSS project exports
• KBLI and risk output
• Licence and verification records
• Site-specific supporting approvals

For reconcile oss projects and licence conditions, record both the accepted position and the rejected alternatives; this prevents a later portal edit or provider message from silently changing the decision. For the adjacent control framework, compare PT PMA Registered Address Requirements in Indonesia .

Align tax, bank, and transaction records

The control file must show how the company will compare Coretax, KPP, bank KYC, invoices, contracts, payroll, insurance, and correspondence with the approved address map. For align tax, bank, and transaction records, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.

Other systems may retain old addresses and affect notices, tax office, KYC, or customer checks. A reviewer should trace coretax and kpp data and bank kyc acceptance to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For align tax, bank, and transaction 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 coretax and kpp data with bank kyc acceptance, then show how invoice and contract masters and insurance and notice records affect the next approval. Record the source for coretax and kpp data, the reviewer of bank kyc acceptance, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

• Coretax and KPP data
• Bank KYC acceptance
• Invoice and contract masters
• Insurance and notice records

For align tax, bank, and transaction 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.

Regulatory Notes and Limitations

PT PMA Address-to-License Reconciliation After Setup 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 PT PMA Address-to-License Reconciliation After Setup, address acceptability depends on the real activity, local spatial plan, building use, lease rights, sector rules, and the specific government or counterparty record being updated.
• For PT PMA Address-to-License Reconciliation After Setup, a corporate domicile, administrative office, warehouse, restaurant, factory, project site, and tax place of business can require different evidence and should not be treated as interchangeable.
• For PT PMA Address-to-License Reconciliation After Setup, local rules and official spatial data should be checked for the precise parcel and intended use immediately before signing or filing.

Official References and Review Basis

Primary materials for PT PMA Address-to-License Reconciliation After Setup 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 PT PMA Address-to-License Reconciliation After Setup.

• 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.
• Directorate General of Taxes guidance on address changes : Official explanation of changing address data versus moving the registered tax office.
• Directorate General of Taxes taxpayer-data change service : Official scope and supporting-document route for company and address data changes.
• Government Regulation No. 16 of 2021 : Building approval, technical standards, and building fitness framework.

Approve corrections and recurring monitoring

For PT PMA address-to-licence reconciliation, sequence corrections, capture before-and-after evidence, and schedule expiry and change triggers. For approve corrections and recurring monitoring, the same street address can be acceptable for one administrative purpose and unsuitable for a particular operational activity, building use, or local spatial rule.

One-time correction decays when leases, providers, activities, or sites change. A reviewer should trace correction sequence and acceptance receipts to current authoritative records and actual operating evidence, rather than a copied template, provider promise, or unexplained portal label.

For approve corrections and recurring monitoring, implementation should convert this stage into a dated control record rather than a conversation summary. It should connect correction sequence with acceptance receipts, then show how lease and licence calendar and signed exception and close memo affect the next approval. Record the source for correction sequence, the reviewer of acceptance receipts, the decision date, any unresolved exception, and the acceptance evidence so later changes preserve the original reasoning.

• Correction sequence
• Acceptance receipts
• Lease and licence calendar
• Signed exception and close memo

For approve corrections and recurring monitoring, the output should name the owner, source evidence, unresolved condition, acceptance test, and the event that permits the next step. Where this stage changes another workstream, review PT PMA Address Requirements for Bank Account Opening .

Place the pt pma address-to-licence reconciliation decision inside HSJGlobal’s Indonesia company registration scope before executing documents, filings, or funding.

Operate from addresses whose functions and licences are reconciled

A PT PMA can legitimately use different addresses for different purposes, but each function must be explicit and supported. Reconcile the corporate, project, tax, bank, contract, and physical-site records instead of forcing them into one unexplained field.

Keep the matrix current through lease, provider, activity, and project changes and block only the unsupported use while corrections are completed.

Related insights

• PT PMA Registered Address Requirements in Indonesia
• PT PMA Address Requirements for Bank Account Opening
• Changing a PT PMA in Indonesia