IFP Suite Overview
6 planning modules, key capabilities, and what changed in v2.0
Getting StartedFoundation20 min
What IFP Does

IFP v2.0 is Anaplan's application suite for the Office of the CFO — covering P&L, cash flow, and balance sheet planning through a set of modules built on the Anaplan Application Framework and Polaris.
Problems IFP Solves
| Problem | How IFP Solves It |
|---|---|
| Inefficient Planning Cycles | Pre-built driver-based forecasting methods automate routine calculations |
| Fragmented Enterprise Planning | Single connected platform — Revenue, OpEx, HC, CapEx, and BS in one place |
| Reactive Decisions | Built-in scenario modeling and what-if analysis |
| Long implementation lead time | Deploy in 8–10 weeks using Application Framework best practices |
| Rigid Systems | Configurable dimensions, planning methods, and extensible architecture |
Six Planning Modules
| Module | What It Plans |
|---|---|
| 💰 Revenue & COGS | Revenue and margins by product, customer, entity — driver-based methods |
| 📊 Operating Expenses | OpEx by GL account — planning methods, line item detail, allocations |
| 👥 Headcount | Job-level workforce costs — pay bands, HC changes, cost sync to FP |
| 🏗 CapEx | Individual assets — depreciation, disposals, P&L and BS impact |
| 📋 Balance Sheet & CF | Working capital, funding logic, indirect cash flow — activity-based |
| 🎯 Top-Down Planning | Executive targets for revenue, margin, OpEx, FTE — vs. bottom-up |
Plus: Reporting & Analysis — consolidated IS, BS, CF reports, variance analysis, statistical analysis, and management reporting pack.
What's New in v2.0
| Feature | What It Means |
|---|---|
| Anaplan Application Framework | Upgradeable, centrally-deployed app — replaces static v1.x configurator |
| Anaplan Data Orchestrator (ADO) | Replaces the data hub model — lightweight pipelines with no memory overhead in the workspace |
| Job-Based Headcount | Plans at role level, not employee — protects PII, enables OWP integration |
| Progressive Disclosure UI | Shows only relevant inputs per planning method — reduces errors |
| Re-architected Models | Polaris engine: optimized for large data volumes compared to the Classic engine |
🚨 Customer Exclusion Criteria
IFP v2.0 is NOT suitable for: customers requiring BYOK on public cloud, customers who cannot use AWS (ADO requirement), public sector/federal organizations, or customers requiring more than 8 dimensions.