Medius accounts payable automation provides additional control levels and options for processing recurring frequent type invoices compared to other purchase order or non-PO invoices. And we know that you get an invoice on a scheduled basis, whether that be monthly, quarterly, or certain set bill dates due to a project or contract. We can track to ensure you are getting billed as planned or even create a routable document in the case of rent payments that you don't receive a physical invoice for. With specific recurring invoice functionality, our customers get value regarding three different important functions. One, notifications to appropriate users and tracking when an invoice is not received. This helps accrue invoices not billed as planned as well as ensure your organization doesn't incur any late fees because someone forgot to download the invoice off of an electricity portal or maybe the bill got lost in the mail. Second, simple exception handling or amount alerts when a bill is higher or lower than anticipated. And third, for the ability of automatic processing, removing the need for a lengthy approval process when it's a bill that you pay every month or, again, on that recurring basis so that both AP and approvers can focus on more value added tasks. Granted, of course, it's within the amount and date tolerances we'd expect. Now when a recurring invoice bill arrives, our customers have the option to place the document in front of AP for review before posting as I'm showing here in my screen, or automatic posting as long as it's within tolerances. Users can review the coding that's been automatically applied and approve it to be integrated to the ERP system. Now as with our other invoice processes, Medius can handle complexities here. Considering scenarios where you might have a single vendor with multiple utility accounts or servicing different locations so that each bill is coded automatically per your business, or even scenarios where the expected billing amount varies for each billing period. For example, utilities won't be the same every month, and we know that. So variations in billing is supported and normal for your specific tolerances. These various ABC power bills are showing how the coding dimensions, splits, and amounts might vary depending on the specific utility account. Now when a bill is received outside of any tolerances you have in place, we can route the invoice to the appropriate user where they're notified, three yellow triangles, what the exact issue is. Upon action, whether that be approving or rejecting the bill, Medius can take care of the necessary coding in the background to eliminate another manual touch AP might be doing today. Users can access the invoicing schedule and expected remounts amounts to get further visibility into any invoices. That that they might be missing. Again, Medius can automatically alert the users if we're missing an invoice so that you don't go five months without payment. But this is just another way to access the data. Pointing out in my case from a utility bill perspective that you're able to see the amounts actually vary on a recurring basis. And I can access an uploaded contract document to review any issues that I might have or do research within the platform. Special reporting is available to provide you the visibility that you need regarding your invoice transactions. In the case that I'm missing multiple invoices, I'm easily able to access that data all within the platform. And Medius' recurring functionality allows our customers to be the most efficient while processing invoices, all while mitigating the risk of service disruption or late fees and providing the support, control, and visibility necessary for invoice optimization in the long term.