Consultants · problem and fix
How to find and explain Excel financial model errors on Mac for Microsoft 365
To find Excel financial model errors on a Mac, start with the tools Excel already has. Open Formulas > Formula Auditing, then trace each output back to its inputs. Turn on error checking under Excel > Preferences > Error Checking. Explaining what went wrong takes the most care, and this page shows how to write it down.
The short answer
- Start with Formulas > Formula Auditing in Excel for Microsoft 365 for Mac, then trace precedents for each output.
- Turn on error checking in Excel > Preferences > Error Checking, and read each flag before you dismiss it.
- Hard-coded numbers inside formulas cause many of the problems you will see. Microsoft's guidance says to avoid them.
- Write one short note per error: the cell, what it shows, what it should show, and which outputs change.
- Lazur can point at menu items and explain a formula out loud, but it does not edit your model.
What formula errors in financial models costs you
Hours spent on checks
Time is the cost you can measure best. A 2025 FP&A survey cited by Datarails found that 46% of FP&A time goes to data collection and validation. A model full of hidden errors fills your week with rechecking. Those hours go to proving the numbers, not to explaining what they mean.
Decisions made on wrong numbers
The most expensive case in the research is JPMorgan's. Forbes reports a $6 billion-plus loss at its Chief Investment Office. A Task Force Report quoted in the article says manual inputs to a VaR spreadsheet increased the potential for errors. Forbes does not blame the spreadsheet alone, so read it as a warning about process.
Client trust and rework
A client who finds one wrong total starts doubting the rest of the model. That reaction is common in review work, but I did not find a study that measures it. The rework lands on you: the file comes back, the deck changes, and the meeting moves. Plan for that from the start.
Money you cannot prove yet
I found no primary study that puts a dollar value on formula errors in consulting work, student models or personal budgets. Any figure you hear is unverified. Say so when you quote a risk, and describe the error you actually found.
Why it happens
Hard-coded numbers inside formulas
A typed number inside a formula never changes when the assumption changes. Someone types a rate into a formula to test something, then forgets it. Microsoft's guidance says to avoid hard-coded constants and put values in cells instead.
Manual inputs pasted over formulas
Someone pastes a value over a formula to get past a problem. The cell looks fine until the inputs move. The JPMorgan Task Force Report, as quoted by Forbes, said manual inputs to formulas increased the potential for errors.
Copied formulas with shifting references
A formula copied to a new row or column can point at a neighbor instead of the cell you meant. Without absolute references, a copy can drift. One odd cell in a row of similar formulas is often the copy error.
Calculation set to manual
If calculation is not automatic, the sheet can show results from an older state of the model. Microsoft's guidance says to keep automatic calculation on. Check this before you trust any total you did not watch change.
Many editors and no single review
Models grow over months, and several people touch them. Each person makes a small change and assumes the rest still works. Nobody re-reads the whole sheet after each edit, so errors build up quietly between versions.
Errors are common by default
Panko's 2008 paper summarizes years of spreadsheet research and concludes that errors are common and non-trivial. The paper treats error as the normal state of a spreadsheet, not as a rare accident. Assume your inherited model has errors until your checks say otherwise.
How to fix it
These work with or without any app.
Turn on error checking
Go to Excel > Preferences > Error Checking, and read which rules are switched on. Leave them on while you review. When a cell gets flagged, decide why it is wrong or why it is right, and write that reason down. Do not clear flags in bulk.
Replace hard-coded numbers with input cells
Move each typed assumption into its own labeled input cell, then link the formulas to it. Microsoft's guidance says to avoid hard-coded constants and put values in cells. After the change, one edit updates every output that uses the input.
Trace from output back to input
Start at the number on the summary slide. Choose Formulas > Formula Auditing > Trace Precedents, then repeat the command to go one layer further. Stop when you reach cells with typed values. Trace Dependents works the other way from an input.
Build check cells
For each important total, build a second route to the same number, such as a sum of segments checked against the grand total. Put the difference in a check cell. Any value other than zero points you to a break. Keep the check cells visible to the next reader.
Read the formulas with Show Formulas
Open Formulas > Formula Auditing > Show Formulas, then scan the detail tabs one row at a time. Look for a cell that breaks the pattern of its neighbors. Panko's abstract says cell-by-cell code inspection is the one technique it found demonstrated to be effective.
Step through nested formulas
Use Formulas > Formula Auditing > Evaluate Formula on any formula with several functions nested inside each other. Read each intermediate result. Confirm the command exists in your build first, since Microsoft's Mac availability is unclear.
Confirm calculation is automatic
Microsoft's page gives the Windows path File > Options > Formulas for the calculation settings. On a Mac, the path can differ, so ask Lazur to point at the setting or check Excel's Help for your version. Confirm the setting before you trust a total.
Get a second reader
Ask a colleague to read the changed cells, not the whole model. A second reader catches the errors you stopped seeing because you wrote the formula. Give them the note for each fix so they know what to check.
Use Microsoft's checklist as a guide
Microsoft's How to avoid broken formulas page lists 22 practices. You do not need all of them on day one. Pick the three that match the errors you found in this model, and use the rest on the next one.
What a formula error looks like in a financial model
A formula error is a cell that returns the wrong result. Some errors are loud. You see a divide-by-zero error shown as #DIV/0, a broken reference shown as #REF, or a total that shows zero when it should not. Others are silent. A total includes one row too many, or a growth rate points at last year's input instead of this year's. Silent errors do the most damage, because nothing in the sheet warns you.
You meet this in models you did not build. A client sends a workbook with several tabs, a forecast that moves when you touch one input, and a file name that says final v7. Your job is to decide whether the numbers hold before anyone puts them on a slide. That is a review, not a rebuild, so your first goal is to find what is wrong.
What formula errors cost you and your client
The cost shows up in three places: time, decisions and trust. Time is the easiest to see. Decisions get expensive when the model drives money. Trust is the slowest to repair. The sections below take each one in turn. Where the evidence is thin, I say so.
The money case is easy to misuse, so read it with care. JPMorgan's London Whale episode is the case most often cited for spreadsheet risk in finance. Forbes reports a $6 billion-plus loss, and quotes a Task Force Report about manual inputs in a VaR model. The same article does not put the loss on the spreadsheet alone.
94%
of business decision spreadsheets contain errors, per a 2024 literature review that Datarails cites
Datarails blog: FP&A Automation in Excel46%
of FP&A time goes to data collection and validation, per a 2025 FP&A Trends Survey cited by Datarails
Datarails blog: FP&A Automation in Excel70% to 30%
Share of report preparation time spent on data management and editing at GFKL, before and after moving reporting to SAS
Forbes: Solutions To Spreadsheet Risk Post JPM's London WhaleFor a consultant, the money at risk usually belongs to the client, and the reputational cost lands on you. A wrong number in a board pack can cost you the next meeting. I did not find a study that prices that. Treat any figure you hear about it as a guess until you see its source.
Why formula errors happen in financial models
Research on spreadsheet errors is long-running and consistent. Raymond Panko's 2008 paper summarizes it, and its abstract says: 'Fifteen years of research studies have concluded unanimously that spreadsheet errors are both common and non-trivial.' The abstract gives no single error rate, so do not quote one from memory.
Most errors come from how models get built and changed. A model grows over months. Several people touch it. Each change is small, and nobody re-checks the whole thing after each edit. The result is a sheet that looked right the last time someone read it.
How to find formula errors in Excel on Mac
Start in the Formulas tab. In Excel for Microsoft 365 for Mac, and in Excel 2024 and 2021 for Mac, the Formula Auditing group holds the tools you need. Open Formulas > Formula Auditing and you will see the commands in the table below. Use them in order: outputs first, then inputs, then the formulas in between.
| Tool | Where on Mac | What it helps you see |
|---|---|---|
| Trace Precedents | Formulas > Formula Auditing > Trace Precedents | Arrows to each cell that feeds the active cell |
| Trace Dependents | Formulas > Formula Auditing > Trace Dependents | Arrows to every cell that uses the active cell |
| Show Formulas | Formulas > Formula Auditing > Show Formulas | Every formula on the sheet, instead of results |
| Evaluate Formula | Formulas > Formula Auditing > Evaluate Formula | A nested formula, one step at a time |
| Error checking rules | Excel > Preferences > Error Checking | Which rules Excel uses to flag cells |
Evaluate Formula needs a caveat. Microsoft's pages list Excel 2024 and 2021 for Mac, but a Microsoft Q&A snippet from March 2025 says the feature is not implemented on Mac. I could not settle that from here. Open a nested formula and run Evaluate Formula. If nothing appears, check your build and Microsoft's current docs.
Trace precedents and dependents, step by step
Pick the output cell first, such as the number that feeds your summary slide. Choose Formulas > Formula Auditing > Trace Precedents. Arrows show each cell that directly feeds the active cell. Choose the command again to step back one more layer. Repeat until you reach the input cells, which hold typed values and no formula.
Then go the other way. Select an input cell, such as a growth rate, and choose Formulas > Formula Auditing > Trace Dependents. The arrows show every cell that reacts when that input changes. If a cell you expected is missing from the arrows, the link is broken.
Arrows are fragile. Microsoft says tracer arrows disappear if you change the formula, insert or delete rows or columns, or delete or move cells. Trace first, edit second, and trace again when you finish. Never trust an arrow picture from a version of the file you have since changed.
Read every formula before you trust a total
Show Formulas turns each cell from its result into its formula. Open it from Formulas > Formula Auditing > Show Formulas. Scan one row at a time. A healthy row has the same logic in every column. An odd cell in the middle of a row of formulas is the classic sign of a copy error.
This is slow, and it is the approach the research supports. Panko's abstract says that only one technique, cell-by-cell code inspection, has been demonstrated to be effective in reducing spreadsheet errors. Read the formulas. Do not just read the results.
Use Evaluate Formula on any formula with nested logic, such as an IF inside a lookup. Step through it and read each intermediate result. You will often see the exact step where the value goes wrong, even when the final number looks plausible.
Explain each error in writing
An error you cannot explain is an error you cannot defend. Write a short note for each one. Start with the sheet and cell, and say what it shows. Then say what it should show and why. Last, say which outputs change when you fix it.
Here is a typical pattern. Summary!D12 pulls revenue from a row that already includes a total. The fix is to point the cell at the detail row. Every output that depends on D12 moves once the double count goes, so the note should list those outputs by name. Keep the log in a separate sheet, not in the client's file.
A worked example: a growth input that never reaches the model
Say a forecast grows revenue each year from a single growth input in C5. The first forecast column reads =B5*(1+$C$5). The dollar signs lock the input, so copying across keeps every year linked. Then one column gets its growth rate typed straight into the formula. The row still looks right, so the error hides.
Trace Dependents from C5 shows the arrows. The typed column has no arrow, and that gap is the clue. Show Formulas on that row makes the typed rate obvious. The note writes itself: this column ignores the growth input, and the fix is to link it to $C$5.
Mistakes people make when they audit a model
The first mistake is trusting a result because it looks plausible. A total can look right and still double count. The second is fixing the symptom. Overwriting an output with a typed value hides the error and breaks the next update. The third is clearing error flags in bulk without writing down why.
Other mistakes cost time. Many reviewers audit only the summary tab, but errors usually sit in the detail tabs underneath. Others change the structure while they check. Inserting rows moves arrows and references, so trace again after each edit. Do not stop at formulas either. A correct formula fed a wrong assumption still gives a wrong answer, and you should say so in your note.
Client data and AI tools: check your rules first
Lazur listens and looks at the screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer, and they are not stored. Content is never used to train AI models. Those are the product facts. Your firm's rules still decide what you may share, and the stricter rule wins.
Where Lazur helps, and where it does not
Lazur helps with the reading and the explaining. Hold ⌥ ⌘ and ask about the formula on screen, and Lazur answers out loud. Ask where a command sits and Lazur draws a circle and a label around it. Ask how to do something, and it guides you one click at a time, waiting for each click. You can start with Lazur for Mac.
Lazur does not audit your model for you in a verified way. It does not click buttons, edit files or operate Excel. A spoken answer about a formula can be wrong. Check it with Trace Precedents before you change anything. You make every edit, and you own the number that goes to the client.
What is still unknown
Two Excel questions for Mac are still open. Evaluate Formula is listed for Excel 2024 and 2021 for Mac, but a Microsoft Q&A snippet says it is not implemented on Mac. Spreadsheet Compare is in question too. A 2017 Microsoft Q&A answer says it does not exist in Mac Excel, and that answer is old. Check the current Microsoft docs for your build before you plan around either.
I did not find a primary study that puts a number on money, grades or burnout caused by formula errors in consulting or student work. The figures here cover time, plus one large loss that was not a spreadsheet alone. Quote them with their limits.
Build the habit, not a one-time audit
A single audit finds today's errors. A habit catches the next ones. Keep error checking on, trace one output after each change, and write a short note for each fix. Pair this with the review plan below, then repeat it on the next model you inherit.
Faster with Lazur
Where Lazur helps with formula errors in financial models
Hold ⌥ ⌘ and say what you want. Lazur sees your Excel window. Lazur looks at your screen and answers out loud.
- 1
Hold ⌥⌘ and talk
- 2
Lazur looks at your screen and answers out loud.
- 3
You stay in Excel. Nothing to copy into a chat window.
More things to say in Excel
- “Where is Trace Precedents in this Excel window?”
- “What does this formula do, and why does it return an error?”
- “Walk me through the Error Checking settings.”
- “Dictate the error note for cell D12.”
- “Draft a short email to the model owner listing the errors I found.”
- “Check whether Evaluate Formula is available in my Excel for Mac build.”
Free for 3 days, then $18/month. Download for Mac
You say“What does this formula do, and why does it show zero?”
Lazur · explains what's on screenLazur reads the formula on screen and explains each part out loud. Check the answer with Trace Precedents before you change the cell.
What consultants say to Lazur for this
Each one is a single hold of ⌥ ⌘.
“Where is Trace Precedents in this Excel window?”
Lazur draws a circle and a label around the command so you can find it fast. It does not press the command for you.
Points at it
“What does this formula do, and why does it return an error?”
Lazur answers out loud about the formula in view. Check its reading with Trace Precedents before you change the cell.
Explains what's on screen
“Walk me through the Error Checking settings.”
Lazur guides you one click at a time and waits for each click. You do the clicking, and you can stop at any step.
Walks you through it
“Dictate the error note for cell D12.”
Hold fn and speak. Dictation types clean, formatted text at the cursor in any app, so the note gets written while the cell is still in view.
Types what you say
“Draft a short email to the model owner listing the errors I found.”
Lazur drafts the text. You read it, edit it and send it yourself from Outlook.
Drafts it
“Check whether Evaluate Formula is available in my Excel for Mac build.”
Research runs in Lazur's own Chrome tabs and comes back with a summary and a report. Treat the report as a lead, then confirm it in your own app.
Researches in the background
“Remind me on Friday to re-check the model.”
Lazur adds the reminder to Apple Reminders, so the re-check does not depend on memory.
Handles the small stuff
A plan you can start this week
- Day 1
Set up the checks
Open Excel > Preferences > Error Checking and confirm the rules are switched on. Save a copy of the model under a new name before you touch anything. Note which tabs feed the client's summary page.
- Day 2
Trace the outputs
Pick each summary number, then use Formulas > Formula Auditing > Trace Precedents until you reach input cells. Write each path down with sheet and cell names, so you can find it again on Day 4.
- Day 3
Read the formulas
Use Show Formulas on the detail tabs and scan one row at a time. Flag any cell that breaks the pattern beside it. Do not fix anything yet. Just list what looks wrong.
- Day 4
Add checks and fix
Build a second route for each important total and put the difference in a check cell. Replace hard-coded numbers with input cells. Re-run the checks after every change, not once at the end.
- Day 5
Explain and send
Write a short note for each error with the cell, what it shows and what changes. Draft a summary email to the model owner in Outlook. If speaking is faster, dictate the notes with fn.
Questions people ask
Does Excel for Mac find all formula errors for me?
No. Error checking flags some patterns, but it cannot tell whether your logic matches what the client meant. Read the formulas yourself, and trace each output back to its inputs.
Where is Trace Precedents on a Mac?
Choose Formulas > Formula Auditing > Trace Precedents. The same group holds Trace Dependents, Show Formulas and Evaluate Formula.
Does Evaluate Formula work in Excel for Mac?
Microsoft lists Excel 2024 and 2021 for Mac on its Evaluate Formula pages. A Microsoft Q&A snippet from March 2025 says the feature is not implemented on Mac. Open a nested formula in your build and see what appears, then check Microsoft's current docs.
Can I paste a client model into an AI tool?
Check your employer's rules on client data first. Lazur sends audio and the screenshot to AI providers only to answer, and they are not stored. Your firm's rules decide what you may share, and the stricter rule wins.
Can Lazur fix the formulas in my model?
No. Lazur points at things, explains formulas out loud, guides you one click at a time and drafts text. It does not click buttons, edit files or operate Excel for you.
Why do my tracer arrows disappear?
Microsoft says tracer arrows disappear if you change the formula, insert or delete rows or columns, or delete or move cells. Trace again after each edit.
Is Spreadsheet Compare available on Mac?
A 2017 Microsoft Q&A answer says it does not exist in Mac Excel. That answer may be out of date, so check Microsoft's current documentation for your version before you plan around it.
What is the single most useful habit?
After each change, trace one output back to its inputs. You learn the model's shape, and you catch a broken link while it is still small.
Sources
- Datarails blog: FP&A Automation in Excel · Datarails (vendor) · checked 2026-11-09
- arXiv: Panko, Spreadsheet Errors: What We Know. What We Think We Can Do · arXiv (Raymond R. Panko) · checked 2026-11-09
- Forbes: Solutions To Spreadsheet Risk Post JPM's London Whale · Forbes · checked 2026-11-09
- Microsoft Support: Display the relationships between formulas and cells · Microsoft · checked 2026-11-09
- Microsoft Support: Detect formula errors in Excel · Microsoft · checked 2026-11-09
- Microsoft Support: Evaluate a nested formula one step at a time · Microsoft · checked 2026-11-09
- Microsoft Support: How to avoid broken formulas in Excel · Microsoft · checked 2026-11-09
Fix formula errors in financial models with Lazur, free for 3 days
Hold a key and ask. Lazur sees your screen, points at the button and talks you through it, in any Mac app. No credit card.