Latest / Extropy on AIR: Finance Transformation, AP Automation & AI in Finance / The Shared Services Paradox: AI, BPOs, and Owning the Outcome with Bo Senu-Hodo
Transcript
- Ravit Gutman: welcome back to XRP on Air. I am Rave Gutman, founder and CEO XRP Advisors, and today we're going to talk about something every finance leader is thinking about. even if you're not saying it right now out loud, but definitely some of the things that we're hearing as well as part of our transforming out loud conversation, which is the shared services and BPO model that was built for scaling people. now is AI is completely automating and shuffling that conversation and really that whole piece of automation is a big part of that same work that we once outsourced. what happens to that model and that paradox that we're going it's what we're going to unpack today. what I'm really excited about that I could not think of any other person than to talk through this today. she's been on our show before and she lives this every single day as a financial leader, working hand in hand with our own external VPO team. welcome back, Bill. Bo Senu-Hodo: Thank you for the opportunity to be on air again. It's always a pleasure. Ravit Gutman: Bo for everyone who missed our last conversation, tell us a bit about your role and what you're working on in terms of outsourced finance team and how does that look for you today? Bo Senu-Hodo: I had the global invoice to pay transformation within a multinational pharmaceutical company and all our Processes, operations is actually outsourced to our BPO partner out in Hyderabad. it's been a journey. we've been outsourced for the last six years, and it goes beyond outsourcing. We're now also taking a look at how do we pivot, how do we get ready for AI, how do we look at our processes and look at our systems, and what kind of technology we have that we need to start rethinking our transformation roadmap. what I'm doing right now is looking at strategy and objective key results. What is our objective and what are the key results and how do we get there using transformation and strategy. Ravit Gutman: I love that. you and I so a little bit on a shared story, but Bo and I officially met in the IOFM and I got to share a conference with her in the last SSON in Orlando. going through the shared services and the and the outsourcing conferences, we're seeing the shift and we're seeing the pressure that is coming from even all the vendors that are on the floor to transform how the work has been done. I know you just got back from SSON, was it San Diego, right? Bo Senu-Hodo: Yeah, San Diego. Ravit Gutman: I'm curious to know, it's been a while since the last SSON conference What are some of the changes you're starting to see there on the floor from the vendors, from the presentation, even the conversation that I know you had is there as a speaker. Bo Senu-Hodo: Yeah, when you look, you're seeing a lot of boutique vendors, and they're coming up with everything you hear is AI is the buzzword, right? I'm not even so fixated on the mix of vendors that I saw, but you see there's a mindset shift in the attendees. They are looking more than looking for more than the next tool. So I held a session that was pretty much the first lab series that was held ever in the history of SSON, where we come together and you look at a process and looking at All the things that was done prior to whether going into a new technology, outsourcing is pretty much what is the issue at hand. It's not about the next technology that's going to save the day. How do we look at our processes holistically, end-to-end? Who are the key stakeholders? What is the OKR? What is the objective and key result? What kind of targets are we setting to drive strategic change? it cannot just be looking at it in silos. you can see the appetite is changing because everyone is like, yeah, AI. But what is AI gonna do for me? that's gonna change my world beyond just FTE reduction, beyond, cost and everything else. What is the impact? To this new era of AI. we see a lot of vendors that I saw, a lot of them doing a lot of workflow stuff. A lot of them are now looking more into how do they take away all the manual effort, different spreadsheets trying to, tie things together and giving more a holistic view where I can, as a global transformation principle, I don't want to just look at my areas that are working. What other areas are deficient? In my whole invoicing process, what is the difference across regions, even within APAC? What is the difference in Korea? What's the difference in in in Thailand? You can't see all of that just sitting in one space. You need a tool. And I was very impressed by some of the vendors that have some of these tools that can give some of us the information we need. And that saves us time. So we know exactly where we need to tackle which area is fully automated, which area is not automated, why? Is it a culture issue? Is it just something that was off the radar? So I think that is pretty much. You know, what I saw in San Diego and I think it's I spoke to quite a number of people after my sessions and CFOs and head of shared services, they're like, Bo, this is time for us to think. And we actually even need to start a community beyond just coming to these conferences to tick the box. Ravit Gutman: I agree, because a lot of these conversations have been about the technology. And I'm curious to know if one of the things that you saw in that conference, so coming from the outsourced space, a lot of time the technology was influenced by that outsourced team that you selected essentially for the job. So if you're going with the whichever team you you're choosing, essentially that comes with its own technology tool and transformation initiatives. Where do you see that space going actually right now? Bo Senu-Hodo: I think I wouldn't really say that they are the ones driving it. A BPO is an extension of you. It's like taking your child to daycare. They are not going to understand your processes like you do. So I think that one of the things that are going to that is going to change in the future, it goes beyond a lift and shift. We've always done lift and shift to meet targets. All our commitments in terms of headcount reduction, cost savings to the C-suite, but that's not the reality. now what's happening is a lot of companies need to start thinking about streamlining, looking at their processes, using data. A lot of times we're driving short service initiatives without data. you send it to the BPO, you don't even understand the BPO's readiness. What is the BPO's transformation journey to also work smarter, work leaner, and work better? And then what kind of systems and Ravit Gutman: Yep. Bo Senu-Hodo: tools are they using? Are they also using third-party tools and partnering with other companies that they don't really understand, but it's just partnering with them to sell it now to the end customer? And it might not even work for my business model. So it's time that we need to partner with the BPOs, and we are the only ones that can let them know where they are lacking, what they need to do in order to service our accounts. Then it's as good as bringing it back in-house, right? Also, looking at what kind of technology are they using. A lot of the BPOs are using antiquated technology. And whatever technology is working for one of the customer A might not be what's going to work for customer B because customer A and B might be at different maturity levels. So that is where we need to speak to their transformation team. So I speak to my BPO's transformation team to understand the alignment. What is the strategy? Where are we headed to? I mean, if I did a lift and shift and you're still doing the status quo, all because labor is cheaper in your area, I used maybe five people. You're able to do ten and there's been no streamlining, there's been no synergy, there's been no change. I mean, it's pointless. Ravit Gutman: that's really where the paradox hits. this is where you are seeing this in your front of the line seat, where that relationship has changed in in the last year with those VPM team because it sounds like what you're saying already that the way the relationship used to be with those outsourced team was just making sure that they throw to people. Take care of the job. And again, a lot of time they came with their own you may have come with a process, but they've definitely have come with their own a solutions, their own tools. it's been like something is under the box. it sounds like finally like teams and and and hearing you taking the front seat on this is you're taking ownership and and actually taking charge of those BPO teams with having the right tools to have the full visibility for these teams, correct? Bo Senu-Hodo: Mm-hmm. Yeah. Exactly. And the other thing is, what does it take for us as a company to move from automation to autonomy? We need to start looking at that holistically, right? Because we see there's so much complexity. But the thing is, we need to start hard with a vision and scale easier. And the other thing, too, that I see is we need to fix the process first, A lot of people, Ravit Gutman: Yes. Bo Senu-Hodo: insured services. We are fatigued because at the end of the day, it's like, what is the way out? But unfortunately, we cannot just bolt on anything. We need to standardize before we automate. It doesn't matter. No matter what AI is going to do, it's machine learning. It's going to learn garbage. It's going to learn broken processes. And every time you're still going to have exceptions, and then you still need intervention. And then you have all these variations. So at the end of the day, you might use AI, but if you look at the cycle time and how much time is taken and all the touch points, you're back to square one. Ravit Gutman: agree. that's what we're hearing a lot in our community as well. we're seeing people that have been a year or two post implementing a phenomenal tool that can provide so much, but still people are stuck in the same way that we're doing things in alt systems. being able to go back and drill down to the actual touches and to the actual activities and making sure that you have that full visibility to impact change is where we're gonna see that change. this is where I would say even from BPO team, I had the on on the previous conference, I just came back from I was talking to one of the probably largest shared services partner. And they said they are scared to even use the BPO term and they're looking to change that terminology as a whole because the whole expectation from them as a partner has completely transformed and what customers are expecting right now. so it's something, it's really a pressure that we're feeling all over. now that you've seen that essentially model shift of clothes, and let's go to the part that you see where the most tension is. let's go back and talk about that paradox. Cause really the paradox is the way I see it for the past twenty years and the value of shared services was essentially how we can scale, how we can put more people in lower cost, standardize the process. essentially now AI can do a lot of that transaction work. we no longer need someone to key in the data and match the data and route the data and and and answer different type of supplier question. These are all the very things that the model was built on. these are the things that now AI are changing. that's one of the big part that is one of the threats that exist to these type of models. when you hear the framing that is coming right now from these teams, how does it match to what you're actually seeing, what you've seen right now in SSON? Bo Senu-Hodo: I a lot of people are worried about AI is going to take my job and AI is going to, take over, even the BPOs. But I don't believe in that, is redefining the human role. One thing we need to see is the agents are going to execute, but the humans are going to govern. we need to look at the governance structure and rather deploy or reassign that human role to more the governance and the accountability. And the agent is going to execute and it's all going to be based on whatever history is going to learn it. Also, we need to look beyond an agent like invoice processing. Even if I have an agent that is doing all the invoice processing or responding to all the vendor inquiries, if there's not another robot in sourcing or doing purchase requisitions and POs that are talking together, we're going to still have a lot of. Exceptions. I don't think there should be a scare on AI is coming to take my job, but more about how do we as a short service organization, as a finance organization, redefine the human rule. And that is something that is not still being thought through. What is the human still going to do versus what is the the the agent gonna do? Ravit Gutman: So that's really interesting point because even for us in the community, governance is the biggest thing. It's to understand how those roles are redefined. between your team today or or even from what you're seeing with other teams, are finance leaders and their BPO teams are talking about this openly yet, or is this still essentially the elephant in the room that no one is touching? Bo Senu-Hodo: So actually it is something we're talking about. So I just I've been on a project rolling out AI enabled OCR. So the first thing is to our BPO. If we enable, we deploy this tool globally, we're gonna have to realize some headcount reduction. And not only headcount reduction for me, I'm big, I'm more on on How many hours is saved so that I can have my employees do more value-added stuff? Instead of getting invoices, scanning invoices, trying to extrapolate data into Ariba and back and forth. It's pretty much when we deploy this tool, what is the objective? The objective goes beyond headcount reduction, but how many hours am I saving? Is it saving my business? Is it saving my vendor? And then what is the end user experience from deploying this AI-enabled tool? And that is how we looked at it. And we've saved over 15,000 hours in the last three months. You're actually driving your vendors to also follow compliant ways of sending invoices. And it's giving the team more opportunity to look at exceptions because a lot of things that the machine doesn't learn, it goes into an exception queue. You're still going to need human beings to eyeball. You're still going to need human beings to make sure invoices are not paid inadvertently, because if there's a lawsuit, there's a problem. The thing about shared services, and I say this, you cannot treat it like Tesla, where you put your destiny into the hands of Groki, and Grocki drives you, understands everything. Even at that, if for any reason you're asleep or you're intoxicated and the cop stops you, is it Grocki that gets in trouble? Or is it you, the driver? So you still need to own that driver's seat, irrespective of whether you're using agents. And I also believe in one thing that is missing. We need to build ones. The reason why we have a lot of hysteria, a lot of confusion. There's nothing different between the day of AI versus the day of RP and all the other things we've seen end to end and everything else. Why are we still stuck? Because there needs to be one foundation and more processes. But we have too many foundations trying to fit it into a process. And that's what is killing shirt services. Ravit Gutman: when you define foundation, what do you explain to our team to what are you referring to? Bo Senu-Hodo: I'll give an example. You have one invoice processor, and your first volume is maybe 10 invoices. You already have systems in place and a process of how an invoice comes until it gets paid. Then you hire two more people. The two people that are coming should follow the same process. Otherwise, what happens is you start having variations as you scale, as you expand. And I think that is one of the big things. The issue is not that we don't have the technology. The issue is now that we don't have the processes, but over time, because we've lost people, tribal knowledge, we keep on moving ahead of ourselves. The foundation has become broken, and then now we're finding different ways to do things when truly processing an invoice is not rocket science. Supplier sending an invoice should be no different. in company to company is just pretty much how it's coming in and the tools that are being used. But the process from end to end, whether it's a PO or non-PO invoice, the variation should be few and far between. Ravit Gutman: That is true. but although in the same time if I take ten years back when we did a transformation project, the goal was really to standardize global operations under the same process. We are seeing now more than ever the requirements that exist per specific regions per specific country right now with all the different a compliance requirements that are coming for invoice processing. So this is where leveraging the right tools, the right partners and building that right foundation is set. I do see that we are heading more towards country specific type of processing where we're looking to consolidate in the past because of just different type of of mandates that are coming now in from countries. Bo Senu-Hodo: Yeah. I have my opinion on that, right? Processing an invoice, let's put tax aside or any statutory requirements, should not be any different. The tax requirements and the statutory ones will be managed on either a regional level or country level, or even on a municipal level, which at the end of the day is only truly twenty percent of the full picture. Vendor invoice needs to be paid. The first thing is to make sure do the goods receipt match. Does the invoice match? Is the bill to ship to? Does it match? What is the date of the invoice? When do I pay the invoice, which is driven on payment terms? It's standard. Then we get into the other in intricacies like e-billing, Brazil Nota Physical, VAT complexities, GSTs, HSTs. That is a separate thing altogether. That even at that, based on the country, you can have agents or tools that can manage that. We're seeing e-invoicing. That is now that. Pretty much all over the place, which should be more streamlined. So I think that at the end of the day, the basics of invoice processing one on one should not be any different, country to country, system to system. Then when we get to the tax bit, that is a different discussion to have. But right now we're seeing a lot of struggles that even before we even get to that, we're already overthinking it about how am I gonna do this? This is not gonna fit because there's a tax requirement in Brazil. It's different than Mexico. It's different in China and all of that. And then we lose traction of the true picture of what we're trying to transform and mature. The maturity of the process of invoice processing has nothing to do with the tax. It's actually on the back, on top of it. Ravit Gutman: True. And the winners there will be the teams that move a lot of these type of things to delivering on those outcomes on both sides and understanding that end to end process that exists underneath essentially as you called it that foundation. otherwise, as you mentioned, the AI is gonna be faster in making a bigger mess. As we are seeing in some Bo Senu-Hodo: Also, Ravit Gutman: cases already. So Bo Senu-Hodo: yeah, and not only that, there's a lot of noise, we need to sit down and look at there needs to be process transformation before automation. if your processes are not transformed, you're running automation parallel is very key. It's like you run an AI-enabled OCR. If you don't have consolidated email addresses or a way for vendors to send you invoices, it's not gonna work. If you have something The machine is not going to learn if the vendors are still sending it to the business partners or they still want to do a snail mail. So there's also a lot of change management that I think we haven't done in the short service space, especially source to pay, that we need to look at. And what is best practice, supplier requirement of billing you is simple. It's not even defined across the board. And maybe we need a tool. To help vendors to make sure that if they're sending invoices that are not compliant, it's rejected. It doesn't even get into your workflow. So it doesn't begin to count into your cycle time. Invoices come in. What are the key exceptions? And how do you start working those exceptions to be fixed, to be in the normal flow? And only leave those exceptions that are very statutory or state or regional or country mandated. It's still something that we've not been able to separate. So we have a lot of noise and we're never able to move things forward. So by the time we go live with anything, there are things that were not talked through, the processes are not talked through, and then you realize that you're only using a quarter of the company using the tool. And then it's just so it's it's a lot of mixed, it's a mixed bag. Ravit Gutman: I agree. I agree. I wanna go back to one of the things that you said on on how you're measuring right now your team on the BPO side and and some of the things that you're you what you're expecting from them. part of that paradox that we talked about is really shifting from volume work to outcome. so you talked about how do you reduce how much time is spent essentially for processing and different things. one of the things that SSON just published on a research with the EY was showing that only eleven percent of shared services organizations are truly recognizing that value creation. when you look at the about most, which is about seventy one percent, I believe I'm still mainly measuring just on cost or service level or even the industry itself is still using that same scorecard. I'm curious to know, how do you measure success today for a BPO team and how does a great month look like? Bo Senu-Hodo: Yeah, so the first thing that I measure my BPO team by is I run data, looking at volume of invoices, and then looking at FTEs, but looking at the quality, right? And efficiencies and being able to look at the outcomes. What is the objective? For my objective is to save a certain number of hours. So my business partners are not bought to bug bugged down with invoice issues, change orders, and everything else. And then also looking at how we're cutting the manual steps. How is my BPO cutting manual steps from intake of an invoice to payment? What technology do they have at their disposal that they're not using? Or why is it working for like the Americas? And I'm seeing a problem in AIPAC. I need them to tell me. So I run data. The other thing, too, is I look at it is okay, if we have PO invoices that are touchless. I need them to explain to me what they are using their time for. Because if the three-way match happens, it goes into the ERP for payment. What else are you looking at? Then I also ask if I see the inquiries coming out of my snow tickets that keep on going up every month, that shows me there's a problem with the process. Because we can process the invoices in a timely manner. But if my invoice queries are like doubling every month, and it's the same thing where a vendor is asking for payment status or There are certain issues, I need to understand where it is broken. Is it a process that needs to be looked at? Is it the vendor issue? Is it the business that is the bottleneck? And I also think that the BPOs need to report those things to us. They should not only wait and give us green. Everything is green. They process, let's say 20,000 invoices, all within SLA, that's great. But out of the 20,000, how many of them have now become an inquiry? Because it wasn't processed accordingly. It was either the wrong coding. The other thing too that I instituted is a playbook. We should have a playbook and me, that playbook now turns into machine learning. You don't need to go to the business each time an invoice comes in. By now you should learn. If it's a utility payment, it's a utility payment. You know it comes from this company code. You know where you need to code it to. Only reach out to the business if it's something new that we've never seen before. So that is one of the things is looking at the BPO. How are you guys working smarter? How are you? Scaling and how you've been efficient. Because if you're just doing the status quo, then there's no point in us outsourcing it to you. And what does your future look like? Where are you guys trying to carry your clients to? Whether it's AI, vendor statement reconciliation. If now the BPO, you have 12 people that are looking at vendor statements on a monthly basis. What kind of transformation are you thinking about to speak to me that hey, we're gonna maybe have to implement a tool, we're gonna have to do XYZ to maybe shrink it down to three people and get Twenty five hours of savings per head. That is showing me that you, the BPO, you're thinking ahead. Ravit Gutman: Wow, there's so much to unpack here and I just took four mental notes on everything that you had here. first of all, kudos to you to start to tackle everything in terms of those manuals and playbooks because I will tell you I should definitely book you to one of our sessions in the community 'cause that was a big discussion point on what is the best way to be able as a leader on on these type of transformation to build those type of playbooks, especially when your team is outsourced, which that is one of the biggest struggle from that aspect. I'm curious to know, from your end, you're extremely data driven and I know that from you because we we had the countless conversations on this. Do you rely on the data that is provided to you by the BPO team, or are you using your own tools to measure essentially the BPO team? Bo Senu-Hodo: my BPO team knows me for one thing. I'll ask them for data, I run the data myself and do a comparative analysis. I've actually kicked off an initiative that I want data every month in a dashboard, telling me the story, and it should tie exactly to the data I'm running out of Kenja or out of any of our systems because it's the same system they're using. That's number one. We should not always rely on the BPO to run the data and give you the outcome. You own the child. You know exactly certain things concerning the child. So you need to communicate what you want and you always need to be cross-checking. You always go need go back and check the diaper to make sure there's no diaper rash, even though the daycare said I change your child six times a day. So you always need to do that. And in all fairness, the BPO is just your extension. So I do the flip. I want to run the data and manage my BPO. Because I want to make sure number one, they understand what they're doing and there's some veracity to the data because they might be executing based on some data that is inaccurate. So I need to give them that data and we need to cross check to make sure there's alignment. Ravit Gutman: You've heard her everyone, because this is the golden nuggets because so many people are relying on that those BPO reports that they're getting that as you mentioned, giving you those green boxes of saying everything is on time, on track, and everything, and it doesn't give you that true value. one of the main piece where I see you're way ahead of the curve on this is understanding you said you built those type essentially dashboards for yourself, but even knowing what to ask from this dashboard is something people struggle with. Would you agree? Bo Senu-Hodo: I do agree. the thing about the dashboard, it's summarizing, but the data behind it, I'll give you an example. We're looking at volume, but then I need to understand my PO versus non-PO split. And when I run and I see that I have a lot of PO, non-POs, but then I'm seeing the same non-PO vendors being paid as POs is a concern. I want to understand why we are doing it as a non PO versus a PO? Is it for trying? Is it, I mean, it's it's what's the reason? Is it because PO has been exhausted? We needed to pay the vendor. And then I need that kind of information to drive something strategically upstream, downstream. And then also using that to also manage the BPO team. Anytime you see non-PO invoices, I see the cycle time for non-PO invoices is 14 days because you're waiting on a WBS from the vendor. But if you look at a pattern, it's the same vendor every month. So you go off the last coding. I also want the PPOs to realize that it's time for them to move away from just following rigid rule-based templates. Whatever SOPs that were given by the client. During transition, a lot of times it's not revisited. And it has to be revisited so that you begin to look at things that are reasonable, adaptable, and you're able to execute multi-step workflows from start to finish instead of following a broken template that came as a lift and shift. And then what happens is a lot of times we the clients are running a mile a minute, we don't even realize something is not working until something is broken. Until there's noise from the business that it's not working, then we start going backwards. But we owe it to the BPO that what I gave you this year, I need to understand what have you done with it? What have you transformed? What are some of the what are some of the the advice or some of the solutions you want to suggest to me? So we move things forward instead of doing the status quo. So I think you owe it to yourself and you need to manage the BPO and not the BPO managing you. Ravit Gutman: I agree. I can tell you that even in our own company, one of the things that I would love to be able to see before we implement any type of change and model how will that change impact the process using those essentially SOPs or impact essentially what type of other errors the system can spit and try to get to a point that it's proactive, but it's been as you mentioned, these SOPs have been an outdated exercise that has been potentially worked by one sided team. this definitely goes back to those type of expectations. I wrote four things that I wanted to unpack from you you you're dealing with so many things that so many of our Customers are in and so many of our audience as well. I want to go back to that statement matching comment that you mentioned that you have 12 team of 12 on the BPO side that is doing statement matching and your expectation for the BPO to to see how you can solve it better. that's where a lot of leaders are struggling right now is how does it work and where is that definitive line is do I ask from that team to come up with the solutions which normally they'll partner up or bring a solution that they work with in another customer and and which as you mentioned potentially not the best fit for me. Or is am I as the leader right now, go and look for a statement patching tool and see how am I taking this team from 12 to Two in an automated way, especially like State of Matching, which is one of the highest use cases of AI today and that can really be reconciled. So what would you tell essentially financial leaders today to approach tasks like this when it's even build versus buy type of technology working with the shared services? Bo Senu-Hodo: I wouldn't let the BPO make that decision. The first thing that I looked at, I did a regional view to understand the pain points. Where do we have a lot of lagging cost and low visibility in invoices? why are we seeing a lot of credit memos on used credit memos where pain invoices, reconciliations are all over the place, and then at the end of the month, it becomes a problem for record to report whether the accruals are done accurately or not. the first thing that I look at is I ask the VPO team, how are you guys reconciling the statements? We're calling the vendor to get a statement, we're pulling the sub the vendor payment history invoices out of SM S4, and we're going and looking at each line item. Obviously, you're going to miss some things. now I need to understand what kind of AI can be used to be able to pull information from S4. Get the vendor statement and is read by this same AI tool and look at what is the supply reporting versus what do we have in the sub ledger. And out of that, doing a summary to say this is missing, spit it back to the vendor, so they send the invoices, or this is what we have. How do we go ahead and process it to short pay the invoice? And I'm doing the RFP with different vendors. I need to understand the fit for purpose. Based on that, I'm asking for proof of concept for free from these vendors. I'm going to give you 900 and something vendors. I need you to go and do an analysis and bring it to me. And I want to see this real time. Based on the outcome, I want to be able to see something just beyond a vendor statement reconciliation telling me what the vendor says I owe them versus what is in my system. But being able to automate also the accrual per vendor aggregated. Per company code and so forth. So that at the end of the day, whatever took 12 people plus the accounting team plus the business and also even work on the vendor side to do is consolidated, and I'm being able to see it that even when I'm in an audit, I don't need to start scrambling back and forth. I go into this tool and I'm able to pull it. I've looked at a couple of vendors and still there's some missing pieces. A lot of them are doing something that is more okay. An aerial view. But if it can drill down, so that some of my processes that are multi-workflows are all amalgamated, we have a problem. So based on that, whoever wins is who the BPO is gonna have to use. Because the BPO, a lot of times, the interest is not so much about getting me the tool, but then at the end of the day, is I mean there's more justification to be done. And at the end of the day, if you don't understand what your needs are, you can't let them be the ones to tell you what your needs are. And based on whatever they're doing, I run a report to see if I'm seeing a lot of credit memos that I'm finding myself and you are not catching it. So what kind of reconciliation are you doing even with these twelve people? I need it to be justified. Ravit Gutman: One of the other things you've mentioned snow, which a lot of teams right now are transitioning. So they're post it post-transformation. And a lot of those AP teams are becoming part of a support organization of different types of issues. We're seeing more and more solutions that have a built-in ticketing system between the business and finance. So it sounds like you're you're already, I would say, head deep in essentially building that process. Can you share a little bit about Bo Senu-Hodo: Yes. Ravit Gutman: that? Bo Senu-Hodo: Yes. So we went on the ServiceNow journey about five years ago. Never got to the optimization, looking at all the different forms, looking at different processes and trying to understand how we can leverage this SNO platform. So the first thing was standardizing. If you don't standardize, you're gonna have different forms all over the place. And now we mature the process to the extent that we have a bar called Tetsu. I update knowledge articles for my space. So the first line is you go to Tetsu. I'm checking on the status of my invoice or vendor invoice. We're still using it internally, it's not yet been rolled out external. Whatever questions you have, you get into Tetsu. Tetsu goes into the knowledge articles and pulls the information for you. After several steps, if Tetsu is not giving you the answer you need, it will now create a ticket for you. And it goes through the snow process. And if we see There are the same questions coming through Tetsu, and Tetsu is not able to explain it. I will get a notification as that process owner to create a knowledge article. ServiceNow has given a lot of visibility, is given a lot of it's auditable. You're able to see the step-by-step of everything that has gone on with that question. And you're able to now get some more metrics out of ServiceNow to see where your pain points are. Is it at the procurement level? Is it at the business level? Is it at the vendor level? And also the other thing has helped has helped us consolidate all these different email addresses that either your business partners are sending emails to, vendors are sending email to, and then you have emails going to individuals. ServiceNow has actually taken all that away and is one place where you can go and see everything you need and it's real time. Ravit Gutman: for you getting notification on building those articles is huge. for any of our solution providers listening, that's a huge takeaway by itself. that is definitely I do know it's a snow activity, but that is definitely where not something I've seen yet in some of those a solutions that exist on the order on the purchase to pay side. So excited to see where where this is going, definitely. I know you are heading soon back to your BPO team, more towards Asia Pacific upcoming soon. I'm curious to know as you're heading before your travel, how do you get really those teams aligned on the definition of success? Bo Senu-Hodo: So basically, the first thing that I ask them is, what does success look like to each of your countries? Because APAC is a cluster. Different culture, different ways of working, different requirements. they will basically now tell you everything. Success looks like we're able to get the invoices, we can code it ourselves, and then we can send it to AP, and then we still want to see it and all that. And then I begin to give them scenarios. We map out their as is, and I did that country by country in order to run this AP capture tool. And in the beginning, there was a lot of resistance. Change is one of the hardest things to get in the APAC region. Because they all work in silos and they have all these different, there's a culture, even how you deal with the suppliers, and even internally how you address things. So basically, is making them a partner, let them own the outcome. I'm just a conduit to help you see that outcome. Because you're going to be the one to live it. So I'm not just going to shove something down your throat. So, Bo, why do we need AP capture? The question is. How long do you want to keep on messing with paper? You can lose it in translation. You can end up even paying for invoices that don't even belong to the company. Wouldn't it be easier for you to see this live? That by the time the invoice gets into your queue for approval, all the checks have been done. And anything red tells you what needs to be fixed. And you go there and fix it. And you can spend more time fostering your vendor relationships, knowing that when month end comes, you're not scrambling. For invoices, you have a cutoff, everything is all over the place. And you're able to work smarter and you're able to be more efficient. That whenever you're asked a question regarding an invoice or vendor, you're not go spinning your wheels in ten different systems, ten different places, emailing everybody. And they're like, Yeah, you have a point. And that is how I've been able to gain that trust and successfully go live. Now, why am I going to APAC to my BPO in China? Because I see it's time to move things to Hyderabad, which is actually the center of the BPO. There's really no reason to have a team sitting in China, a team sitting in Hyderabad. In this day of AI, it doesn't matter whether it's multi-languages, we have tools that can translate processing and invoice in Japan. An invoice in Vietnam or even in the US should be no different. The taxes might be different, but the invoice speaks to the same to speaks the same language. So it's going there and basically saying, own the outcome. How can I help you own your outcome? Ravit Gutman: I love that you heard Bo really. this is where you move the conversation from how many invoices do we process to how do we do we create outcomes and impact and affected cash and suppliers and actually the business and I love that and this is where I also personally seeing a lot of that shift. I Personally love the scorecard method, that everyone have the same type of scorecard on both teams. So after really defining those success and really find that type of scorecard that both team can celebrate together when you're trying to bring those teams together as well as you especially if you have, like I said, that hybrid. But let's say let's move to our next segment. I really wanna talk a little bit about What does AI ready partnerships look like? And and it sounds like you are you're on your road on finding what is the right AI partner for for your firm. It sounds like you had those conversations already with your BPO team. but really in practice, what makes a partnership AI ready? And I think you talked a little bit about, like I said, the foundation and the and the process, but I think where How do you get to the point of of building essentially that trust in the people with those type of tools? Bo Senu-Hodo: I think the first thing is I need them to explain to me how they derive how they derive the rationale to develop those tools. What test case or what scenario did they use? Was it a company? And I want to understand, did you look at all these different data points? Did you look at the pain points? Did you look at the processes that made you create this agentic bar? Also, the thing is, when I'm even looking at AI, I go beyond cost reduction. Cost is one thing, but I want to understand how am I going to have a faster cycle time and efficiency? Number one, with this AI tool you're trying to sell to me. The other thing, too, is it goes beyond the faster cycle times and efficiencies. How am I going to be sure that this AI agent is going to have autonomous exception handling? Whereby I'm going to have minimal intervention because the machine has learned how to handle exceptions. within compliance and within a governance structure. Also, the other question I'm gonna ask you is when you did UAT, what was the enhanced accuracy? So these are some of the things, and they're looking for greater scalability. I want to see how my high-volume invoice processing across all these business entities and all these varying vendor formats, how is this tool going to resolve it without me expanding my headcount? Because if I'm going to expand headcount, I want it to be in a place of governance. Not in where they're still getting into the minutiae and everything else. So, me for me, that is one of the big things I ask these vendors. Another thing, too, that I want to be able to see, and I think it goes beyond AI, and this is just my advice to my peers out there: being ready is not going to be dependent on that AI or that BPO. You need to have a holistic view, whether it's by region, by country, where are my gaps? If it's working in the US, what what why is it not working in Chile? Why is it not working in Colombia? Maturity-wise, which of my countries are more mature? Which of my countries are more automated? So you have that full picture of the landscape? So you know exactly what you're working with, where are the variations? How do I fix these variations to have more standardization? Because you're going to realize that one region is more automated, maybe because that was the focus. Now you want to get the other region to that point. But what are the steps you need to take to get there? Very, very important and you owe it to yourself. AI is not going to change it. Until you get that done, then you're able to see it's mature enough for you to automate. You can never automate an immature process. Ravit Gutman: hundred percent. And I think that's that's your you're hitting the nail in the head. AI is not the strategy, it's just the tool. And I think so many leaders are just seeing it as like, what is our strategy? And and and throwing these, as you mentioned, AI buzzwords. And it's really that there is so much work ahead of it. There is so much things that needs to be prepared. There needs to be a certain level of maturity, as you mentioned, from the partnership. And I'm I'm gonna push a little bit. I'm sure you had like a proof of concept you ran already in the past year or so. Do you have can you share a moment of of like again without naming too much, but really when you had something that you knew that yes, that there is really great use case that we can do here right now. Bo Senu-Hodo: Yeah, so with one of the vendor statement reconciliation vendors, I looked at the tool and I actually gave them a scenario. And I think that is where they realize that, we're not yet we're not there, we're not quite there yet, but we have it on the roadmap. And I made it clear that actually that is more critical than some of the other things that we're seeing, right? And basically they're like, you know what, this is good advice. We need you on advisory because you're giving us more in-depth. AI solution providers should never build a tool without having subject matter experts that have industry experience on the advisory board pro bono if they want to be successful. Otherwise, you see a lot of vendors replicating the same thing, just under a different name. And at the end of the day, it doesn't speak to us. And through the proof of concept, I show them things they needed to fix, I show them what is going to work and what's not going to work. And also explain to them that it goes beyond just an agentic tool. It has to make sense through the whole supply chain. There needs to be business added value. It's not just another tool. And if I'm not seeing that business added value, then I might as well just do status quo. What are you gonna do to shrink these 10 steps into two? And then also, what is the algorithm you're using? What history? And that's the question I asked. No company is going to give these companies data for them to develop the software. So, how are they developing the data based on what data? What data did they use? The pharma industry is different from a manufacturing industry, different than retail. So, my thing is what data is being used is static data. And then I want to be able to see your UAT. What kind of testing did you do to get into that final phase that now you're in the market telling me that this tool is going to work for my purposes? Ravit Gutman: this is why a lot of companies are now in the build versus buy. Because for so many years, a lot of these major players were saying it's okay, this is the best in class, this is this is how you need to use the tool. We've seen that a lot with the SAP world, essentially where everyone needed to fit a certain box. and we Now we're live in a world that we can actually take the uniqueness of the business and the industry and get really those subject matter experts to build those things. And and I can personally attest that we we see that on all of the RFPs we're part of with customers today, that exactly what you mentioned, like doing scenario based demoing is becoming the new things. And also if if you have the right vendor essentially or partner that you're working with, they're gonna listen to you and and Yes, maybe they told you it's it's a roadmap item, but they will listen to your ideas and and and promote that as well afterwards because really those things are coming from the customers. and it's a very Bo Senu-Hodo: And another thing too. Ravit Gutman: sorry. Bo Senu-Hodo: Another thing too that is very important, whatever AI tool we're gonna get, we need to ask ourselves: is this autonomy versus traditional automation? Because we have traditional automation that follows rigid pre-written rule-based scripts. And for AI, it has to be autonomous. It needs to evaluate the context, it needs to plan ahead, and it needs to solve unexpected problems on its own. But if that's not happening, and I still need to interject. Keep putting bodies on there, then we have a problem. And that is something that I'm looking for. I want something that is going to do self-correction. I need a tool that is adaptable. And I need a tool that is bounded by freedom that operates independently, but within human defined guardrails. And that is what I'm still yet to see in some of these tools. Ravit Gutman: And I would agree with you because I'm a lot of the tools that are out there today are still like a very nice macro, behaving like a really good macro on the back end, or maybe some really more advanced machine learning. But few we really are seeing those agentic behaviors. And I think a lot of it is also because I think many companies are still trying to figure out how does essentially that autonomous governance look like? How can each customer can control their governance level? And and this is what I'm starting to see with with some of the more mature solutions out there that they are really taking a lead on that is really really focusing on autonomous governance and how can each customer control a their own governance on the AI. That is really where that configuration would live. That is really where the the subject matter expert can can control essentially these type of things. But I think we're still a long way ahead because even now without seeing an implementation, the data foundation is still garbage. So you can buy the best tool out there, but if your data foundation that you're bringing into the tool As you mentioned, the historical data, everything that that is coming in that essentially the AI needs to feed from is so corrupt, then it's just gonna multiply that issue. And I think we see ourselves a lot of time, like really, even the way we approach an implementation is how do we first focus on the data set, see what we're able to generate from the data, to then take it to the next level and and and and build that essentially autonomous governance. Bo Senu-Hodo: Agree. Ravit Gutman: So I think my last thing is really, I know we talk a lot about the BPO team, but as you know me, the human side is probably the piece that I'm is closest to my heart and I'm most excited about. And I know that you just came back from SSON and you had so many phenomenal conversations in the community level to really talk about exactly that. And and I think you we both agree and we talked about a lot about it, that in the end of the day, AI and all of this technology should really enhance the the people requirement on this. It's not replacing them, it's really making them focus on the area where they are most needed. And and I I feel that there's just more and more areas that are opening up right now. even I saw again another SSON research that found that really 80% 82%, I believe, of leaders and now see that AI and Digital fluency is the number one leadership skill that is needed. I personally, like I said, we spend a lot of time to really what does it mean to build essentially digital leaders today? so I'm curious from your end, again, if it's from SSON or even from your own team, what are some of the roles that you're starting to see that are changing? And if you can share a little bit with our audience, like What are some of the things that you're seeing right now evolving on the people side that gets people really excited and then and and really with some of those leaders on how they're building those type of skill sets? Bo Senu-Hodo: Yeah, so definitely we need to redefine the human role, right? So what we've done is as a company, we've followed the agile framework. We've gotten rid of all the monotonous processing, everything is within the BPO. And then also, even as we leverage like Tetsu and some of this AI-driven technology like the AP capture, we're trying to look at our human capital to do more strategic judgmental stuff like eyeballing. Some of the things to make sure that the machine is learning correctly and doing the right thing. And then also looking at building value teams where you have continuous improvement, continuous adaptation adaptation, because you need that, right? And then also looking at the human experience. There's a psychological part to all of this. So, how do you now have a team that looks at the end user experience? What are some of the things that we're seeing with Tetsu? Some people might be frustrated with Tetsu. But then you want to have a team that actually manages that, whether they're the ones doing the surveys, out of the surveys, they're looking at how we can build the bots better, how we can define the processes. So to me, we still need people, but we need to we're gonna need a different skill set. And even the skill set that we need is not still properly defined. Because once it's defined, then it gives your employees something to think about, whether they need to go for more courses or they need to pivot. But till today, it's still not clear that. What am I gonna do with my current workforce, even though you've moved it to the BPO? The biggest question right now goes beyond us as a business. The BPOs have to start thinking strategically. What is it gonna look like for them in the next three to five years with AI? Because they're also using human bodies. They're using a lot of homegrown tools. But now, how is AI going to fit in the BPO model? There's gonna be a shift. And they're still gonna need human human human beings are gonna be needed. But what is the in-demand skills? What are some of the value centers? I'm seeing more in the future. BPOs are gonna have to have something called value centers. What are these value centers? They are the ones that are creating awareness, they are the ones that have more creativity and relationship management and knowing when to challenge all these algorithmic outputs. Ravit Gutman: I love that. The value centers. Do you think that we're gonna see more with with all this shift, we're gonna see more companies actually bringing things back in-house? Bo Senu-Hodo: To be honest with you, I would rather before any company wants to bring something in the house, you need to be re you have to be informed. You need to really understand what is the pros and cons. What are the pros and cons and what is the benefit? Is it because in your mind you think if I bring it back, all I need are three agents to run the show? What you need to do is to understand what actually was the impetus for you to outsource to begin with. That's number one. And what have you been able to actualize in terms of efficiencies? In terms of savings. And now when you're bringing it back in-house in this current day economy, it's going to be more costly. Do you even have the right skill set to be able to stabilize the process before you optimize? Are you going to deploy the AI and have it tried and tested in the BPO first and actually try to get your ideal model and then shift it back in-house? That will be the smart way. I will deploy my AI. I will get all the things I need, but use it in my BPO. BPO, you have 100 people. I want to be able to see this replace half of your workforce. I want to be able to see the outcome. What is your objective? And based on that, then you move it back in-house. But if you do the reverse, it's going to bite us in the foot. So we really need to think. Ravit Gutman: And then this goes back to your foundation discussions. And I think this is where really not many people in your position or are are getting the opportunity to really think and and go through this all from end to end and potentially does don't have the right tool for this as well. And this is very insightful for many of them because I don't think that reskilling is anymore something that is a nice to have. It's going to be that investment that make this whole transformation work. And and I it sounds like for you, and again this is also part of your amazing personality, that you have been in this reskilling and coaching mode for all of these teams for so long and you're setting essentially a certain standard that many of our audience would really benefit of hearing. as well. So I want to do a quick lightning round. So essentially I'm gonna do a couple of statements and I want you to say the first thing that comes to your mind on any one of those statements. So one word that describes the future of shared services. Bo Senu-Hodo: Move from being a tactician to a strategist. Ravit Gutman: Not a one word, but I'll take it. perfect. the most overrated thing about AI and finance. Bo Senu-Hodo: That is replacing human beings. Ravit Gutman: Okay. And the most underrated thing. Bo Senu-Hodo: Is how much time you can have to raise the bar and carry your business to the next level and build high-performing teams. Ravit Gutman: Okay, that's a good one. One habit that makes a great finance BPO partnership. Bo Senu-Hodo: On the relationship. Ravit Gutman: Gold. This is I think that's that's for me one of the biggest takeaway to to all of our audience that is managing BPO teams. Last thing, a a book, podcast or a person you're learning from right now. Bo Senu-Hodo: I just had a book I was reading on continuous improvement It's actually a good book. Ravit Gutman: Please send it and as I'm in the process of writing my own book on the same topic. So we have our own transforming forward on our forward methodology, really talking about w what is the loop of continuous improvement in terms of playbook and a methodology. I'll make sure you're you're one of my first one to read this, especially if that was a good book. So please share. Bo Senu-Hodo: I found it. It's I found it. Kaizen, the key to Japan's competitive success by Masaki Imama. Yes. Yes. Because improvement Ravit Gutman: I know that book. That is a phenomenal book. Yes. Definitely. Yes. Bo Senu-Hodo: should be continuous, slow, Ravit Gutman: Mm. Bo Senu-Hodo: and incremental. And strategists Ravit Gutman: Yes. Bo Senu-Hodo: just don't bite everything in one goal. It's a process. We need to trust the process and we need to take it step by step. Rome wasn't built in a day. Church services was not built in a day, and we cannot put all the work we've done over the decades just into one day because there's AI. It's gonna break. Ravit Gutman: True, true. And I highly recommend this book as well. I think in general, just learning from the Japanese culture, there's so many different things, but really understanding how this is built. And I personally took this even to how to teach my kids certain things from that book as well, I have to say. I remember it was teaching one of my boy a lesson from that book, so highly recommend as well. Bo if finance leader listening today takes away one thing from this conversation, what would that be? Bo Senu-Hodo: it's time to own the relationship, own your processes, and move from tactical to strategic. It gives you a whole different insight into what a true shirt service model should look like and also what are some of the things you can leverage. Last but not the least, move from autonomy first before automation is key. Ravit Gutman: You heard her. And I I'm going to follow up after this with a special session for our community, Bo, getting all of our finance leaders that are right now in your role and working with different BPO team and for you to have a one of our think tanks together with you, would be extremely beneficial. So we'd love to have you there if you are If you would like to talk to our community as well. Beside that, thank you so much, Bo. It's always a pleasure. really. And for everyone listening, the paradox is real, but it's not the end of the model. So, as you heard, it's just a beginning and building a much better one, building on outcomes, bidding on clean data, on that foundation, on strong partnership. And remember, people are always in the center of all of this, and you've heard Bo as well. if you enjoyed this episode, follow XRP on air Spotify, YouTube, wherever you can find us and share it with someone else on your team. And we will see you next time. Bo again, thank you so, so much. This was such a pleasure. hopefully we'll see you soon in our community session. Bo Senu-Hodo: Excellent. Thank you so much, and thank you to the shirt services and GBS community. We have a lot of good times ahead of us. We just need to be aligned and be of one voice and it will be great. Have a good one. Ravit Gutman: Indeed. Thank you, everyone.