The Short Answer
For 20 years, supply chain planning software and financial planning software were bought by different people, for different reasons, on different budgets. That separation is ending. The reason is simple: supply assumptions became the largest source of financial forecast error. Tariff changes move gross margin. Volume and mix surprises break the revenue plan. Inventory decisions made in an operations tool show up weeks later as a cash forecast miss that the CFO has to explain.
The software market has noticed. Pigment, Anaplan and Board all now sell supply chain planning modules on the same platforms that run FP&A, positioned squarely at the office of the CFO. Dedicated supply chain vendors like Kinaxis, Blue Yonder, o9 and Logility still go far deeper on supply-side algorithms, but they live outside the finance stack. The result is a buying decision that lands, more often each year, on the CFO's desk.
Our view in one paragraph: finance should own the connected planning layer where volumes become dollars, including demand planning at a financial grain, S&OP sign-off, SKU-level profitability and scenario modeling that flows to COGS and cash. Finance should not try to own the deep supply algorithms: multi-echelon inventory optimization, constraint-based supply planning or production scheduling. The rest of this report explains how to draw that line, and who should lead the purchase in each situation.
What Changed: Supply Assumptions Became the Forecast
Ask an FP&A team why the last three forecasts missed, and the honest answer usually involves inputs rather than the revenue model's arithmetic: a volume number from operations that was already stale, a standard cost that no longer matched landed cost, a stockout that took committed revenue off the table. Three forces made those inputs the center of the forecast problem.
The tariff rounds of 2025 and 2026 made landed cost a moving target. A duty change on one input can shift gross margin by whole points within a quarter. Finance teams that modeled revenue scenarios in detail had no way to model a tariff scenario through COGS, inventory valuation and cash. Evenflo, the juvenile products maker, is a public example: it uses Pigment to model tariff scenarios against its supply base. When a policy headline can move your margin, supply assumptions become a board question, and the board asks the CFO.
Post-2020 demand patterns never settled back into clean seasonality. Order books swing, channel inventory distorts sell-through, and a promotion in one region can drain stock allocated to another. Most forecast misses now trace back to a supply-side assumption: a volume number, a mix shift, a cost per unit or a lead time. The revenue model was fine. The inputs feeding it were stale by the time the forecast was published.
Years of higher interest rates repriced inventory. Every excess week of stock is funded at a real cost of capital, and every stockout is revenue the sales team already promised. Inventory is usually the largest balance sheet item the CFO can influence quarter to quarter. Yet in most mid-market companies the inventory plan lives in a supply chain tool, or a planner's spreadsheet, that finance sees only after the cash forecast has missed.
None of these forces is temporary. The structural conclusion is what matters: the financial forecast is now only as good as the supply plan feeding it. A CFO who can't interrogate that plan, in a tool finance can actually use, is signing off numbers nobody in finance has tested.
That's the shift. Supply chain planning stayed an operations discipline, but its outputs became finance's biggest uncontrolled input.
The Old Split: Two Stacks, Two Languages
The separation between supply chain tools and finance tools isn't an accident. The two disciplines grew up solving different problems. Supply chain planning came out of operations research and MRP: units, lead times, capacity, service levels. Financial planning came out of accounting and the Hyperion lineage of EPM: dollars, entities, periods, variance. Each side built software in its own image, and each side's software is genuinely good at its own problem.
| Dimension | Supply chain stack | Finance stack |
|---|---|---|
| Owner | VP supply chain / COO | CFO / VP FP&A |
| Core question | Can we supply what demand needs? | What will the business earn and consume? |
| Unit of account | Units, cases, pallets, days of cover | Dollars, margin points, cash |
| Planning grain | SKU by location by week | Product family by entity by month |
| Typical tools | Kinaxis, Blue Yonder, o9, Logility, SAP IBP, Netstock | Pigment, Anaplan, Board, OneStream, Prophix, Excel |
| Cadence | Weekly S&OP / S&OE cycles | Monthly close, quarterly reforecast |
The split works fine as long as the two stacks only need to exchange numbers occasionally, at a high level of aggregation. It stops working when the business needs the translation between them to be fast, granular and trustworthy. That translation has a name inside most finance teams, even if nobody writes it in the budget. We call it the reconciliation tax.
The Reconciliation Tax
The reconciliation tax is everything your team pays, in hours, errors and decision delay, to keep two planning worlds loosely stitched together. It's rarely itemized, because it hides inside normal FP&A work: the monthly volume bridge, the standard cost true-up, the S&OP pre-read that takes an analyst three days to build. Here is what it's made of.
Supply chain plans against a statistical demand forecast in units. Finance plans against a revenue forecast built from targets and pipeline. They disagree by design, and nobody owns the bridge between them.
Someone, usually an FP&A analyst, converts the volume plan to dollars in a spreadsheet each cycle. Standard costs drift, mix assumptions get simplified, and the conversion itself becomes a source of error nobody audits.
Supply plans move weekly. Financial forecasts move monthly at best. By the time the reforecast is published, the volume assumptions inside it are two to six weeks old.
When the CEO asks what a 10% tariff does to full-year margin, the answer requires an export from the supply tool, a cost model rebuild and days of analyst time. The question expires before the answer arrives.
Finance signs off the S&OP plan without being able to trace how the unit plan became the dollar plan. When the quarter misses, the post-mortem happens in two systems with two versions of history.
In stable conditions, the tax is annoying but affordable. In volatile conditions, it compounds. Every tariff headline and every demand shock requires a fresh translation cycle, and the organization that takes two weeks per cycle answers fewer questions than the one that takes two hours. That difference is what connected planning platforms are actually selling.
A useful exercise: before any vendor conversation, estimate your own reconciliation tax. Count the analyst hours per month spent converting units to dollars, bridging the two forecasts and rebuilding cost models for scenarios. Most mid-market teams we work with land between one and three full-time equivalents. That number is your business case baseline, and it's more honest than any vendor ROI deck.
Why Every EPM Vendor Now Ships an SCP Module
The convergence isn't just a buyer-side story. EPM vendors have reasons of their own, and it helps to understand them before the demos. The technical reason: a modern planning platform is a multidimensional calculation engine with workflow on top. Demand planning, inventory projection and S&OP are, at the grain finance needs, modeling problems that engine handles naturally. Adding an SCP module to an existing EPM platform costs the vendor far less than building a platform from scratch.
The commercial reason: EPM vendors already sell to the CFO. A vendor that lands in FP&A and expands into demand planning and S&OP doubles the account without a new buying center. Positioning SCP as connected planning for the office of the CFO is now standard pitch material across the category. That framing is convenient for vendors. It's also partly true, which is what makes these evaluations tricky. Here's where the three most visible movers stand.
Pigment shipped supply chain planning as a first-class use case on the same platform that runs FP&A: demand and inventory planning, S&OP workflow, scenario modeling with direct P&L impact and SKU-level profitability. The customer list in supply-facing use cases is real, not aspirational: Unilever, Danone, BJ's Wholesale Club, Vita Coco, Ken's Food, Vital Farms, Goodbaby and IDKIDS all use it in supply chain contexts. Ankorstore's leadership reports forecast accuracy improved 20 to 25% after moving demand planning onto the platform. Evenflo uses it for tariff scenario modeling. Implementations typically run two to four months.
The honest caveat: Pigment's supply-side depth is modeling depth, not algorithmic depth. It doesn't do multi-echelon inventory optimization or constraint-based supply planning, and its supply chain modules are years younger than the dedicated tools. If a vendor demo skips replenishment logic and capacity constraints, that's why. Ask directly.
Anaplan has sold connected planning across finance, sales and supply chain for over a decade, with mature demand planning, supply planning and S&OP solutions built on its Hyperblock engine, plus Polaris for very large sparse models. At enterprise scale it remains the most proven single-platform answer to the finance-plus-supply question. Large consumer and industrial companies run genuine S&OP processes on it.
The honest caveat: The cost of that maturity is weight. Anaplan supply chain deployments are SI-led, timelines run long and the models need dedicated builders to maintain. Mid-market teams routinely underestimate the ongoing staffing an Anaplan supply model requires.
Board positions one platform for financial and operational planning, with S&OP and retail and supply use cases as named solutions. It's strongest in DACH and wider Europe, where its retail and manufacturing customer base gives the supply story more substance than a datasheet claim. For European mid-market manufacturers already evaluating Board for FP&A, extending into S&OP is a credible second step.
The honest caveat: Board's supply capabilities are broad rather than deep, and outside Europe the reference base thins out. Ask for a live customer reference running S&OP on Board in your industry and region before weighting it.
Two more names belong in the picture. SAP IBP is the supply-side incumbent for SAP ERP shops: deep, proven and heavy, but it's an operations tool that finance consumes rather than a finance tool that reaches into operations. And the dedicated SCP players (o9, Kinaxis with RapidResponse and Maestro, Blue Yonder, Logility, plus mid-market specialists like Netstock and GMDH Streamline) haven't stood still. They're adding financial views and CFO-friendly dashboards to their own products. The convergence is happening from both directions, which means the real question is where the boundary between the two categories should sit in your company.
What a Connected Model Actually Buys You
Strip away the platform language and a connected planning model buys finance four specific capabilities. Each one is testable in a demo, and you should test all four, because vendors differ widely in how real each capability is once your own data grain and cost structure are loaded.
Profitability computed at the SKU or SKU-customer level, from one model that holds both the volume plan and the cost structure. You see which products earn their inventory and which ones quietly consume margin, freight and working capital.
Verify in a demo: In a demo, ask the vendor to show contribution margin for a real SKU with a mid-quarter cost change applied. Watch whether the change flows to gross margin without a rebuild.
A tariff, a freight rate change or a supplier switch entered once, with the impact visible in gross margin, inventory valuation and the cash forecast in the same session. This is the capability that turns a two-week analyst project into a meeting exercise.
Verify in a demo: Bring your own scenario to the demo: a specific duty rate on a specific input. Time how long it takes to see the full-year margin and cash impact.
The unit plan and the dollar plan are the same model at different aggregations. When finance signs the S&OP output, it can trace every dollar back to a volume, a price and a cost assumption. The monthly argument about whose forecast is right disappears, because there's one forecast with named owners per driver.
Verify in a demo: Ask to see the same plan displayed in units for the planner view and in dollars for the finance view, then change one assumption and confirm both views move together.
Inventory, payables and receivables projected from the operational plan rather than estimated from ratios. Days of cover decisions show up in the cash forecast before the quarter ends, not after.
Verify in a demo: Ask the vendor to change a safety stock target and show the resulting movement in the cash flow forecast.
There's evidence these capabilities pay for themselves when they're real. Ankorstore's leadership reports forecast accuracy improving 20 to 25% after connecting demand planning to its financial model on Pigment. Treat single-company numbers with caution, but the direction matches what we see in evaluations: the gains come less from better algorithms than from removing the translation layer where forecasts used to decay.
The compounding effect: each capability strengthens the others. SKU-level P&L makes scenarios sharper. Shared numbers make S&OP sign-off faster. Faster sign-off means the working capital plan reflects this month's decisions, not last quarter's. Teams that connect one use case well usually connect a second within a year, which is exactly what vendor land-and-expand models count on. That's fine. Just negotiate as if you know it.
What Finance Should Not Try to Own
Here's where this report parts company with the vendor pitch. Connected planning is real, but it has a boundary, and CFOs who ignore it buy themselves an expensive lesson in operations research. Four domains belong to dedicated supply chain tools and the people who run them, no matter how good your EPM platform is.
Setting stock targets across a network of plants, warehouses and channels is a mathematical optimization problem, not a modeling problem. Dedicated engines from Kinaxis, Blue Yonder, o9 and Logility solve it with algorithms EPM platforms don't have and shouldn't rebuild. Netstock and GMDH Streamline cover the mid-market version of this need.
Deciding what to make where, when capacity, materials and labor are all limited, requires a solver that respects hard constraints. EPM scenario engines will happily produce an infeasible plan and present it beautifully. Feasibility is the dedicated tools' whole job.
Sequencing lines, shifts and changeovers inside the week belongs to APS and MES territory. Finance has no business here beyond receiving the cost consequences.
Short-horizon forecast correction from POS, weather and channel signals is a data science discipline with its own tooling. Finance needs the output, aggregated, not the machinery.
The distinction underneath all four is the same one: modeling versus optimization. An EPM platform calculates the consequences of assumptions you give it. A supply chain engine searches for the best feasible answer under constraints. Those are different mathematics, different data requirements and different skill sets. A finance team that tries to rebuild MEIO in a planning platform will get a model that looks right in the demo and quietly recommends infeasible or costly stock positions in production.
The political version of this mistake: finance buys the connected platform, then forces supply chain to abandon its tools and plan inside the finance system at a grain that doesn't work for them. The planners disengage, keep a shadow spreadsheet system, and the connected model fills with numbers nobody defends. The fix is governance: supply chain owns its algorithms and assumptions, finance owns the financial translation, and the interface between them is explicit and versioned.
A workable ownership rule: finance owns the layer where units become dollars. Everything upstream of that layer belongs to operations, whatever tool it runs in.
Who Leads the Purchase: A Decision Framework
The right buying structure follows from where the pain sits and how complex the physical network is. Match your company to the closest profile below. If two profiles fit, you have a joint purchase, and you should staff it that way from the first vendor call.
Tool shape: EPM platform with an SCP module (Pigment, Anaplan, Board). Supply chain co-designs the demand and inventory model and owns its assumptions inside it.
Tool shape: Dedicated SCP engine (Kinaxis, o9, Blue Yonder, Logility) for supply decisions, EPM platform for the financial translation, with a contracted data interface between them. Finance owns the interface spec.
Tool shape: SAP IBP is the default supply-side answer and it's deep, but heavy. Finance should still insist on a planning layer it can model in, and should not accept IBP as the FP&A tool.
Tool shape: Dedicated SCP tool selected by operations. Finance participates to define the financial data feed it needs, then gets out of the way.
Six questions that expose the real answer in a demo
Whoever leads, these questions separate a connected planning capability from a connected planning slide. Ask them with your own data in the room where possible.
One process note. When finance leads, involve the supply chain team before the shortlist exists, not after. The fastest way to kill a connected planning project is to present operations with a tool finance already chose. When supply chain leads, the mirror rule applies: finance defines the financial data contract it needs before the RFP goes out. Our FP&A and EPM buyer's guide covers how to structure the evaluation itself, and our implementation timeline benchmarks give you the schedule reality check before a vendor gives you theirs.
Frequently Asked Questions
Continue Your Evaluation
Weighing Connected Planning Platforms?
Build your shortlist in the CFO Shortlist app: compare Pigment, Anaplan, Board and 35+ other platforms against your size, systems and use cases.