FP&A platform consolidation case study

NetSuite Planning & Budgeting (NSPB) FP&A Consolidation Case Study

A $180M PE-backed multi-entity holdco replaced 22 fragmented budget workbooks across departments, sub-entities, and FP&A leads with a unified NetSuite Planning & Budgeting deployment — enabling driver-based forecasting, real-time scenario modeling, rolling forecast discipline, and a single source of truth for the board.

Client profile: Composite case study based on a $180M PE-backed holdco with 7 active operating entities, NetSuite OneWorld, 7-person FP&A team across HQ and entities, quarterly board cadence with sponsor portfolio review.
See measured results Talk through your FP&A
Before What we built NSPB architecture Results Alternatives FAQ
Case study breakdown

From 22 workbooks to one source of FP&A truth

Company context — and why workbook proliferation is a leading indicator

The client is a $180M PE-backed holdco with 7 operating entities — three professional services firms, two software businesses, and two B2B media businesses, acquired over the prior 4 years. Each entity ran its own budget process when acquired, in its own format, on its own cadence. The HQ FP&A team consolidated those budgets in a separate workbook, applied corporate adjustments, and produced the consolidated view for the sponsor. Headcount on FP&A: 7 people total across HQ and entities.

The pattern that triggered the project: the sponsor asked for a portfolio-wide scenario showing what would happen to consolidated EBITDA if a top customer at one entity churned. The answer took 11 days because the question required 7 different entity-level workbooks to be re-run, then re-consolidated, then walked through corporate adjustments. The sponsor's response — "This shouldn't take 11 days" — became the engagement charter.

  • $180M revenue across 7 operating entities
  • Mix of professional services, software, B2B media
  • NetSuite OneWorld with 7 active subs and 4 currencies
  • 7-person FP&A team (3 HQ, 4 across entities)
  • Quarterly board cadence + monthly sponsor portfolio review
  • Annual budget + monthly rolling forecast + quarterly reforecast
  • 22 active budget workbooks at engagement start

Before consolidation — 22 workbooks, every cadence different

  • Each entity ran its own budget on its own cadence (some calendar, some fiscal)
  • Each entity used its own driver model — revenue drivers, headcount, expense categories
  • HQ rolled up via separate consolidation workbook with corporate adjustments
  • Scenarios required cloning all 22 workbooks and rebuilding by hand
  • Forecast vs. actual variance review lagged 1–2 weeks per entity
  • Sponsor portfolio review pack was a 4-day FP&A team effort each month
  • Headcount planning sat in separate HRIS workbook that didn't tie to budget
  • Capex pipeline lived in a third workbook owned by Ops
  • Treasury cash forecast lived in a fourth workbook, also disconnected

