Living Between Sage Intacct and Excel: The Finance Team’s Real Workday
Ask a controller on Sage Intacct where the month-end really comes together, and the honest answer is neither the ERP nor the spreadsheet. It comes together in the trip between them. Intacct holds the numbers. Excel is where the report gets built, reviewed, and explained. The real work is the commute: moving figures out of one system and into the other, over and over, until the close is done.
Picture the last day of close. The books sit nearly final in Intacct. The CFO wants the management pack by morning: a P&L by entity, a consolidated view with intercompany eliminations, and a variance column against budget. None of that leaves the ERP in the shape the CFO pictured, so the controller opens Excel, and the commute begins.
The trip starts with an export. The controller pulls a report or a CSV out of Intacct, drops it into a workbook, reformats it, adds the formulas the pack needs, and delivers it. The first build goes fine. The trouble is the second build, and the twelfth. A late journal entry lands, a new entity joins the group, an account gets restated, and the numbers move. So the export runs again, the workbook gets rebuilt, and the version questions start. Is this the file with the corrected intercompany elimination, or the one from before it? Which tab holds the current headcount split? The first week of most months goes to report mechanics instead of analysis.
Some of the trip repeats so reliably it stops feeling like work. The same revenue report by location, rebuilt each month because last month’s file carries stale references nobody fully trusts. The same board pack, reformatted from scratch because the export never arrives in the layout the board expects. None of it shows on the close calendar, and all of it happens anyway.
Intacct’s own reporting handles the standard work well. Trial balances, a departmental P&L, the balance sheet: the Financial Report Writer produces them cleanly. The friction starts the moment finance needs something the report writer was never shaped for. A custom layout the board prefers. A multi-entity consolidation with eliminations. Actuals against budget against forecast in a single view. Financial figures sitting beside an operational metric. Each one turns a simple request into a project, and “can you show me this cut a different way” becomes a two-day answer.
Some teams try to skip the export by going straight at the data with a SQL query or an API script. It works until it doesn’t. The person who wrote the query becomes the person who maintains it, and when Intacct renames a field or a new dimension appears, that person turns into the bottleneck. The output arrives as raw data rather than a financial statement, so someone still shapes it into something a board member can read. That shaping happens in Excel, which is where the trip was always heading.
Sage Intacct’s real strength is its dimensions: slicing the numbers by location, department, project, and more. That strength becomes manual work the moment the analysis lives in a spreadsheet. Each new cut by dimension means another export, another reshape, and another reconciliation against the last version. The report the controller built last month cannot simply refresh, because the data underneath it was a snapshot, frozen at the moment of export. When the numbers change, the work restarts rather than updates.
The trip does not end once the pack is built either. It gets emailed out, a reviewer spots a figure that looks off, a number gets corrected in Intacct, and the export-and-rebuild sequence runs again for a single changed cell. Multiply that across the reviewers who each want their own slice, and the close takes on a second life after it was supposedly finished.
The commute lands on the most experienced person in the room. Building a clean consolidation, spotting the elimination that looks off, formatting a pack a board will trust: that work needs judgment, so it falls to the controller or the senior accountant. Their month fills with data movement, and the interpretation they were hired for gets whatever time the trip leaves behind.
The commute persists for a reason that has nothing to do with the team’s skill. Intacct exists to store financial data and enforce controls, and it does that job well, which is also why it resists being reshaped on demand. Excel exists to explore and explain, which makes it the natural place finance works, as long as it stays connected to the system of record instead of becoming a store of one. Nobody built the bridge between the two, so the controller becomes the bridge, carrying numbers across by hand every close.
Any controller on Intacct can measure the commute without launching a project. Over one close, count the exports, the rebuilds, and the version checks. Note the requests that turned into two-day projects because the numbers had to be cut a different way. That total is the real workday, the part that happens in the gap between the ERP and the spreadsheet, and it is the clearest picture of what the current setup asks of the team every single month.