PT PMA Customer Payment Readiness: Account, Invoice, Tax, and Ledger Controls

Design customer payment collection around the PT PMA's own records

A newly registered PT PMA should collect revenue into an account held in its exact legal name unless a documented and lawful payment structure requires otherwise. Before accepting funds, align the contract party, licensed activity, bank account, invoice issuer, tax status, currency, payer identity, settlement provider, refund obligation, and ledger treatment. Using a founder's personal account or an unrelated agent can obscure ownership of funds and complicate KYC, tax, audit, consumer, and dispute evidence. For the payment-collection readiness, the immediate acceptance point is to identify the legal flow against the documented seller, customer, product, price, currency, and refund terms.

For cards, gateways, marketplaces, virtual accounts, or overseas collection, document who is merchant of record, who contracts with the customer, who bears chargebacks and refunds, when title or service performance occurs, how fees and withholding are recorded, and how settlement is reconciled. Test one transaction from order to bank, tax document, ledger, refund, and management report before scaling the channel. Within the payment-collection readiness file, the responsible officer should preserve account owner, merchant of record, settlement, fees, and access as evidence for the decision to control the money.

Prepare for the bank's independent KYC and account decision

A corporate bank account is not issued automatically because the PT PMA has an AHU approval, NPWP, or NIB. The bank independently assesses the company, beneficial owners, shareholders, directors, signatories, business purpose, licenses, address, contracts, expected transactions, currencies, source of funds and wealth, tax residence, sanctions and risk factors, and original-document or presence requirements. Criteria can differ by bank and branch. For the payment-collection readiness, the immediate acceptance point is to complete KYC against the documented UBO, shareholders, directors, and signatories.

Build one KYC file that reconciles the executed deed, AHU corporate output , tax data, OSS licenses, UBO report, ownership chart, passports, corporate-shareholder documents, address evidence, business plan, contracts, and funding narrative. Ask the chosen bank for current requirements in writing, but preserve a fallback institution and visit plan. Before the first remittance, approve signatory combinations, online access, token custody, payment limits, beneficiary controls, accounting evidence, and how paid-up capital will be described and used. Within the payment-collection readiness file, the responsible officer should preserve access, limits, funding, and evidence as evidence for the decision to control before deposit.

Build one invoice release rule for commercial and tax records

A commercial invoice should be generated from the approved contract and delivery facts, while any tax invoice follows the applicable tax status and current Coretax DJP procedure. The company should not let sales staff copy an old template and change only the amount. Legal name, address, NPWP, customer identity, description, quantity, service period or delivery date, currency, bank details, withholding terms, VAT treatment, and references must be validated before release. For the payment-collection readiness, the immediate acceptance point is to keep one traceable history against the documented original, replacement, credit, payment, and journal.

Assign separate checks for contract performance, commercial billing, VAT, withholding, foreign-currency conversion, and revenue recognition. A customer request to omit information, backdate a document, split a transaction, change the supplier name, or pay another account should enter an exception process. Corrections should connect the original invoice, credit note or replacement, payment, tax document, ledger journal, customer acknowledgement, and approval. Within the payment-collection readiness file, the responsible officer should preserve contract, delivery, description, amount, currency, and payee as evidence for the decision to approve the receivable.

The payroll owner can incorporate the evidence gates from the PT PMA monthly tax close to reconcile withholding, payment, return, and ledger before sign-off.

Reconcile tax, bank, and ledger records before they diverge

A bank statement records cash movement; it does not determine the legal or tax character of the transaction. The PT PMA should reconcile each material receipt and payment to the contract, invoice, withholding evidence, VAT document where applicable, ledger account, counterparty identity, exchange rate, and supporting approval. Tax administration now uses Coretax DJP , so inconsistent names, tax identifiers, periods, or transaction classifications can affect filing as well as bank review. For the payment-collection readiness, the immediate acceptance point is to resolve mismatches against the documented legal name, NPWP, bank account, and counterparty.

Create an exception queue for shareholder funding booked as revenue, loans booked as capital, third-party collections, personal reimbursements, net settlements, intercompany charges, refund chains, and transfers without a clear counterparty. Correct the underlying document and accounting treatment before merely editing a narrative. Preserve the bank reference, tax document, journal, approver, correction reason, and any amended return or invoice so the audit trail remains intelligible. Within the payment-collection readiness file, the responsible officer should preserve contract, invoice, tax, and ledger treatment as evidence for the decision to use one supported character.

Test the company before its first commercial transaction

Legal incorporation is only one readiness state. The company may still need verified OSS outputs, sector or supporting permits, tax access, PKP analysis, accounting and invoice controls, payroll arrangements, a bank account, premises evidence, and recurring reporting ownership before it can execute the planned transaction. Each state should be independently evidenced. For the payment-collection readiness, the immediate acceptance point is to activity can proceed under conditions against the documented applicable OSS and tax outputs.

Use DGT registration guidance for the tax registration workstream and Government Regulation 28 of 2025 for the licensing baseline. Build a first-transaction test covering authority, contract, invoice, tax, payment, license, delivery, accounting entry, and reporting. Do not let a certificate date become the commercial launch date unless every required control passes. Within the payment-collection readiness file, the responsible officer should preserve bank, people, premises, controls, and reporting as evidence for the decision to first transaction can be executed.