Skip to content
Godfrey Financial Advisors LLP

Management report commentary: test the explanation before asking for a decision

The draft October pack for a hypothetical service business says: 'Sales are 20% below budget, but cash is healthy and the shortfall is temporary.' The owner reading it is about to approve discretionary spending. The 20% is accurate. The cash balance includes a final payment from a customer who has left. Nothing on file supports the word temporary. One sentence mixes a measured result, a cash claim resting on a receipt that will not recur and an unconfirmed forecast, and it is about to drive a decision.

Published KPI table showing targets, year-end values and achieved assessments for the agency.
An extract from the 2025/26 public-accounts KPI table covering Crown Commercial Service. A target comparison reports a result; the explanation and decision still need their own evidence. These measures are separate from our hypothetical contract example. Contains public sector information licensed under the Open Government Licence v3.0. Crown copyright 2026, Government Commercial Agency annual report 2025/26. Open Government Licence v3.0.

A principle borrowed from external reporting

The IFRS Foundation published a revised Management Commentary Practice Statement on 23 June 2025. It addresses general purpose reports for investors and asks for a concise, coherent narrative connected to the financial statements, within local law and regulation. An entity does not need to apply it to state compliance with IFRS Accounting Standards.

In ACCA's AB magazine in April 2026, Hilary Eastman, founder of Confluence Advisory, argued that reporting should be specific to the business, fit together across sections, and use financial-statement assumptions consistent with the commentary. That is the author's advice, not an ACCA requirement.

Neither source was written for internal management packs. Applying their idea of connected, evidenced narrative to a monthly pack is our method, and following it does not make the pack IFRS commentary.

Test each clause against the records

The example's invented facts: October revenue is 120,000 against a 150,000 budget, a shortfall of 30,000, and 30,000 / 150,000 = 20%. The budget assumed a 30,000 monthly contract would continue. A signed termination effective 30 September and the October billing schedule show it contributes nothing in October. All other revenue totals 120,000, matching its budget. In October the customer paid its final September invoice of 30,000, a receipt against September's receivable rather than October sales. No further receipts from that customer are expected in November.

ClaimEvidenceStatus
Sales are 20% below budgetFixed versions of the October revenue report and approved budgetSupported: 30,000 of 150,000
Cause of the shortfall (not stated in the draft)Termination notice, October billing schedule, other revenue on budgetSupported; should be stated
Cash is healthyOctober receipts include the 30,000 final September invoiceIncomplete: the receipt will not recur, and cash adequacy also depends on upcoming payments
The shortfall is temporarySales lead expects a replacement contract; nothing signedUnconfirmed

Know what the evidence does not show

A 30,000 revenue gap is not a 30,000 fall in profit, and it does not by itself fix November's cash. Costs, other receipts and payment dates all affect those figures. The example also assumes the revenue accounting is already settled; it does not test recognition under IFRS 15.

For the unconfirmed clause, name the evidence that would strengthen it, such as a signed replacement agreement with a start date. A signed agreement is useful evidence, not proof of every future receipt. For this example, we recommend a base forecast without the uncommitted replacement and a separate scenario using the sales lead's proposed start date. That is a cautious choice for this case, not a rule for every forecast. Either way, the commentary's outlook should use the forecast's assumptions.

The rewrite, with a decision attached

'October revenue was 120,000 against a 150,000 budget. The 30,000 shortfall comes from the contract that ended on 30 September, confirmed by the termination notice and billing schedule. October cash includes that customer's final 30,000 payment for September, and no further receipt from them is expected in November. The sales lead expects a replacement contract. No agreement is signed, so the base forecast excludes it, and a separate scenario uses the proposed start date. At the November review meeting, the finance lead will present the cash forecast from November onward on that base, alongside the scenario, so the owner can decide whether to approve the planned discretionary spend.'

The reported amounts and the cause can be traced to records. The replacement forecast and proposed action are identified as assumptions and next steps. Where space is tight, a compact table with columns for result, evidence, supported inference, uncertainty and decision does the same job.

In the next pack, pick the one sentence whose cause or outlook is driving a decision, and put it through the same test before the pack goes out.

Make the next month clearer.

Discuss the accounting, reporting or finance support your team needs.

Talk to Godfrey