Blog · Territory, capacity and quota planning · Finance and FP&A teams
Pro forma analysis turns operating assumptions into projected financial results, then compares them with actuals. Build a business-unit income statement, reproduce the calculations in Excel, and reconcile the profit variance.
Pro forma analysis translates a business plan into projected financial results and compares those results with actuals. Start with explicit operating assumptions, calculate the statement, and explain the difference by business unit. Keep the approved case intact so the comparison measures what happened against what management expected.
For an internal operating review, a projected income statement is a useful starting point. It connects sales volume, selling prices, purchase costs, and operating expenses to profit. The annual operating plan establishes the broader commitments; this analysis tests their financial consequences.
A complete funding plan may also need projected balance sheets, cash flow statements, and capital expenditures. The SBA's business-plan guidance calls for those statements and explicit explanations of the projections. Here, the worked case stops at operating profit, before interest and income tax; use a separate cash flow forecast for collection timing, inventory funding, and capital spending.
This internal projection is also separate from SEC non-GAAP reporting. Public disclosure of non-GAAP measures by a registrant falls under rules including Regulation G, which addresses comparable GAAP measures and reconciliation. Labeling a workbook pro forma does not resolve those reporting requirements.
Consider an illustrative US distributor reviewing the quarter ended September 30, 2026. Its approved plan and actual results cover the same two business units. All sales and expenses below are in USD, costs are positive, and all units sold carry the listed average unit cost.
Keep a plan-version date, business-unit code, period, revenue account, cost account, and expense account in the source files. Reconcile actual revenue and expenses with the closed ledger before comparing them. Keep intercompany transactions and any central costs on the same basis in both cases.
The assumptions occupy columns A through E on a worksheet called Plan:
| Business unit | Units | Net price per unit (USD) | Cost per unit sold (USD) | Operating expenses (USD) |
|---|---|---|---|---|
| Retail | 12,000 | 50 | 30 | 120,000 |
| Industrial | 8,000 | 75 | 45 | 140,000 |
Actuals occupy the same columns on Actual:
| Business unit | Units | Net price per unit (USD) | Cost per unit sold (USD) | Operating expenses (USD) |
|---|---|---|---|---|
| Retail | 11,000 | 49 | 31 | 125,000 |
| Industrial | 8,500 | 74 | 46 | 142,000 |
These are supplied management assumptions and closed-period inputs, not estimates generated from the comparison. Record an owner for each assumption: sales owns volume and price, procurement owns purchase costs, and finance owns accounting consistency.
Revenue = Units sold × Net price per unit
Cost of goods sold = Units sold × Cost per unit sold
Operating profit = Revenue − Cost of goods sold − Operating expenses
In Excel, add these columns on both worksheets and fill down:
F2 = B2*C2
G2 = B2*D2
H2 = F2-G2
I2 = H2-E2
Columns F through I hold revenue, cost of goods sold, gross profit, and operating profit. When actual expense exports contain multiple rows per unit, aggregate them by unit, period, and account first. Microsoft documents SUMIFS for summing rows that meet multiple criteria; a ledger with unit, period, account, and amount in columns A through D can use:
=SUMIFS(Ledger!$D$2:$D$5000,Ledger!$A$2:$A$5000,A2,Ledger!$B$2:$B$5000,$K$1,Ledger!$C$2:$C$5000,$L$1)
Here, K1 contains the quarter key and L1 the required account code. Covirage is not affiliated with Microsoft.
The calculated statement is:
| Statement line | Plan (USD) | Actual (USD) | Actual minus plan (USD) |
|---|---|---|---|
| Retail revenue | 600,000 | 539,000 | -61,000 |
| Industrial revenue | 600,000 | 629,000 | 29,000 |
| Total revenue | 1,200,000 | 1,168,000 | -32,000 |
| Retail cost of goods sold | 360,000 | 341,000 | -19,000 |
| Industrial cost of goods sold | 360,000 | 391,000 | 31,000 |
| Total cost of goods sold | 720,000 | 732,000 | 12,000 |
| Gross profit | 480,000 | 436,000 | -44,000 |
| Operating expenses | 260,000 | 267,000 | 7,000 |
| Operating profit | 220,000 | 169,000 | -51,000 |
With plan in B, actual in C, and variance in D, use =C2-B2. A positive expense variance means higher spending; it is unfavorable even though a positive revenue variance is favorable. Dollar figures are exact here; round only displayed percentages in a larger workbook.
Retail operating profit is $73,000 against $120,000 planned, a $47,000 shortfall. Industrial contributes $96,000 against $100,000, a $4,000 shortfall. Their differences sum to the $51,000 company gap. For interpreting margins separately, use the gross profit margin method.
The company bridge must close:
=-32000-12000-7000
=169000-220000
Both return -51,000. Revenue fell $32,000, cost of goods sold rose $12,000, and operating expenses rose $7,000.
Then test the assumptions behind the revenue gap. Retail's volume effect is (11000-12000)*50, or -$50,000. Its price effect is 11000*(49-50), or -$11,000. Industrial's corresponding effects are $37,500 and -$8,500. Together, -$61,000 plus $29,000 reconciles to -$32,000.
Management can now investigate Retail volume and realized prices rather than applying the same spending restriction everywhere. A revised outlook belongs in a separate version; budget versus forecast explains that distinction.
Bring your approved assumptions workbook and matching actual-results export; Covirage maps the columns, and its tools compute and check the figures by business unit. The external AI model explains the differences with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring a sample of your own data.
See Covirage for finance teams for the broader reporting context.
A budget usually records the approved operating target. A pro forma statement shows the financial result of a stated set of assumptions, which might represent the budget, a proposed expansion, or a downside case. Label the purpose and approval status so readers know which case they are reviewing.
The decision determines the scope. An operating review may begin with an income statement, while a funding or expansion decision also needs projected balance sheets and cash flows. A profit projection alone cannot establish whether the company can fund inventory, equipment, or customer payment terms.
Use the same reporting calendar as the underlying business review, commonly monthly or quarterly. Keep the original approved version when actuals arrive. If assumptions change, save a separate revised case rather than overwriting the baseline and losing the ability to explain the original variance.
Either convention can work if formulas follow it consistently. This example stores costs as positive amounts and subtracts them from revenue. Check ledger exports before combining them with the plan, because accounting debits and credits may use a different sign convention from management reports.