Name: The Modern NetSuite Finance Stack: How to Get Real ROI from Automation, AI, and Your ERP Data
Uploaded: 2026-10-07T17:16:57.477Z
Duration: 50 min 43 s
Description: The Modern NetSuite Finance Stack: How to Get Real ROI from Automation, AI, and Your ERP Data

Transcript for "The Modern NetSuite Finance Stack: How to Get Real ROI from Automation, AI, and Your ERP Data": Welcome, everyone. We'll get started soon. So please grab a coffee, grab your lunch, and we will start in a bit. Alright. So welcome, everyone. This is... This isn't a standard demo about automating a simple task. We're here today to talk about what it actually takes for automation, net... NetSuite data, and AI to drive real value. Even with NetSuite Foundation, a lot of financials, a lot of finance teams are still, trapped in shared inboxes, spreadsheets, and disconnected portals. Today, we'll look at how to fix the broader operating model using accounts payable as our proof of concept. Let's get started with a little introduction to the team. So, unfortunately, Kelly couldn't be part of, the the the webinar today, so it'll be the rest of us, the... Us wonderful people. My name is Justin. I'm part of the SkyHigh ERP team. There's Brandon as well, Ivo and Daniel. If you guys wanna do a little quick introduction, I've been in SkyHigh ERP for, almost a year now. I'll pass it to Bennett. Yeah. Nice to meet everyone. My name is Brandon Rambissoon. I'm a senior consultant here at at at, SkyHigh ERP, and I've been working in the NetSuite space for about five years plus. So excited to show you guys this solution. Nice to meet everybody as well. My name is Ivo Sofijanov. I'm one of the senior account executives here at Zone and Co. I spend most of my time working with NetSuite finance teams that are looking to simplify processes like AP, payroll reconciliation, and reporting without creating another disconnected system around NetSuite. So very much looking forward to walking everybody through today. And I'm Daniel Gallagher. I'm a senior solutions consultant here at Zone and Co. I help both prospective and existing customers evaluate zone solutions in different products. Background about myself, I come from accounting. I've actually done a lot of the work that our solution helps to solve and look forward to showing you what that looks like. Perfect. So let's get started. Finance doesn't usually have an automation problem. It has a fragmentation problem. In most NetSuite environments, the tech is there, but the process is glued together. You might capture an invoice automatically, but you have to correct it manually. Approvals live in emails. Payments happen in bank portals, and reporting is always rebuilt in Excel. Every handoff breaks your visibility and control. That's why automation projects can technically succeed while finance leaders are left wondering where the ROI actually went. So let's look at the next slide, and, let's look at these six statements. Take a look at these statements and find which one hits closest to home to your team right now. If you want, there's a poll exit of presentation, or if you wanna just put in the chat, I'll leave you guys a couple of minutes to just read through them and answer. So while these look like six different headaches, they're almost always symptoms of the exact same root cause. Your workflows, data, and controls aren't connected end to end. So let's take a look how to fix that. So let's go to the next slide. Real ROI happens when automation strengthens your whole finance engine. We break this down into four pillars. The first one, trusted foundations. Clean data... Clean master data, configuration, and ownership. The second one is connected flow. Transactions moving without humans bridging the gaps. The third one is embedded control. So approvals that live inside the workflow, not your inbox. And finally, live intelligence, knowing exactly what needs your attention right now. All of that combined together, the goal is for the system to get us... Get stronger as volume scales. AP is a perfect place to make it tangible, so let's take a look at how it works in practice. So with that foundation in mind, I wanna narrow the conversation specifically into AP like Justin has mentioned. Now AP is usually one of the first places where the fragmentation that Justin just described becomes very visible. There are a lot of transactions, there's a lot of different people involved, there's plenty of repetitive work, and there's several points where information can leave NetSuite. That also makes it one of the clearest opportunities to create measurable value relatively quickly. So for the next few minutes, I wanna walk through what a genuinely connected AP process looks like, starting with the vendor and ending with the payment. Yeah. Before we get into the workflow itself, just a quick introduction to Zone & Co. For anyone who isn't familiar with Zone and Co, we build finance technology specifically around NetSuite. We are a partner within the Suite Cloud developer network. We work with more than 4,500 customers. We've been in the NetSuite ecosystem for more than twelve years, and the broader strategy we have is very simple. Extend NetSuite across the major finance workflows without asking finance teams to constantly move data between any disconnected applications. You can see that across quote to cash, procure to pay, treasury, reconciliation, and reporting. Today though, we're gonna stay focused on this middle section right here, procure to pay. That means vendor onboarding, invoice capture, approvals, and payments. And the important piece isn't really that these are four products, it's that they can create one operating workflow as the connected process directly inside of NetSuite. So where NetSuite AP still breaks down? Perfect. So thank you for that, introduction. So I'm from SkyHigh ERP. We work with many implementations. Our main focus in industries are manufacturing, wholesale distribution, and services. So we've worked with over 85 plus implementations, and we have a 100% track record with our go lives. We're a NetSuite alliance partner, and I've seen firsthand on implementations that I'm currently working on where this is a needed solution. So we have clients that are hung up on their AP process and bill capture, and this is where a solution like some comes in handy. Great context, Brandon. Yeah. So this is really where we see the opportunity in AP to Brandon's point. The technology obviously has to sit inside a well designed NetSuite environment, which is exactly where the sky high side of this equation becomes really important. But fundamentally, NetSuite may still be the financial system of record, but when you look at the actual day to day AP process, a surprising amount of the work can still happen around it. Vendor information might come in through emails or spreadsheets, Invoices arrive in shared inboxes. Approvals get chased through email. And once everything is approved, payments can move into a completely separate banking workflow where none of those things individually, you know, collide and connect. The problem is what happens when you add them all together. Every handoff creates another opportunity for somebody to rekey information, miss context, delay the approval, lose visibility, or just create additional reconciliation work later. And that's really the distinction that we wanna make today. Having automation somewhere in accounts payable is not the same thing as having a controlled AP process. The value shows up when those things actually connect. And that changes how we think about automation. The objective isn't simply to automate more tasks. And if invoice volume increased by 30%, finance shouldn't automatically assume AP workload or headcount also needs to increase by that same 30%. What we want is a process where the normal transactions move efficiently, the exceptions become obvious, and finance has the visibility through the month rather than discovering problems during the close. So the shift on this side is really from individual task automation to operating leverage. Can the business process more volume, maintain stronger control, and give finance better information without adding the same manual effort. That is the outcome that we are after. So here's what that looks like when we put the life cycle together. A vendor enters through a controlled onboarding process. That creates a clean native NetSuite vendor record. An invoice comes in and becomes a coded validated native NetSuite vendor bill. That bill automatically moves through the appropriate approval process and once approved the payment can be initiated without breaking out into another disconnected workflow. And because those transactions remain connected, the reporting and visibility at the end becomes much more reliable. That's the important part of this slide. We're not talking about five unrelated automation tools and putting logos beside each other. We're trying to eliminate the handoffs between those stages so that NetSuite remains the source of truth throughout this process. So let me break down those first four stages very quickly before Daniel actually shows you what this looks like. The first step is often the one that gets overlooked the most because AP automation is usually discussed starting with the invoice. But really, AP starts with the vendor. If vendor records are created from emails, spreadsheets, or incomplete forms, you've already introduced bad data before an invoice ever arrives. The AP team inherits that problem later through coding issues, payment questions, duplicate vendors, missing tax and for information, or banking details that just have not been properly validated. A better model is controlled intake from the beginning. The vendor provides the required information through a structured process, the appropriate checks happen upfront, and only once that vendor is complete and approved does the record become ready for AP inside of NetSuite. That gives everything downstream a much cleaner starting point. Now the next stage is the stage we're all most familiar with which is the invoice capture. And this is probably where the term automation gets used most often. OCR itself is useful, but reading the invoice is actually the easy part. If OCR extracts the text and somebody still has to determine the coding, validate the transaction, match it, correct it, and still manually create or finish the bill in NetSuite, you've automated only one small piece of the job. The bigger opportunity is what happens after the document is read. With zone capture, the objective is to take that incoming invoice and turn it into a coded, validated, and approval ready NetSuite transaction. That can include things like multi subsidiary environments, multiple currencies, matching an exception handling. So the measure of success here isn't really did we OCR the PDF, it's how much manual AP work disappeared after the invoice arrived. That distinction is why we focus much more on processing efficiently than OCR as an isolated feature. Now once you've created a clean bill, the next place process is often slowed down is approvals. The issue usually isn't that companies don't know who should approve something, it's operationalizing those rules consistently inside of NetSuite without AP becoming the traffic controller. So instead of somebody manually figuring out who needs to see every bill, you can route things based on subsidiary, department, account, project, vendor, transaction value, custom field, and importantly, the approver doesn't necessarily have to live in NetSuite every day. They can approve directly through email while finance still keeps the workflow, status, and audit trail connected to the source transaction. That's what a good approval automation should accomplish. Less chasing for AP, but more visibility and accountability, not less. Finally, payments. We get to what I think is one of the most disconnected parts of the AP process. A company can automate vendor onboarding, invoice entry, and approvals really well, but somebody will still end up downloading a file, logging into a bank portal, and reentering all the information, or starting another workflow completely separate from the original process to actually pay the vendor. At that point, we've created another break in the process. The goal with Zone & Co AP payments is to take an approved bill and continue that workflow through payment while keeping the execution connected to the underlying NetSuite transaction. That also becomes especially valuable as organizations deal with multiple entities, currencies, cross border payments, and the complexity of a growing business. So our definition of end to end AP doesn't stop when a bill gets approved, it stops when the payment is executed and the transaction stays connected all the way back through NetSuite. Alright. Rather than spending another ten minutes talking about it in theory, this is a good point to actually show you. So Daniel is gonna take the same process we've just walked through and show you how it operates inside of NetSuite, particularly where the manual handoffs disappear and where finance gains visibility along the way. So, Daniel, I will hand it off to you. Thanks, Ivo. We're gonna jump into our solution. We're gonna walk through onboarding a vendor, getting a bill processed, getting approved, executing the payments, and touching on reconciliation. Most important thing that we're gonna start with that Ivo mentioned is actually before you get a bill. And where I'm gonna go is into our solution. It's an operating layer that's gonna allow you to interact with your vendors. We're gonna send a form to the vendor just by quickly identifying which form we wanna send them. You'll notice I have different forms, in my case, set up by subsidiary. I also even have different forms for more upstream types of vendor processes, security reviews, gathering NDAs. For purposes of today, we're really here to talk about procure to pay. We'll send some forms to make sure we got bank details and tax information so we can process and pay the bill. So we go down to the bottom. All that's needed to kick off this process is an email address. You can also notify other people in the organization so everybody is aligned with what's happening and the fact that this is actually on the vendor to complete their forms, and you click send. That's as simple as it is to do what often happens through email, through different email inboxes, and not everybody has access to. We're now gonna shift gears into the vendor's experience, where we're gonna see what it looks like for them to complete these forms through the portal. Now the vendor is gonna get an email that looks something like this. Now I am the person that sent this. It's my company called Zone & Co demo company. I've got a message that I included. Keep in mind, this is all gonna be personalized, representing who sent it, the company that actually is sending the invite with the message that's relevant. The most important link they're gonna have is to go and complete the form. Now as they go to complete the form, they'll be brought into the portal. Now in this portal... And give me one moment here as I log in, they will be brought to the relevant form where they'll be able to complete the form as you've configured it. Now keep in mind, these forms are configurable. You get to decide what's collected, what type of information do you need from these vendors. And for demo purposes, I did prefill a lot of this information so you don't have to watch me type it in. As we scroll down, we'll see core information related to this vendor. As we get into those bank details, here's where it starts to become particularly powerful. If I just select this drop down in The US, in this example, you'll see routing and account number shows up. That's out of the box. You don't need to know anything specific. The vendor doesn't need to know anything specific. They just put in where they are, and the right bank detail fields will show up. The same holds true if I choose Australia. You'll notice BSB and account number shows up. That's the relevant pieces of information to make payments in that particular country. Really, the idea and the goal here is simplify the process for the vendor, give them the ability to enter this information themselves, and continue through the process. Now I've decided to ask for different forms for my vendor. Again, keep in mind you are in control over what types of information, what types of documents vendors will be adding and uploading as part of this overall process. I'm asking for a bank letter. I'm the vendor. I'm gonna upload my bank letter, and I'm gonna move on to the next step. Now this next section is tax documents. My example, I may have a w nine for US subsidiary. May have different types of information in Canada for other subsidiaries across the globe. The same idea holds true. They'd be able to quickly and simply upload their documents in one fell swoop before they go to the final step of sending their response. Now once the vendor completes their task in the portal, their job's done. You'll still have workflows configurable on your side to determine what happens now that the vendor has provided their information. Keep in mind, we have not created a vendor inside of NetSuite yet. So let's talk about those steps, those controls, and how AI can help accelerate that overall process. We're gonna jump back into the workflows after the vendor completes these forms where we can see what needs my attention. Now that Zone and Co has actually completed their forms, I can see some tasks that need my attention. As I open up those tasks, I'm gonna see the form as completed. I'm even gonna see those different workflow steps on the right hand side. I have a few examples here to walk through. We actually have AI built and embedded into the workflow to help accelerate this process. We also have more deterministic steps, like helping to verify bank details so that name and account details actually matches what's on record with the bank. We have another example of a report that's gonna help compare that bank letter provided with the information completed in the form and our final step to actually complete the record creation or update inside of NetSuite. As I open up this first example, this is workflows, AI built into the overall process. I have a prompt built into this tool, and it's producing some output. It's looking at all the info the vendor provided and checking online to see if it looks legit. It's giving me an outcome saying more information is needed, which is good because this is a demo vendor. And if I want to, I can continue to have a conversation through AI directly in this workflow and have all that information documented in one place. I'll go ahead and mark this as complete. We're gonna go into the next step, which is what I talked about, that more deterministic step, verifying bank account details. All this information is prepopulated. All that needs to happen is a submission takes place, and then Zone & Co is gonna help power surfacing and verifying if these bank details match. We'll return a confidence score so that you'll have assurance to help reduce that fraud risk and make sure you're paying the right people to the right bank accounts. This next example of the AI workflow, like I talked about, this is actually a document. That bank letter that was uploaded, I'm just leveraging it to speed up the process of comparing what's actually on the document against what's been completed on the form. It's gonna give me some insight to help accelerate that process. Again, directly embedded inside the workflow, allowing you to do more faster. Now final step here is actually creating or updating the vendor in NetSuite. Suite. Before we get there, one quick thing I wanna touch on is this comment. This is me being able to interact with other people in my organization. When I open up this comment, you'll notice I actually asked somebody to upload a document, a contract in this example. They replied back through email. They didn't log in to this tool. It's one simple way to actually gather all this information in one spot so we can turn it into actionable insight that can also pass through into NetSuite. We'll go ahead and mark that as complete. We'll come back to that document in just a moment. Last step here is NetSuite, actually creating or updating the vendor. Most important thing is we wanna make sure that you have clean master data. So we're gonna flag any potential duplicates and even show you how close of a match it is. In this example, SmartBug Media does already exist. There is a 100% match. And rather than you creating a duplicate vendor, we're actually gonna just link it and allow you to update that vendor record in one fell swoop. As we scroll down, you'll see all the information exactly as the vendor entered, including tax information, their address, even those bank details. I'm just reviewing it at this point. Take it one step further. This solution also works with custom fields you may have configured and enabled inside of NetSuite. We have an example in our environment that helps connect all this together to define who the default vendor approver is for this particular vendor. I could say Daniel Gallagher is actually the default vendor approver, which means, ultimately, when I get this bill from SmartBug Media, we can help simplify the process of routing this bill to the right person. As we scroll down to the very bottom, those documents, I said I'd come back to it. There have been a few documents that have been uploaded. You get to choose what happens with those documents, if they stay in the solution or if you want to push them into NetSuite, on that vendor record in the file cabinet, it's your option, and you can click submit to make all this happen. Now that's gonna wrap up the vendor onboarding portion of our demo. Where we're gonna go next is actually starting to get bills from our vendors. For the rest of the demo, we'll actually be inside my NetSuite instance. We're gonna be using Zone & Co solution inside of my NetSuite instance. So let's get started. In my NetSuite instance, what we're looking at right now is Zone & Co control center. This is installed as part of our apps, and you'll have one place to go to be able to navigate across our different products and our workflows, like any bills that have come in, any bills that have been processed, those bill payments that we'll get to a little bit later, any approvals that are happening, one place to go across our solutions and across our other products, like Ivo mentioned. We're looking at the dashboard to give us some high level visibility across, in this case, our p two p workflow. I'm gonna go straight into our bills to process. This means bills have come in. That typically happens through email designed to work alongside your existing inboxes, and it's a triage. We just need to quickly review what our technology has already done. As we go into the screen, we'll be brought to our incoming queue and see a list in this example across multiple subsidiaries, including bills that are backed by purchase orders, bills that are stand alone bills. I'll have one clean view. What we're gonna do is first go into an example of an invoice from SmartBug Media that does not have a purchase order behind it. We're gonna see the end outcome, what this looks like once you actually have zone installed to review what our technology has done rather than enter data. As I go into this example, you'll notice the actual PDF that came through email from that vendor on the left hand side. On the right will be my NetSuite bill form as we have it set up, as we have it configured, including any customizations, any custom fields, any standard or custom segments show up on this screen. Zone & Co has helped to populate this information both at the header and the line level. We do this through a combination of different technology, OCR, AI, and also rules. We're giving you the right tools to do this efficiently. On the topic of OCR, if I click into this field, you'll notice as I choose the reference number, we're gonna highlight and show you where on the source PDF is that actually coming from. The same will hold true if I click into amount, if I click into these dates. We can take it a step further, and I can even point and click into a field and populate some data. Like, in this memo, maybe I want the address to show up. I'll just select it on the PDF. It automatically populates in the memo field, and now Zone & Co knows where to go and how to populate this field in the future. As we scroll down towards the bottom, I had mentioned AI. This is available out of the box. I wanna also point out you can also choose to reverse what suggestions has been made by AI. You can also decide to use it, and you can also leverage rules. You don't always need AI to suggest that maybe all the time we get these bills from smart web media should go to marketing and the marketing department in this particular segment value. Again, this works across standard custom segments, tandem custom fields, lots of ways to give you the right tools to quickly and efficiently get bills captured, coded, and entered inside of NetSuite. I'm gonna go ahead and actually create the bill now inside of NetSuite. I'll move it into our approval workflows. We'll get to approvals in just a moment. Before we do that, I wanna touch on two other scenarios. I had mentioned that we do have purchase order matching available. So we're gonna dig into an example of how Zone & Co helps when there are purchase orders and item receipts in scope. So I open up that example. Lots of similar ideas here. We'll see the actual PDF on the left, the bill form on the right. What's a little bit different is we're comparing this vendor bill Zone & Co received against the purchase order that exists inside of NetSuite and if relevant, item receipts that are also recorded inside of NetSuite. As I open up this three way matching pop up, we're gonna see those purchase order lines on the PO in NetSuite, the item receipts also recorded in NetSuite, and the bill lines that Zone & Co has extracted as part of our OCR and automation. Now the intention here is to help visually flag to you all, the users, any exceptions as we go through this process. We'll notice that there is a difference. There's a discrepancy. The rate on the actual bill is different than the rate on the purchase order. You have the ability to define tolerances. What happens if there are differences? You may have a zero dollar tolerance policy. You may have a dollar amount or a percentage. All of those are available functions to help control and automate as these differences are surfaced through our automation. This example also illustrates how to utilize our rules. In this bill, we have freight, and this showed up on the bill. We didn't have it captured or accounted for on the actual purchase order. What Zone & Co allows you to do is leverage those rules to automatically add a line on this expense subtab if we find freight captured as part of our automation. Now that everything is captured appropriately, I can actually just save to create this bill and continue moving through the rest of the workflow. I'm gonna go into one final example here, and this is going to be actually a bill in CAD for a Canadian subsidiary. We'll see in this example, same idea, sourcing and showing our work. We'll see those tax codes, those tax groups that would be relevant for sure for our customers with Canadian subsidiaries and subsidiaries in other countries. As I scroll down, we'll see the same idea here. We've got line level detail being extracted. We've got tax codes being populated, and we have rules. We can even use multiple rules on a single bill from a vendor. We have one overall rule for AWS and even a line level rule helping to apply and automate the overall coding process. Now that we've wrapped up really this portion of the demo, that invoice capture, let's get into the approval exercise. I'm gonna push this bill into the approval process, and what we're gonna see is the approval exercise. Now as Ivo Sofijanov Sofijanov had mentioned and alluded to, we will actually be able to see and help automatically trigger the approval matrix as it's been configured using Zone & Co. As I go into this bill, same bill we've been touching, and scroll down, in these sub tabs, you'll notice Zone Approvals. And in that sub tab, there's a matrix that's been automatically applied. That's determining systematically who needs to sign off on this bill. And as I go into the approval logs, I can see based on that matrix who actually needs to sign off on this bill. It's first come to me, then it goes to Abby, and last, it's gonna go to a role as it's set up and defined in NetSuite. Really, the idea here is we're leaning into existing NetSuite functionality to help simplify the process of managing, administering these rules and these matrices. The matrix itself is a click, not code concept. You don't necessarily need to know all the ins and outs to set this up, manage it, and make adjustments as things may evolve in the business. As we get into the actual approval experience, what I'm looking at is me, my example. I am a NetSuite user. I can approve since it is on me, this bill. I can also reject this bill. I have that same side by side view. Bill PDF compared to what's actually captured inside of NetSuite on the bill form. The alternative is that we can also get emails that go out to these approvers, and those approvers can just sign off based on that email. I'll pull over an example so we can take a look at what that email would look like. This email will give them the ability to approve or reject. They'll have a copy of the actual PDF from that vendor, a copy of that bill record from NetSuite showing the coding, giving them everything they need to quickly make some decisions to approve or reject this transaction. I'll go back into that bill inside of NetSuite. I'm gonna move it along into the approval process. We'll see it move into that next stage based on how that matrix has been set up again in a click not code concept. And one thing that Ivo mentioned and we talked about is those reminders. Often, people are chasing these types of things down manually if they don't have something systematic in place. As part of this matrix, the configuration, you get to define at what point in time a reminder is gonna be systematically sent out to users. It could be after twenty four hours. It could be after forty eight hours. Could be after seventy two hours. You get to decide when do those reminders start going out to folks inside the organization. As we kind of wrap up this approval process, where we're gonna go next, now that we have a vendor, we've got a bill, we've got a bill approved, it's really time to talk about executing payments. Now with Zone, again, using our control center, we can quickly and easily navigate to find the bills that need to be paid. I'm gonna go into our pay bills area where I can search my NetSuite. In this case, I'll look for my US subsidiary, for my bills in USD that need to be paid out of this account. And I'm gonna filter this list of different bills as they actually exist inside of my NetSuite. I'll see a result that I can choose either in bulk or individually, however I want to go about selecting and deciding which bills I wanna actually submit for payment, I can just go to process selected. Again, this is all connected within NetSuite inside of our solution, helping to close the loop. Often, people are doing this outside in their bank portal, and that means they may need to come back and record the actual bill payment for what's actually happening through their bank. This is one flow that also gives you approval workflows so you can actually make sure there's sign off before payments are submitted for execution. As we get pulled into the actual payment batch submission, We'll see that overall approval exercise, the payment batch itself, and be able to route that for our approval process. So here are the bills that have been selected. We'll go ahead and kick that off for our approval process. And now we can have, separate from an invoice approver, a payment approver come in to NetSuite, look at this batch, spot check it, make sure they're good with it before you hit go and actually start to execute these payments. Again, this is all connected in one workflow that works across different subsidiaries, different currencies, different payment methods to vendors all across the globe. Payments. Again, this is all fluid. Bill payments are getting recorded as we're going through this overall process. There's no separate step to come in and mark these as paid. I can quickly and easily connect everything together. So we're building those efficiencies and those different handoffs from vendor onboarding to capturing the bills, getting them approved, and executing the payments. The last thing we're gonna touch on is reporting and analytics. The beautiful thing about Zone & Co solution is we are inside of NetSuite. We're helping to extend that as we've gone through capturing, approving, and making payments. You can use existing NetSuite reports, safe searches to get information. You'll also have the ability to access Zone & Co own AI capabilities. We call it Zoe. And you can just type in plain language, what you're trying to get, what type of reporting or insights you're looking for, and Zoe will actually return some results based on that information. I'll pull open an example here. So imagine you're using this month in, month out, day in, day out. We've gone through transactional, operational usage, but this happens at scale. We now wanna get some meaningful insight. I can actually use, like I said, natural language and start to look for things that I can action on. In this example, I'm asking for regular patterns. Show me vendors that have submitted things that are a little bit unusual. And Zone & Co returning a result that I can actually expand into, giving me an extended analysis, digging a little bit deeper, and showing the actual SuiteQL query, truly showing a work and explaining how we came to this. So you have audible information, things you can look at, help to verify. And if you wanna take it a step further, you can also download this to CSV and do what you need to. Now that is going to wrap up our demo. Just to recap, we've walked through onboarding vendors, simplifying that process, automating it by leveraging AI, capturing bills, PO backed bills, stand alone bills, multiple currencies, multiple languages. We got through approvals, making sure the right folks are signing off on it. We even touched on payments and how Zone & Co can help surface insights by just asking for what you're looking for and getting the results and showing how we got there. With that, I'm gonna stop sharing my screen, and I will pass it back to Justin. Perfect. Thank you so much, Daniel, for this amazing demo. So we'll just wait for the screen. The efficiency wins you just saw are obvious. Fewer touches, faster processing. But the secondary benefit is arguably bigger. Good automation creates better data, and better data creates leverage. When NetSuite is updated accurately and continuously, you stop reconstructing what happened last month, and you really start focusing on what's happening right now on your business. This pattern extends well beyond AP into billing, revenue, project margin, reconciliation, and other financial workflows. That's why we treat automation as a core ERP decision at SkyHigh ERP, not just another software purchase. So if you look at the graph here, you can see that we start from cleaner inputs to more reliable transactions. More reliable transaction, which means we are trying to avoid duplicates like, Daniel was showing in the demo, which we're trying to make it as clean as possible. That creates better NetSuite data, better reporting and visibility into better decision. Now let's talk about AI. Everyone wants to apply AI to finance. AI readiness is an ERP problem before it's an AI problem. If your process are scattered across emails and spreadsheets, AI has really nothing reliable to learn from. Once you build that trusted foundation, you unlock real capabilities, like an all be... Anomaly detection and intelligent exception handling. You'll need to deploy AI everywhere tomorrow. But the work that we're doing today, setting up, explaining the cleaning, explaining the importance of this, will help you build the foundation to make it possible in the future for your business. So how do you actually get there? Sorry about that. Here's a blueprint. Don't start by asking which tool should we buy today. Start by finding your friction points. Where does the data break down? Fix that foundation first, then connect the life cycle. Handle the exceptions, and finally, add the layer of intelligence. That's exactly where SkyHigh ERP comes in. We help you diagnose the environment, design the operating model, and implement NetSuite and Zone to make it a reality. So the the Sky team is a great team to... If you will need to book any appointments, we're always there to, to analyze your system and give you an implementation plan. Now, before we jump into q and a, I'll leave you with this. The modern finance type isn't the collection of point solutions. It's a well connected system that turns transactions into control and control into intelligence. The goal isn't just more automation. It's an operation where your workflows, data, and its suite environment actually reinforce each other. Zone provides the AP technology, and SkyHigh ERP is the partner to help you build and optimize the environment around it. Now I'll pass it back to Ivo for the q and a. Awesome. Thank you so much, Justin. So we've covered quite a bit. We'd love to open it up for questions. Feel free to drop anything into the chat, whether it's around API automation, NetSuite process design, AI readiness, implementation, or just where you're seeing friction and while questions are coming in we do actually have a couple we hear pretty often that were pre submitted as well. So I'll tackle the first one here. Where do you usually see the biggest gap between companies that say they've automated AP and companies that actually have a well governed control AP process? Great question. I would say usually it's that they've automated individual steps not the actual life cycle itself. Example here is maybe invoice capture is automated, but vendor onboarding still happens through spreadsheets and through emails. Or they have a good approvals process, and that's automated in somewhat way, but the payment process still happens in a separate bank portal. Those handoffs are are normally where visibility and control start to break down. So I would say, you know, the biggest difference is when you connect the process from vendor setup through invoice capture approval and payment, it is when you can truly say that you've achieved real automation. Looks like we have one more here. If a company is already using NetSuite, where should they start if they want to improve AP without trying to transform everything at once? Look, I think that's a perfectly fair question. I'd start by mapping the actual vendor to payment process and identifying where the greatest manual effort or risk exists today for your organization. So for one company, like we explained, that might be invoice entry. For another, it might be approvals or vendor setup or payment execution. You don't necessarily need to automate everything at once, but whatever you solve first, it should fit into the broader architecture of what you're trying to build. The thing I would avoid is solving one isolated problem with another disconnected tool and creating kind of what we like to say is an integration tax or a future integration problem later. So that's a great question. Justin, looks like we actually have one for you as well. What level of data hygiene needs to exist in our core NetSuite setup before we can realistically start talking about adding AI or AI adding business value in this case. Yeah. That's actually a really good question and very fair. Since AI is always everywhere, we've kinda... Like I said, we have to make sure that everything is clean. So I would say in three points is completeness, consistency, and centralization. So for completeness and consistency, you cannot have duplicate vendors profile, fragmented classifications, or really use the... Or a a custom field that you basically never use. AI models rely on standardized structured data to recognize the patterns. If your underlying records are inconsistent, the AI insights will be fundamentally flawed. And the second part of it is centralization. AI needs a single unified source of truth. So if a crucial financial context is still trapped in offline spreadsheets or disconnected point system, the AI is essentially fine blind. All relevant data must flow directly into NetSuite as your operational backbone. Great stuff. Really good stuff, Justin. We also have a question here from, somebody. Is zone able to handle complex purchase order approval workflows? The answer is yes. So Lindsay, the approvals module that we we walked through today, it is fully functioning and usable not just for vendor bills, but it does also support purchase orders, purchase requisitions, expense reports, sales orders, credit memos, standard journal entries, and then a few other record types as well. So the answer is yes, we are absolutely able to handle complex PO approval workflows. And if you're talking about it in the context of your three way match inside of NetSuite, we can also configure tolerance thresholds and and really define that process in a way that makes most sense for your team. Alright. Great questions. So really what we also wanna do here before we round off is we wanna leave everyone with the practical next step. If today's discussion does have you thinking about your own NetSuite environment, we are offering a complimentary sixty minute operational excellence assessment with SkyHigh ERP and Zone and Co. The idea isn't just to jump straight into another product demo. What we do wanna do is actually map out your current procure to pay process. Right? How are vendors being onboarded? How are invoices getting into NetSuite? How is matching and approvals operating in your environment? How do payments happen? And then, ultimately, how does all of that impact your reporting and close? From there we can identify where the biggest gaps are, where there's an opportunity to automate, and where process or NetSuite configuration may actually be the the more important issue. So the outcome should be a much clearer picture of where you are today and what would realistically be worth prioritizing next. And for anybody who does want to book the assessment, we will also send you two resources to take away. The first is gonna be our 2026 AI impact versus hype in finance report. That's based on, you know, research with 565 finance professionals and really looks at where AI is actually creating value today versus where there's still more hype than substance. And the second is a library of more than 85 AI prompts built specifically for NetSuite teams. So regardless of, you know, where you are in your automation journey, hopefully, both can give you some practical, takeaways that you can take back to your finance team. So with that, I wanna thank everybody for all of their time and diligence today and the excellent set of questions. We hope this session was very useful. We'll leave this QR code up here for a moment. If you would like to take what we discussed today and apply it to your own NetSuite environment, just scan the code, book a time that works for you, and we'll come into that session focused on understanding your current process first. And from there, we can really determine together where the strongest opportunities actually are. So with that thanks again for joining us today we really appreciate the time and hopefully you're leaving with a few practical ideas from the SkyHigh ERP and Zone teams that you can apply within your own finance organizations. Take care everybody. Take care. Thank you. Thank you.