5 AI Prompts for Financial Reporting and Variance Analysis

A financial-reporting prompt should not begin with “write an income statement.”

The statement belongs in the accounting and consolidation systems. The prompt's job is to transform approved statement data into a controlled narrative, exception report, or review packet without changing the underlying figures.

The following templates are designed for that boundary. Replace bracketed placeholders with approved data or references from your application. Do not paste confidential financial data into an AI service unless your organization has authorized that provider, account, and use.

Five Copy-and-Paste Financial Reporting Prompts

1. Variance Explanation Prompt

You are assisting with a management-reporting variance review.

Use only the verified values and documented business drivers supplied below.
Do not calculate missing amounts, invent causes, or present an assumption as a fact.

Reporting period: [PERIOD]
Comparison period or budget: [COMPARISON]
Materiality threshold: [THRESHOLD]
Verified variance data: [VARIANCE_DATA]
Documented driver evidence: [DRIVER_EVIDENCE]

For each material variance, return:
1. account or metric name;
2. verified amount and percentage change;
3. documented explanation with its source ID;
4. missing evidence or unresolved questions;
5. review status: ready, needs evidence, or needs finance judgment.

If no supported explanation exists, write "cause not yet documented."

2. Management Reporting Narrative Prompt

Draft a concise management-reporting narrative from the approved figures below.

Audience: [AUDIENCE]
Reporting period: [PERIOD]
Approved statement lines: [STATEMENT_DATA]
Approved commentary: [COMMENTARY_WITH_SOURCE_IDS]
Required terminology: [TERMINOLOGY]

Separate verified results from management commentary. Preserve every amount,
currency, unit, sign, and period exactly as supplied. Cite the source ID for
each numerical or causal statement. List missing information instead of
filling gaps. End with a section titled "Items requiring finance review."

3. Financial Statement Analysis Prompt

Analyze the supplied financial statements for internal review.

Use only the approved dataset and precomputed metrics. Do not provide investment,
tax, or accounting advice. Do not calculate a ratio unless its verified value is
included in the input.

Entity and period: [ENTITY_AND_PERIOD]
Approved statements: [STATEMENT_DATA]
Verified ratios and trends: [METRICS]
Comparison basis: [COMPARISON_BASIS]

Organize the response into profitability, liquidity, cash flow, leverage, and
material changes. For every observation, identify the supporting line or metric.
Distinguish facts, supplied explanations, and open questions. Flag incompatible
periods, missing statements, or unreconciled totals before writing conclusions.

4. Month-End Close Exception Prompt

Summarize the unresolved month-end close exceptions below for the controller.

Close period: [PERIOD]
Exception records: [EXCEPTIONS]
Owners and due dates: [OWNERS]
Approved severity rules: [SEVERITY_RULES]

Return a table containing exception ID, affected account or process, supplied
severity, current owner, due date, evidence status, and required next action.
Do not change severity, assign an owner, or claim resolution unless those values
are present in the source. Place missing or conflicting fields in a separate
"Data issues" section.

5. Audit-Trail Review Prompt

Review this generated financial-report package for traceability gaps.

Package metadata: [PACKAGE_METADATA]
Source references: [SOURCE_REFERENCES]
Calculation records: [CALCULATION_RECORDS]
Prompt and schema version: [VERSION_DATA]
Review and approval history: [REVIEW_HISTORY]

Check whether every reported figure maps to an approved source, every calculated
value identifies its calculation version, and every narrative explanation has a
documented driver or analyst-comment label. Return only verified links, missing
links, conflicting records, and the human review required. Do not certify the
package or infer that an absent record exists elsewhere.

These prompts produce review drafts, not accounting conclusions. In an application, replace free-form pasted blocks with validated variables and enforce the output structure in code.

Define the Reporting Contract

A useful template identifies the reporting entity and period, accounting basis and approved definitions, comparison period or budget version, currency and unit scale, source dataset IDs, finance-supplied review thresholds, required output schema, reviewer, and destination.

