Forecast year-end spend

Extrapolates YTD actual spend to project the full-year total and estimate the likely budget gap by cost center.

Finance AnalystCFO๐Ÿ“† MonthlyIntermediateRead-only

Ask it like this

Project our total spend through the end of the financial year

When to use it

Use it from mid-year onwards to estimate total spend for the financial year and the likely gap against your annual budget.

What it produces

Year-end close projection by 2 methods (linear and recent trend), with budget gap if provided and alerts on at-risk centers.

How it works

  1. 1Pulls actual spend since 1 January, by cost centre
  2. 2Projects the annual total by extending the year's average pace
  3. 3Calculates a second projection based on the last three months
  4. 4Spots cost centres where spend is accelerating
  5. 5Asks for your annual budget, which it cannot see, then calculates the likely gap
  6. 6Presents both projections and the cost centres likely to overshoot

What protects you

  • This skill only reads: it changes nothing in Spendesk
  • It acts with your permissions and your role, never beyond
  • The assistant cannot approve or pay
โ–ธTechnical detail73/100 ยท 2 tools
ReportsSpend analysisspendesk_analyze_spendget_cost_centers

# Year-end closing projection (Year-end forecast)

## Purpose
Extrapolate actual YTD spend to project the annual total and identify the likely variance vs budget. Allows leadership to take corrective decisions before the fiscal year closes.

**Limitation:** Spendesk does not store annual budgets โ€” the comparison vs budget must be entered manually or imported from your budgeting tool.

## Instructions

### Step 1 โ€” Retrieve actual YTD spend
```
Call spendesk_analyze_spend with:
  - groupBy: costCenter (or month)
  - Period: from January 1st of the current year to today

For each cost center / month: actual amount spent.
Calculate the YTD total.

Complete months elapsed = number of months between January and the current month.
Remaining months = 12 - complete months elapsed.
```

### Step 2 โ€” Analyze recent trends
```
For a projection more accurate than simple linear extrapolation:

Method 1 โ€” Simple linear extrapolation:
  Projection = YTD / complete_months ร— 12

Method 2 โ€” Weighted average over the last 3 months:
  Recent trend = average_last_3_months ร— remaining_months + YTD
  (gives more weight to recent spend)

Method 3 โ€” Seasonality (if N-1 data available):
  Not applicable without historical Spendesk data (limited to N-1)

Present the first 2 methods and flag the gap between them.
```

### Step 3 โ€” Projection by cost center
```
For each cost center with YTD data:
  Projection method 1 = YTD_CC / complete_months ร— 12
  Projection method 2 = YTD_CC + (average_3months_CC ร— remaining_months)

  Identify centers with strong acceleration (method 2 >> method 1)
  โ†’ signal that recent spend is higher than at the start of the year
```

### Step 4 โ€” Prompt for budget input
```
Ask the user:
  "To calculate the variance vs budget, please provide:
   - Total annual budget: Xโ‚ฌ
   - Budget by cost center (optional): [CC: budget]"

If budget provided:
  Absolute variance = Projection - Budget
  Variance % = Variance / Budget ร— 100
  Status: ๐Ÿ”ด Over budget > 10% | ๐ŸŸก 5-10% | ๐ŸŸข Normal
```

### Step 5 โ€” Projection report
```
Present:
1. Total actual YTD: Xโ‚ฌ (X complete months out of 12)
2. Projection method 1 (linear): Xโ‚ฌ
3. Projection method 2 (recent trend): Xโ‚ฌ
4. If budget provided: Likely variance: Xโ‚ฌ (X%)

5. By cost center:
   CC | Actual YTD | Projection M1 | Projection M2 | Budget (if available) | Variance
   Indicator: โ†—๏ธ acceleration | โžก๏ธ stable | โ†˜๏ธ deceleration

6. Recommended actions for centers likely to overshoot
```

## Points of attention
- Projections are estimates โ€” one-off anomalies (one-off projects) should be excluded
- Consult business leaders to learn about planned spend not yet submitted
- This skill is useful starting from M4 (April) โ€” before that, too little data to project reliably

## Example prompts
- "Our annual budget is โ‚ฌ1.2M: where do we stand, and what is the year-end projection?"
- "Project our total spend through the end of the fiscal year"
- "Here is the budget by cost center: which ones are likely to exceed it by December?"

How to install this skill

/
  1. 1
    Download the file s58-yearend-forecast.md using the button above.
  2. 2
    Place the file in the .claude/ directory of your project (or ~/.claude/ for a global install).
    cp s58-yearend-forecast.md .claude/s58-yearend-forecast.md
  3. 3
    Use in Claude Code โ€” the skill is automatically discovered. Describe your need in natural language and Claude will apply the skill instructions.
๐Ÿ’ก Make sure the Spendesk MCP is configured in your .claude/settings.json with the tools spendesk_analyze_spend, get_cost_centers.

Similar skills

โ˜… Top
95/100ยท๐Ÿ” Ad hocยทExpert

Audit what the MCP covers

Probes all available MCP tools, re-evaluates coverage of 50 persona use cases, detects new fields or tools, and regenerates the gap analysis report.

CFOControllerAP Manager
90/100ยท๐Ÿ“… WeeklyยทBeginner

Card requests via get_requests

Explains how to use get_requests for card requests and why expense reimbursements don't appear there. Avoids a frequent source of confusion between two distinct workflows.

ControllerFinance Analyst
90/100ยท๐Ÿ” Ad hocยทIntermediate

Active vs archived cost centers

Distinguishes active cost centers from archived ones with correct use of get_cost_centers. Avoids the counter-intuitive isArchived vs isActive naming convention pitfall.

ControllerFinance Analyst

Interested in AI Agent services or Custom Integrations?