What does close automation actually mean?
Close automation with a Digital FTE means automating the mechanical steps of the close and leaving the judgement steps to a person, with the FTE preparing the evidence for them. The phrase is often used loosely; a clear version separates the two kinds of work.
Mechanical steps are those with a definite right answer that can be checked against evidence: does this bank line match this invoice, is this transaction in the right period, is this a duplicate. Judgement steps are those with defensible alternatives: how much to accrue, how to treat an unusual item.
Which steps does a Digital FTE automate?
A Finance Controller Digital FTE automates matching of transactions against invoices and bank lines, surfacing of exceptions with the reason and documents, cut-off checks that flag transactions near the period boundary, duplicate and anomaly detection, and assembly of the audit record from the logged decisions.
Automates here means it does the work and proposes the result; approval is still human until a class of action has earned auto-approval from the approval record. Exact matches usually earn it first.
- Matching: proposed with evidence, auto-approved once earned
- Exceptions: surfaced with reason and documents
- Cut-off: near-boundary transactions flagged for a period decision
- Anomalies: duplicates and unusual amounts flagged with the reason
- Audit record: assembled from logged decisions, exported at close
Which steps stay with the controller?
Accrual estimates, revenue recognition questions, treatment of unusual items, and sign-off stay with the controller. The Digital FTE can propose an accrual with the evidence it rests on, but the decision is an accounting decision and is recorded as the controller's.
This is not a limitation to work around. A close where the judgement calls are made by a named accountant from good evidence is a better close than one where they are made by a system, and it is the one an auditor expects.
Why does the close get shorter?
The close gets shorter because the matching happened daily rather than in the first week of the next month. By the time the period ends, the ledger is reconciled and the open exception list is short, so the close is a review of a small number of items rather than a reconstruction of a month.
It does not get shorter by skipping steps. Every step still happens; most of them happened earlier, one day at a time, with their evidence logged as they went.
How do you know it worked?
Record the baseline before the first close with the Digital FTE: days to close, exceptions open at day one, controller hours spent, and adjustments made after sign-off. Run two full closes, because the first includes setup and remit tuning.
Compare the second close against the baseline. A shorter exception list at day one and fewer controller hours on matching are the expected results; if they do not appear, look at the exception reasons, which usually point to a connection or remit issue rather than to the approach.
What does the controller see on the first day of close?
On the first day of close the controller opens the morning brief and sees the reconciled state of the period: transactions matched with documents, the short list of open exceptions with their reasons and evidence, cut-off candidates near the period boundary with a proposed period, and any anomalies flagged during the month that remain undecided. The close mission is already open in the Missions tab with its progress bar at the point the daily work left it.
What the controller does not see is a month of unmatched activity, because the matching happened every morning. Their day one is deciding the exceptions from evidence, approving proposed accruals with the reasoning attached, and routing anything with two defensible treatments to their own judgement. The audit record for the period is an export of what was logged as the month went, not a document to assemble. By the second close on this pattern, the difference between reconstruction and review is visible in the days-to-close number, and if it is not, the exception reasons say where the remit or a connection needs fixing.