A close management tool is, underneath the checklists and the status board, a system for managing handoffs. Task A finishes, person B gets told, person B starts task C.
Which means the honest way to evaluate one is to count the handoffs it will be managing, and then ask why they exist.
At All Gravy the count was high and the reason was structural. 4 markets on 4 different ledgers, and local systems demand local people, so each market needed a bookkeeper who could read that interface and knew its quirks. 4 ledgers became 4 dependencies and 4 places the close could stall. No amount of scheduling fixes a dependency chain where the slowest market sets the group's timetable.
ledgers at All Gravy, which removed 4 separate closes and the handoffs between them
days to close 4 countries at All Gravy, with nobody working nights to get there
people on the finance team running it, unchanged while the company doubled
The two kinds of handoff
Handoffs that exist because work is genuinely sequential. Revenue has to be recognised before the P&L is final. Eliminations need both sides posted. These are real, and coordinating them is legitimate work that a checklist does well.
Handoffs that exist because the data is in different places. Somebody has to export from the Norwegian ledger before anybody can consolidate. Somebody has to mark bills paid by hand because 2 integrations fight over the same bank feed. Somebody has to key 500 to 600 card transactions before the entries are complete.
The second kind is the majority of a long close, and it is the kind close management software is worst at, because it schedules the transport rather than removing it. A well-run export is still an export.
Tillo shows what removing them does. Before, nobody could close an entity, log out and start the next one, and the close ran 12 days. On 1 ledger the team works across the group by function instead: revenue, approvals, reconciliations, each done once for all 4 entities rather than 4 times over. The close is 5 days, and most of the coordination it used to need has nothing left to coordinate.
What the tool does
Schedules the handoff
Owners, dependencies, reminders, status. Genuinely useful for the handoffs that have to exist.
What the ledger does
Removes the handoff
One system means no export step, no import step, and no person in the middle of either. The dependency disappears rather than getting a due date.
What stays
Review, and who signs
Judgment, estimates and sign-off remain sequential and still need coordinating. That list is short.
The single-owner problem
Close management software is sold for large distributed finance teams, and most companies evaluating it do not have one. They have 2 or 3 people, which produces a different failure.
At that size the close is not badly coordinated. It is concentrated. One person knows which entity is behind, which vendor always bills late, and which reconciliation breaks in months with 5 Mondays. That knowledge is not written down, so the close depends on that person being available, and a checklist recording that they are the owner of 40 tasks documents the risk without reducing it.
The version that reduces it is work that runs on a schedule instead of on somebody's memory. All Gravy's collections used to mean downloading balances, assembling a list, reading back through the history with each customer and writing every chaser by hand. It now runs as an agent across all 4 entities, which is 1 fewer thing depending on a person being at their desk.
"The dunning agent gives us the full picture of what is outstanding and handles the chasing. That used to be my afternoon."
Linea Meldgaard Andersen, Finance Analyst, All Gravy
Sign-off, and where it should live
Sign-off is the part of close management with a genuine claim to existing. Somebody has to attest that the period is final.
The question is where the record of that lands. If sign-off lives in the coordination tool and the accounting record lives in the ledger, an auditor gets 2 artefacts and has to bridge them, and the attestation is evidence about a process rather than evidence about the books.
On an immutable ledger the position is different. Every entry is attributable and timestamped, corrections are new entries referencing the original rather than edits in place, and audit agents verify continuously against policy, producing a monthly control report of what was checked, what passed and what was flagged. Sign-off attaches to the record rather than describing it.
The question to ask first
Before comparing close management tools, list the handoffs in the last close and mark each one as sequential or transport.
If most are sequential, a coordination tool will help and the shortlist is worth working through. If most are transport, moving data between systems that should not be separate, then coordination software will make a 12 day close a well-organised 12 day close, and the number will not move again after the first month.
All Gravy's answer was to replace 7 systems with 1 rather than to schedule the traffic between them. The close is 5 days across 4 countries, and nobody stays up for it.
Read why the close is a batching artifact, see how Light closes continuously, or book a demo.