Six Claude prompts a Singapore CFO uses to turn Xero or Quickbooks exports into a CEO-ready board pack — variance commentary, KPIs, narrative included.
CFO work is heavy on structured analysis and narrative writing — exactly what Claude excels at. Variance commentary, board narratives, treasury memos, audit-prep summaries, and investor updates all share the same shape: take structured data, apply business context, write clear English.
Where Claude doesn't help: actually doing the closing entries, performing the consolidation math at scale, or making forward-looking forecasts that depend on judgement about market conditions.
The pattern: CFO does the math (or pulls from accounting system); Claude writes the narrative. CFO reviews, edits, signs off.
1. Variance commentary
*"Below is monthly P&L data for [BUSINESS NAME]. Compute MoM and YoY variance for each line. Write executive variance commentary covering: (a) the three biggest movers (positive and negative), (b) likely drivers based on the context I provide, (c) what to watch next month.
Tone: confident, specific, Singapore commercial English. ~250 words.
Context:
- Business: [SECTOR, SIZE, BUSINESS MODEL]
- Recent events: [LIST]
- Target: [GROWTH RATE, MARGIN TARGETS]
Data: [PASTE]"*
The "context" block lifts this from generic to genuinely useful.
2. KPI dashboard narrative
*"Below are this month's KPIs against last month and against target. For each metric: status (green/amber/red), one-sentence narrative, and one-sentence implication.
Output as a structured dashboard table.
KPIs:
[METRIC, ACTUAL, LAST MONTH, TARGET, OWNER]
..."*
Run monthly. The output goes into the board pack as Section 1.
3. Cash runway memo
*"Below are: current cash, monthly burn (last 6 months), expected receivables (next 90 days), expected payables, and any committed inflows or outflows.
Compute: months of runway at current burn, months of runway under conservative assumptions (no new revenue, all receivables 30 days late). Write a 200-word cash memo for the CEO covering: current position, runway, the three biggest risks to runway, and recommended actions.
Tone: candid, action-oriented.
Data: [PASTE]"*
4. Audit prep summary
*"Below are this year's financial statements draft and last year's audited statements. Identify: (a) accounts with material variance vs. last year, (b) likely audit focus areas given the variance, (c) supporting documentation we should pre-pull for the auditors.
Output as a structured audit-prep checklist.
Statements: [PASTE]"*
Saves the controller 4–6 hours of audit prep at year-end.
5. Investor update
*"Below is this quarter's financial and operational data. Draft a one-page investor update for our [Series X] investors covering: highlights (3 bullets), KPIs (key metrics with brief commentary), challenges (2 bullets, candid), asks (1–2 specific things we want from investors). Singapore commercial English. Tone: confident but honest.
Data: [PASTE]"*
Many CFOs save 3+ hours per quarter on investor letters.
6. Tax-computation review (with caution)
*"Below is our draft tax computation. Identify potential issues: (a) deductions that may be challenged, (b) treatment of items where IRAS guidance is recent or unclear, (c) calculations that look unusual relative to typical SG corporate tax patterns. Output as a review note.
CRITICAL: This is a review aid only. Final review must be done by a qualified tax adviser.
Computation: [PASTE]"*
Useful for catching obvious issues before sending to your tax adviser, not a substitute for the adviser. Reference: IRAS e-Tax Guides.
Putting it together as a tool
For a CFO running this every month, build a board-pack generator as a Claude Code tool:
1. CFO pulls monthly P&L, balance sheet, KPI export to a folder.
2. Tool runs prompts 1–5 in sequence.
3. Outputs a draft board pack (PDF + editable Markdown).
4. CFO edits, finalises, sends.
Total build time as a Functional App Sprint: one week. Time saved per month: 4–8 hours of CFO time.
For more granular workflows, see From Spreadsheet to Board Report: One Claude Prompt, Three Minutes.
Compliance and confidentiality
Three rules.
Enterprise-tier Claude. Financial data is sensitive. Free / consumer Claude tiers may train on input. Switch to Pro / Team / Enterprise.
MAS guidance for fintech CFOs. Document AI use in your governance framework. Reference MAS AI Risk Management Guidelines. Material outputs (anything that informs board decisions or external reporting) need human oversight and audit trail.
Redact where you can. For the variance-commentary prompt, you don't need actual revenue figures — bands or percentages are enough. Reduce the surface area of sensitive data.
For prompt patterns specific to auditors, see Claude for Auditors: Workpaper Review Prompts. For broader prompts across professional services, see The Singapore Prompt Library.
Claude can compute simple variances and ratios reliably. For complex consolidation, multi-entity FX, or anything involving lots of arithmetic, do the math in Excel/your system and feed Claude the computed figures with a request for narrative — not the underlying ledger.
Is it MAS-compliant for fintech CFOs to use Claude?
MAS guidance on AI risk management ([MAS AI Risk Management Guidelines](https://www.mas.gov.sg/news/media-releases/2025/mas-guidelines-for-artificial-intelligence-risk-management)) applies. Use enterprise-tier no-training-on-data, document AI use in your governance framework, and ensure human oversight for material outputs. AI-assisted board pack drafting is consistent with MAS principles when these controls exist.
How does this compare to Datarails or Vena?
Specialised FP&A tools have deep Excel integration and built-in templates. Claude is more flexible and 10× cheaper for SME CFOs, with the trade-off of requiring you to wire up your own data inputs. For Series A–B SaaS or SG SMEs, Claude wins on cost and customisation.
Can Claude write the CEO commentary, or just the variance?
Both, but the CEO commentary is only as good as the context you give it. Without context, it's generic; with context (last quarter's narrative, key business events, target KPIs), it can write partner-level narrative.
Should I show the AI-drafted commentary to the board?
After human review, yes. The CFO is responsible for the content. Use Claude as a writing assistant, not as the author. Most boards don't need to know whether the first draft was AI or analyst.
