Why is the traditional close a scramble?
The traditional month-end close is a scramble because reconciliation is deferred to it. A month of transactions gets matched in the first week of the next month, exceptions surface all at once, and every unusual item is weeks old by the time anyone looks at it.
The pressure is structural rather than a matter of diligence. When matching and closing happen in the same week, the week is long by definition.
How does daily reconciliation change the close?
Daily reconciliation changes the close by removing the matching from it. A Finance Controller FTE matches each day's transactions as they arrive and raises exceptions the same day, so by month-end the ledger is already reconciled and the open list is short.
The close becomes a review: confirm the reconciled state, decide the remaining exceptions, approve the adjustments, and sign off. The work that made it a scramble has already been done, one day at a time.
How does the FTE run the close itself?
The Finance Controller FTE runs the close as a production mission: a bounded push from open items to a reviewed close, with progress visible in the workspace. The manager can see how many items remain, which are waiting on a decision, and which are waiting on a document from someone else.
Each adjustment arrives as a proposal with the evidence and the reasoning, and a named person approves it. Nothing posts on the FTE's own judgement, which is what keeps the close auditable.
- Day 1: reconciled state confirmed, open exception list reviewed
- Days 2-3: remaining exceptions decided, adjustments proposed and approved
- Day 4: cut-off checks, accruals proposed with evidence
- Day 5: sign-off, audit record exported
What still needs an accountant?
Judgement calls still need an accountant: ambiguous treatment, accrual estimates, revenue recognition questions, and anything where two defensible answers exist. The FTE can propose with evidence, but the decision is an accounting decision.
The difference is that the accountant now makes those decisions from an evidence-rich ledger with a short exception list, rather than after a week of matching. Their time goes to accounting rather than to reconciliation.
How do you measure the change?
Measure the change by recording the baseline before the first close: days to close, open exceptions at day one, and accountant hours spent. Run two full closes before drawing conclusions, because the first one includes onboarding.
The second close is the honest comparison. If the exception list at day one is shorter and the accountant hours fell, the daily reconciliation has done its job. If not, look at the exception reasons; repeated exceptions of the same type usually point to a remit or connection issue that is fixable.
What does the close mission look like in the workspace?
The close mission appears in the Missions tab as a bounded push with a start, a target, and visible progress: open items at the start, items resolved, items waiting on a decision, and items waiting on a document from someone else, updated as the work happens. The morning brief during the close puts the items waiting on the controller first, each with its evidence, so the close's human decisions are made from the top of the brief rather than from a spreadsheet.
Each proposed adjustment waits in Approvals with the reasoning and the documents, and the controller's decision is logged with their name. Cut-off checks appear as flagged transactions near the period boundary with a proposed period. When the mission completes, the audit record for the period is an export of what was already logged, and the FTE writes the close's review in the first person: what was reconciled, what exceptions remained and why, what took longest, and what it recommends changing before the next close. Two closes into the record, the review is where the days-to-close improvement is either visible or honestly absent.
Write the close's decision rights into the remit before the first close: which adjustments the FTE may propose, the threshold above which everything stays gated regardless of pattern, and which categories go to the accountant rather than the controller. The mission then runs against rules that were decided calmly rather than in the last week of the month.