These are the features of The Finance Lead that exist today. Each section explains what the feature does, what data it keeps and shows one concrete example.
A template is the reusable list of tasks for one close. Each task has a title, an optional description, a preparer, a reviewer, a due date counted in business days from period end, and a rule for which evidence it needs.
Stores the template name, the monthly or quarterly cadence, and per task the people, the due offset, the evidence rule and the sort order.
Example: the task "Bank statement files, all accounts" is due 2 business days after month end, prepared by Sarah, reviewed by Mike, and requires a link.
Opening a period such as September 2026 copies every template task into the period and calculates its due date. Weekends are skipped.
Stores one period per template, month and year, plus one task per template task with its own due date, status and assigned people.
Example: a task with a 5 business day offset for a period that ends on Wednesday, September 30 is due the following Wednesday, October 7.
Every preparer sees the tasks assigned to them across periods, with filters by status. Overdue due dates are shown in red so nothing hides at the bottom of a spreadsheet.
Shows task title, period, due date and status for the signed-in user.
Example: Alex opens My tasks, sees two overdue items for the revenue deferral schedule, and submits both with a link.
A preparer attaches proof to a task by pasting a link to the document in your own storage, or by writing a short note. The app does not host files, so source documents stay where your team already keeps them.
Stores the link or note text, who submitted it and when. It does not store file uploads.
Example: the evidence for the bank reconciliation is a link to the shared folder with the signed PDF statements.
A preparer submits a task for review. The reviewer approves it or sends it back with a comment. When segregation of duties is on, a database rule blocks anyone from approving a task they prepared.
Stores each submission, approval and change request with the person, the time and the comment.
Example: Mike requests changes on "Accrual support documentation" because one invoice is missing, and the task returns to Sarah as reopened.
The overview counts approved, in-progress, overdue and reopened tasks for the current period and shows which tasks block the close. The close ready indicator turns on only when every configured task is approved.
Calculates from the tasks and evidence already in your workspace. It does not read your ledger.
Example: 11 of 18 tasks approved, 2 tasks missing required evidence, 1 task waiting for review.
Every submission, approval and change request is listed in a trail you can filter by review events and audit events, so you can show an auditor who signed off what and when.
Stores actor, action, affected task and timestamp. Entries cannot be edited from the app.
Example: "Mike Johnson approved Payroll journal evidence on October 2 at 10:14."
Owners and admins invite teammates as admin or member. The app creates an invitation link that you copy and send yourself, because it does not send invitation emails. The Team plan includes up to 8 members.
Stores the invited email address, the role and the invitation status.
Example: you invite a reviewer as member, copy the link and send it in your team chat.
The Plus plan includes an MCP server that lets Claude Code, Cursor and other MCP clients read close periods, task status and blockers. It cannot approve, edit or delete anything.
Stores a hash of each workspace-scoped token, a label and the last-used time. The token itself is shown once.
Example: you ask your assistant which tasks still block the September close and it lists them from your workspace.
Read the MCP setup guide