Let AI draft the management narrative; make finance prove every sentence

AI commentary now sees more of the report than many reviewers expect

Microsoft's August 2026 Power BI update allows Copilot Summary and the Copilot Narrative visual to read visuals hidden by default and revealed through display-only bookmarks. Row-level and object-level security remain enforced, but visibility is no longer limited to what a reviewer happens to see on the current canvas. A hidden scenario chart can now influence a generated executive summary.

That is useful and risky. It lets one report support compact navigation while preserving a richer summary surface. It also means Finance must document which pages, visuals, bookmarks, slicers, filters, and security role produced the narrative. “I reviewed the page” is not enough when the generator can rank relevant visuals across the report and cite content outside the current view.

Microsoft's current documentation exposes the practical limits. Copilot identifies relevant visuals and summarizes up to 20. Large tables can be paginated, long text can be truncated, dense visuals may be sampled, unsupported filters may not behave as expected, and only display-only bookmarks with a user-facing button or navigator are included. Clear labels and a well-structured semantic model improve output, but they do not certify financial meaning.

Oracle EPM shows the same shift from charts to narrative operations. Its current feature catalog includes grounded questions over report grids, notes summarization, and management-report narratives that describe, compare, and propose causality for exceptions. The tools differ, but the control problem is identical: descriptive text can be generated faster than Finance can verify its basis.

It helps to separate three products that are often collapsed into “AI commentary.” A smart narrative can generate dynamic text from visible report structure. A Copilot narrative uses a generative model and a prompt to synthesize selected report content. A report-grounded conversational agent answers questions against a current grid and point of view. None of those functions owns the data model, decides materiality, resolves an accounting policy question, or knows whether management has approved the explanation.

The product boundary should therefore appear in the review packet. Record what feature generated the text, what content it could inspect, whether the text is dynamic or manually edited, what permissions applied, which limitations were active, and where the output was copied. A narrative pinned inside a report can refresh with the data; a sentence pasted into a slide becomes static. The same words now have different update and control behavior.

Build a sentence-to-evidence contract

Reviewing a paragraph as a whole hides different burdens of proof. “Revenue was $12.4 million” is a fact claim. “Revenue grew 8%” adds a comparison. “Growth came from price” is a causal claim. “We expect momentum to continue” is a forecast. “Management should accelerate hiring” is a recommendation. Each needs different evidence and a different owner.

Assign stable sentence IDs before review. The evidence matrix should preserve the original text, classification, visual or source citation, formula, period, filters, reviewer result, proposed correction, and disposition. If the prose changes, the sentence ID remains traceable and the narrative hash changes.

Freeze the report state before judging the prose

A narrative generated from a report is a function of state: source refresh, semantic-model version, metric definitions, security role, filters, slicers, drill state, page selection, bookmarks, visual visibility, and the generator's selection behavior. Save that state before starting review. Otherwise the team can approve text against one view and distribute it with another.

Do not assume the visible page is the AI's full scope. Enumerate display-only bookmarks, hidden pages that become reachable, tooltips, visual fields that are not displayed, and default expansions. Test the same prompt under representative security roles. RLS and OLS may remain enforced while two authorized roles still receive materially different summaries.

Reperform numbers before editing language

Finance reviewers often begin by polishing tone. Reverse the order. First recalculate every material number and comparison outside the generated narrative. Then reconcile the statement to the approved source and metric contract. Only after the evidence passes should anyone optimize clarity.

sentence_id: N-07
text: "Gross margin improved 180 bps as freight costs normalized."
classification: [calculation, comparison, cause]
state: {period: "Q3", scenario: "actual", currency: "USD", entity: "group"}
tests:
  margin_recalc: PASS
  prior_period_basis: PASS
  bridge_to_180bps: PASS
  freight_driver_evidence: FAIL
disposition: "Rewrite as hypothesis or obtain logistics evidence"
release_blocking: true

This record makes a common failure visible: the calculation can be correct while the explanation is unsupported. The approved rewrite might say, “Gross margin improved 180 basis points. The current bridge attributes 110 basis points to product mix and leaves 70 basis points under review; freight normalization is a working hypothesis.” Less polished, more useful.

Worked example: actual-versus-plan revenue commentary

Suppose an AI draft says: “Revenue exceeded plan by $2.1 million because enterprise demand accelerated, supporting a higher full-year outlook.” One sentence contains a fact, a variance calculation, a cause, and a forecast decision. Break it apart.

