What do days to close and exceptions on day one measure?
Days to close is the number of days from the end of an accounting period to the date the controller signs the close, taken from the ledger's own period and sign-off dates. Exceptions open on day one is the count of items, bank lines, payouts, invoices, that were unmatched or had an unexplained difference at the start of the close, taken from the Finance Controller Digital FTE's match record on ftes.ai. Together they show whether daily reconciliation changed the close from a reconstruction into a review, which is the honest claim for a role that proposes every match and posts nothing unapproved.
Neither number claims the FTE closed the books. The controller did, faster, from a matched ledger.
How are they computed, with the inputs left blank?
Period: [month]. Period end: [date]. Sign-off: [date], by [controller]. Days to close: sign-off minus period end, [days]. Exceptions open on day one: items in the match record marked unmatched or partial with an unexplained difference at [date], [count], with their total value, [figure]. Baseline: the same two numbers for the two closes before the pilot, [days] and [days], [count] and [count], from the ledger and from whatever record the team kept of open items. Companions for the period: transactions proposed and approved daily, [count]; match approval rate per class, [rate]; controller and finance staff hours on the close, [hours], from the baseline sheet.
If the team kept no record of open items before the pilot, label the baseline count as reconstructed and rely on days to close and hours.
- Days to close: sign-off date minus period end
- Exceptions on day one: unmatched or unexplained items at close start
- Companions: daily matches, approval rate, close hours
Why these and not transactions matched?
Because transactions matched is activity, and a thousand matches nobody approved are a thousand proposals. Days to close and exceptions on day one are outcomes the business already cares about and already measures, they cannot be inflated by proposing more, and they capture the point of daily reconciliation: that the close starts from a matched ledger with a short exception list. Matches proposed and approved is a useful companion, and it is the denominator for the role's cost per outcome, but it is not the measure of whether the function improved.
The finance FTE's targets are set on the two outcome numbers, with the companions shown beside them.
How does the close change, and when does it show?
In the first close after the pilot starts, part of the period ran without the FTE and the exceptions include items from before daily matching began; label it first-cycle. In the second close, the whole period ran with daily proposals, exact matches under the threshold may have earned autonomy under the Promotion Standard, and the controller opens a ledger where the exception list is the work; that close is the comparison. The controller's hours on the close, from the sheet, usually fall before days to close does, because the judgement items, accruals, revenue recognition, deferred revenue, take the same time regardless and set a floor.
The subscription revenue piece and the time-and-billing piece in the library show the same measures in two verticals.
How do they mislead?
When the period is not comparable: a quarter end or a year end has more judgement work than a month, and the baseline must match. When the sign-off date is soft: if the controller signs late for reasons unrelated to reconciliation, an audit, a system change, days to close moves for reasons the FTE did not cause; note them. When exceptions fall because the threshold was raised: a wider exact-match threshold hides differences rather than resolving them, and the approval record will show partial matches approved without explanation. And when the first close is used as the comparison. Each is a labelling discipline rather than a flaw in the measure.
The CFO persona piece sets the evidence standard for reading these numbers at a board.
How are they applied?
Record the baseline from the last two comparable closes before connecting the ledger. Set the finance FTE's targets on days to close and exceptions on day one at the first review, with the companions shown. Read the match record daily and the approval rate per class weekly. At each close, write the two numbers and the hours in the review note against the baseline, labelling the first close. Use the match approval rate and send-back reasons, not the close numbers, as inputs to the Promotion Standard for exact matches. Compare at the second close and again at the quarter.
The finance FTE remit template sets the threshold and the escalate list the measure depends on.