--- title: How JJ Taylor worked with ENZO to ensure AP automation implementation success url: https://www.medius.com/videos/success-stories/how-jj-taylor-worked-with-enzo-to-ensure-ap-automation-implementation-success/ updated: 2026-09-10T15:16:34Z --- # How JJ Taylor worked with ENZO to ensure AP automation implementation success JJ Taylor, a Molson Coors beer distributor, wanted to [modernize its invoice processing](https://www.medius.com/solutions/medius-accounts-payable-automation/invoice-automation/ "Invoice Automation") and stop relying on manual reconciliation and document storage. The **team chose Medius for its [AP automation solution](https://www.medius.com/solutions/medius-accounts-payable-automation/ "Medius Accounts Payable Automation")**, but early implementation challenges arose. An existing Eostar integration wasn't flexible enough, and a new Sage Intacct integration needed to be built. In this video, Andrew Timmons (Business Analyst, JJ Taylor) and CV Eaton (Director of Implementation Services, ENZO Unified) share how ENZO helped the project. They rapidly created and strengthened integrations using a SQL-based approach, resulting in fewer manual invoices, improved scalability, and a more future-proof integration framework. ### Transcript Hello and welcome to this webinar from Medius focusing on project success and how project success hinges on integration elegance. We have a particular guest list today and of course feel free to submit questions in the chat. We'll leave time at the end to answer any questions that come through from the audience today. Our speakers today there's myself, Rich Revill. I'm VP of Global Pre Sales at Medius. With us I have customer Andrew Timmons from JJ Taylor and C. V. Eaton, Director of Implementation Services from Enzo Unified, our integration partner in this case. You'll be hearing mainly from both Andrew and C. V. Shortly. Just in brief, we want to give you a a media snapshot of who we are very briefly. Snapshot and overview of our AP Automation solution and then shift quickly over to the JJ Taylor implementation. That's where Andrew will jump in and speak about JJ Taylor, how JJ Taylor selected Medius and some of the deployment challenges and showstoppers they hit during the implementation. We'll then shift over to include CV from Enzo talking about the integration approach, saving the project, our tight partnership with Medius Enzo's tight partnership with Medius and then Q and A. Hopefully it will be a very informative session with real world scenarios discussed by real customers and partners here. Brief, Medius has been focused on AP Automation for twenty years now. We're a global organization headquartered in Sweden with locations across the United States, the UK, Europe and Australia. We have over four thousand customers running the same standard product in the cloud, over half a million users worldwide. And we're Gartner Magic Quadrant visionary company. We have a global direct sales and delivery organisation with a strategic partner network that includes Enzo Unified and again we'll be speaking or CV will be speaking to that shortly. Not only are we on the Gartner Magic Quadrant, we're also recognised as a leader by IDC up here on the top right. We're a marketscape worldwide SaaS and cloud enabled accounts payable automation application for the mid market in twenty twenty. That's going to be updated for 2021 and onwards. With our cloud native architecture Medius drives continuous improvement in both system and process performance using machine learning and big data techniques. Very nice. So a quick snapshot of Medius AP Automation, an overview. And it was formerly known as Medius Flow. That's perhaps how Andrew might be referring to it. So it's the same product. It was just rebranded a while ago. So what does AP Automation look like for Medius? Our solution is designed for finance and AP and built for the Azure cloud. So it's not some generic workflow product that we're looking for a problem to solve. It's specifically designed as a specialized solution for AP Automation. We're built for the Azure cloud. So we're not an on premise product stuck in a data center access via a browser and calling it cloud. We rebuilt it eight years ago, starting eight years ago, from the ground up to take full advantage of the security, scalability, and business continuity that Microsoft Azure offers. We have two main components, AP automation and payment execution that we'll just describe briefly here. Part of the key capability, of course, is synchronizing the data from the various ERPs. The master data includes the vendor master, chart of accounts, POs, good receipts and other information. Continually and securely synchronizing that intermediates in the cloud so that we can get to work with a heavy lifting of AP Automation. When the invoices come in from the suppliers, we'll process those. But of course we're very pragmatic. We support a full spectrum of invoice submission channels including, of course, probably the most common is PDF attachment to an email directly from the supplier's billing system. We also offer a supplier facing portal for the long tail of suppliers to upload and query invoice statuses. We of course also can integrate with the invoicing networks for those organizations perhaps with a global footprint that require country specific compliance, often government mandated e invoicing compliance there. And of course the bane of everyone's life even now is paper. So paper invoices are received traditionally into our customers. They scan to email and bring them into the intelligent invoice capture solution here. The capture solution then takes advantage of packaged best practice workflows for AP Automation and a couple of them are represented here in terms of expense or non PO invoices where we're really driving coding accuracy support, moving to automatic coding and distribution, really getting the invoice in front of the right person at the right time to shorten the processing time, expedite the approval so you can pay your supplier on time. The automated matching PO invoices of course the CAPTCHA solution is an advanced cloud based CAPTCHA solution for both header and line level detail which is imperative of course for driving that tedious process for PO based invoices. And we don't just do matching. We go above and beyond traditional two and three way match to drive the highest level of touchless processing possible. An invoice comes in, goes to the workflow and can be posted automatically into the ERP. Of course if there are exceptions, pricing differences or quantity differences or other business conditions, they will be routed to a user for retention. The approved invoices then are posted into the ERP. Part of the handshake is an update into the invoice transaction in Medius of the journal entry and then subsequently customers may choose to modernize their AP and payment processes with a fully managed service for paying suppliers across a full set of supply payment channels there on the right. So that's an option within the same standard user interface without having to hop out into a third party or bank provided solution to modernise the payments part of the process. We provide a supplier facing portal as mentioned here for invoice submission, but you have invoice status and payment status information presented there and a variety of other capabilities across a full spend management suite. And then overlaying this detailed analytics, out of the box analytics providing both operational insights as well as financial insights. As a true cloud solution we don't allow our customers to stagnate. We always roll out innovation and work with them to make sure they're getting the maximum value for continuous value realization within our solution. From an integration perspective, Medius is a multi ERP, multi country, multi company solution. We have packaged integrations listed there on the right hand side, that really helps expedite a rapid predictable deployment of our solution. But what happens when our customers don't have these ERPs as indeed with JJ Taylor. So we do have a fully published set of integration APIs that partners like Enzo can take advantage of to work with our customers to build that integration. That's available publicly on our success portal at success medius.com. In general, why do customers choose Medius? Again, it's that speed to value, a standard product with rapid cloud delivery with package best practice workflows and integrations and consolidated configuration administration and easy adoption for users through a consistent user experience across the full invoice to pay process. In terms of savings that matter, it's a predictable implementation timeline to execute on your initiatives, typically same year ROI, and we provide scalability without additional cost. Part of our pillars of success is the customer success aspect. It's not just a lip service, it's part of our DNA. So we have public peer benchmarks that drive continuous improvement. We have customers with direct roadmap influence and voting and a vibrant user community for networking and knowledge sharing. So these are the main reasons why customers select Medius. That's enough about us for now. Let's get to the real story here with Andrew and JJ Taylor. Andrew, would you like to introduce yourself first and then I'll navigate through the slides for you? Sure. Thanks a lot, Rich. So as he mentioned, my name is Andrew Timmons. I'm a business analyst with JJ Taylor. So just to kinda give you a overview of our company, Rich, go to the next slide. We are a Milton Coors beer distributor based in Jupiter, Florida with locations in both Florida and Minnesota. We've got two buying warehouses and then kind of one drop ship location in Tampa, Fort Myers, and then Treasure Coast, Fort Pierce area. Up in Minnesota, we're centralized in the Minneapolis St. Paul area. On a yearly basis, we're selling about twenty nine million case equivalents or cases of beer. Usually in beer industry, you consolidate kegs and other odd volumes down to a standard twenty four pack case. And as of right now, whether it be by case volume, revenue or profit, we're on average growing at about a five percent tick. Kind of as I alluded to key markets are that big Tampa Bay area we have on the other side of the state and the metropolitan MSP area up in Minnesota. Florida is an odd territory in the middle of the state that we hold. We kinda look like a melting trumpet horn that's facing to the west in Florida. We kinda have a small amount of area in the Port St. Lucie area, which is a big growing market on the east side of the state. And then we've also got a larger span of territory going from north of Tampa down south, just below Cape Coral, where we also have another growing and burgeoning market. Like most beer distributors, we've been around a while. It's a family owned business. Lots of love for the product, lots of love for the employees. So we're going strong and we feel good about where we're at. But of course, with every new month, year of change in the industry, whether it be because of COVID or SKU proliferation or all the changes that come year over year to the beer industry, we needed some ways to get smarter, to get more efficient and to reduce costs in some places. Rich, can we go to the next slide? So in early twenty twenty, I was having a conversation with my corporate controller about the Eostar integration for Medius that actually had already existed. We were looking to replace our document management solution for invoices. We were using DocuPeak at the time. This was good for managing approvals, for making sure that within the business, given invoice that was sent to us was handled and stored away for future reference. The problem was that DocuPeak didn't really offer us any new technology for invoice reconciliation and automation. And that was why we wanted to look into vendors like Medius Flow. So one of the big struggles we had was that inside of the Eostar, we were actually doing manual reconciliation. Some invoices were simpler than others, but either way, we were touching almost every single invoice in order to get it reconciled. Additionally, though it was being done inside of DocuPeak, we were going through similar manual processes for all of our expense based invoices, whether that's standard utility bills or employee expenses that were submitted that way. As we were looking through different options, though, Medius was the first one that came up to us. We were looking at some other competitors in the space. And while there are a lot of quality mature procure to pay options in the market, what we found was that most of them were missing two big things. First was UIs for where a lot of them were relatively modeled. The workflow that one would need to utilize in order to go from the ingestion of a purchase or give an invoice to the reconciliation of it, didn't quite make sense to a lot of our AP staff. And the other big one was really the technological underpinnings and the integrations that make things work for us. In the discovery process, whether it was talking to companies that straight up did not have integration APIs outside of their standard and already built integration, or just the fact that they didn't particularly foresee expanding into other integrations. There just weren't as many companies out there that were willing to work with industry specific or smaller technologies. So the existence of that standardized REST API being the integration platform for Medius, got us to the point where a, prior to us even going live on the platform, there was already an integration that existed because developing one was simple enough. And as you'll see, when we get to explaining the problems that we had, there is extensibility to it. At the end of the day, we just needed some sort of solution where we could reduce the amount of manual work being done and replacing that document management solution that we had in DocuPeak. And Medius gave us the ability to do all of those things as well as integrate into our current environment. So next slide, Rich. Okay. So this is kind of what our current integration environment looks like. Pretty similar to what Rich had mentioned for the broad environment that Medius is going to be involved in. In our particular case, we have Sage Intact doing the standard financial posting for the invoices so that we can manage payments and manage the actual counting side of it. And then we have Eostar feeding the PO information into Medius where things are gonna get reconciled. We do have some additional technologies just on the outside of our supplier and expense based invoices just to help things get emailed to the right location. But the long story short, and one of the issues that we had was prior to our project, both the Intact and well, let me to clarify while the EOSAR integration did already exist, we found it had certain weaknesses and the Sage Intacct integration didn't exist at all up until that point. So we needed to create something in order to actually execute on the vision that we had. Okay, next slide. So the real problem with the project was that while the Eostar integration existed, we eventually discovered that there were some things missing. So when the integration was originally developed, it was developed for another beer distributor, which, you know, when a beer distributor is using a certain piece of software and following certain standardized practices, one might expect that just the existence of the integration is enough. But we found because of the scope of the creation of that integration that there were some problems with the way that it functioned. First was because they were just aiming for a minimum viable product, there were some limitations in the cost components that we consent over. So, you could send the price information, you could send some basic keg deposit information, but there wasn't any handling for advanced freight and there wasn't any handling for some of the extended cost components that you might handle like accruals or some of the more complex and company specific cost components that you might tie to any given product. The second, it was some inflexible design in just the base metadata of what the integration was sending over to MediusFlow. When the integration was originally designed, it was made for an environment where Great Plains was the ERP. Now, because of this, there were certain variables and pieces of information that were specific to Great Plains. That's not inherently a problem. It's just that these were things that couldn't be changed unless we requested a development fix from Rutherford, from EOSAR. Then the other problem being is once information was sent back to Eostar because of the fact that we didn't quite have Eostar didn't quite have a firm look at what medius flow is doing or a firm understanding of it. We didn't have the ability to report on and understand and eventually finalize the bills that we needed to finalize in Eostar. So because of both the downstream and upstream issues with communication through the integration, we simply couldn't enact the kind of workflows that we had eventually hoped for. So after two months of going through the project, this was where we started to realize that, Hey, have we gotten started with professional services? Have we gotten rolling on this? And we just have to pull the plug. We were getting to the point where there were certain issues with the integration where instead of just saying, Oh, we can work around that. They would have been obstacles that would have completely eliminated any ROI that we would have gotten out of it. It was at that point when Jim Mullis, who is kind of a key wizard and technician with Enzo United was on one of the calls that we had with Medius. After we got off, he could tell that things were kind of going south and just asked for a sidebar with me, kind of gave me a quick call and was looking to clarify what the actual problem was. I brought him through the details. I won't bring you guys through all that boring stuff. But at the end of it, the key thing was, and since we'd already had a relationship with him, once I explained it, he literally just sat on the phone and was like, Oh yeah, I can do that for you. Okay, I'll have something for you tomorrow. And sure enough, that's exactly what happened. And that was really where things kind of exploded into showing us what Enzo could do for enabling not only the integration between Medius Intact, which he was there to develop, but also improving upon and shoring up the integration with Eostar to get it to the point where instead of worrying about either killing an implementation or switching to a longer schedule where we have to ask our software provider to give us an enhancement, we were able to rely on Enzo to quickly and very efficiently create an adapter that could handle all the tedious communication. And it's at that point where I think that's where CV can come in and kind of give you some more details about exactly what they do and how they do it for us. Thanks for that description, Andrew. That's great. It actually reflects the occasional times where a cloud product, where the rubber hits the road, it has to rely on the integration, the synchronization of that data from those systems. So it's really interesting to hear that all good intention, the integration in this case was not strong enough for the need. So that leads us to Hello Enzo with CV if you'd like to do an intro and we'll step through the Enzo Unified material. Thanks Rich. My name is CV Eaton. I am the Director of Implementations and all things Enzo Unified and going to kind of give you a high level of how we did this for both Medius and J. J. Taylor and how it works so well. Rich, if you want to jump off to that next screen. So while Jim Mollis, who Andrew was talking about, is a brilliant developer and can do these things, power really is in how we developed Enzo from the beginning, in that we make any data source look and feel and behave like a SQL table. So like Rich just said, you have an API nowadays that's out there in the cloud and you need to be able to hit it. You either have to have your software company build it or you have to go hire your own set of developers. What we do is we make that all look like a SQL table. So it's just data transfer with just standard SQL commands. No wizardry, no long, long time. That's why he was able to spin that up in an afternoon. So kind of as a, from an image standpoint, Rich, if you want to flip to that next screen. Whether we're talking about Medius or Sage Intacct like Andrew had said or Microsoft GP or Ceridian or your HR package or flat files or other databases, you know, there's no, there's no, has been no in the past simple solution to make that all talk. Enzo simplifies that by using just SQL language. So no more, if you've heard of ETL tools or ODBC connectors or development costs, It's with a simple language. So with Medius, the power that they've have given us with all those APIs that Rich talked about is that we can hit any of the data that they allow us to both upload and download to integrate with your ERP or your financial package or your email, whatever those automation pieces need with just the language of SQL. So as it says down below, it's not a marketing slide. It's just arrows and boxes because it's all just talks. So all just using the SQL language. And at the end of the day, the other piece of this that Andrew can probably speak to is that it's repeatable. So he now owns that SQL code. So let's just say that they make a change and they want to start sending a certain type of PO in a certain direction. He doesn't have to call us and say, Hey, go make this change. He owns the SQL code. He goes and does it himself. And so it gives them that flexibility. And it's very cost effective because it's a one time, you own the service and simple, repeatable, cost effective. Rich, you want to go to that next one? And really what this boils down to, we obviously have a very strong partnership with Medius and we think that they have an awesome product, whether it's this or some of their other tools that they have, we've built those integrations. But we've cut down those development times from two months, three months to weeks, or even days in some cases. And so, reduces your total cost of ownership. And once you have Enzo in place, we can also tie it to other things. Another distributor in the same space does kind of a vending thing on their non alcoholic piece. And they were receiving up to a hundred different lines in a SQL, sorry, in an Excel document that they then wanted to convert so medius could then process it. Well, there was no, you know, simple way to do that. Using Enzo, and again, the simple SQL code, we take that Excel document, spin it into a PDF and send it to media so it processes the same. So we've now taken a one off AP processing problem, and we've made it a standard AP processing. So now your AP clerks only have to learn, you know, one way to do things as they process it. We've spun that up. So we've got over one hundred different adapters, Medius being, you know, one of our main ones. And we can, if there is another system out there you'd want to connect to, we can generally spin those up in little as two weeks. The afternoon that Jim spun that up is kind of a one off that he did for Andrew, but generally it's two weeks. Here's a quick screenshot of many of our other adapters that you'll recognize from Microsoft stuff like OneDrive to Google stuff, Google Drive, Google Search. We have analytics. We do it with AWS. And then obviously, Medius being, we have their full suite of products integrated with Enzo adapters already. So Enzo to the rescue. So let's talk about the project success and here we have the schematic now with Enzo in place managing that data synchronization, that richer set of data needed to drive the full power of Medius's APA. Don't know if you want to make more comment here, CV at all. Yeah, so really when we talk about SQL, where it says Enzo Unified, that's where all your SQL views or store procedures or jobs would live And they just play as the talker between, in this example, Sage in Medius or Eostar in Medius. It doesn't matter, we can connect multiple things to it. It just makes everything talk in a single language. And then perhaps as we look to close, if Andrew might want to comment on the case study, the success story, where we are now, thanks to the collaboration with Enzo, Andrew? Yeah, absolutely. So, kind of to summarize all of the things that we've talked about, this is both a transformation from a physical standpoint of how we managed invoice reconciliation to, as well as a technological transformation. We were using this pretty old school document management solution. We didn't have anything in place that could create real automation for the work of actually reconciling our invoices. We didn't have any idea of how long it was taking us, of what kind of work we were doing because we didn't have any metrics tracking how that actually impacted us. All that we knew is that we needed X people to do a job and eventually we needed less of them. At the end of the day, we were saved from massive cost overrun on an implementation, a whole lot of waiting. And when it came to looking at what we got out of the media solution, we suddenly realized that we were starting to cut the number of invoices that we needed to touch almost half. Being able to take big suppliers, take our invoices from Molson Coors, from Boston Beer, from Mark Anthony, your huge distributors in the space and basically get to the point where you can have them come into the system and then just immediately go out of the system because they work the same every time. It's right there, it already sounds valuable, but the value really keeps on coming and it has kept on coming as of today at this point. For every time that we discover a new supplier where we can create a rule or find a strategy with that supplier to get them more touchless, we then find more use cases and more opportunities to eliminate some bloat in the AP reconciliation process. At the end of the day, we're getting to the point where our AP department is just infinitely more nimble than they ever have been. That in combination with one of my colleagues, Ricky, knew full well what Enzo could do. But in the process of getting Enzo in on this project and having them help us execute on what was gonna be a really problematic project, it kind of showed me how not only it could make Medius successful and make this one element of our business really but show us how we could utilize that framework and that nimble technology to execute on that continuous improvement in all other parts of our business, and we're doing exactly that. Day by day, we find new reasons and new ways to engage with Enzo, just as we find new ways to improve upon our supplier invoice reconciliation. So I really couldn't be happier with how the project went. It's definitely been a lot of work and a lot of effort to get it to where it is today. But I think that's a whole lot better than the abject failure it was turning into just because of a problematic technology partner completely outside of Medius' purview. And I think that's the success of this project, Andrew. It's great to hear you'll be able to take advantage of the MediusFlow, the Medius APA specialized solution for a few automation and then with Enzo's help to synchronize that data even outside of the AP process is helping JJ Taylor. You may have noticed the slide I originally presented with a solution footprint with analytic supplier portal and other capabilities in the full media spend management suite. These are additional modules that companies can adopt at their own pace should they need to and particularly in those cases we mentioned it on the Enzo slide for Medius Pay for the modernization of payment execution as well as supply information management. The team at Enzo have already helped customers with synchronizing that data again in the areas where Medius doesn't provide a packaged integration to target ERPs where it's more industry specific or even homegrown ERPs. So it's a terrific partnership for Medius and so we're bringing our customers success in successful deployments and that integration part of it is the linchpin of that successful project. So I think there are any questions Mr Casey, if you have any questions for Andrew or CV or either myself, I'd be happy to take them now or we could certainly look at following up individually afterwards. Actually, just had one come through. I sent that through to you, Rich, if you want to pose that to our panel here. Okay, yes thanks Casey. So the question from the audience what makes Enzo different from some of the bigger name integration platform providers like Boomi or MuleSoft? CV? There's a couple different things. One is price point. We are significantly much more affordable than either of those two. The second is more of a future thinking in that if you go get Boomi or you get a MuleSoft, you also need to get and train your employees to manage and maintain that. They have to learn the UI and how it works. And then if they leave the company for whatever reason, now you're stuck searching for somebody else and, you know, a person who's very good at those is probably going to cost you, you know, upwards of eighty thousand dollars one hundred thousand dollars With EOS, sorry, with Enzo, it's all SQL based. So it's the language of SQL, it's a standard SQL language. And Andrew, if want to jump in, there's nothing special about it, nothing you have to learn. If you know SQL and you can go find a junior SQL person, you can make changes with Enzo. Yeah, and I think to speak to kind of at least within the beer industry, how that ends up working is while my experience might be a little bit more unique among IT staff in the industry, the one thing that I found is someone somewhere in most beer distributorships, or at least in a lot of the more mature ones, somebody knows SQL, somebody knows how to manage it. And even if you don't, I came fresh out of college with an awareness of SQL. And that wasn't with a CS degree, that wasn't me spending four years learning Python, that was SQL is one of those core business technologies that gets taught for the purpose of data management. And it's something that's literally in every organization. Now, you're a beer distributor without that SQL guy. Maybe you just have an IT person to manage that. Maybe you need to go alongside it. The advantage of having that as SQL where it's a more common technology and much simpler technology to interact with really makes it so that, A, it's pretty easy to get shared resources or advice on how to implement those things, Or b, it's good. It's usually gonna be pretty simple to either hire a new resource for that or educate current resources on how to utilize it. You know, I while I have a lot of experience with SQL, really nothing has changed about what I've done with it since about seven or eight years ago. I got going with SQL. I learned how to use it, and then I was ready to fire away. Having it centralized to a bit more I don't wanna say standard, but technology that is more common for users who aren't highly, highly technical really lowers the barrier to access in using the tool to its fullest extent. And one thing I'll add to what Andrew was just talking about, the other piece that Enzo does, because of the way we've got it framed and framework, that two weeks of standing up a new adapter, that's not just a sales ploy. If they have an API, we can stand an adapter up in two weeks. If you try to go to a Boomi or to a MuleSoft and say, Hey, I've got this kind of one off, GPS system that I wanna connect to. They might do it for you, but they're gonna put you on a development path of X time, not two weeks. So we're very flexible. Yeah, no, it's funny because one of the things that we've been, one of the things that we broadly discuss, and I know a lot of organizations in the space are discussing, is just what the next five years of digital transformation are. What does the software landscape look like? Does it include Eostar? Does it include somebody else? Do you go to tier ones and start doing things that way? Do you go at more clandestine things? Do you build own custom environment off of MuleSoft? And so having a tool like Enzo is great because if we were to go with a tier one, go dynamic three sixty five or go MuleSoft, that's fine, we can do that. It's just that my job of business analyst suddenly changes because my CIO is gonna need to go out and probably hire five or six developers to handle the integrations with various different APIs. And then I'm going to become a product manager, learning scrum and basically completely taking on a new different career path from where I'm at now. If you're ready for that transformation, that's fine. But Enzo offers you the opportunity to basically do that digital transformation, but with the tools that you have right now. Yeah, if I could just perhaps comment as well as we look to wrap up here. I think the Enzo offering provides a level of future proof capabilities. So as a true cloud APA solution, Medius is rolling out enhancements and innovation every single month. So our customers, all of our customers, gain the benefit of that investment and that innovation. However, sometimes you need to have the data available to take advantage of those new features in our solution. So we roll out a new feature then Andrew can take the Enzo integration. Oh yeah, need to pass this data through to take advantage of this new feature. That's phenomenal. Absolutely phenomenal. Very agile. That's a big MuleSoft, those other companies are not as agile as we are. Price point and agility. We do have one last question then before we look to wrap. This is for Andrew. Why did JJ Taylor select the media suite for the AP invoice automation project? Were there others who had a more established integration that lacked in other areas that made media stand out? So if you could perhaps respond to that and then any other questions that have been submitted, Casey, we'll follow-up with offline afterwards. Sure. So the funny thing was that the integration, especially even though the Eostar integration ended up being a little weak at the end of it, integration specifically was a big, big weakness of the other platforms that we looked at. The two big ones that we looked at were Avidxchange and Stampli. And what we found was it wasn't something like with the integration with Medius was a little different or it was gonna work in a more or less complex way. It was that both Stampli and Avidxchange more or less said no to us. They're like, sorry, that's your problem. Now, I mean, while we kind of ended up in that vein with Intact, we also got answers. I can't remember which of the two it was, but some of them don't even have integration APIs so that Enzo would have even been useful to us. So it wasn't just about whether or not the integration existed or didn't, but that other software partners just really weren't capable and nimble enough to even execute on an integration if we wanted to. Outside of that, it was really a lot of UI. It was the workflow process made more sense to us in Medius. Looking at Stampli, for instance, they mostly focus on the SMB sector and are interested in integrations with very basic tools, your QuickBooks and stuff like that. And that's fine, that works. It's just that as soon as you have some diversity to what you're gonna ingest, then you have some problems. And the UI seemed to be built around a framework where things only worked one way. And though the OCR and AI technology was highly advanced, the workflow was not. And while Avidxchange was a little bit closer on the UI and workflow, it still was a little muddled in comparison to MediusFlow. And again, with that additional weakness of the strength behind integration and what they could and could not do with other technology partners, it made the decision obvious to us. So, at at the end of the day, really was only one choice for us. Well, for sharing those observations, Andrew. Appreciate that. As we wrap up CV, would you like to make any closing comments? We're excited to work with Medius and know that they've got a top notch solution that we're as Rich kind of said they constantly innovate we innovate right with them you're not going to be stuck in the dark. Thanks a lot. So any additional questions that were submitted we will follow-up separately. We're out of time today. There's our contact information. Feel free to reach out for an additional discussion. Thank you Andrew, thank you CV and thank you everyone for attending. We're going to wrap. Cheers. ## Explore more: ### [Explore Medius integrations](https://www.medius.com/solutions/for-your-erp/ "For your ERP") See how Medius integrates with ERPs and industry platforms through packaged connectors and open APIs. ### [Find a Medius partner](https://www.medius.com/partners/partner-finder/ "Partner Finder") Discover who Medius partners with to make AP automation integrations and processes smooth and efficient. ### [Discover AP automation for complex environments](https://www.medius.com/solutions/medius-accounts-payable-automation/ "Medius Accounts Payable Automation") Automate invoice workflows, even when your ERP or industry system isn’t a “standard” integration. ### [Review AP benchmarks & KPIs](https://www.medius.com/customers/ap-benchmark-report/ "AP Benchmark Report") Track touchless processing, cycle time, and exception rates to measure automation performance. [Watch more videos](https://www.medius.com/videos/ "Watch more videos") ## Ready to transform your AP? [Book a Demo](https://www.medius.com/book-a-demo/ "Book a Demo") [Contact Us](https://www.medius.com/contact-us/ "Contact Us")