Your GL closes in three days. Then FP&A opens 47 CSVs.
Your GL closes in three days. Then FP&A opens 47 CSVs
September 8, 2026
Your GL closes in three days. Then FP&A opens 47 CSVs.
The assembly step, mechanically. And the five diagnostics you can run on your own close this month.
Welcome back to Bridging the Deficit.
This week: the second half of your monthly close, mechanically, on a legacy or on-prem GL.
Under "monthly close," your team runs two workflows. The GL runs the first. FP&A runs the second.
The first is accounting. Sub-ledgers close, accruals post, the trial balance ties. On Dynamics GP, Sage 100, Blackbaud Financial Edge NXT, MIP fund accounting, SYSPRO, Multiview, Elite, or Dynamics NAV (whichever ledger you run), accounting closes in two to three business days. That is the workflow the finance-close calendar tracks.
The second workflow is what happens next, and it is where the month goes. The trial balance has to become a management P&L by department, a variance narrative, a rolling forecast, a board pack, grant-restricted reports where the funder requires them, and a wage-mix analysis wherever labor is the biggest line on the P&L. None of that comes out of the GL. It gets assembled in Excel.
THE ASSEMBLY STEP
Six tasks, every close
- Consolidate. Merge each entity's CSV. Run intercompany eliminations by hand.
- Re-map. Translate GL account codes to management categories through a mapping table. The mapping breaks silently every time a new account is added and nobody updates the sheet.
- Layer in sub-ledger detail. Import payroll, capex, grants, SKU data from separate systems and join to the trial balance.
- Variance to budget. Pull against the working budget model. Sensitive to any layout change in that model.
- Roll the forecast. Push actuals into the driver-based or plug forecast for year-end.
- Build the board pack. Render the tabs the CFO approved, in the layout the CFO approved.
Every one of those tasks lives in Excel. Sometimes it is one master workbook with 10 tabs. More often it is 19 linked files, three of them on the CFO's laptop, with external references across devices.
WHERE THE HOURS GO
The 600-hour number
Two-to-three-person FP&A team, mid-market company, ledger closes cleanly, no accounts change mid-year: 40 to 55 hours a month, in assembly. The ledger runs late, or the chart of accounts gets edited, or the board adds a cut: 60 to 70 hours. Twelve months of that is about 600 hours.
600 hours a year. 16–24 finance-team days every month, spent in the assembly step.
Sixteen days in assembly displace sixteen days of analysis: the variance conversation with the plant manager, the program-cost pass before the next grant proposal, the pricing exercise on a new customer segment. Those get compressed or dropped. Two weeks from month-end to a board-ready pack shows as delay to the audit committee. Your team lives those two weeks at peak effort.
DIAGNOSE IT
Five diagnostics you can run today
Open the last three closes and count:
- Workbook count. More than five FP&A workbooks open between Days 3 and 10, the shadow layer is doing work the ledger cannot.
- Export frequency. More than four manual GL exports a month, assembly hours dominate the calendar.
- Formula breakages. If your team can name specific breakages from the last year, the infrastructure is signalling.
- Days to board-ready. More than seven days between month-end and the variance narrative, assembly is the bottleneck.
- FP&A Manager time allocation. Over 50 percent of the month in assembly, the team is running without owned infrastructure.
Three of five true, the pattern is the pattern.
THE FIX ABOVE THE LEDGER
No GL migration required
GP stays on-prem. Financial Edge NXT stays hosted. NAV, SYSPRO, Multiview, Elite stay where they are. What changes is the layer above the ledger.
A connected FP&A layer pulls actuals from the ledger on a schedule, holds the mapping in one place, keeps the workforce model, the driver logic, and the board layout together. The six assembly tasks stop being manual. Actuals flow. Variance calculates. The board pack renders.
Two finance leaders on legacy/on-prem stacks who have this running today:
"[Centage] auto downloads and uploads from SYSPRO out to whatever a CSV or whatever it is. And then uploads into Centage automatically. I never have to think about it."Steeve Wintle, Controller, Adhesive Technologies (SYSPRO)
"We used to spend days cleaning up formulas. Now the numbers just show up."Mary Flannery, Director of Finance, God's Pantry Food Bank (Dynamics NAV)
The full worked-out version is on the blog: Monica's Day 1 through Day 14 on a five-site behavioral-health nonprofit, the Excel shadow layer inventoried across manufacturers, nonprofits, and professional-services firms, and ledger-by-ledger connector coverage.
Read the Full Piece
What a Monthly Close Actually Looks Like on a Legacy GL
No form. Public blog. 8-minute read.
About Centage
Centage is FP&A software built for finance teams at growing mid-market companies on legacy or on-prem GLs, with supported connectors into Dynamics GP, Sage 100, Blackbaud Financial Edge NXT, Dynamics NAV, SYSPRO, Elite, Multiview, and cloud ledgers. Implementation is 4 to 6 weeks, finance-owned, no IT team.