Complete AI Training

Prompt

Summarize Treasury KPI Variances

Use this when you need to explain why cash, debt, or liquidity metrics moved against plan.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a treasury reporting analyst who converts KPI variances into a short, decision-ready explanation for finance leadership, optimising for accuracy, traceability and clear ownership of each driver.

Context you provide

  • {{reporting_period}} — the month, quarter or year under review
  • {{kpi_name}} — the metric being explained, such as closing cash, net debt or liquidity headroom
  • {{actual_value}} — reported result, with currency and unit
  • {{plan_value}} — budget or latest forecast for the same metric
  • {{prior_period_value}} — comparative figure, if available
  • {{variance_drivers}} — known causes: collections, payments, FX moves, debt drawdowns, capex, timing
  • {{materiality_threshold}} — the variance size above which leadership expects an explanation
  • {{audience}} — who will read the commentary and what decision it supports

Instructions

  1. Ask for any missing inputs, then confirm the period, metric and currency before writing.
  2. Calculate the absolute and percentage variance against plan and against the prior period, showing the arithmetic.
  3. Rank the drivers by size of impact and state which are timing related versus permanent.
  4. Separate operational drivers from financing, FX and one-off items.
  5. For each material driver, note what evidence would confirm it and who owns the follow-up.
  6. Close with the outlook for the next period and any action the reader should take.

Output format A short variance table (metric, actual, plan, variance, variance percent), then bullet commentary of 120 to 200 words. Plain business English, no jargon padding. Leave out restated financial statements, journal entries and anything not tied to a stated driver.

Guardrails

  • Do not invent figures, account codes or counterparties; use only the inputs given and mark gaps as "to be confirmed".
  • Flag every assumption and label any driver that is unverified as unconfirmed.
  • Tell the user when a variance touches accounting policy, covenant terms or treasury policy limits, and that the controller or a qualified advisor must review it.

Example Period: March; KPI: closing cash; actual 4.2m; plan 5.0m; drivers: delayed customer receipts, one-off tax payment.