Treasury architecture

PT PMA Multi-Bank Strategy: Operating, FX, Payroll, and Contingency Accounts

A decision framework for allocating collections, payments, foreign exchange, payroll, capital, and emergency continuity across one or more Indonesian banks.

By Elara Vance Updated July 31, 2026 5-minute read

A PT PMA should add a second bank only when a specific business function or continuity risk justifies the extra KYC, fees, users, tokens, reconciliations, and fraud surface. One bank can be sufficient for a simple domestic operating model, while multiple relationships may be justified for foreign exchange, customer collections, payroll, lender requirements, geographic service, product capability, or contingency access. The architecture should assign each account a purpose, permitted transaction types, funding rule, minimum and maximum balance, signers, system roles, statement owner, and closure trigger.

The strategy must reflect real projected transactions, not an attempt to avoid a bank’s questions or split activity to make monitoring harder. OJK Regulation No. 8 of 2023 requires financial institutions to conduct customer due diligence and ongoing monitoring; each bank relationship therefore needs a consistent ownership, business, source-of-funds, and transaction narrative. The PT PMA should approve a primary operating route first, then open additional accounts only after the control and reconciliation owner can support them.

Functions that may justify a separate bank or account

Separation is useful when it creates a clear control or capability. It is harmful when balances, mandates, credentials, and explanations become fragmented.

Function	Possible reason to separate	Control question
Primary operating	Core collections and supplier payments	Can the bank support required channels and limits?
Foreign exchange	Currency accounts, trade or cross-border execution	Are pricing, cut-offs, evidence, and users suitable?
Payroll	File integration and employee payment cycle	Who validates changes and releases the file?
Customer collections	Virtual accounts, merchant or sector product	Can receipts be identified and reconciled?
Capital and financing	Incoming equity, debt, lender covenant	Does the narrative match company records?
Contingency	Outage, token loss, frozen access, concentration	Is it tested, funded, and governed without evasion?

Key takeaways

Open an additional account for a defined capability or continuity need, not because more banks appear safer.
Each bank should receive a truthful and consistent ownership and business narrative.
Account purpose and permitted transaction types belong in the board mandate and treasury policy.
More accounts create more KYC refresh, token, user, fee, reconciliation, and cyber risks.
A contingency account is useful only when access, funding, approval, and test transactions are maintained.

Map transaction functions before selecting banks

The PT PMA should list the actual flows it expects during the next twelve to eighteen months before selecting banks: paid-up capital, shareholder loans, customer receipts, domestic suppliers, taxes, payroll, rent, cards, foreign-currency payments, imports, exports, and related-party transfers. Each flow needs countries, currencies, values, frequency, cut-off, supporting evidence, and approval roles.

A functional map prevents the company from choosing a bank based only on brand or opening convenience. It reveals whether one institution can support the required account, FX, payroll, collection, digital approval, and service model or whether a specialist second relationship is warranted. Projected activity should remain distinguishable from committed contracts and should agree with the KBLI and current license state.

Control point

Choose the account architecture only after every high-value flow has a destination account and operating owner.

List transaction type, counterparty, country, currency, value, and frequency.
Identify required products such as virtual accounts, payroll, FX, or trade services.
Define cut-offs, statements, reconciliation data, and service escalation needs.
Map each flow to licensed activity and approved company purpose.

Use the PT PMA bank requirements guide to test whether the opening file supports the mapped functions.

Set the primary operating and collection route

The primary bank should receive the majority of routine collections and support authorized domestic payments, taxes, statements, and treasury controls. The decision should consider branch and digital service, product capability, approval limits, integration, data quality, fees, account support, and the bank’s willingness to understand the actual foreign-owned business. The easiest account to open is not necessarily the best operating account.

Published product pages from BNI , Bank Mandiri , and BCA illustrate different public requirements and product features, but the PT PMA should obtain current bank and branch information for its requested facilities. Compare the same transaction scenario and user matrix with every candidate instead of comparing only account-opening lists.

Release test

Approve one primary route with a documented service and control score before distributing flows elsewhere.

Test collections, payments, tax, statements, alerts, and user administration.
Confirm limits, approval combinations, cut-offs, and escalation contacts.
Compare data export and reconciliation identifiers.
Document pricing and service assumptions without treating them as guaranteed.

Read the PT PMA bank support cost guide when estimating the implementation effort.

Compare a second bank against its control cost

Test capability, KYC, users, tokens, interbank funding, reconciliation, fees, and measurable resilience benefit.

Decide whether FX and payroll need separation

A separate FX or payroll relationship is justified when it materially improves execution, control, data, resilience, or required product access. It is not justified solely by an assumed exchange-rate advantage or because payroll data feels separate. The PT PMA should compare total execution, evidence, cut-offs, approval, file security, reconciliation, and KYC work across the proposed arrangement.

For FX, assess supported currencies, conversion workflow, pricing basis, value dates, payment evidence, cut-offs, and who can quote and release. For payroll, assess file preparation, employee change controls, maker-checker approval, confidentiality, rejection handling, and reconciliation. Moving funds between banks adds another transaction, cut-off, fee, and evidence link.

