Why Structural Breaks Matter for Panel Unit-Root Tests
A unit-root test asks whether a series is persistent in a particular way: under the null, shocks do not die out, whereas under a stationary alternative, deviations from the series’ deterministic path tend to be corrected. That path need not remain unchanged over the sample. A policy change, a market redesign, or a measurement revision can shift a unit’s mean or alter its trend. If a test omits such a break, it may mistake a persistent deterministic change for evidence of a unit root.
In a panel, the break may affect every unit at roughly the same time, or each unit may have its own timing and size. Treating those cases as interchangeable can distort both the test statistic and its interpretation. The appropriate procedure depends on the break structure, the panel null and alternative, how dates are chosen, and whether units are cross-sectionally dependent.
A Break-Augmented Unit-Root Regression
Let \(y_{it}\) be the outcome for unit \(i=1,\ldots,N\) at time \(t=1,\ldots,T\). A useful regression representation for a break-aware augmented Dickey–Fuller test is
Here \(DU_{it}=1(t>T_{b,i})\) indicates observations after a proposed break date, and \(DT_{it}=(t-T_{b,i})1(t>T_{b,i})\) allows the deterministic trend to change after that date. The first can represent an intercept shift; the second can represent a change in slope. The lagged differences account for serial correlation in the test regression. A specification may include one, both, or neither break term, depending on the substantive model.
In this representation, the unit-root null is \(H_0:\rho_i=0\); the left-tailed alternative is \(H_a:\rho_i<0\). Panel procedures combine evidence across units, but they do not all use the same panel alternative. A pooled test may impose a common persistence parameter and test a restrictive alternative that all units are stationary. An IPS-style average test typically tests the joint null that all units have a unit root against an alternative under which at least some units are stationary. The test and its calibration determine the precise interpretation.
The displayed regression is a general way to organize the test, not a guarantee that one universal critical value applies. In particular, the deterministic terms and their restrictions under the null must match the chosen test. Break-date selection also affects the null distribution. Critical values or p-values must be calibrated for that full procedure, including any search over dates.
Worked Example: Coding an Intercept and Trend Break
Suppose a hypothetical quarterly series has a proposed break after quarter 5 of an eight-quarter sample. Its deterministic component is allowed to change in both level and slope. Compute the break indicators for quarters 5, 6, and 8.
Using \(DU_t=1(t>5)\) and \(DT_t=(t-5)1(t>5)\), quarter 5 is not yet post-break, so \(DU_5=0\) and \(DT_5=0\). At quarter 6, \(DU_6=1\) and \(DT_6=(6-5)\times1=1\). At quarter 8, \(DU_8=1\) and \(DT_8=(8-5)\times1=3\).
Thus, after quarter 5, the level dummy stays at one while the trend-change regressor increases with time since the break. These terms describe different changes: a permanent shift in level and a change in the rate of deterministic growth.
Suppose a hypothetical break-adjusted test reports \(\hat{\rho}=-0.18\) with \(SE=0.07\). The test statistic is \(t=-0.18/0.07=-2.571\). If the applicable one-sided, break-adjusted 5% critical value is \(-3.20\), then \(-2.571>-3.20\), so the unit-root null is not rejected. The statistic is negative, but not sufficiently negative under this calibrated reference distribution. A conventional no-break critical value should not be substituted.
Common Breaks and Unit-Specific Breaks
A common-break approach is appropriate when the substantive setting supports a shared date, such as the introduction of a nationwide regulation. The procedure can estimate or specify one break date for all units, then combine information across the panel. Depending on the test, break magnitudes and deterministic coefficients may still differ across units. Imposing a common date can improve precision when the date is genuinely shared, but it can misrepresent the data if units respond at different times.
A unit-specific approach allows \(T_{b,i}\) to differ across units. It is more flexible when local adoption, exposure, or adjustment timing varies. If each date is selected by searching over candidate dates, however, the test has used the data to choose a specification. Its reference distribution must account for that search; treating the selected date as if it had been fixed in advance generally overstates evidence against the unit-root null.
These approaches also differ in what a panel rejection can establish. A rejection of the joint null that all units have unit roots does not necessarily imply that every unit is stationary. Conversely, a test designed for a common persistence parameter may not be informative about a panel in which only a subset of units is stationary. The null and alternative should be stated before interpreting a panel statistic.
Worked Example: A Panel Test With a Common Break Date
Consider a hypothetical panel of five regions for which a common break after year 10 is justified by the institutional setting. A break-aware procedure estimates individual augmented Dickey–Fuller statistics of \(-3.0\), \(-2.6\), \(-2.2\), \(-1.7\), and \(-2.4\), then uses their average as its panel statistic.
The average is
Suppose a bootstrap calibrated for this common-break design gives a 5% left-tail critical value of \(-2.65\) and a p-value of \(0.16\). Since \(-2.38>-2.65\), the test does not reject the joint unit-root null at the 5% level. The result is not evidence that all five regions have unit roots; it means this test has not found sufficient evidence against its joint null. Nor would it be valid to compare \(-2.38\) with an ordinary \(t\) critical value: the panel aggregation, break terms, and estimation procedure determine the reference distribution.
Unit-Specific Tests and Combining Evidence
With unit-specific breaks, one strategy is to estimate a break-adjusted test for each unit, selecting or specifying that unit’s break date, and then combine the resulting evidence. For example, an IPS-type statistic averages individual test statistics, while a Fisher combination transforms individual p-values. These are not interchangeable procedures: each has its own null distribution and assumptions.
For a Fisher combination, if \(p_i\) is the valid p-value for unit \(i\), define \(F=-2\sum_{i=1}^{N}\log(p_i)\). Under independent unit-level tests with correctly calibrated p-values, the joint null distribution is chi-square with \(2N\) degrees of freedom. The p-values must already account for any break-date search. Cross-sectional dependence can invalidate the independence-based reference distribution, even when each individual p-value is well calibrated.
Worked Example: Combining Unit-Specific Break Tests
Suppose four hypothetical units have unit-specific break dates selected by a search procedure. After accounting for that search, their unit-root test p-values are \(0.01\), \(0.08\), \(0.42\), and \(0.55\). Assume, for this illustration, that the unit-level tests are independent.
The Fisher statistic is
Under the joint null, \(F\sim\chi^2_8\), because \(2N=8\). The upper-tail p-value is approximately \(0.028\), so this combination rejects the joint null of unit roots at the 5% level under the stated independence and calibration assumptions. The result indicates evidence against the claim that all four units have unit roots; it does not establish that all four are stationary. In a dependent panel, this chi-square reference calculation may be invalid, and a dependence-robust calibration is needed.
Why Omitting a Break Can Distort Inference
The basic issue can be seen with a level shift. Suppose a stationary series has a deterministic mean that changes once: \(y_t=\mu+\delta DU_t+u_t\), where \(u_t\) is stationary. Differencing gives \(\Delta y_t=\delta\Delta DU_t+\Delta u_t\). Since \(DU_t\) changes from zero to one only at the break, \(\Delta DU_t\) is a one-period pulse. If that pulse is omitted, the test regression leaves a large, systematic movement in its residuals. A test designed for an unchanged deterministic mean is then being applied to a misspecified model.
A trend break creates a related problem: the series’ deterministic growth rate changes, so a single straight trend does not describe the whole sample. A break-aware test is not a general solution to every form of instability. The chosen break type must be substantively plausible, and the procedure must account for how many dates were considered. Searching over many dates and reporting the most negative statistic as though the date had been fixed in advance can lead to excessive rejection of the unit-root null.
Choosing and Interpreting a Strategy
The break design should follow the economic or institutional question, not merely whichever specification produces a rejection. A common date is defensible when units plausibly experience the same event at the same time. Unit-specific dates are more credible when exposure and adjustment differ. In either case, state whether the date was known in advance or selected from the data, which deterministic terms were included, and what the panel alternative allows.
Panel dependence also matters. Shared shocks can induce correlated test statistics across units, undermining methods whose calibration assumes cross-sectional independence. Factor-augmented or other dependence-aware approaches may be needed alongside break treatment; adding break dummies alone does not remove common-factor dependence. The inference procedure must address both the deterministic breaks and the dependence structure that remains.
A useful sequence is to specify the null and alternative, choose a plausible break structure, decide how dates will be handled, and then use a critical value or p-value calibrated for that complete procedure. Report the result as evidence for or against the stated joint null, rather than translating a panel rejection into a claim that every unit is stationary.
Common Pitfalls
- Using no-break critical values after adding break terms. Break regressors and date selection can change the test’s reference distribution. Use calibration for the actual specification and search procedure.
- Assuming a common date without justification. A shared break can be efficient when credible, but can hide unit-specific timing and distort inference when imposed incorrectly.
- Treating a panel rejection as proof that all units are stationary. Some panel alternatives require only a subset of units to be stationary. Check the alternative attached to the test.
- Ignoring cross-sectional dependence. Dependence can invalidate simple averages or p-value combinations. Break adjustment and dependence adjustment solve different problems.
- Interpreting a selected date as known in advance. Searching over dates must be reflected in the p-value or critical value; otherwise, the reported evidence can be too strong.
Check Your Understanding
Answer each question by identifying the relevant model feature or inference assumption.
- What does \(DU_{it}\) represent, and how does \(DT_{it}\) differ from it?
- Why can a test that searches over break dates not generally use critical values for a date fixed in advance?
- A panel test rejects the null that every unit has a unit root. Does that necessarily imply that all units are stationary? Explain.
- When would a common-break approach be more defensible than unit-specific break dates?
- Why can cross-sectional dependence make an independence-based Fisher combination unreliable, even if the unit-level p-values are individually calibrated?