The close calendar can make a finance bottleneck visible without explaining its cause. A reconciliation scheduled for day two may wait until day five because a receipt, intercompany agreement or supporting document is missing. Compressing the calendar does not make that evidence arrive earlier.
A useful close improvement starts by following the unfinished work back through the month. Which exceptions could have been identified sooner? Which records were available but unreviewed? Which decisions had no clear owner?
AI and workflow automation can help with evidence gathering, matching and coordination. The case for investment depends on whether those activities sit on the path that actually delays completion.
Benchmark the right duration
APQC's publicly visible monthly-close measure showed a median of eight days across 3,389 companies when accessed on 28 September 2026. Its definition of cycle time includes both active processing and waiting. The page does not state the underlying data vintage or expose the quartile values publicly, so the median is a broad reference point rather than a current target for every organisation. APQC, monthly financial close cycle time
Before comparing your result, define the start and end events. Closing a local ledger, completing consolidation and issuing the management pack are different milestones. Also specify whether the measure uses working or calendar days.
A faster reported close is meaningful only if its scope and quality are maintained. Track post-close adjustments, reopened reconciliations and unresolved material items alongside the completion date.
Separate work that can move from work that must wait
Some tasks depend on period-end information or accounting decisions and cannot simply be pulled forward. Others accumulate because the process only brings them to someone's attention during close.
| Workstream | Useful activity during the month | What still needs period-end judgement or validation |
|---|---|---|
| Bank and cash reconciliation | Match available records and investigate aged differences | Confirm completeness and the final period position |
| Intercompany | Surface mismatches and route queries between entities | Agree final balances and consolidation treatment |
| Supplier and customer exceptions | Gather evidence and resolve known discrepancies | Assess remaining items and their period impact |
| Supporting schedules | Assemble available records and identify gaps | Validate cut-off, completeness and accounting treatment |
| Close coordination | Track dependencies, owners and outstanding evidence | Approve completion and required adjustments |
APQC publishes a month-end checklist covering common closing tasks. A checklist is a useful starting structure, but the local dependency map must reflect the company's entities, systems and policies. APQC, month-end close checklist
The design exercise should make waiting visible. For each delayed item, record what it was waiting for, when that dependency became available and when someone acted on it.
Target the dependency that controls the finish date
Consider a simplified close with three parallel workstreams. Cash reconciliation finishes on day two, intercompany on day five and expense review on day three. Consolidation then takes one additional day, so completion is day six.
Reducing cash reconciliation from two days to one releases effort but leaves the completion date unchanged. Reducing intercompany from five days to three moves the earliest completion to day four, assuming the other dependencies and consolidation duration stay the same.
This is an illustrative scheduling example, not a benchmark or a promised improvement. Real closes have more dependencies and may include resource constraints that change the result.
It demonstrates why a task with large labour savings is not always the task that shortens close. Finance should assess both objectives explicitly: hours released and elapsed days removed from the critical dependency path.
Use AI to prepare the investigation
An intercompany difference may require records from two entities, a currency explanation, a timing check and an owner willing to resolve the discrepancy. AI can be useful in retrieving relevant material and preparing a concise case for review.
Existing products may already assist with parts of this. Microsoft's Finance Agent documents financial reconciliation and discrepancy insights, including preparation of reconciliation reports. Evaluate those capabilities against the datasets and access arrangements you actually have. Microsoft Learn, Finance Agent
The workflow around the analysis still matters. A prepared reconciliation needs a responsible reviewer, a record of unresolved items and a path for obtaining missing evidence. The correct response to insufficient information may be to keep the item open and escalate it.
Do not allow a generated narrative to turn an unexplained difference into an apparently resolved account. Completion criteria should specify the records, reconciliation and approvals required.
Measure the work moved into the month
Moving work earlier can reduce peak pressure without reducing total effort. That can still be valuable, but it should be described accurately.
Suppose 400 exceptions each take 15 minutes to resolve. Total work is 100 hours. Resolving 60% before close leaves 40 hours for the close period and moves 60 hours earlier. No labour saving has occurred unless the time per case also falls or some cases are prevented.
At an assumed £40 an hour, the 60 hours represent £2,400 of capacity shifted away from the peak, not £2,400 of savings. A business may realise value through lower overtime, reduced temporary staffing or a more reliable close timetable; those outcomes need their own evidence.
Measure the number and age of unresolved items before close begins, the active work during close and the final completion milestone. Together these reveal whether the process has become more predictable.
Prove one close dependency first
Select a recurring problem with accessible evidence and a clear owner. Baseline it over representative periods, including the difficult cases. Agree what counts as resolution, how changes will be approved and how the manual process can continue if the automation is unavailable.
The proof should run through a complete relevant cycle. A mid-month demonstration cannot establish how the process behaves under close deadlines, late adjustments or final approval requirements.
Curia's assessment can identify which workflow is worth proving and whether the opportunity lies in matching, evidence gathering, routing or upstream process change. Its managed model then covers the agreed workflow's operation while finance retains accounting judgement and sign-off. The production-readiness guide describes the acceptance evidence to request.
Bring Curia the last close calendar and the items that held it up. We will assess which recurring dependency is worth addressing first. Discuss your close workflow