Living Between Business Central and Excel: The Finance Team’s Real Workday
Ask a controller on Business Central 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. Business Central holds the numbers. Excel is where the report gets built, reviewed, and explained. The reporting layer, in practice, lives outside the ERP. The real work is the commute: moving figures out of the ERP and into the workbook, over and over, until the close is done.
Picture the last day of close. The books sit nearly final in Business Central. The CFO wants the management pack by morning: a P&L by department, a consolidated view across companies, 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 financial report or a raw data export out of Business Central, 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 company 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 eliminations, 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 departmental report, 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 lands in the layout the board expects. None of it shows on the close calendar, and all of it happens anyway.
Business Central’s own reporting handles the standard work. The financial reports built from row and column definitions produce trial balances, a departmental P&L, and the balance sheet. The friction starts the moment finance needs something the report writer was never shaped for. A new subtotal or a reordered layout sends the team back into the design screens to edit the definitions by hand. Reporting by department, customer group, or project depends on Analysis Views that someone has to build and keep synced, and that someone is usually a power user or an administrator rather than the controller. So the moment the board wants the numbers a different way, the request leaves finance’s hands and joins a queue. The final fifth of the polish ends up consuming most of the effort.
Consolidation adds friction of its own. True consolidation in Business Central runs through a separate consolidation company that imports data from each subsidiary, which makes the consolidated figures static rather than live. Intercompany transactions are not eliminated automatically, so the controller identifies and removes them by hand. And the native consolidated reporting does not drill into the transactions underneath a figure, so when the board asks what sits behind a number, the detail gets rebuilt in Excel. Every late journal entry means another round of syncs and reconciliations.
The commute runs both directions, too. Budgets and journals built in Excel have to be reshaped to fit a strict import layout designed for the system’s structure rather than the way finance works day to day. Hours go into reformatting, validating, and reimporting the same figures, just to make them fit. Pulling data out is only half the trip; pushing it back in is the other half.
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 a field gets renamed or a new structure 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.
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. Business Central 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 Business Central can measure the commute without launching a project. Over one close, count the exports, the rebuilds, and the version checks, and add the budgets and journals reshaped to fit the import. Note the requests that turned into queued 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.