Use case
Month-end close, as a checklist.
The close checklist updates as the work gets done: reconciliations tick themselves off, accruals and flux arrive with their evidence, and every task waits for the person who owns it.
Book a demoThe problem
A spreadsheet of tasks nobody trusts.
The close lives in a shared spreadsheet that says what should happen, not what has. Status meetings exist to find out which.
Accruals are rebuilt from memory every month, and flux explanations are written the night before the board pack.
The workflow
Four steps, three of them Tessel’s.
- 01
Your checklist, once
Import the close checklist you already use, with an owner and a due day for each task.
- 02
Tessel does the reconciling
Reconciliation tasks tick themselves off as accounts tie out.
- 03
Accruals and flux arrive drafted
Suggested accruals and movement explanations wait for a reviewer.
- 04
Sign off in order
The controller signs last, with every task and its evidence in one view.
In the product
The month-end close view
March close · reconciliation tasksMarch closeDifferenceΔ 1,240.50
| # | Date | Description | Bank | Ledger | Status |
|---|---|---|---|---|---|
| R1 | 31 Mar | Operating account · tied out31 Mar | 0.00 | 0.00 | Matched |
| R2 | 31 Mar | Payroll account · tied out31 Mar | 0.00 | 0.00 | Matched |
| R3 | 31 Mar | Card clearing31 Mar · 1 line held | 312.00 | — | Flag |
| R4 | 31 Mar | FX account31 Mar | 1,240.50 | 1,240.50 | Open |