How management commentary, MD&A, FSD&A, and professional skepticism affect assurance reporting.
Management communication can help users understand performance, risks, liquidity, and strategy, but it can also mislead if it is selective, inconsistent with the financial statements, or unsupported. The practitioner should read management commentary with professional skepticism and compare it to the evidence.
Management communication and skepticism sit in the Financial Reporting portion of the Assurance route because commentary can affect how users interpret the statements. The issue is whether the communication is neutral, supported, consistent with evidence, and properly separated from required note disclosure.
| Coverage area | Assurance question |
|---|---|
| Commentary content | What performance, liquidity, risk, strategy, KPI, or service-result information is management communicating? |
| Consistency | Does the wording agree with statements, notes, ratios, budgets, minutes, and working papers? |
| Skepticism | Is the wording balanced, supported, and free from selective optimism or omitted negative trends? |
| Disclosure boundary | Does the information belong in required notes, management commentary, or governance communication? |
| Assurance response | Is revision, evidence, disclosure work, governance communication, or report-effect evaluation needed? |
Management communication usually explains the story around the numbers. It should be consistent with the financial statements and should not replace required note disclosure.
| Component | What to evaluate |
|---|---|
| Results of operations | Does the discussion explain major revenue, expense, margin, and variance drivers fairly? |
| Liquidity and capital resources | Does it address cash flow, debt, covenants, financing needs, and restrictions? |
| Risks and uncertainties | Does it identify material business, financial, operational, tax, or compliance risks? |
| Strategy and outlook | Are forward-looking statements balanced and supported by plans or evidence? |
| Key performance indicators | Are non-GAAP or internal measures defined, reconciled, and used consistently? |
| Public-sector service results | Are service outcomes, funding limits, and accountability measures fairly described? |
The practitioner should compare management communication to the financial statements, notes, and working papers.
| Management wording | Consistency concern | Assurance response |
|---|---|---|
| “Liquidity remains strong” while current ratio and cash flow declined. | Commentary may be misleading or incomplete. | Ask management to support the statement or revise wording. |
| “Revenue growth was broad-based” while growth came from one new customer. | Users may misunderstand concentration risk. | Compare to revenue schedules and consider customer concentration disclosure. |
| “No significant uncertainty exists” while going-concern indicators are present. | Commentary conflicts with working paper evidence. | Evaluate disclosure, evidence, and governance communication. |
| “Costs are under control” while unusual expenses were capitalized. | Wording may obscure classification or capitalization issue. | Test treatment and revise commentary if unsupported. |
| “Program targets were met” while service metrics show mixed outcomes. | Public-sector communication may be selective. | Compare to program criteria and explain omitted metrics. |
Professional skepticism is not cynicism. It means management’s wording should be supported by evidence and should not omit important contrary facts.
| Red flag | Why it matters |
|---|---|
| Overly positive language without support | May create bias or mislead users. |
| Omission of known negative trends | Users may not understand financial condition or risk. |
| Selective use of non-GAAP or internal measures | Performance may be presented more favourably than the statements support. |
| Inconsistent explanations across board minutes and public communication | Management may be tailoring the story to users. |
| Forward-looking statements unsupported by budgets or financing plans | Outlook may not be reasonable. |
| Commentary repeats note disclosure but omits required note details | Required financial statement disclosure may still be incomplete. |
Some information belongs in the audited financial statements or notes; other information can sit in management discussion.
| Information | Better location | Reason |
|---|---|---|
| Accounting policy and measurement basis | Financial statement notes. | It is part of the financial reporting framework. |
| Management’s explanation for revenue decline | Management commentary. | It explains performance rather than defining the reported amount. |
| Covenant breach and waiver terms | Notes, with commentary if useful. | Users need formal disclosure and management context. |
| Strategic plan to improve margins | Management commentary. | It is forward-looking and management-owned. |
| Related-party transaction terms | Financial statement notes. | Required disclosure cannot be replaced by commentary. |
| Discussion of service outcomes in a public-sector entity | Management commentary or FSD&A. | It explains accountability beyond the statements. |
Use this order: quote or summarize management’s claim, compare it to evidence, identify inconsistency or bias, state the revision or evidence needed, and explain whether the matter affects notes, report wording, governance communication, or only management commentary.
If the practitioner is helping evaluate commentary, avoid rewriting it as marketing language. The goal is neutral, supported communication that does not impair assurance credibility.
| Pitfall | Correction |
|---|---|
| Treating management commentary as outside assurance concern. | Check consistency with statements, notes, working papers, and other evidence. |
| Accepting optimistic wording without support. | Ask for evidence or recommend neutral revised wording. |
| Confusing commentary with required note disclosure. | Required note content must remain in the financial statements. |
| Ignoring non-GAAP or internal measures. | Define, reconcile, and check consistency before accepting them. |
| Omitting governance implications. | Significant inconsistency or bias may require governance communication. |