The application should confirm these fields before the model sees the data.

Income-Statement Narrative

Supply normalized, verified lines rather than screenshots or copied spreadsheet fragments:

{
  "line_id": "gross-profit",
  "current_amount": 0,
  "comparison_amount": 0,
  "change_amount": 0,
  "change_percent": 0,
  "calculation_status": "verified",
  "source_id": "consolidation-export-id"
}

Ask the model to describe the direction and size of verified changes, use approved terminology, and cite line IDs. Do not let it calculate missing values or infer business causes.

Variance Analysis Needs Evidence

Separate the measured variance from its explanation. A calculation service determines whether a threshold was crossed. The model receives documented drivers from business owners and turns them into a concise draft.

{
  "variance_id": "v-001",
  "threshold_result": "review_required",
  "supplied_drivers": [],
  "unsupported_driver_claims": [],
  "owner": "assigned-finance-role",
  "review_state": "open"
}

When no driver evidence exists, the correct output is “cause not yet documented,” plus an open question. Plausible language is not evidence.

Audit Trail Means More Than a Chat Log

For every generated draft, retain source dataset identity and checksum, extraction and reporting timestamps, prompt and schema version, model settings, calculation version, validation results, user, reviewer, edits, approval state, and final destination.

The organization sets retention and access requirements. A transcript alone may omit the source version, calculations, edits, and authorization that make the result reproducible.

Consolidated and Segment Reports

Use code to verify that the entity set, eliminations, currency conversion, and period match the approved consolidation output. The model may produce separate narrative sections from supplied totals, but it should not combine entities or perform eliminations itself.

When segment definitions change, version the definition and require its ID. This prevents the same prompt from silently comparing unlike structures.

Exception-First Output

{
  "status": "draft",
  "reporting_period": "YYYY-MM",
  "narrative_sections": [],
  "source_references": [],
  "missing_inputs": [],
  "reconciliation_exceptions": [],
  "unsupported_statements": [],
  "finance_review_required": true
}

Downstream code should block publication when source references are missing, calculation status is not verified, or exceptions remain unresolved.

Tie Every Number Back

Narrative generation creates a second representation of financial information, so every amount, percentage, and period in the draft should map back to an input field. A post-generation checker can extract output values and compare them with the approved payload.

Define formatting rules for units, decimals, currency symbols, parentheses, and rounding. If a rounded figure does not reconcile with displayed components, the report should carry an explained rounding state instead of letting the model improvise.

For narrative statements without a number, require either a supplied driver ID or a clear analyst-comment label. This creates a practical review queue: finance can focus on unsupported explanations rather than rereading every verified value.

Handle Corrections Explicitly

When a journal, budget, or mapping changes, create a new dataset and regenerate the affected sections. Do not edit the original input in place. Preserve both report versions and mark the earlier one as superseded so reviewers can understand why the narrative changed.

Keep Accounting Judgment Human

The model should not choose revenue recognition, impairment, reserve, capitalization, consolidation, or disclosure treatment. Those questions depend on facts, policy, professional standards, and accountable judgment.

Finance professionals approve the data, thresholds, explanations, accounting conclusions, and final report. Developers enforce input authorization, calculations, validation, versioning, and publishing permissions.

Read Master Prompts for Finance for the operating model and Automating Financial Documents for document assembly.

Test Before Close Week

Test a clean report, missing line, duplicate line, changed chart of accounts, stale budget version, unexpected currency, late journal, unsupported variance driver, source conflict, and user without entity access.

Also test negative values, zeros, rounding, large values, and narrative length. A structurally valid output can still misstate direction if display rules are ambiguous.

The result should save reviewers from reformatting while making verification easier. It should never make a report look more certain than its evidence.

Browse reporting workflow contracts in the CyWire marketplace.

This article is technical information, not accounting, investment, tax, or legal advice.