Start next year's plan from this year's actuals, even before this year has finished: months that haven't closed yet start from the year before.
You need to be an Owner or Admin of the workspace to create plans.
Before you start
- Import the actuals you want the plan to start from (see Import your sales lines). A plan built after October close typically starts from this year's January to October and last year's November and December, so import both years.
Steps
Open Plans in the left menu.
Under New plan, enter a Name, for example FY2027 plan.
Set Fiscal year to the year you are planning.
Set Start from actuals of to the year the plan copies, usually the current one.
Read Actuals on file under the form. It shows each year's months, for example FY2026 Jan 2026 – Oct 2026 (10 months).
Leave Use the previous year's data for an incomplete year ticked if the year you start from isn't complete. Each month that year has no actuals for (November and December in the example) takes the year before's same month. Untick it to leave those months at zero.
Choose Start prices and costs from (see Which prices to start from below):
- FY2026 sales: average net price and cost per unit. The option names the year in Start from actuals of, and is chosen unless you change it.
- The items file: its current Price and Cost columns.
If the chosen source has nothing for an item, the other one is used. Prices and costs start flat for the year.
Click Create plan.
You should see the plan's grid. Each item's months hold the quantities sold in the matching month of the source year (or of the year before, for the missing months), with prices and costs from the source you chose.
Open History in the panel on the right.
You should see step 1 saying where the plan started and where its prices came from, for example Started from FY2026 actuals; prices and costs from those sales (average net price and cost) (808 prices from the items file instead; 4 items with no price).
Which prices to start from
A plan is quantity × price and cost, month by month. This choice decides only where each item's starting price and cost per unit come from; the quantities are the same either way. Whichever you choose, the price and cost start the same in every month, and you change them afterwards with Change price by % or Change price per unit, for example +3% from April.
Sales of the year you start from
- Each item gets what customers actually paid in that year: total sales amount ÷ total quantity, and total cost ÷ total quantity. A FY2025 plan started from FY2024 actuals gets FY2024's prices.
- Deals and discounts are already in it, so the plan compares like for like with your actuals: a price variance is a real change in price, not the gap between list and net.
- It is that year's price level. Apply price increases since then with a price change after creating the plan.
- It needs sales imported with their amount (and cost) columns. An item that didn't sell that year, or whose sales net to zero or less (all returns, say), takes the items file's price instead.
The items file
- Each item gets the Price and Cost columns you mapped when you last imported items: today's values, whatever year the plan is for.
- If those columns hold frontline or list prices, plan revenue comes out above what customers pay after deals, and every comparison with actuals shows a price shortfall that is only that gap.
- Use it when the items file holds the net or landed prices you plan with, or for a plan that is meant to be at list price.
Which to choose: for most distributors, sales. For a plan of a past year (a FY2025 plan to compare with FY2025 actuals), always sales: today's items file would put this year's prices into last year's plan.
Common mistakes
Revenue and margin are all zero. Neither source had prices: the item file has no Price column mapped, and the sales have no amount. Import items with a Price and Cost column, or sales with their amount and cost, and create the plan again.
Plan revenue far above actual. The plan started from the items file's list prices, and customers paid less after deals. That's fine if it's what you meant; otherwise create the plan from sales prices, or map net or landed prices as the items file's Price.
A past year's plan has this year's prices. It started from the items file, which holds today's prices. Create it from sales prices instead.
November and December come out at zero. The box was unticked, or the year before has no actuals for those months. Import the year before and create the plan again.
An item shows zero in a month although it sold the year before. A month the source year has loaded is never filled from the year before, even for an item that didn't sell in it: the plan starts from what actually happened that month.
Months filled from an old year. The year before fills only months the source year hasn't reached. If Actuals on file shows a gap in the middle of the source year, that month wasn't imported: import it, then create the plan.
Returns larger than sales. A month whose actual is negative starts at zero, because a plan can't hold a negative quantity.