The Excel Paradox: Your Finance Team Lives in Spreadsheets but Starves for Data

A county finance director needs the variance between the GL encumbrance and the PO obligation for the Main Street sewer project explained before the board meeting on Thursday.

A town controller needs to find a mislabelled ARPA expenditure that is holding up the entire closeout process.

A city public works director needs to piece together available overtime budget for street crews ahead of a major storm forecast.

The answers to these questions exist. They are stored inside the ERP, spread across the general ledger, projects module, accounts payable system, payroll records, and grant data.

But getting those answers out in a format that is actually useful remains a challenge.

Some reports can answer these questions if an analyst is given enough notice to work their Excel magic. Other questions require entirely new reports from IT, resulting in requirements gathering sessions, multiple revisions, and weeks of back-and-forth communication before the final report arrives—often long after it would have been useful.

There is a paradox at the center of local government finance. On one hand, Excel is the universal tool of financial analysis: reliable, flexible, and capable of almost anything. On the other hand, the amount of Excel work happening inside an organization is often inversely related to that organization's ability to access data-driven answers. Said concisely: more Excel work means fewer data driven answers.

The Excel Paradox feels counterintuitive because Excel is such a good tool for data analysis. It wouldn’t be as ubiquitous as it is, were that not the case. But the problem is not with Excel itself. The problem is what’s happening before the data arrives in an analyst’s spreadsheet. 

Waiting on manual data extracts. Hand keying workarounds for data quality issues. Adjudicating the correct data from among multiple versions. Integrating data from siloed systems and offline spreadsheets. All of this administrative and operational friction acts as a speed limiter on Excel’s ability to produce data driven answers. 

Often finance teams suffering from these upstream data issues are fully aware of what’s going on. So they tackle them with their trusty battleaxe: Excel. They build out libraries of VLOOKUP/XLOOKUP tables. They write Excel macros that some can use, but everyone can break. They hoard gigabytes of .csv files on the shared drive so Power Query can load in datasets beyond Excel’s million row limit.

This dynamic is what gives rise to the Paradox. Because the more organizations deploy Excel in this manner, the more they use Excel in an attempt to fix what are fundamentally not Excel problems, the more time they spend on Excel work that doesn’t produce the outcome they want:

More reliable, data-driven answers.

Where 80% of the Work Disappears

When finance teams spend most of their time preparing data instead of analyzing it, the cost does not always show up as a line item.

It shows up in missed windows, delayed decisions, audit stress, and highly skilled public servants spending their days rebuilding the same spreadsheet instead of advising the organization.

The pattern is familiar.

The extraction bottleneck. Pulling data from the ERP often requires IT intervention, custom reports, or complex queries. A simple budget-vs.-actual request can sit in a queue for days while council questions, board meetings, grant deadlines, and constituent needs keep moving.

The rearview mirror problem. Static data dumps are stale the moment they land in Excel. Leadership makes decisions from last week’s snapshot while fund balances, encumbrances, payroll costs, and grant expenditures continue to shift underneath them.

The reconciliation trap. Every manual touch creates room for error. Linked spreadsheets, copied tabs, renamed files, offline versions, and manually refreshed pivots all raise the same question: whose numbers are right?

In an environment governed by GASB standards and subject to Yellow Book audits, that question is not theoretical. It is the question that delays the Annual Comprehensive Financial Report. It is the question that slows grant reporting. It is the question that makes finance teams double-check work they should not have had to rebuild in the first place.

What This Costs Beyond Staff Time

Slow financial data is not just an internal inconvenience. In local government, it affects how confidently leaders can allocate public money.

When finance teams cannot get to current numbers quickly, the whole organization becomes less agile.

Delayed fiscal insight. Management sees budget pressure too late to redirect resources toward urgent infrastructure, public safety, emergency response, or community services needs.

Increased audit risk. Manual handling creates inconsistencies that may surface as Yellow Book findings or delays in ACFR publication. GFOA recommends publishing the ACFR within 180 days of fiscal year-end. Many governments still struggle to meet that timeline.

Eroded public confidence. When different spreadsheet versions produce different answers, the finance department loses credibility with the board, council, and the residents they serve.

Opportunity cost. Skilled public servants spend their expertise on data wrangling instead of identifying cost-saving drivers, optimizing federal grant usage across programs like ARPA and IIJA, and advising leadership on fiscal strategy.

Consider a county that discovers during single audit preparation that ARPA subrecipient expenditures were tracked across three different spreadsheets with three different totals. The correct number takes two weeks to reconstruct.

With governed, live access to the source data, the discrepancy never forms in the first place.

That is the real issue. The numbers exist. But they are not reaching the people who need them at the speed public finance now requires.

The Gap at a Glance

The Shift: Enterprise Intelligence for Local Government

