
Cross-border payments are moving faster. Real-time rails are expanding, APIs are making connectivity easier, and ISO 20022 is improving the structure of payment messages. The G20's cross-border payments roadmap has set ambitious targets for speed, cost, transparency and access, many of them for the end of 2027. This progress matters. But it also exposes an old weakness: the payment can arrive before an institution has the information needed to understand it.
A payment instruction describes what should be executed. A responsible payment decision also depends on who is involved, why the transaction makes sense, how it fits the customer relationship and what evidence supports it. When those facts are scattered across systems and teams, a faster rail shortens the response window without reducing the work.
A payment message can identify the sender, beneficiary, amount, currency and destination. It may also carry structured remittance and purpose information. Yet many of the questions that determine whether a transaction can proceed sit outside the message. Is the activity consistent with the customer's business and expected behavior? Who ultimately owns or controls the parties? What is the commercial purpose? Is the source of funds understood? Which documents support the transaction?
The answers may be held in onboarding records, beneficial-ownership files, transaction history, invoices, relationship-manager notes, compliance tools, operations queues and email. If that information cannot be retrieved quickly and assessed together, each question starts a reconstruction exercise. Requests for information become slower and less precise. Operations teams wait. Relationship managers struggle to give clients a clear answer. A payment may be technically complete while remaining operationally incomplete. The consequences are practical: avoidable holds, repeated requests for information, manual workarounds, delayed client responses and less confidence in the status of the payment.
ISO 20022 is a major improvement. Swift has reported that more than 98 percent of payment instructions on its network are now sent in ISO 20022 format. Betterstructured data can improve party identification, screening, automation, reconciliation and transparency. Swift's decision to apply a controlled extension to the structured address timeline also shows that standards adoption is not merely a messaging exercise: it requires changes to data models, customer-information practices and operating processes.
Structured fields improve the message. They do not automatically connect it to the customer's profile, documentation, transaction history or the reasoning behind an approval. Relevant transaction context is essential when an institution must decide whether activity is expected, resolve an exception or explain its decision later.
Regulatory expectations are moving in the same direction. FATF's revised Recommendation 16 seeks greater consistency in the information accompanying cross-border payments, clearer responsibilities across the payment chain and stronger protections against fraud and error. Transparency is becoming part of payment performance, not a separate exercise completed after the fact.
A payment that settles in seconds but triggers a multi-day investigation is not fast in any meaningful operational sense. As money moves more quickly, the ability to understand, question and explain the transaction becomes more important.
Compliance teams need relevant customer and transaction context without rebuilding the file. Operations teams need to see what action is required and who owns it. Relationship managers need accurate status information and a clear explanation for the client. Management, auditors and examiners need an evidence trail showing what was reviewed, what decision was made and under which policy
When these groups work from the same operational context, requests can be more specific, exceptions can be resolved more efficiently and clients can receive clearer answers. Human judgment remains central. Technology should organize the evidence, preserve the workflow and surface what matters; authorized people should continue to apply the institution's policies, risk appetite and decision authority
Sibos 2026 is focused on digital finance for AI-driven economies. AI can help institutions classify documents, identify inconsistencies, prioritize alerts and bring relevant information to the reviewer. Its value, however, depends on the quality and completeness of the information it receives. AI can accelerate review, but it cannot compensate for information that is fragmented, incomplete or disconnected from the payment decision. AI readiness therefore begins with information architecture, controlled access and an auditable connection between evidence and action.
Institutions do not need to replace every core system with one application. They need an operating model that keeps the information, workflows and decisions surrounding a payment connected throughout its lifecycle, even when the transaction crosses several banks, currencies or rails. Access, data quality, local practices and compliance expectations vary by corridor. The payment path may change; the context and audit trail must remain connected.
At Avalo, we see this as an operating-model challenge, not merely a technology one. Our infrastructure works alongside the systems an institution already uses, connecting customer and transaction context, supporting evidence, screening outcomes, required actions, approvals and status throughout the payment lifecycle. Technology makes that connection usable; our payments, treasury, compliance and operations specialists help institutions put it into practice. Policies, decision authority and client relationships remain with the institution.
The industry will continue to accelerate settlement. The institutions best positioned to benefit will be those that can move money quickly and explain it with equal confidence. Payment information cannot remain a compliance add-on assembled after initiation. It must be treated as part of the infrastructure itself. Faster money needs richer information because a payment is only as strong as the institution's ability to understand it, stand behind the decision and explain why