Skip to content This library is free, offered as dana. If it helps your work, donate here →
penguin tree ai
← back to libraryDonate here

This is one of 3,622 free prompts in the penguin tree ai library. Sign up once and the whole library opens, with new prompts by email.

open the library →

Financial close cycle time analyzer

Analyzes a company's monthly financial close process to identify bottlenecks, sequencing inefficiencies, and automation opportunities, then benchmarks cycle time against fast-close standards and delivers a phased plan…

download .md

Purpose

Diagnose exactly where a monthly close is losing days — sequencing dependencies, manual reconciliations, late-arriving data, review bottlenecks — and deliver a phased roadmap to compress cycle time toward fast-close benchmarks without sacrificing control integrity.

When to Use

Invoke this skill when the user asks to:

  • Analyze or reduce their financial close cycle time (days-to-close)
  • Identify bottlenecks in a monthly, quarterly, or year-end close
  • Benchmark their close speed against top-performer or industry standards
  • Find automation or continuous-accounting opportunities in the close
  • Build a fast-close or virtual-close improvement plan
  • Diagnose why the close keeps slipping past target

Inputs Required

Before starting, collect:

  • Close task list: The tasks that make up the close, ideally with owners
  • Current sequencing: What happens on which business day (BD+1, BD+2, etc.), or the general order of operations
  • Current cycle time: Days from period-end to books closed / to reporting delivered
  • Target cycle time: Desired days-to-close, if known
  • Pain points: Where the close consistently stalls, slips, or requires rework
  • Systems in use: ERP, sub-ledgers, reconciliation tools, close management software, spreadsheets
  • Company context: Revenue scale, entity/multi-entity count, industry, team size

If target cycle time is missing, benchmark against a 3–5 business day close for the company's scale and note the assumption. If task-level owners are missing, analyze at the process-area level.

Instructions

Step 1: Map the Close Timeline and Establish the Baseline

Reconstruct the close as a business-day timeline.

  • Plot each task or process area against its business day (BD+1 through close).
  • Identify the critical path — the longest dependent chain of tasks that dictates total cycle time. Cycle time cannot drop below the critical path length regardless of other improvements.
  • Flag tasks sitting on the critical path vs. tasks that could run in parallel but currently don't.
  • Establish the baseline: current days-to-close and where the last business day of work lands.

Step 2: Benchmark Against Fast-Close Standards

Position the current close against recognized tiers:

  • Top performer: 1–3 business days (virtual/continuous close, heavy automation)
  • Strong: 4–5 business days (well-sequenced, mostly automated reconciliations)
  • Median: 6–8 business days (functional but manual-heavy)
  • Lagging: 9+ business days (sequential dependencies, spreadsheet-driven, late data)

Assess maturity across five dimensions and rate each Low / Medium / High:

  • Pre-close activity: How much is pulled forward before period-end (continuous accounting, soft close, pre-accruals)
  • Automation: Auto-reconciliations, auto-journal entries, system-to-system feeds vs. manual
  • Standardization: Documented checklists, templates, defined owners, close calendar
  • Parallelization: Tasks running concurrently vs. waiting on upstream completion
  • Control design: Whether controls are embedded/continuous vs. bolt-on at period-end

Step 3: Diagnose Bottlenecks

Classify every material delay into one of four bottleneck types:

  • Data-arrival bottlenecks: Waiting on inputs — bank feeds, sub-ledger cutoffs, intercompany confirmations, expense reports, revenue data, vendor invoices. Fix by pulling cutoffs forward or automating feeds.
  • Manual-effort bottlenecks: High-touch reconciliations, manual journal entries, spreadsheet consolidations, manual roll-forwards. Fix by automating or templatizing.
  • Sequencing bottlenecks: Tasks running serially that could run in parallel; tasks blocked by an artificial dependency. Fix by re-sequencing or decoupling.
  • Review/approval bottlenecks: Journal approvals, management review, sign-off queues that stall because reviewers are batched at the end. Fix by staggering reviews and reviewing by exception.