Forward-looking local governments are not abandoning Excel. They are fixing what feeds it. Finance teams should not have to choose between the flexibility of Excel and the reliability of governed ERP data. They need both.

The shift is toward live, governed connections between the ERP and the tools finance teams already use every day. The spreadsheet still remains the workspace. But instead of starting with a manual export, it starts with trusted data.

That changes the role of Excel. It is no longer the place where teams spend days cleaning, checking, and reconciling stale information. It becomes the place where they analyze current numbers, build scenarios, prepare reports, and support decisions with confidence.

SplashBI organizes this shift around three moves: Connect, Unlock, and Ask.

Connect: Live Data Where Your Team Already Works

The first step is to establish governed, real-time links between Excel and the ERP. Budget-vs.-actual reports, fund accounting views, grant tracking, encumbrance reports, and project spend summaries can refresh directly from the source instead of relying on manual exports.

When the data refreshes in place, finance teams reduce the risk of reconciliation errors. They also reduce the recurring pain of version control. The question changes from “which spreadsheet is correct?” to “what is the current financial picture?”

That matters for everyday work.

A finance analyst can refresh a fund statement before a meeting. A budget manager can check remaining balances without waiting for IT. A controller can trace a general ledger number back to the transaction detail behind it. A department head can see whether overtime spend is trending beyond budget before the quarter closes.

This makes ERP data usable where finance teams already work.

Unlock: Turn Connected Data Into Enterprise Intelligence

Connected data is only the beginning. The real value comes when more authorized users can work from the same trusted numbers without creating new risk.

BI provides the control layer. Role-based access, row-level permissions, certified metrics, and alignment to the chart of accounts ensure that people see what they are allowed to see and that everyone works from the same financial definitions.

In local government, governance is not optional. Finance data touches public accountability, labor costs, grant compliance, procurement, vendor payments, capital projects, and audit readiness. Broader access only works when the controls are strong enough to protect the integrity of the numbers.

The value compounds when finance connects with HR, payroll, projects, and operations. SplashBI already sees 25-30% of its customers using cross-domain capabilities to break down silos between finance and HR/payroll.

That matters because labor is often the largest single expense. A county cannot fully understand departmental cost if payroll lives in one system, budget lives in another, and finance teams have to manually stitch the two together.

Enterprise Intelligence gives leadership one governed view of what is happening across funds, departments, programs, and people.

Ask: Cross-Domain Answers in Plain Language

With SplashAI, authorized users ask questions the way they would ask a colleague.

The value is not just in getting a faster answer. It is in asking a better question.

For example, “What is my remaining encumbrance on the Main Street project, and how does public works overtime this quarter compare to the same period last year?”

That question crosses finance, projects, and HR/payroll. It pulls from multiple domains and resolves them into one governed answer.

That is the difference between a spreadsheet that shows what happened and a system that helps leadership decide what to do next.

For local governments, this matters because the most important fiscal questions rarely live in one table.

Grant spend connects to project delivery. Overtime connects to staffing and service levels. Fund balances connect to capital planning. Vendor payments connect to procurement and compliance. Payroll connects to departmental performance.

When those answers require five exports and two weeks of reconciliation, the organization moves slowly. When authorized users can ask across domains with governance built in, finance becomes a more strategic partner to leadership.

What This Looks Like in Practice

For public sector finance teams, the change is practical. It shows up in the reports, reconciliations, and board packets they already produce.

Live ERP reporting in Excel. Refreshable, governed ERP data flows directly into the spreadsheets your team already builds in, with no manual exports and no version confusion.

Subledger and grant drill-down. Teams can trace GL balances back to source transactions, projects, vendors, or federal grants for transparency and audit readiness.

Accelerated ACFR preparation. Data preparation and statement refresh cycles can be automated, reducing manual work that consumes finance teams every year.

Self-service for finance teams. Analysts and managers can build fund statements, balance sheets, and GASB-compliant reports without waiting on IT for every request.

Finance plus HR in one view. General ledger, accounts payable, projects, and payroll data come together to show the full cost picture by department, fund, and program.

Governance built in. Fine-grained access controls and audit visibility help expand access without losing control. SplashBI is SOC 1, SOC 2 Type 2, and ISO 27001 compliant.

Ready to Close the Gap?

Public sector finance teams do not need to stop using Excel. They need Excel to stop starving for current, governed data.

A county finance director should not wait on a manual export to answer a board question. A controller should not reconstruct grant expenditures across conflicting spreadsheets. A department head should not have to guess whether overtime spend can hold for the rest of the quarter.

SplashBI helps local governments connect ERP data to the tools finance teams already use, unlock Enterprise Intelligence, and put governed answers in front of the people responsible for fiscal decisions.

Book a demo to see live, governed ERP reporting against your data.

Or, explore how local governments use SplashBI to strengthen fiscal stewardship and public trust.