Lease Schedule Tracker (ROU Asset & Lease Liability)
Enter your leases, let AI present-value the payments, build the right-of-use asset and lease-liability amortization schedules, and draft the monthly journal entries — then post nothing until the controller approves.
A web tool where you import a leases list; AI present-values the payments at your discount rate to compute the right-of-use asset and lease liability, builds the full amortization schedule, and splits each monthly payment into interest and principal. The controller reviews the schedule and the monthly entry, approves, and the tool exports the lease schedule, the GL-ready monthly journal, and a disclosure roll-forward.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A leases list you can export to CSV (lessor, term, payments, discount rate, start date, classification)
- Claude Code or any AI coding agent
The problem this kills
Modern lease-accounting standards turned a simple rent payment into a monthly accounting project. Every lease that used to be an off-balance-sheet footnote now has to sit on your balance sheet as a right-of-use (ROU) asset and a matching lease liability — and every month you have to unwind that liability, split the payment between interest and principal, amortize the asset, and book a journal entry that ties out to a schedule auditors will actually open.
So you keep a giant spreadsheet. One tab per lease, a present-value formula you copied from somewhere, a 60-row amortization grid, and a fragile set of links that feed the monthly entry. Add a lease and you clone a tab and pray. Change a discount rate and half the workbook recalculates the wrong way. At year-end the auditor asks for the disclosure roll-forward — additions, accretion, payments, ending balance — and you rebuild it by hand from twenty tabs.
The dedicated lease software that fixes this costs more than a small accounting team's whole tooling budget. This is exactly the kind of rules-based, high-stakes math that a small internal tool does better than a spreadsheet — and you do not need to be a developer to build it.
What you'll build
A simple internal web tool for lease accounting. You import a leases list — lessor, start date, term, the payment schedule, the discount rate, and operating-vs-finance classification. The tool present-values the payments at your discount rate to compute the opening lease liability and the ROU asset, then builds the full amortization schedule: for each period it accretes interest on the liability, applies the payment, and reduces the liability and the asset. AI drafts each month's journal entry from that schedule and flags the leases that need a human look — modifications, missing rates, short-term exemptions.
The controller reviews the computed ROU asset, the liability schedule, and the proposed monthly entry on one screen, edits or excludes anything that looks wrong, and clicks Approve. Only then does the tool produce the GL-ready monthly journal, the lease schedule export, and a disclosure roll-forward you can hand straight to the auditor.
What's inside the Implementation Plan
The plan is a single file you paste into an AI coding agent. It opens by interviewing you about your business — which lease standard you report under, how your leases are classified, your discount-rate convention, your payment timing (beginning vs end of period), your fiscal calendar, and your nastiest edge cases like modifications and variable payments — and then tailors the data model, the present-value math, and every later step to your answers. This is a build shaped around your lease portfolio, not a generic template.
From there it walks the agent through the database schema, the leases CSV import with its duplicate guards, the present-value and amortization engine, the monthly-entry drafting, the controller's review-and-approve screen, and the export of the schedule, the monthly journal, and the disclosure roll-forward. Every step ends with a ready-to-copy prompt. Because the whole thing runs on CSV in and GL-ready CSV out, you can build and use it this weekend even if you have no direct connection to your accounting system.
The governance it includes (this is the point)
This touches the general ledger, so it is built like it matters: login so only your finance team can use it, row-level security so you only ever see your own entity's leases, and a complete audit trail of every import, edit, approval, and export — who did what, and when. Nothing posts automatically: every monthly entry is a draft until the controller approves it, and approval is the hard human-in-the-loop gate before anything becomes a journal entry. Duplicate guards on the lease ID — and on each imported file — mean the same lease can't be loaded twice and the same month can't be booked twice.
Who it's for
Controllers and staff accountants who have to account for leases under a modern lease standard but can't justify dedicated lease software. If you can explain how you classify a lease and pick its discount rate, you can build this.
You've got this — open the plan, paste the first prompt, and let it interview you about your leases.