Skip to main content

Release Notes

This article is updated weekly with a summary of the latest Leasecake release. Each entry includes new features, bug fixes, and other improvements shipped that week.

5-15-2025 Release -


✨ Features

  • None this week

🐛 Bug Fixes

  • None this week

⚙️ Miscellaneous

  • Added backend validation for Accounting Lease changes so the Changes Effective Date must be on or after the Company's Adoption Date

  • Improved Lease Form performance by replacing large account-wide data preloads with lease-scoped data requests and reducing unnecessary API calls, resulting in faster load times

  • Users can now select a specific discount rate for modifications and adjustments. Previously, the Implicit Rate in the Lease input field was functioning only for Initial Measurements, even though it appeared to be usable for modifications and adjustments.

  • Improved performance for the Dashboards API endpoint by removing unnecessary queries when loading dashboard order and subscription data

  • Improved the overall performance of report pages by implementing an API endpoint to fetch Saved Reports filtered by report type

  • The Total Tenant Improvements value is now correctly displayed on the Leases tab of the Company level ASC 842 Amortization (Consolidated) export

  • Fixed an issue where adjustment entries incorrectly defaulted to the adoption-year IBR instead of using the most recent prior measurement, causing inaccurate rates after modifications. Adjustments now correctly inherit the IBR from the immediately preceding measurement in the chain.

  • Fixed an issue where using the Change Owner action caused a validation error when updating user details

  • Accounts with the indexation feature enabled see one-time payments in the Current Rent widget on the lease page

  • The rent summary calendar now correctly navigates to the selected month regardless of the user's local timezone

  • Improved the overall performance of pages containing Files (Documents) by implementing API endpoints to fetch files associated with a specific entity

  • Improved the overall performance of pages containing Custom Events by implementing API endpoints to fetch Custom Events associated with a specific entity

  • Improved the overall performance of pages containing Custom Attributes by, reducing unnecessary data loading and response time


Did this answer your question?