Unit4 Financials by Coda
Author: Karen Fleck July 21, 2026 6 min read

Your Most Dangerous Financial Tool Has 16,384 Columns

Business professionals reviewing financial reports and performance metrics during a meeting.

*The tool your finance team trusts most may also be the one creating the most risk. That tension deserves an honest conversation.*

---

There is one piece of software that every finance professional on the planet knows how to use. It is the first tool opened in the morning and the last one closed at night. It runs consolidations, tracks intercompany balances, feeds board reports, and handles everything the core system cannot. Or will not.

Excel is the Swiss Army knife of enterprise finance. It is also, for many large organizations, an invisible load-bearing wall.

Keep reading:

The trust problem you cannot see

Nobody sets out to build critical financial infrastructure in a spreadsheet. It happens gradually. A reporting gap in the core system gets filled with a quick workbook. That workbook gets refined over months. Other people start depending on it. Someone adds a macro. Formulas link to other files. And before anyone realizes it, an entire financial process, sometimes one that feeds regulatory reporting, runs through a file that one person built, one person understands, and nobody has ever formally tested.

This is not an edge case. Spreadsheets remain deeply embedded in enterprise finance operations, with penetration rates that have barely moved in years despite decades of investment in core financial systems.

The problem is not that people use Excel. Excel is brilliant at what it was built for: flexible analysis, modeling, ad-hoc exploration. The problem is that spreadsheets routinely get promoted from analysis tool to system-of-record substitute, and that promotion happens without anyone formally approving it.

Where the risk compounds

For small organizations, spreadsheet dependency is manageable. For large, complex enterprises processing high transaction volumes across multiple entities, currencies, and jurisdictions, the risk profile is different. It compounds.

Version control becomes governance theater. When thirty people edit copies of a consolidation workbook, "final version" is a fiction. Finance teams spend hours reconciling versions that should never have diverged. The real question is not whether the numbers are right. It is which copy of the numbers you are looking at.

Formula errors hide in plain sight. A misplaced cell reference in row 4,000 of a 16,384-column grid can propagate through an entire reporting chain before anyone catches it. Unlike a system with built-in validation rules, a spreadsheet will cheerfully calculate the wrong answer and present it with the same confidence as the right one.

Key-person dependency becomes operational risk. Every organization has at least one person whose departure would create a genuine crisis because they are the only one who understands how a critical spreadsheet works. That is not a staffing risk. It is a process design failure.

Audit trails don't exist. A system logs every change, every user, every timestamp. A spreadsheet does not. When the auditor asks who changed a number and when, the answer is often silence.

None of this means Excel is a bad tool. It means Excel is the wrong tool for certain jobs, specifically the jobs that require the governance, auditability, and structural integrity that only a purpose-built financial system can provide.

Analysis tools vs. system-of-record substitutes

The distinction matters. Excel as an analysis layer, where a finance professional pulls structured data from a governed system and explores it in a workbook, is entirely reasonable. Excel as the place where financial data is created, maintained, reconciled, and reported from is a different proposition.

When a spreadsheet becomes the system of record, it inherits responsibilities it was never built to handle: concurrent user access, referential integrity, automated validation, change tracking, role-based security. These are not features you can bolt onto a workbook. They are architectural properties of financial systems that took decades to engineer.

The irony is that spreadsheets proliferate precisely because they fill gaps. They compensate for what the core financial system cannot do or does too slowly. Finance teams are not choosing Excel over their system. They are choosing Excel because their system is not giving them what they need.

That is worth sitting with. The spreadsheet is often a symptom, not the disease.

What changes when the system catches up

Consider what happens when the financial system actually delivers what finance teams have been building workarounds to achieve.

One enterprise found that a process consuming a week of effort spread across 100 Excel files dropped to 30 minutes after moving to a unified financial platform. That is not an automation story. Nobody automated the spreadsheets. The spreadsheets became unnecessary because the system did what the spreadsheets were compensating for: real-time consolidation, drill-down from summary to source, and a single version of the truth that did not require manual assembly.

When the financial data model is unified and always in balance, self-service analysis shifts from a data integration project to a navigation exercise. Finance professionals drill from P&L to balance sheet to cash flow to source document within the system, without extracting data into a workbook to make it usable.

Month-end close accelerates because the reconciliation steps that consumed days simply do not exist. The numbers are always current. There is nothing to reconcile.

The spreadsheets do not disappear entirely. They shift back to what they are genuinely good at: exploratory analysis, scenario modeling, ad-hoc calculations. They stop being the structural foundation and return to being a flexible tool.

 

Professionals collaborating at a conference table in a modern office, reviewing digital and printed business reports.

Guided purchasing via supplier catalogs and punchouts in the Proactis Marketplace

Watch now

A practical path forward

None of this argues for banning spreadsheets. That has been tried. It does not work. What works is addressing the gap that spreadsheets are filling. Build a financial data foundation strong enough that your team no longer needs to compensate for its limitations.

The goal is not fewer spreadsheets. The goal is fewer spreadsheets doing jobs they were never meant to do.

Start by mapping your most critical spreadsheet-dependent processes. Ask which of them exist because the core system cannot handle what your team needs. Then ask whether a specialist financial management platform, one built for the complexity, volume, and auditability that large enterprises demand, could close that gap.

Unit4 Financials by Coda was built for exactly this: large, data-centric enterprises where transaction volumes are high and the cost of getting it wrong is material. If your finance team is spending more time managing spreadsheets than analyzing what is in them, that is a conversation worth having. Learn more.

Sign up to see more like this

Recommended blogs

July 14, 2026 6 min read

The 10-Day Close Is a System Problem, Not a People Problem

Read more
Two professionals sit at a desk in a modern office, reviewing financial or operational data displayed on a computer monitor.

July 7, 2026 6 min read

The CFO's Time Problem: Strategic Ambition, Transactional Reality

Read more
Person presenting workforce analytics and performance dashboards on a large screen during a business meeting, while colleagues review data and reports around a conference table.

June 30, 2026 6 min read

The Reconciliation Tax: What It Really Costs When Your Numbers Don't Agree

Read more
Diverse team collaborating in a modern office around a laptop, reviewing documents and financial data together, with notebooks, coffee and a bright windowed workspace in the background.

Popular blogs

Subscribe to our blog

Don't miss the latest Unit4 blogs

Sign up for industry insights & exclusive content