While implementing SWIFT can make a company bank agnostic, it can also be a catalyst for broader change.
One of the primary reasons for embarking on SWIFT project continues to be the desire for less dependency on proprietary bank channels, allowing corporates to move services among banks more easily.
But it’s not the only reason. SWIFT itself can help push efficiency an efficiency project that may be stuck in neutral. International Treasurer also recently highlighted how moving to the Single European Payments Area program can also start the ball rolling for broader treasury change (see related story here).
At a recent NeuGroup Global Cash and Banking Group (GCBG) meeting, members of one company presented on how they had used the implementation of SWIFT as a catalyst for further treasury improvement in both systems and processes. This project – still ongoing – aims significantly increase global visibility to cash, standardize bank communications (using SWIFT) and consolidate exposure management to their in-house Bank. But using the SWIFT project as the basis for a much larger global project, this company has been able to achieve a best-in-class treasury organization.
Catalyst or not, picking the right channel for SWIFT is critical. When choosing to embark on a SWIFT project, one of the initial decisions must be whether to use a third-party provider as the service channel or go directly to SWIFT via their corporate offerings like Alliance Lite or Alliance Lite2. Each alternative has its benefits and drawbacks.
Working through a service bureau (a third-party) helps to reduce the cost and effort required to set up and maintain the SWIFT connection, and to integrate SWIFT with the ERP or TMS. On the other hand, a direct SWIFT connection is a popular choice for larger companies with lots of transaction volume.
Standardization is the key.
Once the service channel is chosen, the standardization can begin. According to a banker who attended the GCBG meeting, corporates should choose the ISO XML 20022 format to ensure the highest level of standardization across their SWIFT channel. This format provides consistency in the financial messaging exchange between counterparties. This messaging standard is the basis of SEPA and is expected to gain greater momentum as the February 2014 SEPA deadline approaches.
The upshot? Corporates who engage in SWIFT implementation projects will enjoy the benefits of a strong business foundation for future-proofing treasury, allowing them to be ready for e-Everything as automated processing of payments and treasury data continue.
Source: NeuGroup Research; GCBG 2013