How to Compare Excel Exports for Month-End Close
Why month-end spreadsheets need explicit comparison
Close packages pass through many hands: controllers adjust accruals, FP&A updates forecasts, and executives request last-minute reclassifications. Each save can shift a material number without an obvious audit trail in email threads. Comparing two exports surfaces row additions, deletions, and cell value changes in one view.
CompareStack Excel compare extracts tabular data and applies line-oriented diffing—ideal when you need a quick answer to “what changed between draft 3 and what we sent to the board?” without installing a desktop diff add-in.
Establish a locked baseline per close
Finance controls improve when every new export is compared to a named baseline: prior month final, last board-approved forecast, or the submission snapshot from T-2 days. Ad hoc comparisons against “whatever was in my inbox yesterday” miss cumulative drift across the close week.
Name files with date, version, and owner (e.g. 2026-05-close-v4-controller.xlsx). Store the approved baseline in your document repository, not only on a local laptop.
Operational steps before you upload
Sort by account code, cost center, or SKU when row order is not meaningful—stable keys make diffs readable. Remove instruction tabs and cover sheets that add noise unless they are in scope for the review.
Agree whether the audit is values-only or includes formulas. CompareStack focuses on displayed values as extracted from the sheet. A formula change that does not alter visible output still requires inspection inside Excel.
Redact employee PII or compensation detail when policy requires before uploading to any cloud tool. Use aggregated exports when possible.
Escalation rules that save time
Define thresholds: any change to revenue recognition lines, new liability rows, or variance beyond X% triggers a second reviewer. Cosmetic formatting-only diffs can be noted separately so leadership focuses on economics.
Attach the diff summary to your close ticket or ERP workflow comment. Approvers should see exact deltas without re-running the comparison themselves.
Three-export close pattern
Draft close, management review, and board export should each be compared back to the locked draft baseline—not only to the previous email. That pattern catches cumulative edits introduced during review week.
Name files with date, version, and owner. Store the baseline in a shared folder with write access limited after lock.
What to escalate on day three
Escalate unexplained revenue or expense line moves, new cost centers, headcount total changes, and any sheet that appears or disappears between management and board packs. Cosmetic renames of tabs can wait; balance sheet surprises cannot.
Attach the CompareStack summary to the close checklist so controllers and auditors see the same evidence.
- Baseline locked after draft close.
- Daily compare during management review.
- Final compare before board distribution.
- Escalation thresholds written before the week starts.
FAQ: month-end Excel compare
Should every tab be compared? Prioritize financial statements and key schedules first; instructional tabs can be excluded if they add noise.
What if the board pack is PDF? Compare the Excel source that generated it, then spot-check the PDF for narrative changes with PDF compare if needed.