Integrated business planning promises one plan the whole business can commit to, and the numbers behind that promise are real. McKinsey’s assessment of more than 170 companies over five years found that mature IBP practitioners earn one to two additional percentage points of EBIT compared with companies that lack a working process. The same research found something less flattering: for two thirds of the organisations studied, the IBP meeting is a periodic business review rather than part of a continuous cycle of decisions. That is the gap this post is about. Most companies build the demand plan, build the supply plan, hold the executive meeting, and quietly skip the step in between that converts units into money. Without it, the operating plan and the financial forecast stay two different documents, and leadership keeps trusting the second one.
What Is Integrated Business Planning?
Integrated business planning (IBP) is a monthly, cross-functional management process that aligns the portfolio, demand, supply and financial plans into one set of numbers over a rolling 24-month horizon, so every operational decision is evaluated against its profit and loss impact rather than volume alone. It is the process layer above execution: the ERP records what happened, MRP calculates what to buy and make, and IBP decides what the business commits to and what it does about the gap between that commitment and the plan the board approved.
The distinction that matters operationally is the unit of measure. Sales and operations planning balances demand and supply in units, cases, tonnes or SKUs. Integrated business planning carries the same plan a step further and states it in currency, with margin, so a supply constraint stops being a service problem and becomes a revenue and EBIT number an executive team can act on. Everything else people list as a difference, wider function coverage, longer horizon, more senior attendance, follows from that one change.
Integrated Business Planning vs S&OP: What Actually Changes
| S&OP | Integrated Business Planning | |
| Unit of measure | Volume: units, cases, tonnes | Volume and value: revenue, margin, EBIT impact |
| Horizon | Typically 3 to 18 months, tactical | Rolling 24 months, crosses the budget boundary |
| Functions at the table | Sales, demand planning, supply, operations | Adds finance, product and portfolio, and the business head |
| Primary question | Can we supply what we expect to sell? | Does the plan deliver the business result we committed to? |
| Output | An agreed constrained supply plan | A valued plan plus a quantified gap and the actions that close it |
| Failure mode | The plan is agreed and then ignored in execution | The plan is agreed and never reconciled to the financial forecast |
Gartner treats this as a maturity progression rather than two separate processes, and its five-stage S&OP maturity model puts the financial dimension, budgeting and reforecasting decisions taken inside the planning cycle, in the upper stages. Most organisations describe themselves as running integrated business planning long before they are actually taking those decisions in the cycle.
The Five Reviews in an Integrated Business Planning Cycle
The integrated business planning cycle runs as five sequential reviews. The first three produce the plan, the fourth values it and prepares the decisions, and the fifth takes them.
- Product and portfolio review. Confirms what is launching, transitioning and being discontinued, with dates and volumes. This is where next year’s revenue assumptions actually originate.
- Demand review. Produces an unconstrained consensus forecast from the statistical baseline plus market intelligence, and separates what is forecast from what is a sales target. Getting this right is mostly a question of forecast error and override discipline, not of meeting attendance.
- Supply review. Tests that demand against capacity, materials and inventory to produce a constrained supply plan, and states clearly where supply cannot meet demand and by how much.
- Integrated reconciliation. Converts the plans from units to currency, from rates of output to profit and loss impact, and filters the unresolved issues into modelled options with risks and opportunities attached.
- Management business review. The executive team takes the decisions that reconciliation could not resolve, commits to the plan, and owns the remaining gap.
Oliver Wight, which formalised this cycle, describes the fourth step precisely: the integrated reconciliation review converts the plans from units to dollars, from rates of output to profit and loss impact, from functional plans to financial language. Read the list again and note which of the five is the one nobody has a standing meeting for.
Why the Plan and the Financial Forecast Never Tie Out
Integrated business planning breaks in the same place in most companies, and it is not the demand review. It is the conversion from units to money. Four failure modes account for almost all of it, and each one is visible in a single cycle if you look for it.
1. The reconciliation step is merged into the executive meeting
When reconciliation has no separate meeting, no owner and no output document, it collapses into the management business review, where there is no time to model anything. The executive team is then handed volumes and asked for financial decisions, so it defaults to the number it already trusts, which is the finance forecast. This is the mechanism behind McKinsey’s finding that two thirds of integrated business planning meetings are periodic business reviews rather than a decision cycle: the decisions have nowhere to be prepared.
2. Volume is valued at standard price, so mix does the damage
Multiplying the unit plan by a standard or list price produces a revenue number that is arithmetically correct and commercially wrong. Discount structures, channel mix, customer mix and freight recovery move realised price far enough that a plan can hit its volume target and miss revenue, or hit revenue and miss margin. Once that happens twice, finance stops using the operational plan as an input and rebuilds its own, and the organisation is back to two sets of numbers.
3. Nobody labels which number is a forecast and which is a commitment
The demand plan is an unbiased estimate of what will sell. The sales budget is a commitment used to set targets and pay people. They are different objects with different biases, and when a single spreadsheet column carries both, the reconciliation is meaningless before it starts. Supply then builds to a number inflated by target-setting, inventory rises, and the following cycle everyone argues about the forecast instead of the gap.
4. The gap to plan is reported rather than owned
Most integrated business planning packs show the gap between the projected result and the business plan. Far fewer show a list of gap-closing actions with an owner, a date and a value in currency, tracked from the previous cycle. A gap that is reported every month and never assigned is a status update. The process only starts generating value when the sum of the actions is compared against the size of the gap, and the shortfall is escalated as a decision rather than restated as a risk.
| Failure mode | What it looks like in the cycle | The question to ask this month |
| Reconciliation merged into the exec meeting | No separate reconciliation output; the exec pack is the first valued view | Who owns integrated reconciliation, and where is last month’s output? |
| Standard price used to value volume | Plan hits volume, misses revenue or margin, and nobody can explain which SKUs did it | Are we valuing at realised price and margin, or at list? |
| Forecast and commitment in one number | Sales defends the number instead of explaining the change | Which column is the unbiased forecast and which is the target? |
| Gap reported, not owned | The same gap appears in three consecutive packs | What is the currency value of the actions against this gap, and who owns each? |
Across transformation projects, the pattern our team sees most often is that the four failures compound in one direction. A plan that cannot be valued cannot be argued about in the terms an executive team uses, so it is not used to make decisions, so the discipline around producing it decays. The fix is mechanical, not cultural.
How Do You Convert a Unit Plan Into a Money Plan?
Integrated business planning becomes a decision process the month the conversion is done properly. Six steps, in this order:
- Freeze the unit plan at the level the money is made. Usually product family by channel, sometimes SKU by customer. Value a plan at an aggregation coarser than the level where price varies and the mix error is built in from the first line.
- Apply realised price, not list price. Net of discounts, rebates, promotional spend and freight recovery, taken from actuals rather than from the price master.
- Apply margin at the same granularity. Standard cost is acceptable as a starting point only if the variances are reported alongside it and the material-heavy families are checked against current input costs.
- Compare against the business plan and state the gap in currency. Both directions: the volume gap and the value gap, because a plan can be short on units and ahead on margin.
- Convert each gap into an action with an owner, a date and a value. Price action, mix shift, a launch pulled forward, capacity released, a customer prioritised. The sum of the actions is the honest coverage of the gap.
- Carry risks and opportunities separately from the committed number. Never blend a weighted opportunity into the plan; present it beside the plan so the executive team decides whether to bank it.
The output of those six steps is a single page: committed plan, business plan, gap, actions with values, and the residual that needs a decision. That page is the reason integrated business planning exists.
What “One Set of Numbers” Actually Requires
In integrated business planning, one set of numbers is a data condition before it is a governance one. Four prerequisites decide whether the reconciliation step can even be attempted, and all four are usually weaker than people assume.
| Prerequisite | Why it blocks reconciliation | Ready when |
| A product hierarchy that maps to the finance hierarchy | Planning families and reporting families differ, so the two plans cannot be compared line for line | Every planning family rolls up to exactly one reporting line, with a documented mapping |
| Clean item, customer and price master data | Realised price and margin cannot be computed on records nobody owns | The master data cleanup covering item, customer and price is complete and has an owner |
| A genuinely constrained supply plan | Valuing an unconstrained plan produces a revenue number the factory cannot deliver | The supply review states capacity and material limits, and the plan respects them |
| Inventory positioned by policy, not by habit | Working capital moves cannot be planned if buffers are set node by node | Targets are set across the network, for example through multi-echelon inventory optimization |
The honest sequencing test is this. If item, customer and price master data are not trustworthy today, the first three months of an integrated business planning programme are a data project, and calling it anything else guarantees the fourth review never runs. The same holds for the demand side: reconciliation inherits whatever bias the demand review lets through, which is why running the demand planning process on exception management matters more than the sophistication of the model behind it.
What Good Looks Like in Numbers
The case for running integrated business planning properly is not abstract. In McKinsey’s dataset of mature practitioners, service levels run five to 20 percentage points higher, freight costs and capital intensity are 10 to 15 percent lower, customer delivery penalties and missed sales are 40 to 50 percent lower, and planners are 10 to 20 percent more productive because the process removes rework rather than adding meetings. Those are the second-order effects of a plan that is valued, committed to and executed against, and they are the reason the EBIT difference shows up at all.
Where Oritiq Fits
Oritiq’s planning layer overlays the existing ERP and carries the integrated business planning cycle end to end: a consensus demand plan, a constrained supply plan tested against capacity and materials, and an S&OP reconciliation and decision intelligence layer that documents what was committed, what was constrained and which assumptions the number rests on, so reconciliation happens in a system rather than in a meeting. Native master data handling supports the item, customer and price records the valuation step depends on, rather than assuming they arrive clean. The ERP stays in place as the system of record; Oritiq adds the decision layer on top of it.
Closing
Integrated business planning is not a bigger S&OP meeting with more people in the room. It is the same plan carried one step further, into currency, so the executive team can act on it. The step that does that work is integrated reconciliation, and it is the step most companies never staff. If the last three monthly packs showed the same gap with no priced actions against it, the process is reporting, not planning.
Pick one product family this month, value the plan at realised price and margin, and compare it line for line against the finance forecast. The size of the difference tells you how much of an IBP process you actually have.
Walk through your own reconciliation cycle with Oritiq, on your own plan and your own numbers.
FAQs
What is integrated business planning in simple terms?
Integrated business planning is a monthly process that brings the portfolio, demand, supply and financial plans into one set of numbers over a rolling 24-month horizon. It states the operating plan in currency and margin, not just units, so leadership can see the profit impact of a supply or demand decision before committing to it.
What is the difference between IBP and S&OP?
S&OP balances demand and supply in volume across a tactical horizon. IBP takes the same agreed plan, values it in revenue and margin, extends the horizon to around 24 months so it crosses the budget boundary, and brings finance and portfolio into the cycle. The defining difference is the unit of measure, and everything else follows from it.
What are the five steps of the IBP process?
Product and portfolio review, demand review, supply review, integrated reconciliation, and the management business review. The first three build the plan, integrated reconciliation converts it into financial language and prepares modelled options, and the management business review is where the executive team takes the decisions and commits.
Why do integrated business planning implementations fail?
Most integrated business planning implementations fail at the reconciliation step rather than the demand step. Without a separate reconciliation owner and output, volumes reach the executive meeting unvalued, finance keeps its own forecast, and the cycle becomes a business review. Weak item, customer and price master data makes proper valuation impossible even when the intent is there.
Do we need to replace our ERP to run IBP?
No. Integrated business planning is a planning and decision layer that sits above the ERP, reading orders, inventory, costs and master data and writing the agreed plan back. The ERP remains the transaction system of record. Replacing it is a far larger programme than the one required to get a reconciliation cycle running.
Who should own the integrated business planning process?
The business head owns the outcome and chairs the management business review. A dedicated process owner runs the cycle and the reconciliation step, and is deliberately neutral between sales, supply chain and finance. Assigning reconciliation to whichever function has spare capacity is the most common structural mistake.
How long does it take to see results from IBP?
The first valued plan is usually achievable within two to three cycles once master data and hierarchy mapping are in place. Measurable financial effect from integrated business planning follows the point at which gap-closing actions are tracked with owners and values, typically two to three quarters in, because that is when the process starts changing decisions rather than describing them.