search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
SmartStream


securities lending in less time and still avoid any discrepancies. Otherwise they run the risk of late funding requests if trades have not been confirmed and liquidity projections are not correct. While some larger banks already have strong intraday and real-time liquidity solutions in place, other industry participants are still unprepared for real-time liquidity management. These players can either deploy additional operational resources to handle the demands of T+1, or they can invest in advanced technology through external partners such as SmartStream. Whichever path they choose, they will need solutions that deliver real-time cash and liquidity management capability by removing any silos in the systems infrastructure and consolidating all of the necessary data. They will need to capture transactions from internal and external sources to create a single, global view of balances across all currencies and accounts. Doing so will result in banks having a clear understanding of their funding, borrowing and lending requirements in real time. From there, they will be able to use that timely information about payment obligations to identify any sticking points promptly and, crucially, take rapid and meaningful corrective action.


Collateral and corporate actions Collateral management is another key area that will be affected by shorter settlement times. Any shortening of the settlement cycle is likely to reduce credit, market and liquidity risk around unsettled trades. Firms can more quickly get from margin call to settlement, and one effect of this will be a potential reduction in the initial margin they are required to post, as part of that calculation takes into account possible market changes between the time firms agree on collateral and settling the trade.


Again, speed of processes is the crucial factor. Some banks have moved to fully automate their collateral management processes, while others still manage some aspects using spreadsheets. Shorter settlement cycles should push banks towards removing any manual processes from the workflow.


“They have to automate all aspects of the collateral management process, including agreement, booking, substitutions and settlement notifications,” says Brandli. “They must automate connections to internal and external systems, as well as put in place an efficient fails management process. Easily and inexpensively upgradable technology is also desirable.” End-to-end, automated collateral management solutions are out there on the market, and some have been proved in the field by major financial institutions, and the key elements in their performance have become clear. An efficient and effective solution will connect to a bank’s internal systems via APIs, and enable users to send and receive information on a real-


32


time notification basis. Without this seamless interaction, full automation will be hard to achieve. For corporate actions, which usually have an execution date one day prior to the record date to enable trades to settle in advance of the record date cut off, T+1 will require that execution date and the record date be on the same day. This could cause a spike in reconciliations issues and subsequent market claims unless there is a robust and automated technological solution in place.


Corporate actions, which affect instrument static data and, therefore trade matching processes, will need to be processed within 24 hours of execution to avoid failed settlements, so firms dependent on custodian data and spreadsheets are likely to find T+1 compliance especially difficult. Time zone differences and any event-related FX considerations will compound difficulties further. With settlement discipline an increasingly important regulatory focus, there is mounting pressure to avoid errors. The need for greater speed will also affect voluntary events – especially in areas such as prime brokerage and securities lending. Real-time processing for the trade life cycle, and the ability to handle complex events and provide visibility of the corporate actions affecting a business will be invaluable.


Resilient in the face of change Changes in market practice are common, so it is not only T+1 that is making banks reconsider their systems architecture. Indeed, the market is keen to see greater use of Swift and ISO 20022 standards to facilitate the move to an accelerated investment life cycle. “As the industry undergoes a large migration wave to replace Swift MT messages with ISO 20022, one of the biggest challenges is to supply the rich data required,” says Brandli. “This will mean potentially changing underlying legacy systems, which will take time. Another challenge will be the introduction of pre- validation, which is to be welcomed, but not every bank will have this capability, especially the smaller banks with simpler architecture.


“Banks will need scalable, affordable solutions which allow them not only to improve their response times but also enable them to standardise while the different payment solutions still use differing formats and syntaxes,” he adds. “Also, It is a general wish among banks to move to managed services more, because they want to get rid of the headache of middle and back office processes.” With the technology investment or the right third- party relationships, banks will know that settlement processes are automated and maximally efficient, only becoming involved when there is an exception. There are plenty of options in preparation for T+1, but they must make a choice and act quickly. ●


Future Banking / www.nsbanking.com


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53