Alert Banner Text Goes Here Alert Banner Text Goes Here Alert Banner Text Goes Here Alert Banner Text Goes Here
What We Do
Since 1989, Bottomline has been modernizing global business payments with connected solutions for more than 800,000 financial institutions and businesses in 92 countries.
AP Automation AP Automation For Real Estate Payments Hub
Payouts Automation Payments Processing Receivables Automation Payments Hub
Paymode Pay Vendors Receive Payments Partner With Us
Connectivity Services Message Transformation & Enrichment Message Vault Risk Solutions
Connectivity Services Message Transformation & Enrichment Message Vault Payments Verification Payments Verification for Businesses
Global Cash Management Hub Digital Banking
Global Cash Management Hub
Who We Serve
Our Company
With the mandatory introduction of ISO 20022 for payment messages across markets, many institutions will be dependent on translation services to support legacy applications that can’t handle ISO 20022 native data by the set deadline. At Bottomline, we are supporting translation primarily through our Transformation and Enrichment Service.
For messages that need to be translated from a legacy format to ISO 20022, there is little or no risk that the messages will suffer from truncation. This is because the flexibility and extensive nature of ISO 20022 means that invariably there will be sufficient fields and character sets and field lengths to support any legacy standard – as we have seen so far with SIC, SWIFT, Fedwire, Bacs Std18, ISO 8583 and others. Rather, it is the reverse translation where the risk lies in in the conversion of ISO 20022 into a legacy formatt where all the earlier mentioned challenges are in play;
In many legacy formats the length of a field is less than it is in ISO 20022. Historic translation and the current offering from SWIFT for ‘in-flow translation’ halt the field at the historic limit and replace the last character available with a ‘+’. See example:
1. Follows the example above and continues to truncate the field with a (+).
2. Extends the field length. To retain the full information passed in the original ISO 20022 message, the limitations of the legacy standard are overruled, and an extended field can carry the full information from the ISO 20022 message.
a. Applicable for messages that will not then pass back through the network and be subject to validation.
b. Requires the back-office system to be flexible to support the extended field.
3. Creates a Companion Message: Following industry practice from other areas of financial messaging (e.g., Corporate Actions), a companion message is created to carry the additional information. This is a related message, that transfers the related reference of the associated message.
a. Requires the ability to handle and process the related, companion message.
4. Leverages API: For those clients that are using Bottomline’s Transformation and Enrichment Service, we can provide the Truncated data either alongside the executed transformation or specifically in response to an API call to request the full data.
a. Requires the ability to make API calls to the Transformation and Enrichment Service.
Many legacy standards are limited to a character set that does not support characters that are in common usage now and for languages other than English. ISO 20022 supports a full range of character sets - as shown by the adoption of ISO 20022 in India and China for their domestic payment’s infrastructures. Even the most widely adopted ISO 20022 market practice for payments supports the full Latin character set. However, Truncation may cause problems when screening or incorrectly identifying information for onward routing.
1. Adheres to SWIFT FIN Network Validation and replaces invalid characters with a ‘.’
2. Allows extended Character sets in the translated FIN message, enabling processing on the full, unaltered data.
a. Needs to be compliant with any constraints of the payment system.
b. Can’t pass network validation over SWIFT for FIN messages
Due to the larger size of ISO 20022 Reporting messages, there is no need to ‘split’ statements into a sequence of messages, as is done with legacy reporting messages – such as MT 940/950. This creates challenges when converting a single ISO message into a sequence of linked MT messages. The formatting is complex and in fact is not offered in many translation solutions.
1. Creates an ‘oversize’ legacy format message, to support all the statement lines within the ISO 20022 message.
b. Can’t pass network validation over SWIFT for FIN messages.
No ISO 20022 translation solution is a ‘solve-all’ or future-proofed. Ultimately the best strategy is to progress towards becoming ISO 20022 native across all your applications. However, if that is not possible immediately, then a scaleable model that doesn’t impact business continuity is essential. Bottomline offers this flexibility & agility through a tailored approach for each institution’s existing road-map, systems and operation processess. Using truncated data carries risk and is not sustainable. Any solution you choose to mitigate this risk must consider the full data. By working with Bottomline and selecting the Transformation and Enrichment Service you can ensure that you are implementing the configuration that best meets your needs.
“As a satisfied customer, we were confident that by partnering with Bottomline on the message transformation project, we would achieve our primary objective of being able to comply with the ISO 20022 messaging standards within the deadlines set by the BSP. Choosing Bottomline to work with on this project was simply a given.” -Rodel Garcia, Head of the Fund Transfer Department at EastWest Bank
“As a satisfied customer, we were confident that by partnering with Bottomline on the message transformation project, we would achieve our primary objective of being able to comply with the ISO 20022 messaging standards within the deadlines set by the BSP. Choosing Bottomline to work with on this project was simply a given.”
-Rodel Garcia, Head of the Fund Transfer Department at EastWest Bank
Learn More
