What is in this pack
This page is a reference for chatgpt prompts for finance professionals: a set of ready-to-use prompts covering the routine analytical and communication work that finance teams do every week. It is written for team leads and analysts who use AI tools daily, not for developers building integrations.
The pack is organized into six categories: budget commentary, variance analysis, stakeholder reporting, forecasting support, audit and compliance prep, and ad hoc modeling support. Each prompt includes a note on when to use it and what to change first.
One honest caveat before you start: AI is genuinely weak at catching arithmetic errors in complex spreadsheets. Use these prompts for drafting, framing, and explaining financial content, not for verifying calculations. A model will confidently restate a wrong number if you give it one.
For prompts built around other functions, see AI prompts for business teams or browse the full prompts-by-role library.
The prompts, by category
These prompts are grouped by the type of work, not by seniority. A CFO and a senior analyst will find useful material in the same category. Each prompt includes a note on timing and the first variable you should customize.
Budget and forecasting
Variance explanation draft
When to use: After month-end close, when you need to explain actuals vs. budget to a non-finance audience. Change first: [VARIANCE_AMOUNT] and [BUSINESS_REASON].
Variables: [DEPARTMENT], [PERIOD], [BUDGET_AMOUNT], [ACTUAL_AMOUNT], [VARIANCE_AMOUNT], [BUSINESS_REASON]
Write a clear, non-technical explanation of a budget variance for a department update email.
Department: [DEPARTMENT]
Period: [PERIOD]
Budget: [BUDGET_AMOUNT]
Actual: [ACTUAL_AMOUNT]
Variance: [VARIANCE_AMOUNT]
The main reason for the variance is: [BUSINESS_REASON]
Write three short paragraphs. First, state the variance plainly. Second, explain the business reason without jargon. Third, describe what happens next. Keep the tone matter-of-fact, not apologetic.Rolling forecast narrative
When to use: When updating a rolling forecast and you need a written summary for the board pack. Change first: [KEY_ASSUMPTION] to reflect whatever drove the revision.
Variables: [COMPANY_NAME], [FORECAST_PERIOD], [PREVIOUS_FORECAST_REVENUE], [REVISED_FORECAST_REVENUE], [KEY_ASSUMPTION], [RISK_FACTOR]
Write a one-page narrative summary of a revised rolling forecast for inclusion in a board pack.
Company: [COMPANY_NAME]
Period covered: [FORECAST_PERIOD]
Previous forecast revenue: [PREVIOUS_FORECAST_REVENUE]
Revised forecast revenue: [REVISED_FORECAST_REVENUE]
Main assumption change: [KEY_ASSUMPTION]
Key risk to the revised forecast: [RISK_FACTOR]
Structure: opening headline number, explanation of what changed and why, sensitivity to the key risk, and a closing sentence on management's response. Avoid bullet points. Write in plain business English.Scenario comparison table
When to use: Before a capital allocation decision, when leadership needs to see best/base/worst side by side. Change first: [METRIC_LIST] to match whichever KPIs your CFO tracks.
Variables: [DECISION_CONTEXT], [METRIC_LIST], [BASE_CASE_ASSUMPTIONS], [UPSIDE_ASSUMPTIONS], [DOWNSIDE_ASSUMPTIONS]
Create a scenario comparison table for a finance decision.
Decision context: [DECISION_CONTEXT]
Metrics to compare: [METRIC_LIST]
Base case assumptions: [BASE_CASE_ASSUMPTIONS]
Upside assumptions: [UPSIDE_ASSUMPTIONS]
Downside assumptions: [DOWNSIDE_ASSUMPTIONS]
Output a markdown table with four columns: Metric, Downside, Base, Upside. Add a two-sentence interpretation beneath the table. Do not add commentary inside the table cells.[NEEDS REAL OUTPUT]
Annual budget assumptions memo
When to use: At the start of budget season, to align department heads on shared assumptions before they submit numbers. Change first: [MACRO_ASSUMPTION] should reflect your actual planning rate (inflation, FX, headcount growth).
Variables: [FISCAL_YEAR], [MACRO_ASSUMPTION], [HEADCOUNT_ASSUMPTION], [CAPEX_GUIDANCE], [SUBMISSION_DEADLINE]
Draft an internal memo to department heads setting out the finance team's assumptions for the [FISCAL_YEAR] budget cycle.
Macro assumption: [MACRO_ASSUMPTION]
Headcount: [HEADCOUNT_ASSUMPTION]
Capex guidance: [CAPEX_GUIDANCE]
Submission deadline: [SUBMISSION_DEADLINE]
Tone: direct and collegial. Three sections: shared assumptions, what departments own, and the submission process. No more than 350 words.Financial analysis and commentary
P&L commentary for non-finance readers
When to use: When finance needs to present P&L results to a leadership team that does not read spreadsheets closely. Change first: [AUDIENCE] so the model calibrates vocabulary correctly.
Variables: [PERIOD], [REVENUE], [GROSS_MARGIN_PCT], [EBITDA], [NET_INCOME], [NOTABLE_LINE_ITEM], [AUDIENCE]
Write a plain-English P&L commentary for [PERIOD].
Revenue: [REVENUE]
Gross margin: [GROSS_MARGIN_PCT]
EBITDA: [EBITDA]
Net income: [NET_INCOME]
Notable line item to explain: [NOTABLE_LINE_ITEM]
Audience: [AUDIENCE]
Lead with the most important number. Use one analogy if it genuinely helps clarity. Do not use the word "robust." Flag any figure that needs a footnote rather than inventing context.Cost driver analysis summary
When to use: After identifying an unexpected cost increase, before presenting findings to a budget holder. Change first: [COST_CATEGORY] and [PERIOD_OVER_PERIOD_CHANGE].
Variables: [COST_CATEGORY], [PERIOD_OVER_PERIOD_CHANGE], [SUSPECTED_DRIVERS], [DATA_SOURCE]
Summarize a cost driver analysis for an internal finance review.
Cost category: [COST_CATEGORY]
Period-over-period change: [PERIOD_OVER_PERIOD_CHANGE]
Suspected drivers: [SUSPECTED_DRIVERS]
Data source: [DATA_SOURCE]
Write in three sections: what changed, what appears to be driving it, and what further analysis would confirm or refute the hypothesis. Use hedged language where causation is not yet confirmed. Do not state conclusions as facts if they rest on incomplete data.[NEEDS REAL OUTPUT]
KPI dashboard text panel
When to use: When populating the text commentary boxes in a Power BI or Tableau dashboard. Change first: [WORD_LIMIT] to match your dashboard's character constraints.
Variables: [KPI_NAME], [CURRENT_VALUE], [TARGET_VALUE], [PRIOR_PERIOD_VALUE], [WORD_LIMIT]
Write a short dashboard commentary for a single KPI.
KPI: [KPI_NAME]
Current value: [CURRENT_VALUE]
Target: [TARGET_VALUE]
Prior period: [PRIOR_PERIOD_VALUE]
Word limit: [WORD_LIMIT]
One sentence on current status vs. target. One sentence on trend vs. prior period. One sentence on the most likely explanation. Nothing else.Investment case executive summary
When to use: When a project team needs to present a capex or strategic investment to a board or investment committee. Change first: [EXPECTED_RETURN_METRIC] to whichever return measure your committee actually uses (IRR, payback period, NPV).
Variables: [PROJECT_NAME], [INVESTMENT_AMOUNT], [EXPECTED_RETURN_METRIC], [STRATEGIC_RATIONALE], [KEY_RISK], [DECISION_NEEDED_BY]
Write a one-page executive summary for a capital investment proposal.
Project: [PROJECT_NAME]
Investment required: [INVESTMENT_AMOUNT]
Expected return: [EXPECTED_RETURN_METRIC]
Strategic rationale: [STRATEGIC_RATIONALE]
Key risk: [KEY_RISK]
Decision needed by: [DECISION_NEEDED_BY]
Structure: opening recommendation, financial case in two sentences, strategic fit in two sentences, key risk and mitigation, call to action. Formal but not stiff. Do not pad.Cash flow and treasury
Cash flow commentary
When to use: For weekly or monthly cash reporting to the CFO or treasurer. Change first: [SIGNIFICANT_MOVEMENT] to the actual transaction or timing shift that needs explaining.
Variables: [PERIOD], [OPENING_BALANCE], [CLOSING_BALANCE], [SIGNIFICANT_MOVEMENT], [FORECAST_NEXT_PERIOD]
Write a cash flow commentary for [PERIOD].
Opening balance: [OPENING_BALANCE]
Closing balance: [CLOSING_BALANCE]
Most significant movement: [SIGNIFICANT_MOVEMENT]
Forecast for next period: [FORECAST_NEXT_PERIOD]
Four sentences maximum. State the net movement, explain the significant item, flag any variance to forecast, and give the forward view. Do not editorialize.Payment terms negotiation brief
When to use: Before a procurement or finance lead opens a supplier conversation about extending payment terms. Change first: [CURRENT_TERMS] and [TARGET_TERMS].
Variables: [SUPPLIER_NAME], [ANNUAL_SPEND], [CURRENT_TERMS], [TARGET_TERMS], [RELATIONSHIP_CONTEXT]
Draft a brief for a payment terms negotiation with a supplier.
Supplier: [SUPPLIER_NAME]
Annual spend: [ANNUAL_SPEND]
Current terms: [CURRENT_TERMS]
Target terms: [TARGET_TERMS]
Relationship context: [RELATIONSHIP_CONTEXT]
Include: our position and rationale, what we can offer in return, likely objections and responses. Keep it to one page. Do not promise anything that requires sign-off we haven't got.[NEEDS REAL OUTPUT]
Liquidity risk summary
When to use: When preparing a treasury section for a board risk report. Change first: [STRESS_SCENARIO] to whatever scenario your risk policy requires.
Variables: [AS_OF_DATE], [AVAILABLE_LIQUIDITY], [COMMITTED_FACILITIES], [STRESS_SCENARIO], [MINIMUM_LIQUIDITY_THRESHOLD]
Summarize the company's liquidity position for a board risk report.
As of: [AS_OF_DATE]
Available liquidity: [AVAILABLE_LIQUIDITY]
Committed facilities: [COMMITTED_FACILITIES]
Stress scenario: [STRESS_SCENARIO]
Minimum threshold per policy: [MINIMUM_LIQUIDITY_THRESHOLD]
State current headroom plainly. Describe what the stress scenario implies. Note whether the result is within or outside policy limits. Flag if a management action is triggered. Three paragraphs.Reporting and compliance
Audit committee update
When to use: When preparing a written update for the audit committee between formal meetings. Change first: [OPEN_ITEMS] to your actual list from the last committee minutes.
Variables: [REPORTING_PERIOD], [OPEN_ITEMS], [NEW_RISK_FLAGS], [CONTROL_CHANGES], [NEXT_MEETING_DATE]
Draft an update memo to the audit committee.
Period: [REPORTING_PERIOD]
Open items from last meeting: [OPEN_ITEMS]
New risk flags: [NEW_RISK_FLAGS]
Control changes: [CONTROL_CHANGES]
Next meeting: [NEXT_MEETING_DATE]
Format: status table for open items (item, owner, due date, status), then a short narrative section for new matters. Keep the narrative under 200 words. Do not bury bad news in passive language.Internal audit finding summary
When to use: When turning auditor field notes into a formal finding for the management letter. Change first: [SEVERITY_RATING] to align with your own audit methodology.
Variables: [FINDING_TITLE], [CONTROL_AREA], [OBSERVATION], [ROOT_CAUSE], [RISK_IMPLICATION], [RECOMMENDATION], [SEVERITY_RATING], [MANAGEMENT_RESPONSE_PLACEHOLDER]
Write a formal internal audit finding.
Title: [FINDING_TITLE]
Control area: [CONTROL_AREA]
Observation: [OBSERVATION]
Root cause: [ROOT_CAUSE]
Risk: [RISK_IMPLICATION]
Recommendation: [RECOMMENDATION]
Severity: [SEVERITY_RATING]
Standard audit finding structure: Condition, Criteria, Cause, Effect, Recommendation, Management Response (leave as [MANAGEMENT_RESPONSE_PLACEHOLDER] for the business to complete). Formal register, no passive voice where active is possible.Regulatory disclosure draft
When to use: As a first draft only, before legal and compliance review. Not a substitute for qualified review. Change first: [REGULATORY_FRAMEWORK] to the specific regulation or standard (e.g., IFRS 7, SEC Item 303).
Variables: [DISCLOSURE_TOPIC], [REGULATORY_FRAMEWORK], [KEY_FACTS], [MATERIAL_UNCERTAINTY], [REVIEW_DATE]
Draft a regulatory disclosure on [DISCLOSURE_TOPIC] for review by legal and compliance.
Framework: [REGULATORY_FRAMEWORK]
Key facts to include: [KEY_FACTS]
Material uncertainty (if any): [MATERIAL_UNCERTAINTY]
Scheduled review date: [REVIEW_DATE]
Write in the formal register appropriate for a public filing. Flag every sentence that relies on a legal interpretation rather than a stated fact. Mark uncertain figures with [VERIFY]. Do not present this as final.[NEEDS REAL OUTPUT]
Communication and stakeholder management
Finance all-hands talking points
When to use: When the CFO or finance lead is preparing for a company-wide or department all-hands. Change first: [KEY_MESSAGE] to the single most important thing the audience needs to leave with.
Variables: [AUDIENCE_SIZE], [MEETING_CONTEXT], [FINANCIAL_HEADLINE], [KEY_MESSAGE], [SENSITIVE_TOPIC], [Q_AND_A_TOPICS]
Draft talking points for a finance all-hands presentation.
Audience size: [AUDIENCE_SIZE]
Context: [MEETING_CONTEXT]
Financial headline: [FINANCIAL_HEADLINE]
Key message: [KEY_MESSAGE]
Sensitive topic to handle carefully: [SENSITIVE_TOPIC]
Likely Q&A topics: [Q_AND_A_TOPICS]
Three to five talking points, each with a one-line headline and two supporting sentences. Add a section of likely Q&A pairs. Do not oversell the financial position. Do not use the word "exciting."Stakeholder email: explaining a reforecast
When to use: After a material reforecast, when you need to brief business unit leads before the numbers land in their inbox. Change first: [REFORECAST_REASON] to the actual cause, stated honestly.
Variables: [RECIPIENT_ROLE], [ORIGINAL_FORECAST], [REVISED_FORECAST], [REFORECAST_REASON], [IMPACT_ON_RECIPIENT], [ACTION_REQUIRED]
Write an email to [RECIPIENT_ROLE] explaining a reforecast.
Original forecast: [ORIGINAL_FORECAST]
Revised forecast: [REVISED_FORECAST]
Reason: [REFORECAST_REASON]
Impact on recipient's area: [IMPACT_ON_RECIPIENT]
Action required from recipient: [ACTION_REQUIRED]
Short subject line, no more than three paragraphs. State the change up front. Explain why. Say what the recipient needs to do and by when. Do not bury the number in paragraph two.Finance policy one-pager
When to use: When rolling out a new or updated finance policy to a non-finance audience. Change first: [POLICY_NAME] and [KEY_RULE] to match the specific policy.
Variables: [POLICY_NAME], [EFFECTIVE_DATE], [WHO_IT_APPLIES_TO], [KEY_RULE], [WHAT_CHANGES], [WHERE_TO_GET_HELP]
Write a one-page plain-English summary of a finance policy for non-finance staff.
Policy: [POLICY_NAME]
Effective: [EFFECTIVE_DATE]
Applies to: [WHO_IT_APPLIES_TO]
The most important rule: [KEY_RULE]
What changes from current practice: [WHAT_CHANGES]
Where to get help: [WHERE_TO_GET_HELP]
Use short sentences. Avoid accounting terms unless you define them immediately. Add a "What this means for you" section at the end. No more than 350 words.[NEEDS REAL OUTPUT]
Month-end and close
Close checklist review email
When to use: At the start of close week, to align the team on what is outstanding and who owns what. Change first: [OUTSTANDING_ITEMS] to your actual open task list.
Variables: [CLOSE_DATE], [TEAM_MEMBERS], [OUTSTANDING_ITEMS], [BLOCKER], [DEADLINE_FOR_ESCALATION]
Draft an internal email to the finance team at the start of close
## Real example outputs
Five prompts in this pack have been run against real models to show what good output looks like. Those sections are marked [NEEDS REAL OUTPUT] and will be updated once outputs are captured and reviewed by a finance professional.
:::keypoint heading="Worth pausing on"
Model output for financial tasks can look authoritative while containing subtle errors, especially in period-over-period calculations and tax references. Always have a qualified person review figures before they leave the team.
:::
Until those examples are published, the table below shows what each flagged prompt produces and what to watch for in the output.
| Prompt | Expected output type | Common errors to check |
|---|---|---|
| Budget variance narrative | Plain-English paragraph with percentage callouts | Wrong direction on favorable/unfavorable |
| Investor update email | 150-250 word email with metrics inline | Numbers copied without units |
| Cash flow forecast assumptions | Bullet list of named assumptions | Missing seasonality factors |
| Board-ready KPI summary | Short table with trend indicators | Period labels inconsistent |
| Cost-reduction scenario analysis | Numbered options with estimated impact | Percentages not tied to a base figure |
When real outputs are added, each will include a "what to notice" line pointing to a specific choice the model made and whether it held up under review.
## How to adapt these for your team
These prompts are starting points. The fastest way to get consistent output is to replace the generic variables with your own defaults before you share anything with colleagues.
A few changes that make the biggest difference:
- Swap `[company name]` for your actual entity name so every prompt is ready to run.
- Add your reporting currency and fiscal year end. A prompt that assumes a calendar year will produce the wrong period labels for a June-close shop.
- Specify your audience. "Summarize for the CFO" and "summarize for the board" are different tasks, even when the underlying numbers are identical.
One honest caveat: these prompts work well for drafting, structuring, and sense-checking. They do not replace a qualified accountant's judgment on recognition policies, tax treatment, or anything that feeds a signed set of accounts. If a prompt output is going anywhere regulated, review it properly.
:::keypoint heading="Worth pausing on"
Prompts shared across a team drift over time as individuals edit their own copies. Storing a single canonical version in a [shared folder](/product/shared-folders) keeps everyone working from the same baseline.
:::
## Save this folder to your workspace
If your team runs on shared prompts, the fastest way to stop people rewriting the same variance-analysis request every quarter is to save these to a shared folder in Convergence. Everyone pulls from the same version, edits flow in one place, and new hires start with something that already works.
:::cta heading="Want your finance team using the same prompts?"
Convergence [shared folders](/product/shared-folders) let you store, organize, and update prompts across ChatGPT, Claude, Copilot, and Gemini. One folder, every model.
:::
A few practical notes before you set it up:
- Pin the prompts your team uses every close cycle at the top of the folder. Scroll fatigue is real.
- Keep variable brackets in place. Stripping them out feels like a time-save until someone submits a report with [ENTITY NAME] still in it.
- Review the folder once per quarter. Prompts drift out of date when reporting formats or chart of accounts change.
For prompts built around other team roles, the [full prompts-by-role library](/prompts) covers everything from [marketing](/prompts/marketing) to [business operations](/prompts/business).
## Frequently asked questions
### Are these chatgpt prompts for finance professionals compatible with other AI tools?
Yes. Every prompt on this page works in ChatGPT, Claude, Copilot, and Gemini without modification. The formatting conventions, bracket variables, and instruction patterns are model-agnostic by design.
### Can I use these prompts if my team has no AI experience?
You can. Each prompt is written to run as-is, with only the bracketed variables swapped out. No prompt engineering background is needed.
### Will AI produce accurate financial figures?
No, and this matters. AI models can hallucinate numbers, misread formulas, and confuse fiscal periods. Treat every figure in any AI output as a draft that requires human verification before it enters a report or goes to a stakeholder.
### How do I share these prompts with my whole finance team?
[Convergence shared folders](/product/shared-folders) let you store, organize, and push prompts to everyone on the team so the whole group runs the same tested versions.
### What other role-specific prompt packs are available?
Convergence publishes packs for [marketing teams](/prompts/marketing), [business functions](/prompts/business), and a growing [library of role-based prompt collections](/prompts).