For each bottleneck, note: where it sits (business day), estimated days/hours lost, and whether it is on the critical path.

Step 4: Identify Automation and Continuous-Accounting Opportunities

Map candidate improvements to concrete techniques:

  • Continuous accounting: Move recurring reconciliations, accruals, and allocations to happen throughout the period rather than at close
  • Reconciliation automation: Auto-match transactions (bank, AR, AP, intercompany); reconcile by exception
  • Journal automation: Recurring/standard journals, template entries, sub-ledger auto-posting
  • Consolidation automation: Replace manual spreadsheet roll-ups with system-driven consolidation for multi-entity
  • Task orchestration: Close management software to enforce sequencing, ownership, status, and dependency tracking
  • Materiality thresholds: Reconcile and review by exception above defined thresholds rather than everything

For each opportunity, estimate: effort (Low/Medium/High), expected days saved, and dependency on system/tooling change.

Step 5: Prioritize Improvements (Ranked by Cycle-Time Impact)

Produce a ranked list of 8–12 improvements. Prioritize by:

  1. Critical-path impact — improvements that shorten the longest dependent chain rank highest
  2. Effort-to-payoff ratio — quick wins that don't require new systems come before multi-quarter tooling projects
  3. Control safety — flag any change that alters a control so it can be re-designed, not removed

Each ranked item: the change, the bottleneck it resolves, estimated days saved, effort level, and whether it's on the critical path.

Step 6: Build a Phased Roadmap and Target State

Structure improvements into three phases:

  • Phase 1 — Quick wins (0–1 close cycle): Re-sequencing, pulling cutoffs forward, staggering reviews, checklist standardization — no new tooling
  • Phase 2 — Automation build (2–4 close cycles): Auto-reconciliations, recurring journals, materiality thresholds, task orchestration
  • Phase 3 — Continuous close (4+ cycles): Continuous accounting, virtual/soft close, embedded controls

State the projected new cycle time after each phase and the target state. Define 3–5 metrics to track improvement (days-to-close, % auto-reconciled, critical-path length, rework/reopened entries, on-time task completion rate).

Output Format

  • Structure: Business-day timeline map, benchmark rating, bottleneck diagnosis, automation opportunities, ranked improvement list, phased roadmap with projected cycle times
  • Length: 1,000–1,400 words
  • Format: Structured document — timeline and bottleneck sections may use tables; improvement list as a ranked numbered list; roadmap organized by phase
  • Sections: Baseline & Timeline → Fast-Close Benchmark → Bottleneck Diagnosis → Automation Opportunities → Ranked Improvements → Phased Roadmap & Target State
  • Tone: Controller-to-controller — analytical, control-conscious, direct. Names specific days saved and specific mechanics, not generic "improve efficiency" advice.

Quality Checklist

Before delivering output, verify:

  • [ ] The critical path is explicitly identified, and improvements are flagged as on-path or off-path
  • [ ] Current cycle time is benchmarked against a specific tier (top performer / strong / median / lagging)
  • [ ] Every material bottleneck is classified into one of the four types with estimated days lost
  • [ ] Automation opportunities cite a specific technique — not just "automate more"
  • [ ] The ranked improvement list is ordered by cycle-time impact, not arbitrary
  • [ ] The roadmap states a projected new cycle time after each phase
  • [ ] Any change that alters a control is flagged for re-design rather than removal

Notes

  • Cycle time can never fall below the critical path — always attack the critical path first; off-path optimizations feel productive but don't move days-to-close.
  • The fastest wins are usually re-sequencing and pulling cutoffs forward — these require no tooling and can land in the next close.
  • Speed without control integrity is a false win; frame every acceleration as "close faster and keep the controls" — a slipped control that triggers a restatement erases every day saved.
  • Continuous accounting is the highest-leverage structural change but the slowest to implement — sequence it after quick wins have already compressed the timeline.

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

  • ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
  • <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

  1. Drag this file into a new chat, or copy and paste its contents
  2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills