Get FP&A best practices, research reports, and more delivered to your inbox.
That's the whole plan in one line, and most of the risk in an FP&A implementation comes from breaking it. Teams start connecting the ERP in the last week of the month, the controller gets pulled into mapping questions on day two of close, and the new tool goes live on numbers nobody has reconciled. The fix is scheduling, not software: build the integration in the quiet weeks, test it against a close you're running anyway, and switch only when the two sets of numbers agree.
This guide is the detailed version of the close-safe cutover. For the broader rollout, see our seven FP&A implementation steps and typical implementation timelines.
Bottom line: Start the day after a close ends. Connect the ERP and HRIS with read-only access in weeks 1 and 2, run the next month's close in parallel in week 3, and cut over in week 4 only if the trial balance, department spend and headcount all tie. Then decide, before go-live, who maintains the tool.
The four-week cutover plan, mapped to your close
The plan assumes a close that runs roughly the first week of each month. Shift the weeks to match yours; the rule is that nothing new touches the ERP while the books are open.
Before week 1: pick the start date and the owners. Start the first business day after a close is signed off. Freeze the scope for phase one (usually reporting and budget versus actual, not every model at once), and name one owner for each workstream in the RACI below.
Week 1: connect the ERP, read-only. Give the new tool read-only credentials, or connect it to a sandbox if your ERP has one. Map the chart of accounts and department structure, load at least 12 months of history, and check that the trial balance for the last closed month ties to the penny. That single reconciliation validates most of your mapping.
Week 2: connect the HRIS and decide the sources of truth. Headcount rarely ties on the first pass, because effective dates, payroll cutoffs and GL posting periods don't agree. Decide which system is authoritative for headcount and which for compensation cost, and write the rule down instead of fixing each difference by hand. Connect the budget and the models your team already uses.
Week 3: run the next close in parallel. The controller closes the books exactly as before. Once close is done, FP&A produces the month's reporting twice: once the old way, once in the new tool. Keep the parallel run on FP&A's side of the close so it never delays the controller.
Week 4: tie out, then decide. Compare the two outputs line by line using the checklist below. If everything ties or every difference is explained, switch off the old process for the following month and train budget owners. If not, fix the mappings and run one more parallel close. One extra month is cheaper than finding a bad mapping in front of the board.
The parallel close tie-out checklist
The parallel close only works if you agree in advance what "ties" means. Check each of these against the old process before cutover:
- Trial balance by account and month. Every account matches for the parallel month and the history you loaded.
- Department operating expense. Each department's actuals match, which confirms the department mapping.
- Headcount by department. Matches the HRIS on the rule you chose in week 2, with any timing differences explained.
- Revenue by source. Billing, CRM and GL revenue reconcile to the level you report on.
- Budget versus actual. The same variances appear in both versions, at the same size.
- Key metrics. ARR, gross margin, burn or whichever numbers leadership reads first come out the same.
Set a tolerance before you start (for example, zero for the trial balance and a small documented threshold for timing items). Anything outside it needs a written explanation before cutover, not a manual fix in the new tool. If your data isn't clean enough to tie, our data readiness checklist covers what to fix first.
Who owns what: a RACI for an FP&A implementation
Most implementations stall because two people each think the other owns the mapping. Name the owners before week 1:
The last row is the one teams leave blank. Fill it in before you sign.
Who maintains the tool after go-live?
This is the failure mode that shows up a year later. A tool is chosen, implemented by a team that includes someone who knows the system inside out, and then that person leaves or the team shrinks. The planning tool still needs its data connections fixed, its mappings updated when the chart of accounts changes, and its models adjusted when the business reorganizes. If nobody left on the team can do that, finance quietly moves back to spreadsheets and the tool becomes shelfware.
Ask these questions before you buy, and again before go-live:
- Who fixes a broken connector? The vendor, as part of the subscription, or your team?
- What happens when the chart of accounts changes? Is remapping a setting a finance analyst can change, or a services project?
- How many admin hours a month does a team like ours spend? Ask a reference customer of your size, not the sales team.
- Can the models be maintained by the people who build them today? If your team works in Excel, a tool that keeps models in spreadsheets is easier to maintain than one that requires learning a new modeling language.
- What does a new hire need to learn? If the answer is weeks of training, you've built in a dependency on one person.
Our breakdown of why FP&A implementations fail covers the other five failure modes.
Change management for the people, not just the systems
Connecting the ERP is the technical half. The other half is getting budget owners and the finance team to actually work in the new tool. Prosci's change management research found that projects with excellent change management were about seven times more likely to meet their objectives than projects with poor change management.
For an FP&A rollout, that mostly means four things:
- Tell budget owners what changes for them, and when. One message before the parallel close, one at cutover. Keep it to what they'll do differently.
- Train on their own numbers. A session using each department's real budget beats a generic demo.
- Retire the old files on a date. If the old spreadsheet still works, people will keep using it. Archive it the month after cutover.
- Set permissions before you invite anyone. Budget owners should see their own lines, not everyone's salaries. See role-based access controls in FP&A.
What makes the integration easier in the first place
The less custom integration work the tool needs, the less there is to break during close and to maintain afterward. When you compare tools, check whether the vendor offers managed connectors to your specific ERP and HRIS, whether it can read your existing models instead of forcing a rebuild, and whether a finance analyst can adjust mappings without the vendor.
Aleph connects to 150+ systems, including NetSuite, Sage Intacct, QuickBooks, Rippling, BambooHR and ADP (full list), and puts live data into the Excel and Google Sheets models your team already maintains, so the cutover is about connecting data rather than rebuilding models. For the ERP side in more depth, see FP&A tools that integrate with NetSuite, and for how the tool fits the rest of your systems, the modern finance tech stack for SaaS companies.
Plan your cutover with Aleph
Aleph connects your ERP, HRIS, CRM and billing and delivers live data into Excel and Google Sheets, so you can run a parallel close on the models you already have instead of rebuilding them first.
Get FP&A best practices, research reports, and more delivered to your inbox.
