A plausible workbook can still be wrong
Spreadsheet AI creates a specific review trap: the output looks native. A generated formula sits in a normal cell, a chart carries the expected colors, and the explanation uses finance language. That visual fit can hide a stale range, the wrong sign, a hardcoded assumption, or a source version that never reconciled.
Recent practitioner discussions show the gap between demos and routine work. An r/Accounting commenter described spending an hour correcting figures exported by an AI file processor and concluded that manual entry might have been faster. In r/FPandA, reviewers warned that AI often proposes formulas that are more complicated than the task requires. Another recent thread described formula auditing as a useful narrow application while questioning the business case for expensive general automation.
Microsoft's own guidance draws the necessary boundary. Copilot can use Python-backed analysis, expose generated code, add formula columns and rows, and show referenced source data in some analysis experiences. Microsoft also tells users to review, edit, and verify AI-generated content. Its current COPILOT function reference says the function is best for semantic, generative, and exploratory tasks where deterministic accuracy is not required. That sentence should be written into every finance rollout plan.
The practical position is not anti-AI. AI is valuable when it reduces the time needed to understand a workbook: inventory tabs, group formula patterns, explain a legacy model, compare a copied formula to its neighbors, document lineage, and draft tests. It becomes dangerous when a fluent explanation replaces calculation evidence or when an agent edits the same workbook it later declares correct.
Core rule: Use AI to find where a reviewer should look. Use deterministic tools and controlled source data to prove the number.
Give AI an inspection role before an editing role
Start with read-only mapping. Ask the assistant to list sheets, named ranges, external connections, queries, macros, formulas, constants, error-handling patterns, hidden rows or sheets, protection settings, and material outputs. The first deliverable is not a cleaner workbook. It is an inventory of what exists and what remains unknown.
Next, let the tool explain formula families and anomalies. A workbook with 20,000 formula cells may contain only 40 repeated patterns. Grouping those patterns makes review tractable. The unique formulas, breaks in a copied range, hardcoded overrides, and inconsistent references deserve attention first.
Only after the map is reviewed should AI propose edits. Apply changes to a copy, preserve a cell-level diff, and keep formulas visible. Do not let an agent silently replace formulas with values or remove error signals to make the workbook appear clean. Any modified external connection, macro, query, named range, hidden state, calculation setting, or protection rule should enter an elevated review lane.
| AI task | Reasonable use | Required human or deterministic check |
|---|
| Explain a formula | Translate logic and identify referenced cells | Inspect the actual formula and referenced values |
| Find inconsistencies | Compare formula patterns across rows and periods | Confirm whether the difference is an error or intentional exception |
| Generate a formula | Draft a transparent starting point | Recalculate test cases, copy behavior, edge cases, and control totals |
| Summarize a model | Map inputs, calculations, outputs, and assumptions | Owner validates purpose and lineage |
| Produce final numbers | Not as sole evidence | Controlled formula, SQL, Python, or source-system re-performance |
| Approve a workbook | Never | Named qualified reviewer signs the exact version and audience |
Run the review in six evidence-producing passes
1. Freeze the workbook and its sources
Record the filename, reporting period, entity, currency, timestamp, version, hash, calculation mode, and owner. Inventory external links, data connections, Power Query, macros, add-ins, hidden sheets, named ranges, protected ranges, and source extracts. A later approval is meaningless if the reviewed workbook cannot be reproduced.
Keep the original read-only. Create a review copy and an AI-edited candidate copy. If the platform changes the workbook in place, export or duplicate the baseline before the session. Record which model or product made changes and preserve the prompt or instruction that materially shaped them.
2. Map material outputs backward
Start with the cells that drive a report, close, forecast, covenant, board chart, journal entry, pricing decision, headcount plan, or cash action. Trace each output back through intermediate tabs to source cells and assumptions. Record units, signs, period, entity, scenario, and owner. This lineage map matters more than a complete commentary on every decorative cell.
3. Review the change set
Compare pre-AI and post-AI versions. Review formulas, values, names, links, queries, macros, protection settings, hidden state, and formats that convey accounting meaning. A formula that did not change can still produce a different result if an input, link, named range, or calculation mode changed.
4. Re-perform material calculations
Use an independent method. If AI generated the Excel formula, reproduce the material result with controlled Python, SQL, a separate workbook, or the source system. If AI generated Python, recalculate a sample with known spreadsheet formulas and control totals. Independence is about method and evidence, not merely using a second model.
# Illustrative independent tie-out
source_total = ledger.groupby("cost_center")["amount"].sum()
workbook_total = reviewed_export.set_index("cost_center")["actual"]
variance = workbook_total.sub(source_total, fill_value=0)
exceptions = variance[variance.abs() > tolerance]
assert exceptions.empty, exceptions.to_dict()
The script is not proof by itself. Preserve the source extract, code version, tolerance, output, and reviewer. Tie the result to approved control totals and investigate every unexplained difference.
5. Stress the workbook
Add a row, extend a period, use zero, blank, negative, duplicate, and error inputs, refresh a source, and copy the formula. Check whether ranges expand, absolute references stay fixed, errors remain visible, and outputs update. A formula can be correct for today's shape and fail the first time the workbook changes.
6. Resolve exceptions and bind approval
Each issue needs a cell or range, description, impact, materiality, evidence, owner, due date, status, and blocking decision. The final reviewer signs the exact workbook version, source set, purpose, audience, and conditions. A material edit after sign-off invalidates the decision.
Prefer boring formulas that survive review
WorkstreamBench evaluates end-to-end finance spreadsheet tasks rather than only question answering or single-cell edits. Its quality examples illustrate basic controls that remain easy to miss: absolute references for fixed assumptions, visible error handling, labeled assumptions instead of repeated hardcoded values, dynamic ranges, and readable workbook structure. These are not cosmetic standards. They determine whether a model remains correct when copied, refreshed, or handed to another analyst.
| Risk pattern | Example | Review test |
|---|
| Relative reference to fixed assumption | =B5*B1 copied down | Should the assumption be $B$1? Copy through the full range. |
| Hardcoded constant | =Revenue*0.03 | Move the rate to a labeled assumption cell with owner and period. |
| Stale fixed range | =SUM(D5:D40) | Add a row and verify the total includes it; prefer a table or governed dynamic range. |
| Blanket error suppression | =IFERROR(complex_formula,0) | Test the error path; determine whether zero hides a broken source or invalid denominator. |
| Overcomplicated lookup | Nested INDEX/MATCH for a direct same-row value | Ask whether a simple reference is correct and more auditable. |
| Entire-column calculation | SUMPRODUCT(A:A,B:B) | Check performance, mixed data types, headers, and unintended future rows. |
| Silent formula-to-value replacement | Copied output no longer recalculates | Compare cell types and formula inventory before and after AI edits. |
| Cross-version link drift | Forecast v4 pulls assumptions from v3 | Inventory external links and reconcile source versions. |
A complex formula is not more professional because it uses more functions. Complexity must buy a needed property: better error behavior, performance, maintainability, or an accurate business rule. If two formulas produce the same result, prefer the one a second reviewer can understand and test.
Create a cell-level evidence record
Research systems point toward the same design. Pista decomposes spreadsheet-agent work into visible actions so users can intervene. AUDITFLOW separates adaptive search from deterministic verification because financial correctness depends on structured evidence and recomputation, not plausible text. A professional workflow can use those principles without adopting either research system.
EXC-017
Workbook: Forecast_Q4_v12.xlsx
Version hash: sha256:92a...
Output: Summary!H22 - gross margin forecast
Changed by AI: Yes
Formula before: =IFERROR(H8/H5,0)
Formula after: =IFERROR((H8+H9)/H5,0)
Claimed reason: Include service revenue
Evidence: Service revenue is already included in H8 via Detail!H410
Independent result: Original formula ties to source within 0.01%
Risk: Double count service revenue; board forecast overstated
Status: BLOCKED
Owner: FP&A model owner
Required action: Restore formula, recalculate, refresh charts, rerun tie-out
Reviewer decision: [blank]
The record separates the assistant's explanation from the review conclusion. It also makes correction efficient. The reviewer can reproduce the issue, identify downstream cells, fix the smallest boundary, and confirm that the released workbook no longer contains the error.
Microsoft's current validation guidance uses four checks: Source, Verified, Context, and Resilient. For a workbook, that translates into identifiable source cells, independently checked calculations, correct business definitions, and logic that survives refreshes and edge cases. Polishing a chart or explanation does not satisfy any of those tests.
Failure modes the workflow must catch
| Failure | Why it looks plausible | Blocking control |
|---|
| Wrong source version | The numbers are real, but from another refresh | Source register, timestamps, hashes, and control totals |
| Formula copied inconsistently | Most rows are correct | Pattern grouping and unique-formula review |
| Hardcoded assumption | The result matches the current period | Labeled assumptions with owner, period, and sensitivity test |
| Stale range | The workbook worked before a new row arrived | Dynamic-range test and added-row regression case |
| Hidden error | IFERROR replaces failure with zero or blank | Test underlying expression and prohibit unexplained suppression |
| AI explanation disagrees with formula | The narrative describes the intended logic | Inspect and re-perform actual formula logic |
| External connection changes | Visible cells remain unchanged | Connection, query, link, and refresh-setting diff |
| Approval applies to later version | Filename stays the same | Hash-bound sign-off invalidated by material changes |
Adopt the workflow without slowing every workbook
Select one recurring modelChoose a meaningful internal workbook with known control totals and prior versions.
Define material outputsName the cells, charts, reports, and decisions that receive the strongest review.
Create the version recordCapture baseline, AI candidate, source snapshot, hash, owner, and audience.
Run AI read-only firstMap tabs, formulas, links, queries, macros, hidden state, and unknowns before edits.
Build an independent tie-outUse controlled spreadsheet formulas, SQL, Python, or source-system totals.
Seed defectsTest a stale range, wrong sign, hardcoded rate, hidden error, changed link, and double count.
Set blocking rulesStop on unexplained material differences, unknown sources, unreviewed code, or version ambiguity.
Name the approverFinance or accounting owns the exact workbook, purpose, audience, and conditions.
Measure correctionsTrack exceptions found before use, review time, post-release fixes, and recurring formula debt.
Risk-tier the process. A low-impact personal analysis may need a source check, formula spot-check, and clear draft label. A board, audit, covenant, tax, liquidity, close, or external reporting workbook needs full lineage, independent recalculation, specialist review, and exact-version sign-off. The workflow pack provides the full lane; teams can define documented minimums for lower-risk use.
FAQ
Can AI audit an Excel workbook?
It can accelerate mapping, formula explanation, pattern comparison, and exception discovery. It cannot provide independent assurance when it generated the same logic under review. Material outputs still require deterministic re-performance and qualified human judgment.
Is a second AI model an independent check?
Usually not. Two models can share the same missing context, source error, or reasoning pattern. Independence comes from controlled source data, a different calculation method, explicit expected results, and a reviewer accountable for the decision.
Should finance use the COPILOT function for calculations?
Microsoft describes it as suited to semantic, generative, and exploratory tasks where deterministic accuracy is not required. Use standard formulas or controlled code for material calculations and reserve AI functions for bounded text classification, explanation, or exploration that is visibly reviewed.
What is the minimum evidence for a low-risk workbook?
Keep the exact version, source list, material formulas, control totals, changed-cell review, exceptions, and named reviewer. Higher-impact work requires fuller lineage, specialist review, and stronger release controls.
Does this replace internal controls or audit procedures?
No. Map it into the organization's existing close, reporting, model governance, access, change management, internal control, disclosure, audit, and retention requirements.