So let's look at what else we need to consider when making an efficient liquidity solution. You need to match together the best liquidity solutions, the most efficient transaction processing, and the most automated route for a client to be able to do its reconciliations on any combination of legal entity, geography, and currency basis. Now, all this should be transacted across as few bank accounts as possible with as few different banks as possible to make things efficient within the customer space. We want as much automation at their end as well as at the bank end. What we want to make use of is the most advanced infrastructure available from both the bank and the client to allow straight through processing so there is no touch within the customer or at the bank. Now, here's a clue we need to look at combining both cash concentration and notional pooling to achieve the best liquidity solutions by currency and geography. As a corporate, I want to make sure that the banks I use and have easy access to the currencies of markets I'm requesting. We've already touched upon this a couple of times on this slide. We want to make as much use of technology as possible, so we want to be linking the customer's enterprise resource planning system or ERP and possibly their treasury management system to the bank to allow end-to-end automation. If a customer is using an ERP platform, you'll probably find out that they're also using things like shared service centers and payment factories. Any solution that we discuss with our clients should always be future proof. That means it's got the ability to be scaled up or scaled down. It's also got the ability to add or take off different legal entities, and also is regulatory friendly for changes combined with future proofing. We want to be able to make sure that the systems we put in place we'll be able to make use future bank technology advancements.