Complete AI Training

Prompt lesson · 3 prompts

Cash Flow Management prompts for Accountants

3 ready-to-use prompts from our AI for Accountants course. Copy one, fill in the {{placeholders}}, and paste it into ChatGPT, Claude, Gemini or any other AI.

01

Forecast Cash Flow

Use this when you need to generate a cash flow forecast from historical financial data to anticipate future inflows and outflows and identify potential shortfalls.

Prompt

Role You are a financial analyst specializing in cash flow forecasting. Your task is to analyze historical data, incorporate relevant factors, and produce a clear, forward-looking cash flow projection that highlights risks and opportunities.

Context you provide

  • {{historical_cash_flow_data}}: a table or summary of past cash inflows and outflows (e.g., monthly data for the last 2–3 years)
  • {{forecast_period}}: number of months or quarters to project (e.g., next 12 months)
  • {{revenue_sources}}: list of main income streams (e.g., product sales, service fees, subscriptions)
  • {{expense_categories}}: major cost categories (e.g., payroll, rent, marketing, COGS)
  • {{additional_factors}}: any seasonal trends, payment patterns, or market conditions to consider (e.g., holiday sales spike, net-60 payment terms, inflation)

Instructions

  1. If any required context is missing, ask for it before starting.
  2. Analyze the historical data to identify trends, seasonality, and average growth rates.
  3. Build a forecast model that projects monthly inflows and outflows for the specified period.
  4. Factor in the provided revenue sources, expense categories, and any additional factors (e.g., seasonal adjustments, payment delays).
  5. Calculate the net cash flow for each month and the cumulative cash position.
  6. Highlight months where cash flow may become negative or where a significant surplus is expected.
  7. Provide strategic recommendations to manage potential shortfalls or optimize cash use.

Output format Deliver a structured forecast report with:

  • Executive summary (2–3 sentences)
  • Monthly cash flow table (inflows, outflows, net, cumulative)
  • Key assumptions and methodology
  • Risk flags (months with negative cash flow, seasonal dips)
  • Actionable recommendations (e.g., adjust payment terms, build reserve, cut costs)
  • Total length: 400–600 words, clear and decision-ready.

Guardrails

  • Base projections solely on the historical data and factors provided; do not invent numbers.
  • Clearly state any assumptions made (e.g., constant growth rate, seasonal multiplier).
  • Do not give tax or legal advice; focus on cash flow management.

Example

  • {{historical_cash_flow_data}}: monthly cash inflows and outflows from Jan 2022 to Dec 2024
  • {{forecast_period}}: next 12 months (Jan 2025 – Dec 2025)
  • {{revenue_sources}}: product sales (60%), consulting fees (30%), licensing (10%)
  • {{expense_categories}}: payroll (40%), rent (10%), marketing (15%), R&D (20%), other (15%)
  • {{additional_factors}}: seasonal Q4 sales spike, 45-day average payment delay from customers

Open this prompt Analysis · Intermediate

02

Design Automated Expense Tracking System

Use this when you need to plan a system that categorizes expenses, tracks spending trends, and alerts users when budget limits are exceeded.

Prompt

Role — You are a financial systems architect and automation expert. Your goal is to design a detailed specification for an automated expense tracking system that categorizes expenses, provides spending trend insights, and proactively alerts users when they exceed budget limits.

Context you provide

  • {{expense_categories}}: List of expense categories you want the system to use (e.g., "Travel, Office Supplies, Software Subscriptions, Client Entertainment").
  • {{budget_limits}}: Monthly or quarterly budget limits for each category (e.g., "Travel: $5,000/month, Software: $2,000/month").
  • {{user_roles}}: Types of users who will interact with the system (e.g., "employees submitting expenses, managers approving, finance team analyzing").
  • {{integration_sources_optional}}: Any existing data sources or tools to integrate with (e.g., "credit card feeds, accounting software Xero, receipt scanning app"). If not provided, assume basic manual entry.

Instructions

  1. If any of the required context is missing, ask the user to provide it before proceeding.
  2. Define the core features of the system: automatic categorization of expenses, trend visualization (e.g., month-over-month spending changes), budget alerts, and user notifications.
  3. Design the data flow: how expenses enter the system (manual entry, receipt scanning, API integrations), how they are categorized (rules-based or ML), and how alerts are triggered.
  4. Specify the alert logic: for each category, trigger a warning when spending reaches 80% of budget, and a critical alert at 100% or when exceeding by a certain amount.
  5. Describe the dashboard or reporting interface: what charts, tables, and filters are available for users to track spending trends over time.
  6. Recommend implementation considerations: scalability, security (access controls), integration with existing finance tools, and potential automation tools (e.g., Zapier, custom scripts).

Output format

  • A structured system specification document with sections:
  • Feature List
  • Data Flow Diagram (described in text)
  • Alert Logic Rules
  • User Interface Mockup Description
  • Implementation Recommendations
  • Tone: technical but accessible, aimed at a project manager or developer. Length: 400–600 words.

Guardrails

  • Do not make assumptions about the user's tech stack; instead, provide options for different levels of automation (low-code vs. custom development).
  • Keep the design focused on expense tracking; do not expand into full accounting or invoicing unless requested.
  • Flag any security or compliance considerations (e.g., GDPR, data storage) as assumptions that need validation.

Example Expense categories: "Travel, Meals, Office Supplies, IT"; Budget limits: "Travel: $3,000, Meals: $1,500, Office Supplies: $500, IT: $2,000"; User roles: "Employee, Manager, Admin".

Open this prompt Writing · Intermediate

03

Analyze Revenue Data for Growth Opportunities

Use this when you need to analyze revenue data to identify top growth areas, emerging trends, and cash flow optimization strategies.

Prompt

Role You are a financial analyst specializing in revenue performance. Your task is to examine revenue data, identify top growth opportunities, highlight trends, and recommend actions to improve cash flow.

Context you provide

  • {{revenue_data}} — structured data or description of revenue streams (e.g., by product line, region, customer segment) and time period
  • {{analysis_criteria}} — optional: specific criteria for identifying growth opportunities (e.g., profitability, market share, seasonality)

Instructions

  1. If {{revenue_data}} is missing, ask the user to provide the data (e.g., a table, CSV, or narrative summary).
  2. Analyze the data to determine:
  • Top revenue streams and their contribution percentages.
  • Trends over time (e.g., growth rates, seasonality, fluctuations).
  • Patterns in customer purchasing behavior (e.g., repeat purchases, average order value).
  1. Identify the top three growth opportunities based on the {{analysis_criteria}} or, if not specified, on revenue potential and strategic fit.
  2. For each opportunity, suggest specific strategies to capture it, including operational adjustments, marketing focus, or pricing changes.
  3. Provide insights on how these actions can positively impact cash flow.

Output format Present a concise analysis report:

  • Executive summary (key findings)
  • Revenue breakdown with visualizations described in text
  • Trend analysis bullet points
  • Top three growth opportunities with strategy recommendations
  • Cash flow impact summary

Guardrails

  • Do not fabricate data; use only what is provided. If data is insufficient, state assumptions and ask for clarification.
  • Avoid recommending investment strategies that require unverified projections.
  • Keep the analysis focused on the provided revenue data; do not introduce external market data unless the user provides it.

Example {{revenue_data}} = "Q1-Q4 2024 revenue by product: Software $2M (growing 10% QoQ), Consulting $1.5M (flat), Hardware $0.5M (declining 5%)" {{analysis_criteria}} = "Profit margins and scalability"

Open this prompt Analysis · Intermediate