Industry sign banking arkansas word free
I'm very happy that you have all joined us thank you very much I'm Laura Paul financial services industry lead for Appian and I am really thrilled to be sharing with you a really exciting initiative that appian is collaborating on with the Swift Network I imagine that most of you are probably familiar with Swift they are the world's largest financial messaging network they've got 12,000 financial institutions and corporates sending 24 million or so financial messages every single day so they have huge scale and huge reach and in 2017 Swift launched its global payments innovation initiative which is really aimed at solving the complex challenges surrounding cross-border payments transactions so making them faster making them more transparent with end-to-end trackability and they've got today over a hundred billion dollars going across GPI on a daily basis across 1,200 country corridors and 3,500 financial institutions so significant uptake at this point and those numbers are continuing to grow and as part of GPI case management of payments investigations and exceptions on payments transactions actually rose to the top of the priority list for innovation enhancements for GPI by the member institutions and so that is where a paean comes in so a paean is going to be integrated directly into Swift GPI facilitating case resolution on interbank payment transactions basically from initiation to resolution simple cases all the way through to complex cases which is really happy in sweet spots something that a paean does very well and they're going to be operational regulatory compliance related types of investigations essentially anything that slows down the payment there's going to be now an end-to-end case management fully automated capability to really make sure that the customer experience is what it should be with these cross-border actions improve operational efficiencies and get the real value from the platform so where are we in the process right now a peon is participating in a pilot with Swift there were also 16 banks who are participating in the pilot at this point and very importantly and what I wanted to let you all know is that there's opportunity for you all to join the early adopter program so you can begin to you can actually implement at the end case management G case as we've been referring to it to improve upon your cross-border payments solution and we'll talk a little bit more about what that looks like and show you a little bit about that as well and so and I invite you by the way please feel free after this session to reach out to me or reach out to your a paean Account Executive we'd be really happy to share more details with you on this and talk about how you can how you can get that implemented so I am very pleased that Daniel Lynch from Swift is here with us today Daniel heads up Swift payments innovation in the Americas Daniel please come on up and Daniel's gonna share a little bit more about being case management about gpi's some of the background and reason the case management was so important in some of the benefits the industry is expecting to to gain from this and just before we get started I also want to mention then Satya who is a pians solution principal architect is also going to along with Daniel take you through a demonstration and really highlight some of the key features and functionality and bring it to life a little bit so please welcome Daniel thanks everybody thanks for coming the session thanks for I guess after perhaps having a few drinks on the Midway last night and maybe a very carb oriented lunch I would probably be tempted to take a maybe a quick nap but I appreciate you coming out to hear about this that case management initiative today I don't know how many you are familiar with GPI alright cool very nice so the GPI initiative is basically a thing that we all decided collectively Swift and about 20 of our largest GT B's about three years ago to undertake there were a few currents happening in 2017 there was increasing competition to Swift but Swift is really just a messaging layer on top of the correspondent banking system we found that there were things like in China where the banks had lost maybe a hundred percent of the retail payments to folks like Ali pay and WeChat in the course of three years and they were starting to be a little bit distressed about the possibility of losing the wholesale franchise right additionally there's these heightened customer expectations where you know you can order a good from Amazon it's gonna arrive the next day you can track it you can trace it you can pay things instantly and then suddenly you go to work you're the same person that's doing this outside and you want to send a two billion dollar payment to Central Europe and then suddenly you're you're shocked that it's lost or it's taking four days and then probably cynically lower interest rates probably helped us out a little too but we got together with these banks and we decided that each year we would have a process where we would determine some marginal or iterative sometimes larger revolutionary changes that we could apply to this correspondent banking model I think we've been a little bit of a victim of our own success because a lot of people think this process what's happening today is GPI but it's really what's live now so these initial 20 global transaction banks in Swift 2025 I got together and said you know what's urgent not necessarily like important what do we need to fix like day one and everyone said of course you know the fact that I can't trace a you know million billion dollar payment is crazy the fact that I don't know who all the players and this correspondent banking chain is wild the fact that I don't have settlement finality always so I'm not getting a confirmation and the end beneficiaries being credited of course I don't have transparency on the fees that each player is up or the charges rather let alone the FX rates and then of course finally that the speed we wanted to have a heightened SLA where we could expect that all payments will be settled same day or same value date right and this was very successful we've got as mentioned about a third of our network using it now in terms of participants they represent about 80 percent of cross-border payments we've been able to extend it out beyond the Swift Network the Fed participates with us the Clearing House backs Bank of Japan etc so it's really becoming an end and cross-border payment solution not just for the swift layer but the entire initial ordering to end beneficiary process now in the coming years as we got uptake it was no longer just these top 20 global transaction banks we had a pretty large base about 450 banking like corporations sometimes with subgroups that are fairly independent you can think about some of these very multinational banks was more of like a holding structure we so we thought how is it that we can continue to improve this but really take into account large banks regional banks Development Bank's investment managers custodians etc and we'd Estela we decided to develop a process that's not dissimilar from like the presidential primaries we have like the party primaries and that's when we go to London and we go to UK and we go to Istanbul and we go to Shanghai and we get all the bank's together and we decide you know what would have we not addressed yet what's not working where do you still have pain points and they have sort of the primary vote and then in November the top 30 GPI banks sort of the general election vote where we decide what it is that we're gonna develop the next year and the 2016 we decided that we would build a few thing or 2017 sorry 2016 rather we decided we would extend out a few things than GP I go and be on customer credit payment transfers to cover payments we decided that whether a payment passes through a GP I participant or not it should be universally trackable so we asked all Swift participants to begin to use this end-to-end tracking reference and we developed in a replicable stop and recall that would let you stop a payment in flight and those have all been actually successfully up taken and I think last year the primaries got a little wild where people actually raised to us about 7 initiatives they wanted us to undertake this year and those include things like a pre validation API for you know verifying and beneficiary before initiating a payment having actual real-time are close to real-time corridor so like cross-border payments and 45 seconds 24 by 7 or at least 20 by 5 we developed a settlement layer for smart contracts for folks who want to use smart contracts on DLT but maybe you're a little scared of tokens for FX or regulatory reasons because maybe the SEC hasn't determined whether the securities are not and one of them is actually this case management service and it's funny it was actually the winner of the mo AI took part in these primaries and in the general election and it was consistently the most voted upon priority for us to build this year so very excited to be building it and I think especially salient is that instead of just building it with the banks and then going out to our solution providers as we did in the sort of the first two rounds of this GPI innovation we were very lucky to have a peon involved in the development process from day one so it's very helpful to have the actual users and the providers you know in the same room building a service together so I think we can go to the so I mean Y case management I guess why did everyone vote so much and Swift we did a survey they said something like 2 to 6 percent of payments lead to an inquiry or don't have straight through processing I've heard John Hunter from JP Morgan who probably I guess maybe is a little bit even more exposed to more respondent banks than we are which may have more issues has raised the number as high as 10% of payments having an inquiry investigation exception happening and I think the big problem there is that they rise costs up to 25 to 35 times that of a payment with SDP so you can think about it even if it's happening 2 to 3 percent of the time these 2 to 3 percent of payments are costing you as much as the entirety of the rest your of your transactional banking franchise that has STP so we thought about you know how can we how can we start to address this I think we found three major problems number one is that first of all you're playing telephone right so banks no longer hold direct messaging relationships necessarily with all the parties because wolfsburg because a kyc because of de-risking etc right so on Swift it's increasingly difficult to send the the traditional enquiries investigation messages to the bank you want to talk to right you have your your relationships are concentrated through major correspondence if you've got to reach the First National Bank of Daniel which is a four five branch in Arkansas Daniel I'm just making this a fictional Bank but if you have to reach them you're gonna have to play telephone where you're gonna have to send a message your correspondent who's gonna send a message their correspondent it's just a it's it's not a very efficient process secondly that it's very difficult to have like an audit trail like when these when these cases were opened when they were receive what you're doing to resolve them and the number three they weren't structured enough so we started to think about you know we are the standards body for ISO 20022 and we started thinking about codifying all these things around you know incomplete debtor name and complete creditor named non matching value dates and hoping that in codifying them in working with solution partners like Appian we could hope to automate some of these case resolutions so again yeah we were taking a look at some of the the larger issues and again incorrect settlement date you know incomplete debtor-creditor information we thought you know there's three things that we'd really like to do there and that's have the ability to identify a case have you be able to route it directly to the bank you of the issue with right so if I have to reach out I'm a I'm a mid-sized correspondent bank in Luxembourg right but I suddenly have to be able to reach out to a you know a small community bank or credit union in Connecticut or in Arkansas or and wherever how is it that I can reach out directly to them and get that information that really only they have right of course and then again not just identifying communicating them but we also want to be able to modify and resolve the issues within the same case management tool is that pretty clear does that resonate with some of the issues that you're facing today cool so clearly a need for case management within this GPI platform and thanks for sharing that Daniel it's super helpful to hear how how they kind of got to that as being one of the main priorities and so Appian will be integrated directly into Swift GPI it's going to be in flight cloud-based allow for dynamic query handling between banks so enabling them to resolve issues quickly again they could be operational compliance regulatory type issues it could be that there's missing information from the payment instructions or incorrect information the payment instructions which can throw off the entire you know payments transaction along the payments chain and just make it that much slower and that much inefficient more inefficient um standardized iso 20022 as daniel just mentioned so a peon will be standard you know standardized so banks can exchange requests and responses in a structured manner again making that process again very very efficient and here just um another view of some of the key areas of value i mean all of the all of the things that a peon case management does really well we're gonna bring to bear here and and add on everything else around payments around reason codes around the the messaging you know to make it tailor to this particular use case but it will be of course right in a pian the sweet spot of case management shortening time to resolve issues across the entire payments chain facilitating automating coordination of the entire end and process and removing the need for manual intervention daniel touched on this for a minute but it's it's maybe surprising to hear I mean banks are going back and forth with faxes emails phone calls direct messaging in some cases and of course every bank has their own process right so all of these things just really caused a lot of friction in the payments process and this has been a long-standing problem for years I mean we've been talking about this in the payments industry for a long time now about fixing this and so just having this case resolution you know GPI is going a long way to fixing that problem but when an issue comes up along the payments chain which they're bound to happen in fact you know two to ten percent of transactions we need to make sure that all transactions are going through quickly so that customers are having a good experience and costs are kept down and so it's just a good experience you know all along the way creating visibility into details and status of a particular case but then also the ability to aggregate data and also provide insights around patterns case patterns so perhaps there's a bad actor counterparty or a particular transaction type that cute that's reassuring you know having that view and then having management view of key performance indicator you know which would be helpful just in managing the whole process in terms of how many cases are outstanding or they buy a particular counterparty you know and at a certain stage in the flow of that transaction centralized workflow you know there's a whole laundry list and again I want to say everything that comes that's inherent in a peon case management will be brought to bear with this solution and the ability also to integrate with AI to make the process smarter the ability to append documents to the cases all of those things and really importantly and I want to say last but certainly not least is the ability to integrate with the financial institutions existing infrastructure so this is not something that you all are gonna have to go out and build this whole new process for and I w
nt to make sure to emphasize that because this to me is really one of those I mean I'm I am very excited about this whole initiative and very passionate about it because they truly believe that this is really going to make a big difference for all of you and for our financial institution customers in helping you solve a real pain point a real problem you know some of you may be involved in the cross-border payments processes within your institutions or certainly you know know those folks who are but we really think this is going to make a huge difference so again I invite you to please reach out would love to talk with you about how we can get started it's the early adopter program and it's it's ready now so with that perhaps just that yeah brief word Satya's going to do a pretty cool demo of how you would be interacting with this case management service within you know within your interface at a paean but just to give you an idea again of how this is working we initiated this tracker such that initial ordering banks intermediaries and beneficiaries would have a full view into payments that were inbound outbound the finality on the outbound side the fees lifted etc which was interesting you know we get a lot less of beneficiary claims non-receipt or you do and you can say hey go talk to your beneficiary bang because they're sitting on the funds it's not my problem right we've seen a lot of white labeling of this too into [Music] customer portals such they can self-service and find the status of their payments there's also been some interesting things around once you're sitting on all this data you give them more routing suggestions but with the case management we decided that we could also use this tracker as a bus for like routing these requests between the institutions so you take intermediary institution again it's a let's say it's a you know Portuguese bank right or better yet it's it's it's a it's a branch of like ICBC in China or something right you have an issue with this small initial ordering Bank in say whatever Pennsylvania rural Pennsylvania I don't think that with the time zones they shared with language issues with having to route these in this case there's one intermediary agent but we know then reality you can have two three sometimes right so in terms of intelligently routing the request to them we're gonna be doing that through the tracker so you don't have to go through your correspondence anymore you don't have to incur unnecessary RMA relationships and fill out more Wolfsburg surveys which you know no one's no one's a fan of of course we're gonna also try to and then also have an audit log so you know who was the SME who was the I Center a signer who was the s ik knee of course whether it's a person whether it's a back office system we wanna have positive acknowledgments that the initial ordering Bank receive this request for say like a person's date of birth and then of course to reduce manual intervention as much as possible we're hoping that in using these ISO 20022 codes and working with our solution partners it won't be a question of somebody you know shuffling through files to find Daniel's date of birth so we can resolve this payment but rather solving it in an automated and efficient fashion this is just so this is one thing I actually added in this this in here because I thought I thought it was interesting so these are participating banks quotes around this there was recently a big press release on this and and there will be a lot more information in the press but I mean you know Daniel mentioned earlier on that these financial institutions voted this as being the most important thing that the biggest kind of headache for them really that they see is managing these cases and so I'm not gonna read these but just just some quotes here around really the value that this is going to provide all right with that saw - you're out you wanna we're gonna show you a demo and bring some of this to life thank you before we get started let's get one important question out of the way how many of you guys had a brilliant time last night did all right so with that said I'm gonna talk about how we went through the journey of using the swift API to integrate seamlessly for both what I would call as the assignor bank who's going to raise a transaction dispute and the assignee bank who are gonna act on it right so there's a two independent parties totally two different banks from two different spectrums how can they seamlessly collaborate using the API under tracker as the backbone now here's the biggest difference traditionally if you use any of the standard DPM software that you might have come across you will have to define what we call as a process for every step of the way so that's pretty heavy heavy way if something changes you have to go Andriy Architect your entire solution with a peon given that we are both processed and data centric we are actually taking advantage of the data that comes straight from the api's from swift and then piggybacking that displaying it to the user to interact with that in an informed manner connecting the organization's data are they moving the ball forward or forward on backward as it needs to go so that's what you're gonna go and see in this demo before I go through the demo I just wanted to share what value this brings him right I'm not a big slide guy so I don't build very good slides I did build good demos but not slides so when I created this slide and sure I was just talking to my daughter she's 10 years old she looks at this and says dad you should have asked me I would have done a better slide than you so bad with me on those slides I'm pretty much black and white so the biggest value I call it as a big chain now given that happy and powers the entire end to encase resolution using the API the advantage you get out of the box is that it allows you to connect with ease so you can connect to not only the GK's api as you are interacting with these systems you need data from within your organization as well so if with a pians platform you can pull and push data seamlessly the other thing is it allows you to resolve with confidence so daniel mentioned it very briefly the full audit trail so we can make the full audit trail visible to you all the time so you know exactly who acted on it what was done and what was the resolution and it will always remain so you can go back and see what was done and last but not the least it allows you to gain full visibility now in some part of the world they call it as 360-degree view have you guys heard of the term 360-degree view yeah you have right so I'm not a big fan of that the term I tell me why have you ever thought how world will be if you can see around 360 degrees you will have no idea whether you are going forward or backward right now I would like to call it as 120 degree view and 360 degree awareness so you need to know what's happening around you all the time but it should be laser focused on what is happening next and that's what you're going to get out of the box this is step one but in reality the chain is big the chain is so big that when you have this implemented as part of your entire solution of handling an entire dispute or payments or transaction this is just part of the chain so you might have additional functionalities coming in the future so you don't need to run around looking for another product to implement you can use the platform to evolve and add additional functionalities it allows you to expand it allows you to accelerate because once you built you can reuse those assets and last but not least you can automate using both or PA and AI which is part of a digital transformation journey okay so with that said I'm gonna switch very quickly to show you how this gets realized for the purpose of this demo we are going to play under play two roles I'm gonna call one as the assignor Bank the other one as the assignee bank right both are covered by the appian platform now this need not be the case a different bank can use a totally different technology but a peon can act as both as you need now I'm gonna call it as the red bank and the blue bank we don't want to name any bags right there a lot of colors so let's keep it simple red bank and the blue bank so the red bank is going to be the assignor bank so they are going to see that transactions and they're gonna trace a dispute on all of the transactions you will see how that flows down to the blue bank which is going to act on the transaction and then you'll see the exchange of information happening between the two right so a syrette bank I've logged into the platform so what you see is an a P an example stream if I may just to bring it back to that correspondent bank world for a minute the the red is the assignor am i correct yes yes the red bank could either be a correspondent bank that's furthering a payment on for further credit or it could be a beneficiary bank that wants to credit that end beneficiary but still needs some some more clarity around an issue in the blue bank would likely be in an initial ordering Bank although it could in theory be an intermediary as well because we see some cases in the u.s. of larger banks aggregating on behalf of smaller credit unions and respondent things right perfect thank you very much so well once in login based on that I'm in the journey I can see the list of transactions right over here and the data that you see here is darkly powered by the API there's no process there is no database a penis storing that information we are going to query the data in real time okay if we are going to allow you to search sort filter do all those kind of things over here now I'm going to take an example I'm gonna pick on one of the transactions from the top of the list for the purpose of the demo now as I click on that we are sending this request to the GK's API through the API layer and pulling all the transactions in formation in real time okay so what I see is it's a transaction there are three participating Bank in this transaction so you can see that chain on the top on the left hand side you can see the big codes and what they call as you ETR which is the unique reference that allows you to identify that transaction and at the bottom you see what this transaction is about you see it is four thousand dollars it's a recent code is G double zero two and it's status is a CSP right and as the bank need to have internal collaboration we can also connect the people element to the process and data so in short we are trying to connect people process and data together which in other software you might probably need three components to connect them together so if I want to collaborate I can collaborate on this particular entity right over here so to keep it brief I'm just just going to create a new case so this is where I'm initiating a transaction dispute so when I click on this one again we go back to the api's and saying I need to create a new transaction dispute and we are pre-populating most of that information for you from the transaction such as what is the payment reference number what is the message ID and you can generate unique ids as you need so I can change this one to a message code of 107 this identification is what a bank could provide to uniquely identify in this particular case now keep in mind you can have multiple cases for a particular transaction so you can give unique IDs for each and every one of them in a peon you can have a peon generated code on its own just click on this key button and it will generate a unique code every bank will have their own concept on how you want to create this unique reference number we can do the same thing or you can explicitly specify a code as well so I'll just call it as red to for for the interest of time I can specify what the instruction is and last but not the least we follow the principle of get it right the first time this is one of the core principles of like what I call as operational efficiency like you know why do I need to go down the chain to identify a data was incorrect where I can validate and correct it right in the front so here what are you seeing on the screen are the different types of reasons for which I can initiate that transaction so if I say an on field related issue the recent code is related to what I select now if I happen to change the reason I can instantly see a different set of code making sure that you do not add an incorrect combination that costs you time and value down the chain so we can think about how these apply a little bit some real-life situations so non field related maybe I got a cousin and he's he's a carpenter and he lives in Miami Florida but his name happens to be like nicolas maduro who's also like the president of venezuela who's under some sanctions right now you may want to reach back and ask that birthdate or some additional information to ensure that he is in fact the nick Maduro who lives in Coral Gables and you know has this it's carpentry shop right so there's no unfilled related once you get that clarifying information you can know that he is in fact you know this this is pretty chill carpenter from Florida other ones are in fact field related so these would be ones that are actually associated with the instructions and a payment instruction and we think there's gonna be quite powerful because you won't just be able to identify but then also request to modify and complete so if you have like incomplete debtor informations that our agents so it could be like in the case of maybe it's just like Maria Sanchez there's a lot of boats called Maria they're all sanctioned maybe you want to get her second last name or some additional data and once you get that to be able to actually resolve the issue you'll also be able to have a request that they can modify the 1:03 that's in flight and be able to send the payment on for further credit so there's a distinction between field related non field related but we're hoping that it they cover a range of issues and I'll tell you a little bit at the end about why that's important how we hope to work with you on building that out further thanks Anna so I'm going to follow up and down in skew on create reason as in club incomplete deadness name and click on submit so all we have done is created a screen which captures some basic information and push the information back through the API the swift GK's api and let the api hand in the case so what has happened as this is pushing the data through and over here I'm back under the dashboard and I can instantly see confirmation from the API that tells me what has happened so this is a complete list of all that that has happened within that API so if I expand that I can say that the transaction was created those are the first two lines the third line indicates that it was assigned on the fourth line which stands details it says that it was successfully assigned to the target bank positive acknowledgment that the initial ordering Bank in fact has received the case you know that they're they're the very least cognizant and responsible for therefore resolving it yeah precisely now let's switch gear and go to the assign EEB assign the bank and see what has happened from that point of view if we go to the assign s Bank so this is the blue bank and first and foremost thing the screens look very similar for the purpose of continuity we have kept it very simple but it can be customized based on the target what you see over here is my task list so unlike a traditional task list this task list is getting powered directly by the API so there is no appian process or anything that's powering this particular list it's coming directly from this API and I can see that there was one case and it has been assigned to me this information comes directly from the API for us so this is a very different paradigm to a typical process centric assignment this is assigned and owned by the G case so if they make any change we can directly reflect that over here without you reengineering your process now I'm gonna go ahead look into the details and clearly the details will be very similar to what we saw earlier and I'm gonna go ahead and I can choose this case as mine so take ownership of it or I can forward forwar
this one to a different party so in this case I'm just gonna click on it is mine so I signal does mine and click on accept so accepting it again sends a notification to the API ggk api our gkp ice changes the status once again to accept it as you can see it over here and I can also see the tracker at the bottom that says that it's been assigned to me mine stands for the status is assigned to me now the last step is to resolve this particular case so the resolution can either be you can close it that no further action close it by taking a further action or you can return the modified empty back to the bank with that information so you have any of these combinations done the system is going to ask you further questions based on what you choose so for the purpose of this demo I'm going to simply return the empty back to the sender with the modification and once I'm happy with that click on return that case so now it is calling the tracker again sending that information back to the Red Bank so this is how the two banks can seamlessly collaborate together using the GK's api as the underlying bus backbone now while we are here I can also see the entire history of all the transactions that I have been doing so the read to the one I created you can see that on the top so I can click drill down to see what has happened it's not like fire-and-forget you fire it but it still has the handle for you to go back and see what was done what is the status where is it currently residing right now all right since all these transactions are now flowing through a peon we now have the power to combine the data that the tracker provides us with the data that is existing in within the organization and slice and dice it in the way that is most meaningful I can create cross payment transaction reporting that tells me what is my transaction reporting happening so tell me here over here tell me month or month slice it by region by country or by volume or by revenue so I can go by on historic basis so I can say show me the trend for the last three years select the multiple years and then I can see the trance I can see them by total revenue so how much revenue am i creating if I don't want a couple of regions I can deselect them directly standard out-of-the-box functionalities I can also hotspot various transaction like tell me the regions which are creating a lot of transactions are flowing through should I wish to do so all those things are now becoming visible straight out of the box now to conclude this case if I go back to the Red Bank I can see that the transaction has come back to me and now I can specify what I want to do with the transaction so I can close it because I've received the modified MD I can close it or I can take further action and reject this particular empty so for the purpose of the demo just to wrap it up I'm just gonna say modified empty was received everything is good conclude the case and that concludes the end-to-end lifecycle just to recap putting a paean as a case layer on top of this API we are now able to take full advantage of the abeyance dynamic case management capabilities by taking advantage of treating data people and process as a first-class citizen at this moment I would like to hand over to Daniel yes so I guess if there's anything we could leave you with is that Swift has changed a little bit how we roll out some of these initiatives over the past few years before perhaps privet perfectionist where we wanted something to work and cover you know a variety of use cases or we wanted something to be absolutely perfect before we released it to market what we're trying to do now more often is to take a look at what things can we address that are very urgent that are that are you know blocking issues for institutions and then roll out additional improvements as were necessary with the experience of the community so for now based on the pilot these are the cases that we've identified that we think could be useful in case resolution anyone who wants to join the early adopter program I I invite you to join us in Swift and a pian to try it out the goal is by the end of this year that these will cover 95% of cases if they don't you see we have a narrative generic code if we find that we're not reaching that 95% level we're gonna go and incorporate in the new use cases so that we can hopefully address 95% of these case management right I guess it's more of a horizontal look but then additionally as we move forward we're also going to try to go into some other some other case resolution sort of vertical sort of like claims management or invoice reconciliation so hopefully with these early adopters by the end of the summer by autumn we will have enough of these ISO 20022 codified cases rolled in the API consumed by your back office is such that we can eliminate about 95% of these cases and then concurrently we want to begin exploring with you what we can do around claims and and and other things are on the invoice pio reconciliation with underlying payments so thanks for listening and certainly hope to be working with you all on this in the coming coming months yeah thank you all I really think there's huge opportunity around this so again please please reach out we'd love to talk to you more about oh one very important detail from the Swift side we need network and network effect in capillarity so no banks will actually have to subscribe to the service until 2021 so feel free to play with it and perfect it with us over the next 16 months 17 months so looking forward to that yeah thank you everybody [Applause]
