Critical Path from PT PMA Licensing to the First Customer Payment

A PT PMA should set its first customer payment date by working backward from one defined transaction, not by adding generic days after incorporation. The company must know which legal entity will contract, which five-digit KBLI and project location cover the activity, which risk-based license state permits the promised operation, what must be delivered or accepted, how the invoice and tax treatment will work, and which company bank account can receive and identify the funds. Government Regulation No. 28 of 2025 and the official OSS portal make the activity’s risk level central to the required licensing products.

An NIB may be sufficient for a low-risk activity but does not prove that every medium-high or high-risk activity is ready to operate; the actual Standard Certificate, verification, permit, basic requirement, and sector conditions must be checked. A bank account number also does not prove that collections, currencies, virtual accounts, limits, statements, and user controls are active. Management should issue a first-transaction readiness certificate only when the license, contract, invoice, delivery, collection, tax, accounting, and evidence owners have each signed their gate.

Key takeaways

• Use one real first transaction to define the readiness path.
• License readiness depends on the exact activity, location, risk level, and required status.
• Contract signing, invoicing, delivery, and collection can have different release dates.
• Test the expected currency and collection reference before the customer pays.
• Record a stop owner for every gate rather than letting sales assume that incorporation means readiness.

In this article

• Define the first transaction
• Verify the license gate
• Release contract and invoice steps
• Regulatory Notes and Limitations
• Official References and Review Basis
• Test the collection route
• Issue the readiness certificate
• Release the first PT PMA invoice only when the license-to-cash path is complete

First customer payment release gates

The transaction may move only as fast as its last blocking gate. Parallel preparation is useful, but signing or invoicing should not assume an unresolved operating condition.

Define the first customer transaction precisely

The PT PMA should describe the first transaction in one page: customer legal name and country, product or service, KBLI activity, project location, contract entity, currency, value, signing date, invoice trigger, delivery or performance, acceptance, tax document, payment terms, receiving account, and evidence of completion. A generic goal to ‘start sales’ cannot identify the licenses and controls required.

The transaction sheet should distinguish confirmed facts from assumptions and show which team owns each field. Sales may own the customer need, but legal, licensing, tax, finance, and operations must confirm their respective release conditions. If the first transaction changes, the critical path should be recalculated instead of carrying forward the old readiness date.

• Name the contracting entities and authorized signers.
• Describe deliverables, location, acceptance, and customer dependencies.
• Record currency, payment method, value, timing, and collection reference.
• Identify tax, customs, sector, data, employment, or premises inputs as applicable.

Use HSJGlobal’s Indonesia company registration scope when the transaction reveals a deed, KBLI, location, or license gap.

Verify the operational license gate for the promised activity

The licensing owner should confirm the risk level and current operational status for the exact KBLI-location activity. The OSS portal explains that four risk levels determine required licensing and obligations; official OSS guidance distinguishes NIB-only low-risk outcomes from higher-risk cases involving Standard Certificates, verification, or permits. The PT PMA should also verify basic and sector-specific requirements that condition operation.

The evidence should show the issued product, status, effective entity, location, scope, capacity, conditions, validity, and any pending verification. A screenshot of an OSS dashboard or an NIB that lists the KBLI is not enough if another document or condition must become effective before the promised activity. Counsel or the relevant specialist should address uncertain sector boundaries.

• Confirm five-digit KBLI, activity description, risk level, and project location.
• Identify NIB, Standard Certificate, verified status, permit, and PB UMKU as applicable.
• Check spatial, environmental, building, facility, personnel, and sector conditions.
• Record restrictions, capacity, validity, and ongoing obligations affecting the transaction.

Read the Indonesia registration process guide for the wider entity-to-license path.

Make the contract, invoice, and delivery sequence lawful

The PT PMA should separate authority to sign, license readiness to perform, invoice issuance, and the evidence that triggers payment. A contract may be signed before full operation only if its terms, conditions precedent, representations, and planned performance are lawful and accurately disclose the readiness state. The company should not state that a permit is effective when verification remains pending.

Legal and tax owners should confirm entity names, signers, scope, price, currency, tax allocation, invoice fields, withholding, payment terms, acceptance, cancellation, and dispute provisions. Operations should confirm that the company can deliver and preserve evidence. The release matrix can allow preparation while preventing performance or invoicing before the required gate.

