Excel is useful. It should not carry the control burden.
Excel is not the problem. In treasury and finance, spreadsheets are often where good thinking starts. They are flexible, familiar, fast to adapt, and useful for modelling a new idea before it becomes part of a structured process. Most treasury teams will continue to use spreadsheets for analysis, ad hoc calculations, scenario sketches, and preparation work. That is not only realistic. It is also sensible.
The problem starts when spreadsheets become the control layer for decisions that affect liquidity, financial risk, intercompany settlement, hedge accounting, guarantees, bank limits, or CFO reporting. At that point, the spreadsheet is no longer just a working file. It becomes the place where business-critical logic sits, where assumptions are changed, where approvals are implied, and where decisions are justified after the fact. For modern treasury, that is too much weight for a file that was never designed to be the operating backbone of control.
Why spreadsheet-supported control survives for so long
Spreadsheet-supported control rarely appears as a strategic decision. It grows quietly. A forecast template becomes the standard. A manual netting file becomes the trusted source. A hedge accounting workbook becomes the monthly close routine. A list of guarantees becomes the only practical overview of contingent exposure. A cash report assembled from bank portals, ERP exports, and local entity updates becomes the CFO pack.
Over time, the spreadsheet becomes familiar enough to feel safe. The team knows where the formulas are. Someone remembers why a column exists. A senior user can explain the logic. For experienced treasury professionals, that familiarity matters. They do not want to replace proven routines with vague promises of transformation. They need stability, auditability, and control. This is exactly why the conversation should not be about eliminating Excel. It should be about deciding which work belongs in Excel and which work requires system-supported governance.
The risk is not the spreadsheet. It is the missing control layer.
A spreadsheet can calculate. It can organise. It can model. But it does not naturally enforce ownership, approvals, permissions, version control, audit trails, segregation of duties, or process status across a treasury workflow. These control elements can be added manually, but they are difficult to maintain when multiple entities, banks, currencies, instruments, and users are involved.
This matters because treasury control is no longer a narrow operational task. Treasury teams are expected to answer questions about available liquidity, expected cash flows, FX exposure, hedge positions, intercompany funding, guarantees, credit capacity, and payment execution. In Nomentia's Treasury & Cash Management 2026 research, many treasury teams were shown to be in a transitional state: they have moved beyond fully manual processes, but full end-to-end automation remains limited. The same research found that Excel and manual spreadsheets still form part of treasury and cash management processes for a significant share of respondents. That is not surprising. It shows where many finance teams are today: partly automated, partly controlled, but still dependent on manual bridges.
Where spreadsheets become too fragile for modern treasury
The fragility becomes visible in the processes where treasury decisions need both calculation and governance. Intercompany netting is a good example. A spreadsheet can calculate bilateral or multilateral positions, but the process also requires participant control, cut-off dates, dispute handling, confirmations, settlement instructions, FX treatment, and an audit trail. If the calculation is separated from the workflow, treasury may still get a number, but control over the process remains fragile.
Hedge accounting creates a similar challenge. A workbook can hold valuation inputs, effectiveness calculations, and journal logic. But hedge accounting also requires documentation, designation, rebalancing, de-designation, OCI postings, accounting entries, and evidence for auditors. If these steps rely on manual files, the month-end process becomes dependent on individual knowledge and repeated checks rather than on embedded controls.
Guarantees and letters of credit are another area where spreadsheets often hide complexity. A guarantee register may look complete, but treasury also needs to manage issuance, amendments, utilisation, expiries, counterparty exposure, bank limits, approvals, and historical changes. When these elements live outside a controlled system, contingent exposure can be reported, but not truly managed.
The CFO does not ask for a spreadsheet. The CFO asks for a reliable answer.
The CFO rarely asks how the number was assembled. The question is usually simpler: How much liquidity is available? Which entities need funding? What exposure is open? Are internal payments under control? What will happen if forecast assumptions change? How much capacity is tied up in guarantees? Are the hedges correctly documented and reflected?
A spreadsheet-supported answer can be correct. But correctness is only one part of confidence. The CFO also needs to know whether the answer is current, complete, consistent, and explainable. If the answer depends on a file sent by email, a hidden formula, a manual copy-and-paste step, or one person who understands the logic, the organisation may have information, but not enough control. This is where the role of treasury technology has changed. It is no longer only about producing reports faster. It is about making the path from data to decision more reliable.
A modern foundation keeps Excel in the right place
The practical goal is not to ban spreadsheets from treasury. The better goal is to move critical control points into a structured foundation, while keeping Excel available for analysis where flexibility adds value. Treasury teams should still be able to test assumptions, compare scenarios, and prepare management views. But they should not have to use spreadsheets as the primary place for approvals, audit evidence, exposure ownership, settlement status, or month-end control.
A modern treasury foundation should connect data from banks, ERPs, payment processes, forecasts, intercompany flows, financial instruments, and contingent exposures. It should provide workflow status, permission-based access, history, audit trails, and reporting that does not need to be rebuilt every period. It should also create a better basis for analytics and AI because trusted outputs depend on controlled inputs. AI-supported forecasting, natural-language reporting, and advanced treasury analytics cannot work reliably if the underlying data is scattered across uncontrolled files.
From spreadsheet-supported control to system-supported judgement
Treasury teams do not need less judgement. They need better support for the judgement they already apply every day. When routine reconciliation, status tracking, confirmations, documentation, and evidence collection are handled in a controlled system, treasury professionals can spend more time interpreting what the numbers mean. They can explain liquidity movements, challenge forecast inputs, assess risk positions, manage internal settlement, and support the CFO with clearer recommendations.
This is the real end of spreadsheet-supported treasury control. Not the end of Excel. Not the end of flexible analysis. The end of relying on spreadsheets as the unofficial system of record for decisions that require governance, traceability, and trust. Modern treasury needs flexibility, but it also needs structure. It needs fast analysis, but also controlled workflows. It needs familiar tools, but not fragile foundations.
Read more blogs of this series: