good morning. So, as Michelle mentioned, so I'm going to go over the audit letter. So this is a, you know, in addition to the opinion that we issue, we also issue this end of audit letter. It's a follow to our pre audit letter that we would have sent out earlier in the audit to kind of go through our plan and scope and timing of the audit. This is kind of like, Hey, this is the end. Here's here's our conclusion from from the audit, and so talking about the internal control related matters. So we had two material weaknesses or controls that we deem to be material weakness, and then one significant deficiency, or deficiency so material weaknesses we identified to the census data and it process. These are repeat findings, a little bit differences from prior years, so for the census data, so if you recall, so the total pension liability, or the net pension liability that we. Present on the on the previous screen, assets are as a 630 24 but the census demographic data, like an individual's pension payment, who's active, who's retiree, all of that, that's actually as a 630 23 so that's on a on a year lag. And so that data that we have to is actually coming still from the old system. So the old IT system that ran and it would produce, so a lot of the same census data issues that we had identified in the past came up again this year. One of them, you know that we've been in the latter intentional salaries and how the system was, you know, before giving to Gabri, rotor was taking information from the city, but then trying to annualize the pay for component one, instead of just saying, Okay, here's, here's what actual base pay for. You know, pensionable wages were for component one. So we've talked to, you know, Dave Ramsey and Dave, they've talked to the IT group of just like, hey, the new system, make sure we're not annualizing pay. We're just taking years actual pay. So we feel like that that will come off for next year. We noted other other items related, again, to like, you know, some being improperly included or excluded from the census data. And so we actually had, as we have in the past years, gave a rotor kind of go through and do a look back, sort of hey, here's the data we had on active and term vested individuals, different vested individuals. Here's how they had made assumptions on based on their data, what their liability was. And then now we know, hey, they've come in and retired. So we know here's their final payment. And so they've done a kind of a look back to see how off were they, and they determined that a, you know, it was materially correct. They didn't need to put what we call a load on any of the liabilities. So if they're seeing that, hey, everybody's potential wages is coming in 5% lower, we should raise 5% to in our assumptions. They've done that in the past. Years ago, they did not feel like they needed that to do that as it relates to information technology process. So again, this is, you know, kind of different as the system is, is implementing some of the new ERP software. So we do have an item, again, related to the IT system, on the old system for census data, but everything else really is on the new system, and teleplans related to benefit payments and whatnot. So we've, we've identified other things about like just user access, reviews, admin access, doing reviews of that. So we talked to the IT group we talked to Andy day Kelly, they're well aware of, and I know Kelly already had mentioned that she had already started talking to John, and it about some of the admin account access and whatnot, yeah, um, the last thing we had asked, yeah,