ISO 20022 alone won't fix reconciliation

Richer payment messages can improve automated matching, but only when the right information survives the complete journey from ERP to reporting.

ISO 20022 promises to improve one of the most persistent problems in international payments: a payment arrives but the beneficiary cannot easily identify what it relates to.

The payments messaging standard creates that opportunity. It supports richer, more structured information, including invoice references, creditor references, payment-purpose codes and details of the parties involved. In theory, this gives finance teams the information they need to match incoming payments with outstanding invoices automatically.

The transition to ISO 20022 is being driven globally by SWIFT, central banks, commercial banks, payment providers and corporate treasuries. As organisations modernise their payment infrastructure, the focus is shifting from simply adopting the standard to ensuring richer payment data is preserved and used effectively throughout the payment journey.

However, richer data alone does not guarantee better reconciliation.

ISO 20022 defines how information can be structured and exchanged. It does not guarantee that every system and provider involved in a payment will capture, retain and report that information correctly.

A payment can therefore be fully compliant with the standard and still require manual reconciliation at the end.

The information must survive more than the payment message

The data journey often begins inside an ERP or treasury management system.

From there, payment instructions typically pass through payment providers, banks, correspondent networks and local clearing systems before returning to finance teams through statements, APIs or reconciliation platforms.

Every hand-off creates a potential point of failure.

A corporate system may hold several invoice numbers but export them as a single free-text field. A provider may accept the information but map it to a field with a different character limit. An intermediary or local payment rail may not support the same data structure. The beneficiary bank may receive the information but display only part of it through its online banking interface. Finally, the reporting file returned to the finance team may contain less detail than the original instruction.

Swift's CBPR+ framework protects rich ISO 20022 data across the Swift portion of a transaction. However, international payments frequently extend beyond that environment into corporate systems, provider platforms, domestic market infrastructures and reporting channels. Those connections still need to be tested.

Even where every participant supports ISO 20022, market practice differs between jurisdictions. Domestic payment schemes may implement different subsets of the standard, while banks often apply their own validation rules, field limits and reporting formats. Understanding how each payment corridor behaves in practice is therefore just as important as understanding the standard itself.

This is where a payments specialist such as APA adds value. Rather than treating the payment as a message sent from one bank to another, APA can help businesses examine the complete route, including how instructions enter the payment process, which rails and banking partners are used and what information is available once the payment has settled.

Start with the reconciliation outcome

Instead of asking simply whether systems can produce or receive the correct message format, businesses should ask whether they can reconcile a payment automatically.

The better starting point is to identify the information that actually drives matching.

For one business, that might be a single invoice number. Another may need a customer identifier, legal-entity reference and several invoice numbers. Some may need to distinguish between payments made on behalf of different subsidiaries.

Finance and treasury teams should determine:

• Which fields the reconciliation system uses;
• Whether those fields are mandatory or optional at each stage;
• How many references can be carried;
• What character and formatting restrictions apply;
• What happens if information is truncated, reformatted or moved into free text; and
• Which data appears in statements, APIs and downloadable reports.

The route should then be designed around those requirements. APA's network of banking partners and payment rails allows it to consider not only currency, cost and settlement speed, but also the operational requirements surrounding the payment.

Test real payments through representative corridors

A schema-validation test proves that a message is technically acceptable. It does not prove that the beneficiary will receive the required information or that it will return to the payer in a usable form.

Businesses should send controlled payments through representative routes and compare the information at each stage of the payment journey:

• What left the ERP or treasury system?
• What did the payment provider accept and transmit?
• What could the beneficiary see?
• What appeared in the payer's and beneficiary's reporting?

Testing should cover different currencies, beneficiary banks, local rails and payment types. It should also include less-than-perfect scenarios, such as multiple invoice references, long references and optional fields left blank.

A specialist provider can help coordinate this testing across markets and identify whether a problem originates in the source data, field mapping, chosen route or downstream reporting. In some cases, the answer may be to change the mapping. In others, it may be to use a different route or supplement payment-message data with reporting that preserves the reference needed for matching.

Conclusion

ISO 20022 gives businesses the ability to exchange richer payment information. Whether that translates into faster, more accurate reconciliation depends on whether the right information survives the entire payment journey.

Organisations that understand not only message standards but also routing, banking connectivity and reporting are best placed to realise the full benefits of ISO 20022. APA helps businesses look beyond message compliance to improve the operational performance of international payments - from routing and settlement through to visibility and reconciliation. If you're investing in ISO 20022, the real test is simple: does the payment data your finance team needs survive the complete journey?