• Match contract scope to licensed activity and project location.
• Use current signatory authority and company details.
• Define invoice and tax document fields before customer onboarding closes.
• Create delivery, service, acceptance, and change-control evidence.

Connect the contract sequence with the post-registration steps guide .

Regulatory Notes and Limitations

The earliest lawful transaction date depends on the exact KBLI, location, risk level, sector, license conditions, contract, tax treatment, bank facilities, and operating facts. This page does not establish a universal post-registration timeline.

• An NIB is not proof that every higher-risk activity has completed verification or received its required permit.
• A bank account number does not prove that all currencies, collections, limits, or digital controls are active.
• Contract signing and performance may have different legal and license gates; conditions and representations must be accurate.
• Tax, customs, sector, data, employment, and premises requirements should be added where the first transaction triggers them.

Official References and Review Basis

Primary materials were checked on July 31, 2026. These links support the regulatory and banking framework used in this article; they do not replace a matter-specific legal, tax, licensing, accounting, security, or bank review.

• Government Regulation No. 28 of 2025 : Current risk-based business licensing framework and official unofficial English translation.
• Ministry of Investment and Downstream Industry/BKPM Regulation No. 5 of 2025 : Current investment-value, paid-up capital, capital-use, OSS, and LKPM framework.
• Online Single Submission risk-based licensing portal : Official explanation that four risk levels determine the business licensing and obligations to be fulfilled.
• OJK Regulation No. 8 of 2023 : Customer due diligence, beneficial-owner review, ongoing monitoring, and electronic verification framework.
• BNI Giro corporate-account requirements : Published checklist covering the deed, NIB, NPWP, management composition, authorized official, and initial deposit.
• BCA Current Account requirements : Published corporate account, representative, power-of-attorney, management, shareholder, NIB, and license requirements.

Activate and test the customer collection route

The receiving account should belong to the PT PMA and support the customer’s currency, country, payment method, reference, and expected value before the invoice is released. The bank’s KYC narrative should already include the legitimate transaction type, and the account should have active statements, alerts, reconciliation access, and authority. A customer payment routed through a director, provider, affiliate, or foreign parent can create contract, tax, accounting, and KYC mismatches.

Published corporate requirements from BNI and BCA are account-opening baselines, while collection products and limits require current bank confirmation. Finance should run a low-value test or bank-accepted validation of account data and reference fields, then give the customer one controlled instruction. Changes to beneficiary details should use fraud-resistant verification.

• Confirm legal beneficiary, account, bank, currency, and payment reference.
• Test statement access, alerts, remittance data, and reconciliation owner.
• Verify limits, cut-offs, fees, FX, and returned-payment process.
• Use controlled customer verification for any bank-detail change.

Use the company bank evidence guide to align customer onboarding with the bank file.

Issue a first-transaction readiness certificate

The PT PMA should release its first transaction through a short internal certificate signed by the owners of entity and authority, license, contract, tax and invoice, operations and delivery, bank collection, accounting, and evidence retention. The certificate should name the exact transaction and date, not claim that the company is ready for every future activity.

Open conditions should be classified as blocking, permitted with an approved condition, or post-transaction follow-up. Any exception should identify the decision owner, legal or operational basis, expiry, and evidence. After the customer pays, finance should close the receivable against the bank statement and remittance, record FX and fees, confirm tax and delivery evidence, and feed lessons into later transactions.

• Record the transaction version, customer, scope, value, and planned dates.
• Require named sign-off for each readiness gate.
• List approved conditions and stop triggers with expiry dates.
• Close the first receipt, ledger, tax, delivery, and evidence exceptions.

Link the certificate to the PT PMA compliance calendar so the first sale enters ongoing reporting and control.

Release the first PT PMA invoice only when the license-to-cash path is complete

Work backward from one actual customer transaction. Confirm that the PT PMA, KBLI-location activity, operational license, contract authority, invoice and tax setup, delivery evidence, and bank collection route all support the promised sequence.

Do not let incorporation date or account number become a substitute for readiness. Issue the invoice through a transaction-specific sign-off, preserve stop conditions, and close the first receipt through the bank, ledger, tax, delivery, and evidence records.

Related insights

• Indonesia registration process
• Post-registration steps
• Indonesia company bank evidence