1. Verify the fact: actual revenue and approved plan share the same entity, currency, period, consolidation basis, and revenue definition.
2. Recalculate the variance: independently compute actual minus plan and confirm $2.1 million is within the approved rounding rule.
3. Build the bridge: price +$0.6 million, volume +$0.9 million, mix +$0.2 million, FX +$0.7 million, timing -$0.3 million. The bridge ties to $2.1 million.
4. Test the cause: enterprise bookings and delivered volume support part of the volume change, but the bridge also contains FX and timing. “Because enterprise demand accelerated” overclaims.
5. Test the outlook: a favorable month does not authorize a forecast increase. The forecast owner must approve revised assumptions and downside sensitivity.

A reviewable release reads: “Revenue was $2.1 million above plan, comprising $0.7 million of favorable FX, $0.9 million of higher volume, $0.6 million of price and $0.2 million of mix, partly offset by $0.3 million of timing. Enterprise deliveries contributed to volume; the full-year outlook remains unchanged pending the scheduled reforecast.” Every clause now has an evidence path.

Causal language needs the strongest gate

Oracle's product language explicitly distinguishes description, comparison, and causality. Finance should mirror that hierarchy. Description states what changed. Comparison establishes a basis. Causality claims a driver changed the outcome. Moving from one level to the next requires new evidence, not stronger prose.

Use a variance bridge when components are additive and controlled. Use operational metrics when the mechanism is measurable. Ask an accountable business owner to confirm one-off events, but treat opinion as opinion. Look for alternative explanations and lag effects. Residuals are not a license for narrative invention. If the bridge does not reconcile, stop.

Community skepticism is useful here. In a recent r/excel discussion, the most-supported objection to a generated spreadsheet function asked why a nondeterministic output should sit inside a spreadsheet. The same principle applies to management commentary: use generation for draft language and challenge questions, but keep control numbers, bridges, and acceptance tests deterministic.

Approve the exact text, not the idea of the report

Management narratives are copied into emails, slides, board packs, planning systems, and meeting notes. A dashboard approval does not automatically travel with each copy. Create a release manifest that binds the approved text to the report and evidence state from which it was derived.

If a scheduled refresh changes a cited value, if a bookmark adds a visual, or if an editor changes a material sentence, invalidate the manifest and rerun the relevant checks. Version control for prose is now part of financial reporting control.

Failure modes to test before leadership sees the summary

Run a 30-day pilot on one recurring report

Choose one monthly management report with stable owners, known source totals, a small number of material KPIs, and a real review meeting. Preserve the current manual commentary as a baseline. Generate a shadow narrative, but do not distribute it during the first cycle.

Measure accepted sentences, numeric exceptions, unsupported causes, missed material visuals, reviewer minutes, rework minutes, refresh invalidations, disagreement, and post-release corrections. Time saved before review is not the target. Net time to an accepted, evidence-backed narrative is.

In the second cycle, release only sentences that pass the matrix and exact-text gate. In the third, expand scope only if error rates fall, exception ownership works, and reviewers can reperform the evidence. Stop if the tool repeatedly changes material meaning, hides limitations, or produces a review burden larger than the drafting benefit.

This guide complements the Finance dashboard release workflow, the variance-analysis skill, and the report release gate. Those pages govern the artifact, calculations, and distribution. This page governs what the narrative claims.

Frequently asked questions

Can we publish a Copilot summary directly from Power BI?

Treat it as a draft. Microsoft provides citations and enforces report permissions, but Finance still must verify scope, metric meaning, calculations, comparison basis, causality, materiality, and exact text.

Do hidden visuals create a data-access problem?

Not necessarily: Microsoft says RLS and OLS remain enforced. They do create a review-scope problem because hidden-but-reachable visuals may influence the summary. Record and test that scope.

Should every sentence receive the same review?

No. Route by claim class and materiality. A low-risk descriptive sentence may need source confirmation; a causal claim, forecast, accounting conclusion, or public statement needs stronger evidence and more qualified owners.

Can AI rewrite an unsupported cause to sound safer?

Only after the unsupported claim is preserved in the exception record. The correction should state what is proven, what remains a hypothesis, who owns follow-up, and whether the gap blocks release.

What changes invalidate approval?

A material change to source data, refresh, semantic model, metric definition, security role, filter, bookmark, cited visual, exception, or narrative text should trigger re-review under the release policy.