GASB 87 Leases Implementation Overview

This overview delves into the implementation process of GASB Statement No. 87 on leases, focusing on identifying lease populations, categorizing lease types, and addressing issues related to embedded leases. Key steps, considerations, and exclusions are discussed, providing valuable insights for organizations undergoing similar implementation processes.

• GASB 87
• Lease Implementation
• Lease Categories
• Embedded Leases

everlei Follow

Uploaded on Feb 23, 2025 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. U. T. System GASB 87/Planon Implementation Dana Malone and Marili Cavazos

2. GASB Statement No. 87, Leases First begin considering software that you will use We ruled out PeopleSoft and other software solutions with no lessor side or those that would not be ready for our timeframe We reviewed AMT, UGAAP, CCH and Planon in the RFP process because they were the only ones who responded to our RFP. Downside of implementing software early is less options available 2

3. GASB Statement No. 87, Leases Step #1 is identifying your population We were fortunate enough at System Administration to have Content Navigator where all non-real estate contracts are stored System Administration was also fortunate for all real estate contracts to go through Real Estate Office Unfortunately, System Administration has lots of lessor leases Institutions had a mixed bag of central and decentralized leases, which makes it harder to identify your population 3

4. GASB Statement No. 87, Leases Once we identified our population, we broke it down into the following buckets Commodities Construction Hotel Event Insurance Services (look for embedded leases) Leased equipment Leased space MOUs Online Data Service Software Cloud-Based Software PC Server Based 4

5. GASB Statement No. 87, Leases UT System primarily has Copiers PC s Vehicles Leased space lessee and lessor Ground Leases Excluded leases due to following reasons Month to Month/Year to Year leases - paragraph 12 cancellable leases Leases based solely on usage paragraph 22 based on usage excluded, example parking where amount changes based on usage (disclosure only) Short-term leases paragraph 16 MOUs with no term indefinite Interdepartmental leases 5

6. GASB Statement No. 87, Leases Issues we identified with our leases Embedded leases example, buy coffee supplies get coffee machines free and buy sandwiches get vending cooler free Parking revenues where number of staff and receipt varies monthly Rental of copiers includes card reader software with separate software contract included copiers, but not software due to exclusion 6

7. GASB Statement No. 87, Leases We created program codes (AKA chartfields) for all lease payments to help us distinguish between short-term and long-term leases We query that information to make sure we had our entire population to validate that we had not missed any leases This is also necessary to validate the lease payments being removed in the journal entries 7

8. GASB Statement No. 87, Leases While we have implemented many GASB Statements over the years, we have not implemented many software solutions, therefore we engaged a Project Manager that has worked on several software implementations to help us This proved invaluable to keeping us and all the institutions on track creation of dashboards She also was very helpful in translating the IT lingo when dealing with software vendor 8

9. GASB Statement No. 87, Leases Once a software is picked, you must decide how contracts will be entered Rather than enter each individual lease, we entered each lease including all assets on each schedule with same start and end date This was done for ease, as well as vendors often charge based on volume The Comptroller s Office allows computing NPV based on individual leases or schedules Obviously entering individual leases will lead to more immaterial leases We also made the decision early on not to replicate the GASB 87 calculations into the PeopleSoft Asset Management System 9

10. GASB Statement No. 87, Leases Since we are audited, we had to prove to the auditors that our immaterial leases were in fact immaterial We had Planon compute the NPV for each lease and flag any that fell under $100K as immaterial Accounting entries are only produced for material leases, but we can run reports on immaterial leases for auditors 10

11. GASB Statement No. 87, Leases We close leases monthly in Planon to generate journal entries that interface with PeopleSoft Now that GASB moved the effective date of GASB 87, we post and unpost monthly until next fiscal year Don t underestimate the time needed to be sure the interfaces work, because that took more time than anticipated 11

12. GASB Statement No. 87, Leases We benefitted by implementing the software early and allowing more time to practice lease modifications, applying options, and terminations What was unanticipated was the amount time required for system maintenance (upgrades and refreshes). For other software like PeopleSoft, the IT department handles the maintenance. Our PM is on contract to handle this for us. This will be an issue with any software. We also did not anticipate how much of Marili s time would be required going forward for this GASB Statement. 12

13. Questions? 13