Month-end variance commentary for management accounts

Nothing here is financial advice, and none of it replaces your own checks.

Use the model to produce a first draft of the variance commentary, not to decide what the numbers mean. You give it a controlled set of monthly inputs, require it to label evidence and assumptions, then review every material statement against the source files. This is for finance managers and management accountants assembling a monthly reporting pack.

Nothing here is financial advice, and none of it replaces your own checks. The final commentary remains a finance work product that you, your reviewer and finance leadership must validate.

1. Build one evidence pack

Create a folder or workspace for the reporting cycle. Use files with clear names, such as Management accounts - April, Budget - April, Latest forecast, March actuals, and Operational notes - April.

Prepare a short reporting brief before you upload or paste anything. Include:

• Reporting entity, business unit and currency.
• Current reporting month and year-to-date period.
• Comparison columns required, for example actual versus budget, actual versus forecast and actual versus prior period.
• Materiality rules, including the monetary threshold, percentage threshold and any items that must always be explained.
• Sign convention, such as whether positive operating profit variance is favourable.
• Known accounting entries, reclassifications, one-off items and changes in allocation method.
• The intended reader, for example finance director, executive committee or board.

Use one approved version of each source. If the forecast changed after management accounts were closed, label it with its issue date and state whether you want commentary against the latest forecast or the forecast available at month end.

2. Extract the numbers before asking for prose

Create a variance schedule with one row per account, cost centre or reporting line you expect to discuss. Keep this structured rather than relying on a formatted pack page.

Include these fields:

Field	What to provide
Reporting line	Revenue, gross margin, payroll, operating profit, working capital or the relevant local line
Actual	Current-month and year-to-date actuals
Comparator	Budget, forecast or prior-period value, clearly named
Variance	Monetary and percentage variance, calculated in your finance file
Driver evidence	Operational metric, ledger detail, named event or management explanation
Status	Confirmed, provisional, estimate or requiring owner confirmation

Calculate the variances in your controlled workbook or reporting system first. Then give the model the resulting schedule. This prevents a polished paragraph being built on an unspotted extraction error.

If you provide documents directly, ask the model to quote the relevant line name, period and source when it identifies a movement. File handling, supported inputs and behaviour can vary, so check the current guidance in the xAI documentation overview.

3. Use a prompt that separates facts from judgement

Paste the reporting brief, variance schedule and operational notes. Then use a fixed instruction like this:

Draft monthly variance commentary for the reporting pack.

Use only the supplied material. Do not calculate or infer figures that are not stated. For each material movement, state the reporting line, actual, comparator, monetary variance, percentage variance and whether the variance is favourable or adverse under the stated sign convention.

Write each item under these labels:
- Evidence: figures and facts directly supported by the supplied sources.
- Explanation: confirmed operational or accounting driver.
- Assumption or open point: anything not confirmed, with the owner or evidence needed.
- Action or decision: what finance leadership needs to confirm, approve or monitor.

Do not treat management commentary as verified fact unless it is supported by a named source. Flag inconsistent figures, missing comparators, unclear periods and unsupported causal claims. Use concise language suitable for a monthly management pack.

Ask for the output in the order your pack uses: headline performance, revenue, gross margin, operating costs, operating profit, cash or working capital, then risks and actions. This makes it easier to transfer into the pack without losing the distinction between evidence and explanation.

4. Review the draft line by line

Treat the first output as a review schedule. Check the material items before you edit for style.

For each paragraph, test four things:

1. Number accuracy: Reconcile actual, comparator, variance and percentage to the approved schedule. Check units, currency, signs and rounding.
2. Period accuracy: Confirm that the sentence does not mix monthly and year-to-date results, or compare actuals with a forecast from another version.
3. Causal support: Confirm that the stated driver appears in an operational note, ledger analysis, accrual support or another supplied source.
4. Decision usefulness: Check that an unresolved item names the person or team who needs to confirm it, plus the date or next reporting step where appropriate.

A useful final paragraph is specific: “Payroll was above budget due to three unbudgeted temporary roles, confirmed in the April headcount report. Finance to confirm whether roles continue into the next forecast.” A weak paragraph says only: “Payroll was adversely impacted by staffing.”

5. Look for signs the output is wrong

Do not be reassured by fluent writing. Variance commentary is wrong when it sounds plausible but changes the comparison, period or certainty level.

If you see this	Treat it as	What to do
A driver not found in your evidence pack	Unsupported inference	Remove it or label it as an assumption requiring confirmation
A percentage that conflicts with the schedule	Calculation or unit error	Recalculate in the controlled workbook and replace the sentence
“Improved” or “declined” without a comparator	Ambiguous conclusion	Add budget, forecast or prior period explicitly
A large movement missing from the draft	Selection failure	Check materiality rules and add the line to the variance schedule
An open issue described as settled	Overstatement	Restore the uncertainty and name the required owner

Also check the totals. The individual explanations may be sound while the sum of stated drivers does not reconcile to the reported variance. If drivers explain only part of the movement, say so. Do not force the remainder into a convenient narrative.

6. Publish a reviewed version and keep the audit trail

Move approved commentary into the management pack only after the finance reviewer has completed the checks. Retain the source schedule, the draft, the reviewed version and a record of material edits. This gives you a repeatable month-end habit and shows where management explanation changed after challenge.

For the next cycle, keep a list of recurring lines and their usual evidence sources, such as volume reports for revenue, headcount reports for payroll and stock reports for margin. Reuse the structure, not the prior month’s conclusions.

When the draft does not work

If the output is generic, provide a tighter variance schedule and require the source reference for each claim. If it misses important lines, restate the materiality rules and list mandatory reporting lines. If it invents explanations, remove broad narrative notes and require unsupported statements to be placed only under Assumption or open point.

If source figures conflict, stop drafting. Reconcile the management accounts, budget version and forecast version with the relevant finance owner before requesting another draft. A better prompt cannot resolve an unresolved close, a mapping error or an unapproved accounting judgement.