Stop condition

Separate a function only when the control owner can state the measurable benefit and operate the interbank funding rule.

Model expected transaction volume and the full cost of execution.
Separate quote authority from payment release where feasible.
Protect payroll files, employee changes, and rejected-payment data.
Set interbank funding limits and avoid unexplained round-sum sweeps.

Use the bank evidence guide to keep interbank flows consistent with the KYC narrative.

Build contingency without using it to bypass controls

A contingency account can support business continuity after a platform outage, token loss, cyber incident, mandate update, service failure, or bank-specific restriction. It must not be used to route transactions a primary bank questioned, conceal activity, or avoid a lawful review. The PT PMA should disclose the business purpose truthfully to each bank and maintain complete records across the architecture.

The fallback needs an active mandate, current KYC, tested credentials, a controlled balance or funding procedure, beneficiary setup, payment limits, statements, and a clear activation authority. A dormant account with an expired token or departed user is not continuity. The treasury policy should define which events permit activation and who informs management, banks, customers, and suppliers.

Record standard

Test the contingency route periodically with a low-risk transaction and close every exception it reveals.

Define activation events and prohibited uses.
Maintain current signers, users, tokens, contacts, and KYC documents.
Pre-approve essential beneficiaries and emergency payment limits.
Reconcile and report all fallback transactions to the primary treasury view.

Read the bank delay guide before treating a second bank as a shortcut for an unresolved KYC issue.

Govern all accounts through one treasury register

The PT PMA should maintain one board-approved register for every bank, account, currency, purpose, signer, digital user, token, limit, statement feed, balance owner, KYC date, fee, and closure status. Central visibility is essential even when different teams operate payroll, collections, or foreign exchange. No local user should open, repurpose, or abandon an account outside the register.

The monthly treasury close should reconcile all balances and interbank transfers, confirm that account activity fits the approved purpose, review dormant or unusual accounts, and track KYC and mandate changes. User access should be recertified after staff, director, shareholder, or role changes. Management should close relationships whose capability no longer justifies their control burden.

Decision rule

Approve the multi-bank architecture only when one owner can demonstrate complete account, access, and cash visibility.

Record account purpose and permitted transaction types.
Inventory signers, makers, checkers, releasers, administrators, and token custodians.
Reconcile interbank transfers as linked transactions.
Review fees, dormant balances, KYC refreshes, and closure triggers quarterly.

Connect the register with the PT PMA compliance calendar and board risk reporting.

Place this decision inside HSJGlobal’s Indonesia company registration scope before executing documents, filings, or funding.

Regulatory Notes and Limitations

This framework does not recommend a particular bank or number of accounts. Product availability, prices, branch procedures, risk appetite, verification, account approval, and transaction execution depend on current bank decisions and the PT PMA’s facts.

Multiple banks do not reduce the duty to provide accurate ownership, beneficial-owner, business, and transaction information to each institution.
A contingency account should not be used to evade a hold, inquiry, sanction, license restriction, or customer due diligence review.
Additional accounts increase cyber, credential, reconciliation, fraud, fee, and KYC-refresh obligations.
The account mandate and digital user design should remain consistent with the deed and corporate resolutions.

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.

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.
Bank Mandiri Giro requirements : Published corporate current-account documents, identity, authority, and power-of-attorney conditions.
BCA Current Account requirements : Published corporate account, representative, power-of-attorney, management, shareholder, NIB, and license requirements.
Limited Liability Company Law No. 40 of 2007 : Company-law framework for shares, capital, corporate organs, records, and authority, as amended.

Approve a PT PMA banking architecture, not a collection of accounts

Start with transactions and controls. Give each account a specific capability, truthful bank narrative, operating owner, permitted flow, access model, reconciliation feed, and closure test. One capable bank may be sufficient; a second relationship must earn its cost through a real function or continuity benefit.

Stop account proliferation when no one owns the complete register or when a new bank is proposed to avoid an unresolved question. Fix the underlying KYC, licensing, authority, or transaction issue before duplicating it across institutions and test the approved fallback route.

Create one treasury view across all accounts

Frequently asked questions

How many bank accounts should a new PT PMA open?

There is no universal number. Start with the minimum architecture that supports real collections, payments, currency, payroll, and control needs, then add a relationship only for a documented capability or continuity reason.

Should paid-up capital use a separate account?

Confirm the selected bank and company’s accounting and control design. Whether separate or combined, the capital receipt and permitted uses must remain traceable and consistent with corporate records.

Is a second bank a solution when the first bank asks KYC questions?

Not by itself. Resolve the underlying ownership, business, source-of-funds, authority, or transaction issue. Do not use another institution to conceal or bypass a lawful review.

What makes a contingency account operational?

It needs current KYC and mandate, tested access, users and tokens, controlled funding, essential beneficiaries, limits, statements, an activation policy, and periodic test evidence.

Can payroll and FX users have different bank roles?

Yes, subject to the bank’s systems and a valid corporate mandate. Define maker, checker, releaser, administrator, quote, and view rights by function and recertify them when personnel change.