z-logo
Premium
Causes and Consequences of the Relation Between Split‐Adjusted Share Prices and Subsequent Stock Returns
Author(s) -
Brown William D.,
Pfeiffer Ray J.
Publication year - 2006
Publication title -
journal of business finance and accounting
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.282
H-Index - 77
eISSN - 1468-5957
pISSN - 0306-686X
DOI - 10.1111/j.1468-5957.2006.00645.x
Subject(s) - economics , stock (firearms) , inefficiency , portfolio , financial economics , econometrics , hedge , microeconomics , mechanical engineering , ecology , engineering , biology
  In this manuscript, we document and explain an empirical artifact — a persistent and substantial negative relation between split‐adjusted share prices and subsequent stock returns — that has potentially important ramifications for capital markets research design. This relation pervades all commonly‐used commercial databases and is insensitive to the choice of database used for either prices or returns. We investigate four potential causes of the empirical regularity: survivorship bias, asymmetric returns to low‐priced stocks, extreme returns, and the effects of stock‐split adjustments on portfolio classifications. We find that survivorship bias accounts for approximately half of the returns documented to a share‐price‐based hedge strategy and that re‐classifications caused by stock split adjustments account for substantially all of the remaining returns. We do not find that controlling for either low‐priced stocks or extreme returns is effective in purging the data of the empirical price artifact. These findings and our explanations thereof are important, as they show that there are potentially troublesome consequences of using share price as a deflator in markets‐based research. In particular, we note and illustrate cause for concern when interpreting associations between share‐price‐scaled variables and subsequent returns as evidence of market inefficiency.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here