It’s the Wednesday after WD3. You’ve walked past the FC’s desk for the third time today. She’s still got NetSuite open in one window, Excel in another, and a coffee that went cold around 4pm.<\/p>\n
You ask how it’s going.<\/p>\n
“Good, just rebuilding the OPEX pack.”<\/p>\n
Rebuilding.<\/em><\/p>\n The pack she rebuilt last month. And the month before. And every month for the last four years. Since the day your business signed the NetSuite contract, in fact. The contract that came with a slide deck claiming “real-time financial visibility” and “single source of truth.”<\/p>\n Lol.<\/p>\n Let me tell you what’s actually happening on her screen.<\/p>\n She runs the consolidated P&L. She hits Export. Excel throws a security warning about the XML Spreadsheet 2003 format, because it’s 2026 and NetSuite is still serving up a file format from when George W. Bush was in office. She clicks through. She reformats columns. She rebuilds subtotals. She pastes into last month’s pack template. She starts checking numbers.<\/p>\n Then someone posts a late journal entry.<\/p>\n She does it all again.<\/p>\n This is not a workflow anyone designed. This is a workaround that calcified into process. And there is one of these in every NetSuite-implemented finance team I have ever seen.<\/p>\n Every CFO has, at some point, said the words: “Surely we can get this out of NetSuite directly?”<\/p>\n You bring in the NetSuite admin. You bring in the implementation partner. You spend $40K on a “reporting optimization” engagement.<\/p>\n Six weeks later you are back where you started. Why?<\/p>\n Because the FCs aren’t dumb. They knew about the report builder. They knew about saved searches. They knew about Financial Report Builder. They tried all of it. They went back to Excel because the export-rebuild cycle is faster<\/em> than fighting the native tools.<\/p>\n That should make you uncomfortable. It means the problem is not your team.<\/p>\n It is the tool.<\/p>\n NetSuite serves more than 40,000 customers across 219 countries, with the bulk of them sitting in the 100-249 employee range (Anchor Group, 2025). Mid-market.<\/p>\n Mid-market FCs need very specific things from their reporting layer. Board packs. Lender covenant calcs. Departmental P&Ls with custom KPIs. Investor updates. Budget-vs-actual with commentary. The kind of output a board chair will actually look at.<\/p>\n The native NetSuite report builder was not built for any of that.<\/p>\n I’ll let NetSuite consultancy Coras Consulting (2025) say it for me: “the system cannot automatically generate a complete monthly reporting pack without external tools.”<\/p>\n Translation: even the consultants who make a living configuring this thing admit it can’t do the job. (Same dynamic plays out across other ERPs and tools like QuickBooks<\/a>, by the way. NetSuite is just where the problem is most expensive.)<\/p>\n You can’t group accounts outside your COA structure without workarounds. You can’t blend financial and non-financial data in one view. You can’t produce presentation-quality formatting that won’t embarrass your CFO in front of the board. Want a Web Query connection to Excel or Power BI? Available for transactional data. Not<\/em> available for financial reports. The single feature that would bridge NetSuite to a usable reporting front end is missing exactly where the problem lives.<\/p>\n These aren’t bugs. These are architectural decisions baked in a decade ago.<\/p>\n Let me put a number on this.<\/p>\n Each export-rebuild cycle is 10-15 minutes per report. Sounds like nothing. Now count the reports in a typical month-end pack.<\/p>\n Consolidated P&L. Balance sheet. Cash flow. Departmental breakdowns (multiply by however many cost centers you have). Budget-vs-actual at total and department level. KPI summary. Cash position. Headcount. Top customers. Top vendors. Aged debtors. Aged creditors.<\/p>\n Twelve, fifteen, twenty reports. Each a 10-15 minute export-rebuild. Each vulnerable to version drift.<\/p>\n Finance pros burn up to 25% of their time on manual data extraction and prep (Zone & Co, 2025), and half of finance teams take six business days or more to close their books (Ledge, 2025). A quarter of one of your most expensive employees is being torched on work a machine should be doing.<\/p>\n Then the late journal lands and you do it all again.<\/p>\n This is the real cost of manual reporting<\/a>, and most CFOs run it without ever measuring it.<\/p>\n Here’s the part that should give every CFO of an audited company a cold sweat.<\/p>\n The moment a NetSuite report leaves the system as an export, it exits NetSuite’s security model. No access controls. No audit trail. No version log.<\/p>\n Five stakeholders ask for the same report at five different times in the close cycle. They get five Excel files. Different cuts. Different timestamps. Different numbers.<\/p>\n Which one did the board actually review? Which one did the auditor sign off on? Which one is “the truth”?<\/p>\n I’ve sat in audit committee meetings where this exact question landed and nobody could answer it. Just a long silence and an FC suddenly searching her downloads folder.<\/p>\n 96% of FP&A teams use spreadsheets daily (Association for Financial Professionals [AFP], 2025), not because they prefer it, but because native ERP reporting doesn’t meet the bar<\/a>. For a private company that’s a process problem. For a listed company, it’s a continuous disclosure problem dressed up as one.<\/p>\n Whenever I raise NetSuite reporting limitations with an admin, the first response is always the same: “have you tried a saved search?”<\/p>\n Yes. Everyone has tried a saved search. Saved searches are great for transactional data. They fall over fast on financial reporting.<\/p>\n Period comparisons need scripting. Budget overlays need scripting. Hierarchical account groupings need scripting. Large datasets hit the 5,000-row CSV export ceiling or time out completely. Building a complete financial picture means stitching together multiple saved searches by hand. Which is just the spreadsheet problem in a NetSuite skin.<\/p>\n The saved search is the ERP equivalent of “have you tried turning it off and on again.” Costs nothing to suggest. Almost never solves anything.<\/p>\n Yes. Finance is cross-functional. And 56% of teams cite cross-departmental dependencies as a close blocker (Ledge, 2025). Worth understanding how to structure dimensional variance analysis<\/a> across departments to address this.<\/p>\n But the real reason your OPEX variance commentary is so thin is not because Sales and Ops are slow. It’s because pulling a single coherent view across NetSuite GL, AP, AR, and the CRM module requires either custom development or external tools. Your FC has spent the close cycle being the integration layer herself.<\/p>\n When “why did OPEX increase 12%” lands in the board meeting, the answer lives across three NetSuite modules and two spreadsheets that someone manually reconciled last Tuesday. By the time it’s pulled together, the conversation has moved on.<\/p>\n There are two real categories of fix. Stop wishing for a third.<\/p>\n 1) Live data layers.<\/strong> Tools like Zone & Co’s Solution 7 (and a handful of others) create a two-way live sync between NetSuite and Excel. Your FC keeps her spreadsheet workflow, but the data is live. No more export. No more rebuild. Refresh the file, the numbers are current. Cube and Planful do something similar with a more structured planning layer on top. These are not bad answers. They eliminate the mechanical work without forcing your team to learn a new front-end.<\/p>\n 2) AI agents that draft the work.<\/strong> Newer model. Tools like Planir connect to NetSuite, look at the data, and draft the financial sections of your board pack, variance analysis, and budget-vs-actual directly. The FC stops being the assembler and becomes the editor. She reviews the AI’s draft, overrides where business context demands it, and writes the strategic narrative on top. Every number traces back to source data through an auditable pipeline, which closes the governance gap that AI in financial reporting was supposed to introduce<\/a> but actually fixes when implemented properly.<\/p>\n The dividing line: live data layers automate the export<\/em>. AI agents automate the analysis<\/em>. Both beat what you have. The right one depends on whether your bottleneck is mechanical work or analytical capacity. (Reporting automation vs the Excel-first approach<\/a> covers the trade-off in more depth.)<\/p>\n“Just train her on the report builder”<\/h2>\n
Why this is structural, not configuration<\/h2>\n
The real cost<\/h2>\n
The bit nobody talks about: governance<\/h2>\n
The “have you tried a saved search?” answer<\/h2>\n
“Well, finance is cross-functional”<\/h2>\n
What actually fixes this<\/h2>\n