What Ledger Summit implemented

  • NSPB deployment with 7 entity models and consolidated portfolio model
  • Standardized chart of accounts and dimension model across entities
  • Driver-based revenue forecasting per entity (each entity's drivers preserved)
  • Workforce planning module with headcount, comp, benefits drivers
  • Capex pipeline integrated into budget
  • 13-week cash forecast layered on the budget structure
  • Five preset scenario sets (base, downside, upside, M&A, refinance)
  • Sponsor portfolio review pack auto-generated
  • Forecast vs. actual variance review automated, refreshed daily
  • Integration with NetSuite GL for actuals; HRIS (Rippling) for headcount actuals

NSPB architecture — the model design

NSPB (NetSuite Planning & Budgeting, formerly PBCS / Hyperion) is Oracle's cloud planning platform. It handles multi-entity budgeting, rolling forecasting, scenario modeling, and consolidation in one model. The architecture decisions shape whether the deployment delivers value or becomes another rigid system.

  • Application architecture: Single application with 7 entity-level cubes and 1 corporate-roll-up cube. Each entity preserves its operating-business drivers.
  • Dimension model: Account, entity, period, scenario, version, currency, custom dimension (department, project, customer-segment as relevant).
  • Driver hierarchy: Top-level corporate drivers (rev growth, EBITDA margin) inherit from entity-level drivers (per-entity revenue model, headcount, expense ratios).
  • Currency: Functional currency per entity, USD reporting; FX rates centrally managed and refreshed quarterly.
  • Workflow: Approval routing per entity, with HQ FP&A as final reviewer; sign-off audit trail.
  • Actuals integration: Daily NetSuite GL pull; entity-level reconciliation to ensure budget-vs-actual integrity.
  • Reporting: Sponsor pack, board pack, entity-leader pack, all from same model.

Implementation timeline — 14 weeks from kickoff to first quarterly cycle

  • Weeks 1–3: Discovery and design. 22 workbooks inventoried, driver models documented, COA standardization plan, dimension model, approval workflow design.
  • Weeks 4–8: Build. NSPB application configured, 7 entity models built, corporate roll-up, workforce planning module, capex module, 13-week cash forecast layer, scenario engine.
  • Weeks 9–10: Data load. 3 years of actuals loaded, opening budget loaded, driver assumptions calibrated against history.
  • Weeks 11–12: Parallel run. NSPB ran alongside 22 workbooks for the Q3 close. Variances reconciled to zero (12 reconciling items found, all spreadsheet errors).
  • Week 13: Cutover. First quarterly cycle on NSPB. Sponsor portfolio review pack generated from the new system.
  • Week 14: Hypercare. Three rule refinements, training waves for entity-level FP&A, sponsor walkthrough.

Measured results

MetricBeforeAfterDelta
Active budget workbooks221 unified NSPB application—
Quarterly forecast cycle12 business days3 business days−75%
Portfolio scenario response time11 days30 minutes−99%
Forecast vs. actual variance lag1–2 weeksSame-day—
Sponsor portfolio review pack prep4 daysSame day−100%
Headcount-budget tie-outManual reconciliationNative in workforce module—
Capex pipeline visibilitySeparate workbookIntegrated to budget—
FP&A team time on consolidation~120 hrs / cycle~25 hrs / cycle−79%
Scenario depth available to sponsor1 (base)5 preset + custom—

When NSPB is the right choice

  • $50M–$500M revenue with multi-entity operations
  • Already on NetSuite OneWorld (single-vendor stack, native integration)
  • Quarterly board cadence + monthly forecast review
  • PE-backed or sponsor-driven cadence with portfolio reporting
  • Driver-based forecasting need across diverse entity shapes
  • FP&A team of 4–12 with at least one designated platform owner
  • Budget complexity beyond Excel but below Anaplan-level enterprise modeling

Alternatives considered

OptionTime to live3-year costStrengthsWeaknesses at this scale
Anaplan5–7 months$650K–$1.1MMost powerful modeling; deep scenario depthImplementation cost rarely justified at $180M; learning curve steep
Adaptive Planning (Workday)4–5 months$400K–$680KStrong long-term forecasting; clean UINetSuite integration less native than NSPB
Vena3–4 months$280K–$420KExcel-native; gentle learning curveExcel ceiling shows up in multi-entity consolidation
Cube / Mosaic2–3 months$180K–$280KModern UI; fast to deployLess depth on multi-entity consolidation
Centage / Planful3–4 months$280K–$380KMid-market FP&A focusIntegration with NetSuite less tight than NSPB
NSPB (selected)14 weeks$220K–$340KNative NetSuite integration; one-vendorUI less modern than Cube/Mosaic; learning curve moderate
Stay on Excel + better discipline0 (no change)$0 (license) + ongoing painNo new vendorDoesn't solve the consolidation problem

Frequently asked questions

Why NSPB and not Adaptive Planning or Anaplan?

NSPB has the tightest NetSuite integration and avoids a second vendor relationship. Adaptive Planning is excellent but the integration overhead with NetSuite makes the total deployment longer. Anaplan is over-scoped at $180M revenue.

How do you handle entity-specific drivers?

Each entity preserves its operating-business drivers (e.g., professional services use billable utilization × bill rate × headcount; software uses ARR × growth rate × churn). The corporate roll-up doesn't try to standardize down to a single driver model — that would lose the operational meaning.

What about multi-currency?

Each entity budgets in its functional currency; corporate consolidation translates to USD at managed FX rates. Variance analysis presents both functional and reporting currency views.

How do you manage the ongoing maintenance?

HQ FP&A owns the platform; entity-level FP&A leads own their entity model. Quarterly governance review on driver assumptions and dimension model. Annual full review.

Can entity FP&A leads still work the way they used to?

Mostly. NSPB has Excel front-ends (SmartView) for users who prefer Excel; entity-level data entry can happen in Excel and write back to the cube. The discipline is shared dimensions and shared cadence; the workspace is flexible.

What does NSPB cost?

License: $30K–$80K annually depending on user count and modules. Implementation: $140K–$220K for a deployment of this scope. Ongoing optimization: $25K–$60K annually if retained.

How do you handle M&A — adding a new entity to the model?

New entity model added to the application, new entity dimension, opening balances loaded, drivers calibrated against the acquired company's history. Typically 4–6 weeks per acquisition. Pre-built templates accelerate.

What about workforce planning?

NSPB workforce module handles headcount, comp, benefits, and timing. Integration with Rippling/Workday/Gusto pulls actuals; planning happens in NSPB. Critical for service-business clients where labor is 60%+ of cost.

How does this interact with the close?

NSPB consumes actuals from NetSuite daily; budget vs. actual variance flows back into the close cycle for management reporting. The 5-day close calendar feeds the variance review.

Can sponsor diligence walk this directly?

Yes. The sponsor pack is generated from the same model that produces internal reports; one source of truth. Sponsor due-diligence teams can drill from portfolio totals into entity detail in three clicks.

Budget workbook proliferation slowing FP&A?

A 30-minute call walks your current FP&A stack and tells you whether NSPB or another platform is the right fit.

Book a free call