Mastercard’s SME findings put payment complexity under the spotlight

The announcement

Mastercard’s 16 September 2026 Asia Pacific release presents findings from its Dreamonomics report and describes a One Credential pilot with City Union Bank in India. The company reports that 74% of surveyed Asia Pacific SMEs consider integrated business tools critical. It also says respondents use an average of four payment methods for business expenses. The report is company commissioned research, and its regional findings should not be treated as a description of every small business.

The merchant analysis below focuses on the operational question behind the announcement: how to keep payment choice from creating administrative confusion. It does not assess the suitability of a particular bank product or assume the pilot is available to every merchant. The suggestions are a framework for examining an individual business’s own processes.

More options can create more work

A small business may add a payment tool to solve a specific problem: paying a foreign supplier, separating employee expenses or collecting from a new customer group. Each addition can be reasonable in isolation. The difficulty emerges when no one maintains a complete view of how the tools interact. Finance staff then spend time identifying transfers, matching records and explaining discrepancies across several systems.

The starting point is a payment inventory. List every account, card, gateway and business payment service in use, alongside its purpose and owner. Record which legal entity holds the relationship and which team has access. The exercise is useful even if the company makes no immediate changes. It reveals unused arrangements, duplicated responsibilities and essential processes known only to one employee.

The inventory should distinguish incoming customer payments from business expenditure. A provider that simplifies staff spending does not automatically improve merchant acquiring, and a new checkout option does not necessarily solve supplier payment reconciliation. Keeping those purposes separate makes it easier to evaluate products on the problems they actually address.

A connected view starts with consistent records

Integration is valuable only when the underlying information can be interpreted consistently. If one system records a trading name, another a legal entity and a third an informal abbreviation, a dashboard may simply display conflicting versions of the same business. Merchants should agree on reference formats and core identifiers before expecting software to reconcile everything automatically.

A practical example is the relationship between an order, its invoice and the resulting payment. Those records should remain connected when an order is partly fulfilled, adjusted or refunded. Staff should not have to guess which receipt belongs to which customer. The goal is a process that remains understandable when the person who originally handled the transaction is away.

For outgoing payments, the equivalent question is whether a finance reviewer can identify what was bought, who approved it and which business entity incurred the expense. Combining information from multiple funding sources can be useful, but the reporting must preserve those distinctions. A convenient payment experience should not blur accountability in the company’s own books.

Cash visibility is a management discipline

A merchant’s displayed balances may not all represent money available for the same purpose or at the same time. Businesses should define the figures they use in cash planning and understand how those figures are produced. An operational forecast should connect expected receipts, scheduled obligations and known adjustments, with unresolved items clearly identified rather than silently assumed to be available.

A suggested weekly review can be simple. Finance and operations examine receipts that have not matched an order, overdue customer balances, pending refunds and supplier payments awaiting approval. Each exception receives an owner and a next action. The aim is to prevent small unexplained differences from accumulating until they become a major month end exercise.

Management should also identify which decisions require a current cash view. Ordering inventory, committing to advertising and accepting a large custom project can each depend on different assumptions about incoming funds. A payment tool should help make those assumptions visible. It should not encourage a business to treat every displayed number as equally certain or immediately spendable.

Access control matters as the business grows

Payment administration often begins with a founder doing everything. That arrangement becomes fragile when more staff join, responsibilities change or an external bookkeeper gains access. Merchants should define who can view information, create instructions, change destinations and approve payments. These permissions should reflect actual duties rather than convenience or seniority alone.

A useful review includes former employees, shared credentials and emergency access. The business should know how to remove access promptly and how to continue operating if the usual approver is unavailable. Where possible, sensitive changes should leave a record that can be reviewed. These suggestions concern general internal control and should be adapted to the capabilities of the products actually used.

Training should use ordinary scenarios rather than abstract warnings. Ask staff how they would handle a supplier requesting new payment details, an employee disputing an expense classification or a customer querying a duplicate receipt. A process that people understand and can follow is more useful than a lengthy document that is ignored during daily operations.

Test simplification before consolidating

Consolidation is not automatically the right answer. Moving every function into one service can reduce some administrative tasks while creating dependence on that service. Merchants should identify the specific work they expect to remove and the contingency process if the consolidated tool becomes unavailable. The assessment should include both everyday convenience and the ability to recover from disruption.

A controlled trial can compare reconciliation time, unresolved transactions and reporting quality for one part of the business. Include the staff who actually perform those tasks, since a polished demonstration may hide manual work that appears only with real records. Document the previous process so that the business can judge whether the new arrangement creates a measurable improvement.

Before changing a core tool, confirm export options and the information needed for accounting, disputes and internal review. A business should be able to retrieve its operational records in a usable form. The provider’s explanation of portability and support should be part of the decision, especially where several business functions would depend on the same relationship.

For every business, regardless of its operating size, the implementation plan should include a named owner for each connection between systems. When an export stops working or a field changes, staff need to know who investigates and which temporary process applies. Review that ownership whenever the company adds a new entity, market or product line. A connection that worked for a single domestic operation may need reassessment when the business becomes more complex. Maintain a brief change log recording what was altered, why and how the result was checked. This is not bureaucracy for its own sake: it helps a small team avoid repeating the same investigation and makes it easier for a replacement employee or adviser to understand how the payment records are produced.