Stub Period Adjustment in the QoE Report
Stub period adjustments bring partial-year financials onto a full-year basis. Learn what they are, why they arise, and how FDD teams handle them.
A stub period arises when a business's financial history includes a partial year — for example, because it was acquired mid-year, changed its accounting period, or was carved out of a parent group partway through a financial year. Stub period adjustments are a standard part of QoE analysis, but they require care to execute properly.
What Is a Stub Period?
In the context of a QoE report or EBITDA bridge, a stub period is any accounting period that covers less than twelve months. Common causes:
- Change of accounting reference date: The company shortened or extended an accounting period to align with a new owner's year-end.
- Incorporation or acquisition mid-year: The business was set up or acquired partway through a period, so the first or last statutory year is partial.
- Carve-out transactions: A subsidiary being carved out of a larger group may have been reporting into consolidated accounts rather than standalone, creating non-standard period coverage.
Why Stub Periods Create Analytical Problems
When a QoE analysis presents three years of historical EBITDA, it is typically comparing like-for-like twelve-month periods. A stub period disrupts this comparability. A six-month period that shows strong EBITDA cannot be directly compared with two preceding twelve-month periods — it could look better or worse simply because of its length.
More specifically, stub periods create issues where:
- Revenue and costs are seasonally skewed (a stub period covering the busy half of the year will overstate run-rate profitability)
- One-off items fall disproportionately within the stub (restructuring charges, one-time revenue items)
- Working capital analysis is distorted by the different period length
How to Adjust for a Stub Period
The standard approach is to annualise the stub period financials to create a comparable twelve-month view. The mechanics depend on the nature of the business:
Simple Annualisation
Divide the stub period EBITDA by the number of months and multiply by twelve. This is appropriate for businesses with relatively stable, non-seasonal revenue patterns.
Example: a six-month stub with EBITDA of €2.4m → annualised EBITDA of €4.8m.
Seasonality-Adjusted Annualisation
For seasonal businesses, simple annualisation can be misleading. The FDD team will compare the stub period months with the same months in the prior year to build a seasonally adjusted estimate.
Example: a stub period covering January to June for a business where H1 represents 40% of annual revenue. Annualising by multiplying by two would overstate. Instead, the team uses the actual H1/H2 split from the prior year to scale the stub period appropriately.
Pro-Forma Twelve-Month Period
Where the data allows it, the FDD team may reconstruct a full twelve-month period by combining the stub with the preceding partial year from management accounts.
Disclosure in the Report
In the QoE report, stub period adjustments are typically presented with:
- A clear explanation of why the stub arises
- The methodology used for annualisation
- Sensitivity analysis showing the impact of different seasonal assumptions if relevant
- A note on any items within the stub that are not representative of a full-year run rate
Where the stub is the most recent period, it often has heightened importance — buyers use it as a signal of current trading. Extra care in the disclosure is warranted.
Common Pitfalls
- Ignoring seasonality when it matters. A retail business with a December-heavy trading pattern needs a careful approach if the stub covers October to March.
- Double-counting one-off items. An item that falls in the stub may already have been excluded as a non-recurring item — adjust only once.
- Overstating annualised EBITDA. Management teams sometimes present annualised stub figures that flatters performance. Challenge the assumptions.
Understanding period construction and adjustment mechanics is essential for QoE analysis. Our programme works through these concepts across 8+ case studies with over 150 EBITDA adjustment examples. One payment of €119.99.